> ## Documentation Index
> Fetch the complete documentation index at: https://docs.deepblocker.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Every message DeepBlocker sends to your staff

> The five messages a member of your staff can receive from DeepBlocker, who gets each one, what triggers it, the channel, the sender and what it says.

Your staff only ever receive the messages below. Each one is sent only when you set up the campaign or action that triggers it.

| Message | Who receives it | What triggers it | Channel | Sender | What it says |
| - | - | - | - | - | - |
| Warm-up notice | The person about to be called | A campaign with a warm-up on. Sent 2 to 30 minutes before the call (5 by default). | SMS, email, or both | SMS: a DeepBlocker number, or the sender you chose on the campaign. Email: DeepBlocker, [hello@deepblocker.ai](mailto:hello@deepblocker.ai) | A short heads-up from one of four templates, **IT account check**, **Payment query**, **Delivery** or **HR document**, for example that the IT team will call shortly. The email subject is the first line of the notice. The email has an opt-out link. |
| Call-back trap message | Each person in a call-back trap campaign | Launching the campaign | SMS, email, or both, as chosen on the campaign | As above. Email subject: **Please call us back** | One of four templates, **Invoice query**, **Subscription renewal**, **Delivery** or **HR document**, asking the person to call the trap number. |
| Video call invitation | Each person in a video call campaign | Their video call being set up | SMS when they have a number, email when they have an address | As above. Email subject: **A quick video call** | One of three templates, **Quick call**, **IT check** or **HR document**, with a one-use link to the meeting page. |
| Coaching note | A person who was coached at the end of a failed call | The reveal script was heard in full | Email | DeepBlocker, [hello@deepblocker.ai](mailto:hello@deepblocker.ai) | Subject **Your phone security training call today**: the script they heard, what to look out for next time, and your training link if you set one. See [Coaching at the end of a failed call](https://docs.deepblocker.ai/vishing/results/coaching.md). |
| Voice consent request | The executive whose voice you want to clone | Clicking **Add an executive voice** | Email | DeepBlocker, [hello@deepblocker.ai](mailto:hello@deepblocker.ai), "on behalf of" your company | Subject **Your company asks for your consent to a voice clone for security training**, with your company's name in place of "Your company". A one-use link that expires in 7 days, what the copy is used for, and how to withdraw. See [Clone an executive's voice with consent](https://docs.deepblocker.ai/vishing/executive-voice-consent.md). |

## Rules that apply to every message

* A message may name the person and their own company. It never names a real outside brand: a list of well-known brands is blocked, and a message that contains one is refused.
* A message to staff phones or inboxes needs the tick **Messages to staff phones and inboxes are in scope for this engagement.** in the campaign's authorisation. See [Authorise and launch](https://docs.deepblocker.ai/vishing/campaigns/authorise.md).
* A person who replies STOP to a text, or clicks the opt-out link in an email, gets no more notices.
* Warm-up notices are capped at 500 per workspace per day.
* Nothing is sent to anyone who is not on your People list, except the executive you name for a voice clone.

> [!NOTE]
>
> Messages to you, rather than to your staff, are covered elsewhere: the minutes email on [When you run out](https://docs.deepblocker.ai/vishing/minutes-exhausted.md), and team invites on [Invite your team and roles](https://docs.deepblocker.ai/account/team.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.