Banner, custom message, and template best practices
Banners
You can add custom banners to Material Detections. Banner content for User Reported messages are added by default.
Custom Messages
Custom messages appear on a page your user is redirected to after a detected message is speedbumped or blocked. They are appended to the default messaging.
Consider these best practices when you write your messages:
Be clear, concise, and succinct: Being with a straightforward statement about the situation. Clearly indicate that an email was identified as a potential phishing attempt and that you have taken steps to protect everyone. Avoid jargon to ensure everyone understands.
Provide guidance: Offer next steps for anything you want your users to do as a result of this remediation. For example, you could remind them to avoid clicking on suspicious links, report any suspicious emails, and ensure their security settings are up to date.
Reassure and Educate: End the message by reassuring employees that their security is a priority and that you’re taking necessary actions. If relevant, you could also reference recent security training or announcements.
Templates
Templates are default responses sent to users when they report a suspicious message. You can have multiple templates for Admin classified Safe, Admin classified Malicious, or Admin classified Spam so that you can customize your response on a case by case basis once you classify the message.
How to create a template
From User Reports > Settings, under Acknowledgement templates, expand either Admin classified Safe, Admin classified Malicious, or Admin classified Spam
From the template drop down, click Create a New Template

Create a new template Enter the details for your template then Save. To choose an available variable to personalize your message, choose one from the drop-down.
Send classification responses to initial reporters
Default responses once you've classified don't send to the users who reported per classification by default. However, you can update this on a case by case basis and trigger another response to let them know how the issue was classified. In the issue, choose Also send to previous reporters.

Send reporter acknowledgements with other tools
You can use a webhook to create your own reporter acknowledgement via Slack or other tools. It's not represented in the issue timeline, but all the settings apply to it even if it's the event fires.
Last updated
Was this helpful?

