How to Maintain an Internal Do Not Call List

An internal Do Not Call list records the telephone contacts your organisation should exclude from marketing calls. Its job is to carry an objection forward into future campaigns, including when the same number arrives again through a new lead source.

Deleting a person from one spreadsheet is not a reliable substitute. The next CRM export or purchased list may contain the number again. A maintained suppression process makes the exclusion repeatable.

Internal Do Not Call lists and TPS checks are different

TPS and CTPS are external registers. Your internal list records preferences communicated to your own organisation. A number can be absent from the registers and still belong to someone who has asked you not to call.

DataSoap’s TPS, CTPS and DNC service supports register screening and internal Do Not Call management. This article focuses on maintaining the internal process, rather than repeating our wider guides to TPS checks.

1. Make objections easy to record

Give agents a clear way to record an objection during a call. It should not depend on remembering to email another team at the end of a shift. Agree which system owns the record and who deals with exceptions.

Record what the person actually asked for. An objection to marketing calls and a request to stop all direct marketing may have different scope. Do not narrow a clear general objection simply because one campaign uses the telephone.

The ICO’s guidance on respecting preferences explains the role of suppression lists and why simply deleting all evidence can allow unwanted marketing to resume.

2. Keep enough information to recognise the objection

Design the record around identification and evidence, rather than creating a second copy of the full customer database. Suggested operational fields include:

• the phone number in an agreed matching format;
• the relevant organisation or brand scope;
• the channel or marketing activity covered;
• the date the objection was received;
• the source, such as an agent interaction or customer request;
• a minimal reference to supporting evidence where needed.

These are process suggestions, not a prescribed DataSoap import layout. Keep only what is necessary for the purpose and restrict who can view or change the records.

3. Standardise numbers before matching

The same UK number may appear with a leading zero, a +44 prefix or additional spaces. Choose a consistent representation for comparison while preserving the source record where useful for audit.

Do not apply UK conversion rules blindly to an international file. Missing country context can turn a plausible-looking correction into the wrong number. Route ambiguous values for review.

Test that the forms your agents use and the files supplied by external providers follow the same matching rules. A suppression process is only as useful as its ability to recognise the number when it returns.

4. Screen imports before they enter the dialler

Use suppression as an import rule, not just a campaign filter someone must remember. Check fresh enquiries, purchased data and reactivated CRM segments against the appropriate internal list.

A practical sequence is to normalise the lookup value, apply internal objections, perform relevant register checks and then create the final audience. Keep a reason for every exclusion so someone investigating a missing contact can understand the decision.

For a dialler, consider a final eligibility check close to the call. An objection can arrive after a campaign was assembled. The exact implementation depends on the systems involved; the aim is to avoid relying on an export that becomes stale.

5. Prevent reimports from overwriting preferences

Set a clear priority rule: an ordinary lead import should not replace a recorded objection with a default “contactable” value. Treat preference changes as explicit events with evidence, rather than a side effect of refreshing customer details.

When merging duplicates, preserve the objection history. Do not let a clean-looking surviving record erase the preference stored on the record being merged.

A worked example

A business receives a request not to call a particular number. The agent records the request and the number is suppressed. A month later, a supplier delivers a lead file containing that same number in a different format.

If the import matches only literal strings, the record may slip through. If it standardises the number and checks internal suppression first, the objection is recognised and the record stays out of the calling audience.

The number’s technical validity is irrelevant to that exclusion. A live mobile result does not cancel a marketing objection.

6. Assign ownership and monitor exceptions

Name the team responsible for the list, access permissions and failed synchronisations. Decide how agents can report a suspected mismatch without editing a central record casually.

Monitor useful operational measures: objections captured, delay before exclusions reach calling systems, blocked reimports and exceptions awaiting review. Test the process when you add a new lead source, dialler or brand.

Use controlled test records to check formatting variations and integration behaviour. Do not make a real marketing call to a suppressed person to test whether the system works.

7. Review retention and changes carefully

Suppression exists to prevent contact from resuming accidentally. Avoid deleting the exclusion purely because an ordinary campaign file has reached its retention date. Equally, do not keep unrelated personal details indefinitely under the label of suppression.

If someone later changes their preference, follow a documented process that captures the scope and evidence of that change. Resolve uncertainty before restoring marketing eligibility.

Frequently asked questions

Is a Do Not Call list the same as blocking a phone on an agent’s handset?

No. A central suppression record is intended to apply across the relevant campaigns and systems. A local block may not affect other agents or future imports.

Does checking TPS replace internal suppression?

No. The external register and an objection made directly to your organisation are separate checks. You need a process that considers both where relevant.

Can we keep an exclusion after a marketing objection?

The ICO explains that keeping enough information to honour an objection is distinct from continuing to use that information for direct marketing. Apply appropriate access and retention controls.

Make the exclusion survive the next campaign

Define the matching rules, connect every import route and give someone responsibility for exceptions. Explore DataSoap’s suppression and register checks or talk to the team about your calling workflow.