Sample emails are realistic phishing examples sent to the users you choose. They let you see the banners in a real mailbox and show colleagues what they will look like. They are not the test email of Step 3: Test Deployment.
- Do
- Expected result
- Verify it worked
- Revoke or undo
- Limit the scope
- Which samples can I send?
- Why are Key People needed?
- Before you send: tell your security team
- Can I see a real banner without the samples?
Do
- Open Send sample emails.
- In Phishing scenario, select one or more scenarios.
- In Target users, select the recipients. Only Active users are listed: activate them first in Smart Banners › Users.
- Click Send sample emails.
Send sample emails: scenarios and target users selected, and Test emails already sent ticked
Expected result
The toast The emails have been sent. appears, Test emails already sent shows a green tick and the step is ticked. The selected users receive the samples, each with the banner shown in the table below.
Verify it worked
Open the samples in a target mailbox and compare the banners with the table. A banner may carry more reasons than expected, for example the first-time-sender line on a mailbox that never received mail from that sender.
Revoke or undo
The samples stay in the mailboxes like any other email; users can delete them. You can send them again at any time.
Limit the scope
Only the users you select receive the samples.
Which samples can I send?
Each scenario exists in English ([EN]) and French ([FR]). All of them raise an orange banner, except the CEO scenario (red) and the test email (green).
| Scenario | What it imitates | Expected banner |
|---|---|---|
| ceo-impersonation | An urgent request from your CEO, sent from an outside address (uses your Key People) | Red |
| docusign | An electronic signature request with an HTML attachment presented as a PDF | Orange |
| laposte | A parcel delivery failure from a look-alike domain | Orange |
| atos | A request for proposal with a zipped attachment | Orange |
| microsoft-password-modification | A Microsoft password update notice from a look-alike domain | Orange |
| google-password-modification | A Google password update notice from a look-alike address | Orange |
| supplier-bank-change | A supplier announcing new bank details, with a macro-enabled spreadsheet attached | Orange |
| test-email | The test email of Step 3: Test Deployment | Green |
Why are Key People needed?
The CEO scenario imitates the CEO set in General Settings › Company Scan › Key People. If no CEO is set and you select that scenario, the step shows To use this feature, the Key People must be filled out. and the button stays disabled. For a test, you can set another person as CEO.
The CEO scenario selected while no CEO is set in Key People: the button stays disabled
Before you send: tell your security team
If a user clicks Report email on a sample, it reaches your security team like any reported email. Tell your team before sending samples. What Report email does: Banners and user actions › Where does a report go?
Can I see a real banner without the samples?
Yes. An active user writes to their work address from a personal mailbox that shows their own name. The email arrives with a grey banner saying the sender has the same name as them.
Details: the banners and what users can do with them: Banners and user actions.