DNC Solution
Voice & TelephonyConnect AI agents to DNCScrub from Contact Center Compliance, the do-not-call compliance service. Agents scrub phone lists against federal, state, and internal DNC registries, check reassigned numbers, and evaluate whether a time is legal to call before a dialer runs.
What This Integration Enables
Most connectors in a marketing or sales stack make work faster. This one is a control. DNCScrub, from Contact Center Compliance, exists so that an organization placing outbound calls can demonstrate it checked each number against the federal and state Do-Not-Call registries, its own Internal DNC list, the known litigator databases, reassigned number data and the calling-time restrictions that apply where the phone actually is. FlowRunner connects to that check so it runs at the moment the list is used rather than at the moment the list was built.
That timing is the whole point. A list scrubbed on Monday and dialled on Friday is a list that has aged past four days of registry additions, four days of number reassignments and any state emergency declaration issued in between. The connector makes the check cheap enough to repeat: Scrub Phone Numbers takes up to 10,000 numbers in a single call and returns a result record per number with a result code, a reason, line type, carrier and location. Around it sit the narrower lookups you reach for when a single number needs a specific answer: litigator only, reassignment against carrier deactivation data or the FCC database, right-party verification, residential versus business, real-time connected status, and the calling-time family that resolves a number to its timezone, its legal windows in UTC, its state's restricted holidays and whether that state is currently under an emergency restriction.
Two things this page will not overstate. First, the verbs. This connector evaluates calling-time rules, it does not enforce them. Is Time Legal To Call returns whether a solicitation is permitted at a given UTC datetime and how many seconds remain in the window; acting on that answer is your dialer's job and your flow's job. Nothing here can stop a call. Second, this connector has no triggers. The DNCScrub API documents no webhook or event-subscription surface of any kind, so there is nothing to subscribe to and nothing is pushed to FlowRunner. Every check is a call your flow makes, on a schedule you set or immediately before a dialer run. Design for that: the scrub is a gate you place in front of the campaign, not an alarm that will find you.
The failure mode that actually causes fines deserves saying plainly. A scrub that errors, times out or returns fewer result records than numbers submitted has not told you those numbers are clean. It has told you nothing about them. An agent that treats a missing verdict as an absent hit will happily hand a dialer a list of numbers nobody checked, and the resulting exposure scales with the number of calls placed rather than with the number of mistakes made. So build the flow to fail closed: compare the count of returned results against the count submitted, treat any number without a verdict as not callable, and stop the run rather than shrinking the suppression list. That is what automation exceptions look like in a compliance control, and they are the ones you never want quietly swallowed.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The scrub moves to the moment before the dial
A flow runs immediately ahead of each dialer session rather than on list import. It pulls the batch queued for that session, calls Scrub Phone Numbers with the campaign and project identifiers, and splits the response three ways: numbers with a clean result code, numbers suppressed with the reason recorded, and numbers with no result record at all. The clean set goes to the dialer. The suppressed set is written back to the CRM with its reason so nobody re-imports it next month. The unresolved set stops the run. Before releasing the clean set the agent calls Get State Emergencies, because a state that entered an emergency restriction overnight will not be reflected in a list scrubbed yesterday, and Is Time Legal To Call for the session's window. The list the dialer receives was checked minutes ago, and the record of that check exists.
Consent and reassignment checked together, because they are the same question
A number on which you hold consent is only useful if the person who gave it still has the number. A flow enriching a lead calls Check Reassigned Authority or Check RND Enhanced with the date consent was captured, which returns whether the line was reassigned since then and, for the FCC database lookups, whether the result qualifies for safe harbor. It calls Check Real-Time Disconnect for live line status and Get Premium Phone ID for the carrier, phone type and the date the line data was last observed. Numbers that changed hands are moved out of the consented segment in HubSpot rather than being called on a consent that no longer belongs to the person answering. Scrub Litigator List runs alongside as its own pass, because a match there is a different kind of problem and deserves a different queue.
Suppression requests that are honored the same day
A customer replies to an email or tells an agent on a call that they want no further contact. A flow catches that in Zendesk, calls Manage Internal DNC List with Add for the phone number and Add To Do-Not-Email List for the email address, and confirms with Scrub Email Addresses and a Status check that the suppression is now in place. It writes the timestamp and the source of the request back onto the CRM record. The reason this is worth automating is not throughput. It is that suppression requests arriving through a channel nobody monitors for them are the most common way a well-run programme ends up calling somebody who explicitly asked it not to. Note the asymmetry the flow should preserve: adding to the suppression list is safe to automate, and removing from it is not.
Human-in-Loop Highlight
The dangerous write in this connector is not the scrub. It is the pair of actions that move a number in the other direction, from suppressed to callable. Add EBR Record creates an Existing Business Relationship or consent record, and EBR records exist precisely to establish an exemption from DNC scrubbing. Manage Internal DNC List with the Remove option takes a number off the list your own organization put it on, which in most cases is a list somebody landed on by asking not to be called. Both writes make a future Scrub Phone Numbers return callable for a number that would otherwise have come back suppressed, and both do it silently: after the write, the scrub result looks exactly like a number that was never on a registry at all. Nothing downstream will ever flag it, because the whole point of the record is to make the number pass.
So the agent never creates an exemption on its own inference. It can gather everything: the transaction or interaction that would justify the relationship type, the date of last contact, the reference and brand to store with the record, the current suppression status from Manage Internal DNC List with the Status option including the date the number was added and last modified. Then it stops and puts the case in front of the person who owns compliance for the programme: "Request to add an EBR record for +1 512 555 0142, relationship type Inquiry, date of last contact 2 August, source: web form submission ref 88214. This number is currently on the Internal DNC list, added 14 March. Adding this record will make it pass future scrubs. Approve?" A named person reads that and answers, and only then does the agent call Add EBR Record or Manage Internal DNC List. The agent did the assembly, which is real work and takes real time. The judgment about whether a documented relationship justifies calling somebody who is on a do-not-call list stayed with a human, where the accountability already sits.
Agent Capabilities
27 actionsCompliance Scrubbing
2- Scrub Phone Numbers Scrubs numbers against the federal and state Do-Not-Call registries, wireless and VoIP identification, known TCPA litigators, your Internal DNC list, EBR and permission records, and calling-time restrictions in a single call. Accepts up to 10,000 numbers per request and returns a result record per number with a result code, reason, line type, carrier and location data. Always reconcile the returned record count against the submitted count.
- Scrub Litigator List Checks numbers against the database of known TCPA litigators and serial plaintiffs, and only that. It does not check the federal or state registries, line type, Internal DNC, EBR or calling-time restrictions. Returns each number with a boolean indicating a known litigator.
Reassigned Numbers
3- Check Reassigned Authority Checks whether a number has been reassigned to a new owner since a given consent date, using carrier deactivation data. Returns reassignment status along with validity, line type, carrier, timezone and location detail.
- Check RND Basic Queries the FCC Reassigned Numbers Database to determine whether a number was reassigned after a given consent date, and whether the result qualifies for safe harbor. Returns status only, without carrier or line-type metadata.
- Check RND Enhanced Queries the Enhanced Reassigned Numbers Database, combining the FCC data with carrier deactivation data for broader coverage. Returns reassignment status from both sources plus the safe harbor qualification.
Phone Data
5- Verify Phone Owner Right Party ID: verifies ownership by matching a number against supplied name and address data, returning a verification code and a match type and level indicating how closely the identity matches the registered owner.
- Check Residential Or Business Determines whether a number is associated with a residential or a business line, returning the number and its classification.
- Get Premium Phone ID Returns premium phone identification data for a number: phone type, operating carrier OCN, telco name and the date the line data was last observed. That observation date is what tells you how stale the answer might be.
- Append Phone From Name And Address Reverse phone ID append: looks up a phone number from supplied name and address data, returning the matched number, contact and business name fields, a confidence score, a deliverability code and line metadata.
- Check Real-Time Disconnect Checks the live line status of a number to determine whether it is currently connected or disconnected, returning the number with its connection status.
Calling Time Compliance
5- Get Timezone Info Returns timezone information for one or more North American numbers, including timezone name, state or province, UTC offset, whether daylight saving applies, and LATA and rate-center detail.
- Get Legal Call Times Returns the legal calling windows, in UTC, during which a telephone solicitation may be placed to a number on a given date, optionally across a range of consecutive days.
- Is Time Legal To Call Returns whether a solicitation to a number is permitted at a specific UTC datetime, accounting for the number's timezone and state calling-time restrictions, and when permitted also returns the seconds remaining in the window. This evaluates the rule; enforcement happens in your dialer.
- Get State Restricted Holidays Returns all US states together with the holidays on which telephone solicitations are restricted or prohibited in that state, each entry giving the state, the date and the holiday name.
- Get State Emergencies Returns all US states and whether each is currently under an emergency declaration that restricts telephone solicitations. Worth calling immediately before a run rather than relying on a list scrubbed earlier.
List Management
5- Manage Internal DNC List Adds, removes, counts or checks the status of numbers on your account's Internal Do-Not-Call list. Add and Remove change the list, Count returns the total, and Status returns per-number membership with the date each was added and last modified. The Remove option un-suppresses a number, so treat it differently from the rest.
- Add EBR Record Adds or refreshes an Existing Business Relationship or consent record for one or more numbers. EBR records establish exemptions from DNC scrubbing based on a documented relationship. Relationship type and date of last contact are required; brand, reference and email are optional.
- Scrub Email Addresses Checks email addresses against your account's Do-Not-Email suppression list, returning each email with a suppression flag, the date it was added and any reference stored with it.
- Add To Do-Not-Email List Adds or updates an email address on your account's Do-Not-Email suppression list, optionally storing a reference, and returns the resulting record with its suppression status.
- Remove From Do-Not-Email List Removes one or more email addresses from the suppression list, returning each email with the result of the removal. Like the Internal DNC removal, this moves an address back into contactable territory.
International
1- Query International Phone Global Connect lookup for a non-US number, returning its country, region, city, timezone, number type, carrier and language. Supply the international dialing code together with the national number.
Reputation Monitoring
5- Add TrustCall Numbers Adds numbers to TrustCall monitoring so their carrier spam scores are checked over time. Each number is registered under the same label, service type and legal entity.
- Remove TrustCall Numbers Removes numbers from TrustCall monitoring, returning each number with the result of the removal.
- Get TrustCall Spam Scores Retrieves the current carrier spam scores for specified monitored numbers. A rising score on an outbound number is an early warning that answer rates are about to fall.
- Get All TrustCall Spam Scores Retrieves current carrier spam scores for every monitored number in the account, up to an optional maximum record count.
- Get TrustCall Legal Entities Retrieves the legal entities associated with your account, including IDs, legal names, EIN and address. Use a legal entity ID when adding numbers to monitoring.
Account
1- Validate Authentication Validates the configured API key and optionally confirms that a specific campaign ID or project ID exists and is accessible. Use it as a connection check before a scrub run rather than discovering a bad credential halfway through a batch. Note that DNCScrub echoes the presented key back in authentication error bodies, which is why this connector does not log those bodies.
Frequently Asked Questions
What can FlowRunner do with DNC Solution?
FlowRunner agents can run Validate Authentication, Scrub Phone Numbers, and Scrub Litigator List in DNC Solution, plus 24 more actions.
Does connecting DNC Solution to FlowRunner require OAuth?
No. DNC Solution connects to FlowRunner with an API key, no OAuth flow required.
Can DNC Solution trigger a FlowRunner workflow automatically?
DNC Solution doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with DNC Solution
$100 in credits. No card required. Connect in minutes.