DNC scrubber checks before a lead reaches your dialer
Screen phone numbers against federal and state do-not-call lists and your internal suppression lists before outbound contact. ConsentVerified brings DNC checks into the same workflow as consent certificates and lead verification. Upload a list or use the API to check incoming records, then review the results before deciding which leads can enter your contact process.
Check the federal National Do Not Call Registry
The federal National Do Not Call Registry gives consumers a way to limit covered telemarketing calls. Sellers and telemarketers must follow the applicable access, screening, and calling rules, including keeping registry checks current. A list screened in the past should not be treated as permanently cleared. Build the required refresh process into your campaign preparation rather than relying only on the date a lead enters your database.
ConsentVerified checks numbers against the federal registry as part of its DNC workflow. Registry obligations can involve authorized access, applicable subscription requirements, and limits on how registry information is used. Use the results for suppression and compliance review. A screening tool supports that process, but it does not remove your responsibility to follow the rules governing your own outreach.
- Include the federal registry check before covered telemarketing outreach.
- Keep list freshness and applicable access requirements in your operating process.
- Use registry information for its permitted compliance purpose.
Include state list checks in the review
State do-not-call requirements can apply alongside the federal framework. Some states maintain separate lists, and state rules can differ in their scope, exceptions, and operational requirements. A federal result alone does not answer every state-law question. Review the laws relevant to the recipients and campaigns your team handles rather than assuming that one national check settles the entire decision.
The DNC list scrubber includes state list checks so your team can examine those results together with federal and internal suppression information. Keep separate compliance requirements, such as permitted calling times or other state restrictions, in your campaign controls. A list match is a screening result. It is not a complete assessment of every state rule affecting a particular contact.
- Review relevant state list results alongside federal results.
- Identify other state requirements that are outside a list check.
- Escalate unclear exceptions or conflicting information before contact.
Carry consumer requests into the next campaign
Your internal suppression lists record requests that may never appear in a public registry. A consumer who asks your team to stop should not be returned to the contact queue simply because a vendor supplies the number again. Keep internal lists connected to the same checks you perform for newly uploaded or incoming leads. The current preference matters even when an older certificate records an initial opt-in.
ConsentVerified checks internal suppression alongside federal and state sources. Your process needs to bring requests from agents, support, and messaging workflows into the relevant suppression records. For texts, keep SMS consent and STOP evidence available so the team can review both the initial subscription and the later request. Define responsibilities for maintaining the list and resolving uncertain requests.
-
Include direct requests received by your business in internal suppression.
-
Check repeat and purchased leads against current suppression information.
-
Keep later revocation evidence connected to the relevant consumer record.
Scrub before the dialer receives the list
Do not call list scrubbing works best as a release check before outreach. Run the relevant checks while there is still time to remove a matched record or investigate missing information. Screening only after a campaign starts leaves your team responding to results after contact has already occurred. Keep your dialer intake process dependent on the review you require.
A record without a DNC match does not prove that your intended communication is permitted. Use TCPA consent verification to review the agreement and the technology or channel involved. A registry match can also raise questions about applicable exceptions, which need review under the relevant rules. Neither a certificate nor a screening result should silently override a later request to stop.
- Screen records before releasing them into the outbound queue.
- Hold matches and incomplete records for the review your policy requires.
- Recheck as needed to meet applicable freshness requirements before later campaigns.
- Assess consent, suppression, calling context, and other applicable restrictions together.
Use uploads for lists and the API for incoming leads
Upload a list when preparing a campaign or reviewing an existing set of records. Use the API when a lead enters your intake process and your system needs a screening result before routing it further. These entry points let operations use the same DNC scrubbing software across scheduled list work and ongoing lead intake instead of maintaining unrelated review practices.
Keep the phone number being checked connected to the lead and the result your team reviews. Decide how matched records, incomplete checks, and unresolved exceptions are handled before connecting the result to an outbound workflow. The broader consent verification features combine these checks with certificate capture and lead verification, which address different questions about the proposed contact.
- Upload a list for campaign preparation and batch review.
- Call the API as part of the incoming lead workflow.
- Route records for review when a check does not support release.
- Keep a record of the decision your operations process makes.
Choose monthly capacity for the checks you run
Plans start from $149 a month with Starter. Starter includes 5,000 DNC scrubs per month, Growth includes 50,000, and Scale includes 250,000. Enterprise provides custom DNC volume. These are monthly allowances, so estimate the number of checks your process performs, including repeat screening needed for ongoing outreach, rather than counting only the number of leads in an initial import.
Starter, Growth, Scale, and Enterprise also include consent capture, lead verification capacity, SMS and 10DLC records, and evidence retention according to plan. Compare TCPA compliance software pricing for the complete allowances. Certificate and verification limits are separate from DNC capacity, which helps you choose a plan around the actual mix of work your team handles.
- Starter includes 5,000 monthly DNC scrubs.
- Growth includes 50,000 monthly DNC scrubs.
- Scale includes 250,000 monthly DNC scrubs.
- Enterprise provides custom monthly volume.
Keep the screening result in its proper context
DNC screening is part of a compliance process that also considers consent, revocation, call purpose, calling hours, caller identification, and applicable state rules. A business relationship or written agreement may affect certain restrictions, but exceptions have conditions and do not create blanket permission. Review an exception under the relevant rule before applying it, especially when the consumer has directly asked your business to stop.
Keep the related evidence available for your compliance team and counsel. The proof of consent workflow explains certificate capture and retrieval, while consent data security covers protection and retention. ConsentVerified is a compliance tool, not a law firm. The information here is not legal advice, and a screening result does not guarantee that a call or text is lawful.
Put suppression checks into the path to contact
Create your workspace and choose an upload or API workflow for the lists your team handles. Combine current DNC screening with consent verification and internal suppression so the decision to contact a lead has the relevant checks behind it.