Common questions about UK TPS/CTPS screening.
Short answers first, expanded explanation under each. If you have a question that is not here, get in touch.
What is the TPS?
The Telephone Preference Service is the UK register of consumers who have opted out of unsolicited live marketing calls.
TPS is operated by the DMA and backed in law by the Privacy and Electronic Communications Regulations (PECR). About 28 million UK numbers are on it. Calling a TPS-registered number with an unsolicited live marketing pitch is unlawful unless the specific person has given you specific consent.
What is CTPS?
Corporate TPS is the equivalent register for corporate subscribers, covering company-owned numbers.
CTPS covers numbers belonging to companies, partnerships, public bodies and other corporate entities that have opted out. About 3 million corporate numbers are on the register. B2B teams calling direct-dial numbers at corporate prospects need to screen against CTPS, not just TPS.
Is using TPSClear legal?
Yes. Screening against TPS and CTPS before calling is a legal requirement under PECR, and the tool exists to help you do that automatically.
PECR places the obligation to screen on the calling organisation. TPSClear is a DMA-licensed list-cleaning tool that helps you meet that obligation by checking numbers in real time as they change in HubSpot. Compliance responsibility still sits with you as the caller.
How fast is screening?
Real-time. TPSClear listens for HubSpot phone-change events and writes the verdict back within seconds.
When a contact or company phone is created or modified, HubSpot fires a webhook, TPSClear normalises the number, queries TPS and CTPS, and writes the result to the record. Typical end-to-end latency is single-digit seconds. A daily backfill cron also sweeps records the webhook may have missed.
What if a number is in the wrong format?
TPSClear normalises numbers to E.164 (the international format) before screening, and flags ones it cannot parse as Unknown.
We accept the common UK shapes (07xxx, 020 xxxx xxxx, +44 7xxx, with or without spaces and brackets) and convert them to E.164 for lookup. Numbers that are obviously not UK, or that we cannot parse, are stored as Unknown so reps can investigate before dialling.
Does it work on the free HubSpot tier?
Yes. TPSClear supports HubSpot Free.
The app uses webhooks, custom properties and a workflow action, all of which work on Free. Some HubSpot features (for example workflow-based automations beyond the action itself) require paid HubSpot tiers, but the screening itself does not.
How is my data handled?
Phone numbers are processed in transit only and are not retained beyond what is needed to write the verdict back to your HubSpot record.
TPSClear stores the minimum needed to operate the service: a hashed log of which numbers were screened and when, the verdict, and basic operational telemetry. We do not sell or share contact data. TPSClear is the data processor, you remain the data controller for your HubSpot records. A formal DPA is available on request.
Do I need to install anything outside HubSpot?
No. Everything runs inside HubSpot once installed.
TPSClear is a HubSpot marketplace app. You install it from the marketplace, authorise the required scopes, configure a few options, and screening runs on every phone change. There is no on-premises component, no Chrome extension, and no separate dashboard for reps to learn.
How is this different from the existing UK TPS app on the marketplace?
The existing app screens overnight in batches and charges over £3,500 per year. TPSClear screens in real time and is free during private beta.
The incumbent runs an overnight batch and exposes a single combined status. TPSClear fires on every phone-number change so the verdict is on the record before a rep opens it, separates TPS and CTPS so you can see exactly which register a number sits on, and offers a workflow action plus a daily backfill. Pricing details are on the pricing page.
What is the data source for screening?
TPSClear is licensed under the DMA TPS list-cleaner programme and screens against the UK TPS and CTPS registers.
We hold the DMA list-cleaner data licence. The live TPSL data feed is rolling out across customer accounts during private beta. Until your account is on the live feed, verdicts use a representative UK development dataset; the switch happens automatically once the live feed is enabled for your portal.
What happens if a contact is on TPS but I have their consent?
PECR allows calls to TPS-registered numbers if you have specific prior consent from that person. TPSClear flags the listing so a rep can confirm consent before dialling.
Specific prior consent is the legal escape hatch. TPSClear does not block the call, it surfaces the listing on the HubSpot record so reps and managers can decide whether documented consent exists for that specific person. If you record consent in a HubSpot property, you can build a workflow that overrides the default behaviour using the verdict and the consent flag together.
Can I trigger screening on demand?
Yes. The Screen for TPS/CTPS workflow action lets any HubSpot workflow run a fresh screen.
Use the action in HubSpot Workflows to re-screen on a schedule, when a deal stage changes, after a form submission, or anywhere else automation makes sense. The daily backfill cron is the default safety net, the workflow action is the precision tool.
Still have questions?
We are a small team and we read every email. Tell us about your HubSpot setup and we will reply.
Contact us