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

# Do-not-call registry

> The numbers of people who asked your organization not to call them: how a number gets into the registry, how to add and remove it by hand or with a file, and how the registry protects campaigns.

# Do-not-call registry

The **Do not call** section of the cabinet menu keeps the numbers of people who asked your organization not to call them. **A number in the registry is never dialed by any campaign of the organization.**

![The do-not-call registry: filters and export, the manual entry and bulk operations block, and the table of entries with the History and Remove buttons](https://mintcdn.com/hubtalk/iZJZ2s2ncd6_0_vL/images/v4_dnc_registry_en.png?fit=max\&auto=format\&n=iZJZ2s2ncd6_0_vL\&q=85\&s=2b8845144f6862d0eb561e6c0560fedf)

## How the registry protects campaigns

* **Before launch**, every campaign checks its contacts against the registry. If there are matches, the wizard asks what to do with them — see [Do-not-call matches](https://docs.hubtalk.ai/v4/platform/campaign-launch.md).
* **Before every dial**, the number is checked again. So a number added to the registry during a campaign is no longer dialed: all its remaining retries are cancelled.
* Numbers are compared by their last 10 digits, so the format does not matter: `+1 (202) 555-0117`, `12025550117` and `2025550117` are the same number.

## How a number gets into the registry

Every entry has a **source** — the **Source** column of the table:

| Source | How the entry appears |
| - | - |
| **Manual** | A cabinet user added the number in the manual entry block. |
| **Bulk upload** | The number came from an uploaded file. |
| **Trigger phrase** | The caller said a phrase from the trigger phrase list during a call, for example "remove my number". |
| **Model classification** | A trigger phrase put the number forward as a candidate, and the model decided from the conversation context that the person really asks not to be called. |
| **Agent classification** | The call ended with a status or a field value the organization set as a sign of refusal. |

Automatic entries — all except manual and uploaded ones — appear when a call ends: outbound, inbound and calls placed through the API. Such an entry has a piece of the transcript in the **Snippet** column — the evidence the number was added on. Test calls from the cabinet do not add to the registry.

**The model's outcome.** Entries from the model show **Confirmed refusal** or **Uncertain** in the **LLM outcome** column. A number with the uncertain outcome is not dialed either, but its entry goes to the **Review queue**: find it with the outcome filter, check the snippet and click **Confirm** — the entry gets the "reviewed" mark. If the model decides there is no refusal, no entry is created.

## Finding a number

* **Search by number in any format** — part of the number is enough.
* The state filter: **Active** (default), **Removed** or **All**.
* Filters by source, model outcome and period.
* **Clear filters** brings back the default view.

Above the table there is the **Entries: N** counter. The **History** button in a row shows all entries of that number in order: when, by whom and why it was added and removed.

**Export CSV** and **Export XLSX** download the entries with the current filters applied. The file holds the number, state, source, reason, snippet, outcome and model, campaign, who made the entry and when, and a summary at the end: how many entries and with which filters.

## Adding and removing a number by hand

In the **Manual entry and bulk operations** block:

1. Type the number in the **Phone number** field and, if you like, a **Reason** — for example, "Written request to support".
2. Click **Add** to add the number, or **Remove** to take it out of the registry.

You can also remove a number with the **Remove** button in its row. A removed entry is not deleted: it stays in the number's history with the **Removed** state, and the number can be dialed again.

A number already in the registry cannot be added again; a number that is not in the registry has nothing to remove — the cabinet says so.

## Uploading a file

* **Upload file (add)** adds every number in the file to the registry.
* **Upload file (remove)** removes every number in the file.

The file is CSV, TXT or XLSX, one number per row, and only the first column is read; up to 100,000 rows. The legacy `.xls` format is not accepted — save the file as `.xlsx` or `.csv`. Samples are under the buttons: **Download sample CSV** and **Download sample XLSX**.

After the upload the cabinet shows a report: **Applied**, **skipped**, **unreadable** and **duplicates**. Skipped are numbers already in the registry (when adding) or not in it (when removing); unreadable are rows no 10-digit number can be read from; duplicates are numbers repeated in the file.

## Trigger phrases and the model

Organizations with the US market profile have a second tab in this section — **Capture**: it sets how numbers get into the registry from calls.

* **Organization trigger phrases** apply on top of the platform set. An empty list means the platform set is in effect; changes apply at once, without a restart.
* **Model classification** — the model that decides on a candidate put forward by a trigger phrase. Without a model, the phrases add the number by themselves.
* **Classifier prompt** — every edit is saved as a new version with its author and time, and every registry entry refers to the version it was decided by.
* **What is in effect now** — the result: how many phrases work and which statuses and fields count as a refusal.

The tab is visible to the organization's administrators and developers.

## Who can

All users of the organization see the section. Any cabinet user, members included, can add and remove numbers, by hand and with a file.


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