How to Build a Do-Not-Call Process
Every team that makes sales calls needs a do-not-call process. It protects the people you call, keeps your business on the right side of federal rules, and helps your caller ID reputation. This guide walks you through building one from scratch.
This is general information, not legal advice. Have counsel review your written policy.
The two lists you must handle
1. The National Do Not Call Registry. Run by the FTC. Consumers register numbers they do not want telemarketing calls on. Sellers must scrub call lists against a version of the registry obtained no more than 31 days before calling, unless an exemption applies.
Source: https://telemarketing.donotcall.gov/ (accessed October 17, 2026)
2. Your internal do-not-call list. Your company's own list of people who asked you to stop calling. FCC rules require you to keep it, even for numbers not on the national registry.
Some states also keep their own lists. Check the states you call into.
What the FCC rules require for your internal list
Under 47 CFR 64.1200(d), you must:
- Have a written policy for maintaining your do-not-call list, available on request.
- Train everyone involved in calling on the policy.
- Record stop requests and honor them within a reasonable time, not more than 10 business days from receipt.
- Honor each request for 5 years.
- Give the called party the name of the seller and a contact number or address.
Source: 47 CFR 64.1200, https://www.ecfr.gov/current/title-47/chapter-I/subchapter-B/part-64/subpart-L/section-64.1200 (accessed October 17, 2026)
Step 1: Write the policy
Keep it to one or two pages. Cover:
- Who owns the process (one named role, such as sales operations manager).
- Which lists you check and how often.
- How stop requests are captured from calls, texts, email, and web forms.
- How fast requests are added (aim for same day, well inside the 10-business-day limit).
- How long you keep records.
- How you train new hires.
Date the policy and keep every version.
Step 2: Capture every stop request
People do not always say "add me to your do-not-call list." Train reps, and configure any AI agent, to treat plain language as a stop request:
- "Stop calling me."
- "Take me off your list."
- "Don't call this number again."
- "I'm not interested, please don't call back."
Make "Do not call" a one-click disposition in your dialer or AI calling tool. A good AI agent should end the call politely when asked to stop and log the request automatically.
Also capture requests from:
- Text replies like STOP, QUIT, or END.
- Emails asking to stop contact.
- Web forms or support tickets.
Step 3: Sync it everywhere
A stop request in one tool must stop every tool. Connect your internal list to:
- Your CRM.
- Every dialer and AI calling tool.
- Your texting platform.
- Any vendor or agency calling on your behalf.
Use native integrations, webhooks, or automation tools to push updates in near real time. Test it: mark a test number as do not call and confirm every system blocks it.
Step 4: Scrub before every campaign
Before any list is loaded for calling:
- Remove numbers on your internal do-not-call list.
- Scrub against the National Do Not Call Registry using a download no older than 31 days.
- Scrub against any applicable state lists.
- For older lists, check numbers against the Reassigned Numbers Database at https://www.reassigned.us/.
Save a record of each scrub: date, list name, registry version, and how many numbers were removed.
Step 5: Train and retrain
Cover the do-not-call process in onboarding and refresh it every quarter. Keep a training log with names and dates. Short is fine. A 15-minute session with real call examples works better than a long slide deck.
Step 6: Audit
Each month, check:
- A sample of calls marked "not interested" to see if any were actually stop requests.
- Whether any number on the internal list was dialed after the request date.
- That scrub records exist for every campaign.
Fix gaps right away and note the fix.
Why records matter
Federal rules include a safe harbor for occasional errors if you have written procedures, train staff, maintain your list, and use a current registry version as part of your routine practice. Records are how you prove that routine exists. A policy written after a complaint will not help.
Quick checklist
- Written, dated do-not-call policy
- One named owner
- Plain-language stop requests recognized on calls
- Text, email, and form requests captured
- Requests added same day
- Internal list synced to every tool and vendor
- Registry scrub within 31 days of calling
- Scrub and training records kept
- Monthly audit
A strong do-not-call process is not just about avoiding fines. It shows people you listen. That is a good reputation for any sales team.