> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/ai-voice-agents/how-to-create-your-first-campaign-in-dapta/do-not-call-list.md).

# Do Not Call list

Keep the numbers that must never be called out of your voice sequences. Add a number by hand, from a contact in the CRM, or let your voice agent add it when someone asks on a call, and Dapta checks th

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-d86c3637fe1bbced46a505ce9668bd6ec0382b9d%2Fsequences-do-not-call-list.mp4?alt=media>" %}

{% file src="/files/4H2NSwxwTSectiN4IEHv" %}

Some numbers must never be called again: a customer who asked you to stop, a lead who already bought, a number your legal team flagged. The **Do Not Call list** keeps them out of your voice sequences. Add a number once, and Dapta checks the list before every outbound call a sequence places.

{% hint style="info" %}
The list covers the outbound calls your **voice sequences** place. It is checked on scheduled runs, re-dials and callbacks alike. WhatsApp templates have their own list: see [WhatsApp do-not-contact list](https://docs.dapta.ai/ai-text-agents/campaigns/whatsapp-do-not-contact-list.md).
{% endhint %}

***

## How it works

* **Checked before every call.** Each time a voice sequence is about to dial a contact, it looks the number up on the list first.
* **Two scopes.** A number blocked for the **entire workspace** is never called by any sequence. A number blocked for **one sequence** is skipped by that sequence only; your other sequences can still call it.
* **Blocked contacts leave the sequence.** A contact whose number is on the list is excluded from that sequence, so it no longer waits in the queue.
* **Safety first.** If the list can't be checked at that moment, the sequence places no calls until it can. A number is never dialed because a check failed.
* **Three ways in.** Add a number on this page, add it from the contact in your [CRM](https://docs.dapta.ai/crm.md#do-not-call-from-a-contact), or let your voice agent add it when someone asks on a call: see [Let your voice agent add numbers](#let-your-voice-agent-add-numbers).
* **Only a person removes a number.** Agents add numbers and never take them off. Remove one here or from the contact.

***

## Add a number

**Step 1: Open the Do Not Call list.**

Go to **Sequences** and open **Do Not Call list** in the menu.

***

**Step 2: Click Add number.**

A dialog opens with three fields.

| Field            | What to enter                                                                                                                                                                  |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Phone Number** | Required, in international format with the country code, for example `+57 300 123 4567`.                                                                                       |
| **Scope**        | **Entire workspace**: no sequence calls this number. **Specific campaign**: only the sequence you pick skips it. Choose it in the **Campaign** field; type to search the list. |
| **Reason**       | Optional. Why this number should not be called, for example *Asked us to stop calling*.                                                                                        |

***

**Step 3: Click Save.**

The number appears in the table right away and is skipped from the next call on. Adding a number that is already on the list with the same scope changes nothing: there is one entry per number and scope.

***

## Manage the list

The table shows every blocked number with its **Scope** (a **Workspace** chip, or the name of the sequence), the **Reason**, the **Source** and the date it was created.

| Source   | Where the number came from                                                                                                                                                    |
| -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| *manual* | Added by a person: on this page or from the contact in the CRM.                                                                                                               |
| *agent*  | Added by a voice agent after a call. Its **Reason** reads `call:` followed by the call's id; open the contact in the CRM to see **Asked for it on a call** and **View call**. |

* **Search.** Type a phone number in the search box and press **Enter**.
* **Pages.** A long list is split into pages; move between them at the bottom of the table.
* **Remove a number.** Click the **Remove** icon on its row and confirm. The number can be called again from the next call on.

***

## Let your voice agent add numbers

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-601d014472f95c3838d65197efc711df9568380b%2Fcrm-do-not-call-contact-and-agent-en.mp4?alt=media>" %}

{% file src="/files/UTvzJkcw092RvuglttNX" %}

When someone says "don't call me again", the agent can put the number on the list itself, the moment the call ends. The rule lives in the agent's **Dapta CRM** after-call destination, on its **Do Not Call** step: see [Send results to the Dapta CRM](https://docs.dapta.ai/ai-voice-agents/analyze-your-calls/post-call-analysis-destinations.md#send-results-to-the-dapta-crm).

**Step 1:** In **Data Retrieval from your Calls**, ask the agent for a yes/no variable, for example `wants_no_more_calls`.

**Step 2:** In the **Dapta CRM** destination, on the **Do Not Call** step, complete **Add to the Do Not Call list when this condition is met** with that variable, for example `wants_no_more_calls` **is yes**. With two or more conditions, choose whether **all** or **any** of them must be met; a rule takes up to 10 conditions. The step is optional: **Skip** saves the destination without a rule.

**Step 3:** Save. After each call that meets the rule, the number goes on the list for the **entire workspace**, with the agent's name and the call behind it, even when the caller isn't in your CRM yet.

* **Test calls never add a number**, and neither does the destination's **Test now**: it shows **Would add to Do Not Call · test, not added**.
* The destination's **History** says what happened to each call's number: **Added to Do Not Call**, **Already on Do Not Call** or **Skipped** with the reason.
* The agent only adds numbers, always for the whole workspace. It never removes one.
* Text agents never add numbers: their Dapta CRM destination has no **Do Not Call** step.

***

## Add or remove a number from a contact

Open the contact in **CRM**. A contact whose number is on the list wears a red **Do Not Call** tag; click it to see each entry: the scope, who added it, when, and the reason or the call it came from. The phone-off icon in the header adds the number for the whole workspace (**Add to Do Not Call**) or removes it (**Remove from Do Not Call**, after you confirm). The details are in [Do Not Call from a contact](https://docs.dapta.ai/crm.md#do-not-call-from-a-contact).

***

## Mirror list: keep a sequence in step with its source

A sequence that pulls its contacts from **HubSpot**, **Google Sheets** or an **HTTP API** can follow that source when contacts are taken off it. In the sequence's **Connections** tab, each of those sources has a **Mirror list** switch. When it is on, a contact removed from the source list is also removed from the sequence, so nobody is called from a list you already cleaned up.

The switch is off by default, and it is not offered on **Webhook** sources, which push contacts into the sequence instead of being read by it.

***

## Best practices

* **Block for the entire workspace when a person asks you to stop.** A **Specific campaign** block only skips that one sequence; your other sequences can still call the number.
* **Let the agent do it on the call.** A yes/no variable in **Data Retrieval from your Calls** plus the **Do Not Call** rule puts the number on the list the moment the call ends, so the sequence's next attempt already skips it. Nobody has to copy numbers by hand.
* **Rehearse the rule with Test now.** It shows **Would add to Do Not Call · test, not added** without touching the list, and test calls never add a number either.
* **Use international format.** The list matches numbers by their digits with the country code, and a contact whose phone has no country code can't be blocked from the contact until you fix the number.
* **Block, don't delete.** Deleting a contact doesn't stop the calls: if the number is imported again, it is called again. A number on the list stays blocked whatever happens to the contact.
* **Removing is deliberate.** Only a person removes a number, from this page or from the contact, and the sequence calls it again from the next attempt on. Blocks for a single campaign stay when you remove a workspace block.

***

{% content-ref url="/pages/8yIUCoPD1oNPbiGLgIRU" %}
[Call Logic & Limits](https://docs.dapta.ai/ai-voice-agents/how-to-create-your-first-campaign-in-dapta/call-logic-and-limits.md)
{% endcontent-ref %}

{% content-ref url="/pages/oAicUT9kkH5vABsAXEao" %}
[Managing your sequence](https://docs.dapta.ai/ai-voice-agents/how-to-create-your-first-campaign-in-dapta/managing-your-campaign.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dapta.ai/ai-voice-agents/how-to-create-your-first-campaign-in-dapta/do-not-call-list.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
