> ## 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. # Send warm-up notices from your own domain > What a warm-up notice is, how the text and email versions work, and how to verify your own sending domain on the Fair testing page. A warm-up notice is a short text or email sent a few minutes before a test call. It makes the call refer to something the person has already seen, the way a real attacker primes a target. The campaign sends the notice, waits the delay you chose, then places the call. > [!NOTE] > > Any campaign that sends a notice needs the tick **Messages to staff phones and inboxes are in scope for this engagement.** at launch. See [Authorise and launch](https://docs.deepblocker.ai/vishing/campaigns/authorise.md). ## Before you start * A campaign where you want the notice. It is set under **Before the call** on the **Who calls** step. See [Build a campaign](https://docs.deepblocker.ai/vishing/campaigns/create.md). * For email from your own domain: access to your domain's DNS records. ## How a warm-up notice works | Setting | Options | Default | | - | - | - | | Channel | **Text**, **Email**, **Text and email**, or **No warm-up** | **No warm-up** | | Delay before the call | 2 to 30 minutes | 5 minutes | | Template | **IT account check**, **Payment query**, **Delivery**, **HR document**. You may edit the text | **IT account check** | | Placeholders | `{name}`, `{company}`, `{caller}`, `{time}` | Filled from the person, your workspace name, the caller name on the campaign, and the planned call time | | Length | Up to 600 characters | | The rules that apply to every notice: * The text may name the person and their own company. It may never name a real outside brand. A notice that names one is refused and the default template is used instead. * A person who replies STOP to a text, or clicks the opt-out link in an email, gets no more notices. * Notices are capped at 500 per workspace per day. * A person with no address on the chosen channel gets no notice. The report shows which notice each call had. Every call records the notice it had, so the results page compares calls with and without one. See [Read your results](https://docs.deepblocker.ai/vishing/results/overview.md). ## Who the notice comes from | Channel | Sender | | - | - | | Text | A DeepBlocker number. On the campaign you may set a different sender: a phone number, or a short name of up to 11 letters and digits such as "IT-Support". It must be a sender our text provider is allowed to use. | | Email | DeepBlocker, [hello@deepblocker.ai](mailto:hello@deepblocker.ai), or your own verified domain | Today the verified domain is not yet used as the sender: warm-up emails still come from [hello@deepblocker.ai](mailto:hello@deepblocker.ai), even when your domain shows **Verified**. ## Steps to verify your domain **1. Open the sender card** In the console, open **Red Team**, then the settings page titled **Fair testing**. Scroll to **Warm-up email sender**. **2. Add your domain** Under **Sending domain**, enter a domain you own, for example `mail.yourcompany.com`. The help text says: "Must be your own company domain, never a third party's." Under **From name (optional)**, enter the name to show on the email, for example "Your IT team". Click **Add domain**. The status shows **Pending verification** and two DNS records appear. **3. Add the two DNS records** Add both records at your domain host. Use the copy icons next to each **Name** and **Value**. | Purpose | Type | Name | Value | | - | - | - | - | | SPF | TXT | your domain | `v=spf1 include:spf.mtasv.net ~all` | | DKIM | CNAME | `deepblocker._domainkey.` followed by your domain | `deepblocker._domainkey.` followed by your domain, then `.dkim.mtasv.net` | If your domain already has an SPF record, add `include:spf.mtasv.net` to it instead of adding a second one. **4. Verify** Click **Verify DNS**. Each record shows **found** or **not found**. When both are found the status becomes **Verified** with the date. If not, the page says: "Not verified yet. DNS can take a while to spread; try again shortly." ## What happens next The domain stays on your workspace. **Update domain** changes it. **Use our sender instead** removes it and goes back to [hello@deepblocker.ai](mailto:hello@deepblocker.ai). ## Problems > [accordion] Verify DNS says Not verified and one record says not found > > DNS changes can take up to an hour to spread. Check the record name is exact, including the `deepblocker._domainkey.` part, then click **Verify DNS** again. > [accordion] It says Enter a domain such as mail.yourcompany.com > > The value is not a domain. Enter the domain only, without `https://` or an email address in front. > [accordion] The notice did not arrive > > Check the person has a phone number or email address on their contact for the channel you chose. Check the daily cap of 500 has not been reached. A person who replied STOP or opted out gets no notice. > [accordion] The notice was sent with the default text, not mine > > Your text named a well-known outside brand, or was over 600 characters. The default template was used instead. Edit the text and keep to your own company name. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.