Before an AI caller dials anyone, decide who it may never call again and how fast that rule applies. Good do not call list management depends on three things: catching opt-outs, treating wrong numbers, and cleaning the list often.
Set one suppression list before you dial
Build one master do-not-contact list that every campaign checks before every dial. Give each entry a reason code: opt-out, wrong number, complaint, deceased or legal hold. The codes matter because each reason needs a different follow-up. A wrong number needs a fresh number found. An opt-out needs nothing, ever. A legal hold needs a lawyer.
Copies are a common leak. A duplicated campaign must leave out anyone added to the list since the original ran. Check that your setup also has consent marking, calling hours, retry rules, a test call to your own phone and a do-not-call list.
Next, scrub purchased or imported numbers against the national registry for each region you call. Examples include the FTC's National Do Not Call Registry in the US, and the UK and EU have their own national registries and rules. Find the one for each market and scrub the same way. In the US, sellers and telemarketers must delete all National Registry numbers from their call lists at least every 31 days.
Keep consent proof per contact. In the US, the FCC's February 2024 Declaratory Ruling confirmed that TCPA rules apply to calls that use AI to generate voices. It says callers need prior express consent or prior express written consent before making AI-generated voice calls, depending on the call. So store when, how and for which number each person agreed.
Capture opt-outs during the call
Treat any request to stop as an opt-out, in whatever words the person uses. Phrases like "stop calling me," "take me off your list," "don't call again" and "remove my number" all count. Write the phrase list into the agent's instructions, and add the soft versions: "I'm not interested, don't ring me." When in doubt, treat it as an opt-out. A wrongly honoured opt-out costs one contact. A wrongly ignored one can cost a complaint or a fine.
The flow should have four moves:
- Detect: the agent listens for a stop phrase at any point, including mid-pitch.
- Confirm: one short line, such as "Understood, I'll make sure you're not called again."
- End: hang up politely. No retention offer and no "are you sure?"
- Record: write the number to the master list with the reason code "opt-out" before the call closes.
Speed matters. Do not wait for a nightly batch job. Make the write immediate, so a redial a minute later is impossible.
Then audit. Insight7 voice campaigns, currently in beta, have a do-not-call list and consent marking. A reviewer can read each transcript once a call ends, and call outcomes are pulled from it. Contacts come in by CSV upload or typed entry, so run your list checks on every import. Sample transcripts weekly and look for stop phrases that never reached the list. Confirm in the app how opt-outs reach the list.
Treat wrong numbers differently from opt-outs
A wrong number is a data fault. The person who answered never refused anything, and may never have been your contact. Handle it as an error in your list, not as a "no."
When the answerer says "you have the wrong person," the agent should:
- Apologise.
- Say nothing about the contact's name, account or reason for the call.
- End the call politely.
- Flag that number as wrong for that contact.
Then suppress the number everywhere. Put it on the master list with the reason code "wrong number," so no campaign dials it again. Keep the contact record so someone can find a fresh number for a real customer.
Numbers also change hands. In the US, the FCC's Reassigned Numbers Database lets callers check whether a number has been permanently disconnected. As a safe practice, do not assume consent from the old owner covers the new one. Check the database before you reuse an old number.
Set retries that stop at the right moment
Cap retries by outcome, because not every failed call means the same thing. Wrong numbers and opt-outs stop all retries at once. No-answer retries follow the retry rules you set in the campaign. Set a maximum number of attempts and a minimum gap for each campaign type.
Keep wrong numbers apart from other outcomes that look like failure:
- No answer or voicemail: retry within your capped rules.
- Silence or only the AI speaking: not counted as reached.
- A carrier's temporary refusal: does not use up a retry.
For cadence, one consumer lender's pilot found that three to four calls worked best, and that morning and evening calls got more answers. Start there, then test on your own list.
Plan the handoff too. If a person says "let me talk to someone," the agent should pass the call to a human or log a callback. It should not retry the contact by machine. Tag that contact "human follow-up" so no automated campaign dials them until a person clears it.
Clean the list on a fixed schedule
Rescrub the list before every campaign, and never let the gap run past 31 days where that registry rule applies. Check the internal suppression list at the same time. A number that opted out last week is not on any registry yet.
Then clean the file itself:
- Dedupe contacts who appear twice under different names.
- Normalise every number to E.164, the international format with country code.
- Drop invalid formats and every contact flagged "wrong number."
Respect channel preference. Move contacts who ask for messages to SMS or WhatsApp. One delivery operator told us its high-end customers write "no calls" on their orders and want app or WhatsApp messages. A call to those people costs you goodwill, even if the law allows it. Honour a "stop" reply on every channel you use.
Set a sunset rule. Remove a contact after a fixed number of failed attempts across all campaigns. Pick the number that suits your list and your regulator.
Set retention limits for personal data and consent proof, and delete both on schedule.
Buyers also ask first whether a tool plugs into their CRM. Make sure an opt-out in the dialer reaches the CRM, and one in the CRM reaches the dialer.
Track four numbers monthly:
- opt-out rate
- wrong-number rate
- complaint count
- reached rate
Only calls where the customer spoke count as reached. A jump in opt-outs points to bad targeting or a weak script, so fix those before you redial.
Related reading: Warm Transfer vs Callback vs Ticket Handoff for AI Voice Agents Compared, How AI Voice Agents Handle Callback Requests and Reschedule Calls Automatically and How to Detect Voicemail and Avoid Wasted Minutes on AI Outbound Calls.
Questions people also ask
How does the do not call list work?
The FTC's National Registry is a list that tells registered telemarketers which numbers not to call. It does not block calls. Your own internal list covers people who asked you directly. Check both lists before every dial.
Does the do not call list apply to AI voice calls?
Yes. The FCC treats AI-generated voices as artificial voices under the TCPA, so consent rules apply. The FTC adds that a selling robocall is illegal without written permission. Keep consent proof for each contact.
How do you add someone to a do not call list?
Consumers register free at DoNotCall.gov or by calling 1-888-382-1222 from the phone in question. On your side, the agent writes the opt-out to the do-not-contact list during the call, with a reason code.
How long do you have to honour a do not call request?
Stop calling at once and write the request to your list before the call ends. The registry's 31 days is the cycle for scrubbing registry numbers, not a grace period for someone who just asked you to stop. Ask counsel for your region's exact deadline.
Does the do not call list expire?
No. An FTC registration never expires. The number leaves only if it is disconnected and reassigned, or the owner asks. Keep your internal opt-outs permanent too.
Does the do not call list apply to text messages?
Treat texts the same as calls. Check consent before sending, scrub texts against the same suppression list, and honour a "stop" reply on every channel. Ask counsel how your region's rules apply to texts.
What should an AI agent do when it reaches a wrong number?
Reveal nothing about the contact, and flag the number so it is never dialled for that contact again. Log the outcome so reports stay clean. The call is not counted as reached unless the customer spoke.
One list, checked before every dial
Opt-outs, wrong numbers and stale lists all need one shared suppression list, checked right before each dial. Insight7 voice campaigns, in beta, have consent marking and a do-not-call list. Before you start, confirm in the app how an opt-out reaches that list.

