Screening your do-not-call list at import is not enough

Every dialer on the market will tell you it screens against do-not-call lists. Almost all of them are telling the truth. The question worth asking, and the one that separates them, is a different one: at what moment does the screening happen?

Most systems screen at import. You upload a list, the system checks it against your suppression records, drops the matches, and loads the rest into the campaign. That feels thorough. It is also the moment furthest away from the call.

The gap between loading and dialling

Lists are not dialled the instant they are loaded. A campaign works through its records over days or weeks, paced by agent availability and retry rules. So a number screened clean on Monday morning might not actually ring until Thursday afternoon.

Now consider what can happen in between. Someone on that list calls your office and asks not to be contacted again. An agent marks a record do-not-call after a conversation. Your compliance team imports a fresh suppression file. Each of those events updates your records correctly, and none of them helps if the only screening happened before they occurred.

The number is still sitting in the campaign queue, already approved, waiting its turn. It rings on Thursday. The person who explicitly asked you not to call is called.

Screening at the moment of dialling

The fix is conceptually simple and worth insisting on: check again at dial time. Immediately before a number is actually dialled, the system re-checks it against current suppression records. If the number went onto a list an hour ago, or a minute ago, this is the check that catches it.

TelVox screens at import and again at the moment of dialling. It also holds do-not-call records at three levels, so the answer depends on where the request applies:

• Organisation: never call this number, from any campaign we run.
• Campaign: this number is out of scope for this specific programme.
• List: suppress within a particular list without affecting the others.

And when a number is added to any of those, queued leads are purged immediately rather than at the next import. The request takes effect on the campaign that is running right now, not the next one you load.

Screening a list is a data-hygiene task. Screening a call is a compliance control. They sound the same and they are not.

What to ask a vendor

If you are evaluating dialers, this is one of the more revealing questions you can ask, precisely because it sounds like a detail. Push past the first answer, which will almost always be yes, we screen against DNC.

1. 01At what points is a number checked? Import only, or import and dial time?
2. 02When a number is added to suppression, what happens to leads already queued?
3. 03Can suppression be scoped per campaign and per list, or only globally?
4. 04Is the check enforced by the system, or is it a report someone is expected to action?

That last one matters more than it looks. A dialer that only flags a problem has handed the work back to your team. It does that on your busiest day, when nobody has time to read the report. A control that is only as good as the attention paid to it is not really a control.

The general principle

The same reasoning applies beyond do-not-call. Calling hours should be evaluated against the customer's time zone at the moment of the call, not when the list was built. Attempt caps should be enforced when the call is claimed, not only when the queue was filled. Anywhere there is a gap between deciding and doing, the rule should be checked at the doing.

None of this is exotic engineering. It is a design choice about where the check lives. But it decides whether your system documents compliance or enforces it. Only one of those helps at four on a busy Thursday.