Direct dials for B2B sales: a UK screening checklist
A phone number is contact data, not permission. Review the number type, person, jurisdiction and calling restrictions before it enters a dialling queue.
A direct dial is not automatically a mobile number
Before buying phone data, ask the supplier to define its labels. A company switchboard, an extension, a work mobile and a personal mobile are not interchangeable. For procurement, use direct dial to mean a number claimed to reach a particular person without the main switchboard, then ask what evidence supports that claim. Do not assume it means a private number you are entitled to use.
This article focuses on UK live B2B marketing calls. It is a planning checklist, not legal advice or a complete compliance assessment. Other countries, automated calls and regulated sectors can have different requirements. Sync Scala can look up phone numbers when you ask for them, and checks each one is a live line before returning it, but a live line settles none of the questions below. Use this checklist before any number, from us or anyone else, enters a dialling queue.
Start with the regulator's baseline
The ICO's live-calls guidance says that, for most unsolicited live marketing calls, a number must not be on the TPS or CTPS and the recipient must not have previously objected, unless an applicable consent exception permits the call. Claims-management and pension-related calls have stricter rules. Other regulators may also impose restrictions. Read the relevant guidance for your activity before relying on the general rule.
The ICO's Business-to-business marketing guidance also requires callers to identify themselves, display a caller number or alternative contact number, and provide contact details or a Freephone number if asked. Where personal data is involved, data-protection obligations still apply. A B2B label is not a blanket exemption. The linked regulator pages are the source for these requirements.
Make the review visible in the record
Our suggested operational approach is a review record attached to each proposed call. Keep the contact's company, claimed role, number type, country, source and collection date together. Add who reviewed the record and what evidence they used. A salesperson should not need to reconstruct this history from a screenshot in a private chat.
Keep a separate field for the latest screening outcome and when it was checked. Do not overwrite the phone source with a vague approved label. If the person has changed employers or the number type is unknown, route the record for review rather than guessing. The objective is a defensible decision trail, not a large collection of apparently complete rows.
- Identity: the intended person and their current business role.
- Number: the claimed type, country and supporting source.
- Review: the responsible owner, screening evidence and decision date.
- Disposition: approved for a defined use, held for review or suppressed.
Keep suppression separate from enrichment
An enrichment run may find a number again after someone has objected. Your workflow must not mistake rediscovery for permission. Design a separate suppression step that runs after enrichment and before a dialling queue is released. This is our implementation recommendation for avoiding that failure, not a claim that any particular supplier performs the step for you.
Decide how an objection reaches every system that needs it. For example, a caller records the request, an authorised owner checks the update and future exports consult the same controlled record. Test the process with dummy data before using it with prospects. A suppression list that only exists in one salesperson's spreadsheet is easy to bypass accidentally.
Buy evidence, not just a headline accuracy rate
Ask a prospective supplier for a sample with field definitions. Check whether a correct company number counts as a successful direct-dial result in its reporting. Ask how wrong-person numbers are handled, what the verification date means and whether a correction can be propagated. These questions expose differences that a single percentage cannot explain.
Set acceptance criteria before the trial. An illustrative rule might reject switchboards when the order is specifically for named-person numbers, hold unknown number types for review and require a documented source. Keep identity accuracy, connection rate and business relevance as separate measures. A person answering the phone does not prove you reached the right buyer.
Give the caller a reason, not a script that hides it
Prepare a short explanation of who you are and why the offer could be relevant to that business. Do not invent a prior conversation or imply that an AI-generated inference is something the recipient told you. If the role or problem is wrong, record the correction rather than pressing on with a rehearsed pitch.
The final release decision should answer three questions: do we have enough evidence about this contact, have the applicable rules been checked, and can the caller explain the business relevance plainly? If any answer is no, a new data provider is unlikely to solve the underlying problem. Fix the process before increasing the volume.