The short answer
DNCScrub is not something you connect. Rexa holds one platform-level key and absorbs the cost, so Do-Not-Call screening is standard rather than a paid add-on you enable. Before a number is dialled it is checked against the registry, and the vendor’s own single-letter result code is stored verbatim beside the check so an audit shows exactly why a call was blocked.
Last reviewed
DNCScrub result codes Rexa stores verbatim
| What the code means | |
|---|---|
| D | Federal Do-Not-Call list hit |
| P | Internal prohibition |
| T | TCPA class-action settlement list |
| L | State list hit |
| I | Invalid number format |
| M | Mobile-only restriction |
| B | Business number — allowed, informational |
What gets checked before a call?
Two separate lookups. The DNC check returns whether the number is on a Do-Not-Call list together with the result code above. The reassignment check returns whether the number appears to have been reassigned to a different person and, where the vendor knows, when. Both take the number in E.164 digits plus a country.
The two are separate because they answer different questions. A number can be perfectly callable and still have moved to someone who never gave you consent.
Why is the raw vendor code kept?
Because "blocked" is not an audit trail. The single letter distinguishes a federal list hit from a state list hit from your own internal prohibition, and those have different implications in a review. Rexa persists the vendor’s string exactly as returned, in both the cache and the audit log, so the provenance of a decision survives long after the call.
Storing a re-derived boolean instead would be smaller and would quietly destroy the evidence that makes the record worth keeping.
How does it interact with number-validity checking?
The screening gate short-circuits. If the DNC check already blocks the number, the validity lookup is skipped — the call is not happening, so there is nothing to learn from asking whether the number is a mobile.
The two vendors sit behind separate interfaces on purpose. Validity checking can be toggled independently, and a future vendor might cover one area without the other.
What is there to set up?
Nothing. The credential is platform-level rather than per tenant, which is what makes it possible for the platform to absorb the cost instead of asking every account to open a vendor contract before it can dial safely.
Frequently asked questions
- Do I need my own DNCScrub account?
- No, and you cannot use one. Rexa holds a single platform-level key covering every account. That is a deliberate trade: you give up direct vendor access and quota visibility, and in exchange screening is on by default rather than gated behind your own vendor contract.
- Is Do-Not-Call checking charged as an extra?
- No. The cost is absorbed at the platform level, which is the whole reason the credential is platform-level rather than per tenant. There is no add-on to enable and no per-check line item.
- What is kept for an audit?
- The vendor’s own result code, exactly as returned, together with the time the check was performed. That is stored in both the check cache and the audit log, so a later review can see which list a number was on rather than only that something blocked the call.
Scope, limitations, and sources
This is a screening aid, not legal advice, and it does not make you compliant on its own — you remain the caller of record and are responsible for the rules that apply in each region you call. Coverage is whatever DNCScrub returns for that number and country, so it is only as current as the vendor’s data, and reassignment detection in particular depends on data recency. A vendor outage is classified as retryable rather than treated as a pass or a block by the adapter; how the gate then behaves is a platform decision, not a vendor guarantee. Because the key is platform-level you cannot supply your own DNCScrub account, see its quota, or query the vendor directly through Rexa.
Sources
- Do-Not-Call screening, calling windows, consent handling and audit evidence. rexa.ai (accessed )
- The per-minute rate, what it includes, and how bring-your-own telecom is billed. rexa.ai (accessed )
Spotted something out of date or wrong? Tell us on the contact page and we will correct it and update the review date.