Three things to have in place.

Open the TPSClear listing in the HubSpot App Marketplace and click Install. The Install on HubSpot button on tpsclear.co.uk goes to the same place.

HubSpot shows which account you are signed into and what TPSClear will be able to access. If you have more than one HubSpot account, pick the one to connect first.

HubSpot lists nine required permissions and one optional one. They cover contact and company records, their property settings, and the account itself. What TPSClear uses each for:

Leave View details about contact lists ticked, tick the terms box, then click Connect app. Connect app is greyed out until the terms box is ticked.

Step 2 of 2 confirms the install. In the background TPSClear has created its fields on contacts and companies. Explore app features opens the app's page in HubSpot. Customize app cards jumps straight to adding the card, covered on the next page.

After the install you land on TPSClear's page inside HubSpot. Four tabs: Overview shows who installed the app and when, Feature discovery links to this guide, and Settings is where the rest of the setup happens. You can come back here any time from Settings, Integrations, Connected Apps.

Open the Settings tab, then App cards. The TPSClear card starts as Ready for setup, added to no views. Click Manage locations.

On the Contacts tab, under Record Page, tick TPSClear in the Right sidebar column for the Default view. The sidebar stays in view whichever tab is open, so the verdict sits beside the Call button while you log the call. Switch to the Companies tab and tick the same Record Page row. Then Save. The Middle column works too if you prefer the card on the Catch-up tab. The card only appears on the views you tick, so include any custom record view your team uses. Customer Success and Account Preview can stay unticked.

HubSpot confirms with Your changes were saved, and the card reads added to 1 view on contacts and on companies. It now sits in the right sidebar of every contact and company record. If it lands below other sidebar cards, drag it to the top with Customize on any record. Manage locations again later to add the card to more views or remove it.

Created on contacts and on companies at install, for the Phone Number property. Each further phone property you tick under Which properties to screen gets its own pair, named after the property: Mobile Phone TPS Result, Mobile Phone TPS Last Checked, and so on. Find them under Settings cog, Properties, search for tps.

TPSClear writes both fields at every screening, and the help text on each field says so. Editing them by hand does not screen a number. A Last Checked date moved back makes the card show the result as expired; one moved forward delays the nightly re-check. The real check times stay in TPSClear's own log, which the compliance report reads. On HubSpot Enterprise, a Super Admin can stop other users editing them: Settings cog, Properties, open the field, Manage access. TPSClear can still write them.

Phone TPS Result is a dropdown with seven values. The card on the record shows the same answer as a badge.

The first thing on the settings page after a new install. The five checks are real checks against the live registers, on your real records, and count down as you use them. See plans opens the pricing page. Card payment switches screening on the same minute, and the box disappears once a plan is active.

The Account tab opens first. Screening is on turns all of TPSClear on or off, and Usage shows the checks used in the current allowance period and when the allowance resets.

Below them: Allow overage lets checks carry on past the allowance at £15 per 1,000. It is off on a new install, so checks pause at the allowance until it resets. On Standard and Scale the allowance is the fair-use ceiling (1,000,000 or 3,000,000 checks every 28 days). Help links to the setup guide, how TPSClear works and support.

The two checkboxes save on click.

Phone Number on contacts and on companies is on from install. Tick Mobile Phone Number or any other phone property to screen it too. Ticking a property creates its own TPS Result and TPS Last Checked fields. Unticking stops future checks and keeps the answers already written.

Screen numbers as they are added or changed is on from install and saves on click. A check runs the moment a ticked phone property is filled or edited, on new, imported and existing records. The segments and rules of the nightly re-check do not apply here. It covers HubSpot's own phone fields and the common custom names; a field the picker marks as having no instant check yet is still screened by the nightly re-check, Re-screen now, the workflow action and Screen a segment, and we add the name on request.

Open a contact or company and press Re-screen now on the TPSClear card. The answer is written to the record straight away. The same box has the App cards link for putting the card on your record views.

Choose a segment in the Segment dropdown and click Screen segment. Any contact segment appears here, static or active. Numbers checked within the last 27 days are skipped instead of spending a check.

Large segments take a few minutes. The button reads Screening..., a Pause button appears next to it, and the count updates as it goes. Pause stops the scan where it is; Screen segment again carries on from there. If you leave the page first, TPSClear carries on in the background and the result shows here.

The result line gives the contacts in the segment, the numbers checked and what came back (on a register, clean, not a valid UK number, on your suppression list), the contacts skipped (no number, or checked in the last 27 days) and the records updated. The per-record answers are on each contact's TPS Result fields and card.

Re-check numbers every night is off until you tick it. Once a night it re-checks numbers whose last check was 27 or more days ago. A number checked more recently is left alone. The law gives a new TPS or CTPS registration 28 days before it applies to your calls (PECR regulation 21(3)), so each number is re-checked inside that window, with a day allowed for the register's daily update. On a large database the first night uses many checks. With it off, older numbers are checked from the Real-time screening tab or by a workflow.

The checkbox saves on click. The re-check runs each morning, shortly after the DMA publishes the updated register, usually around 05:45 UK time. Re-check now in step 6 runs it straight away.

Only re-check contacts in these segments limits the nightly re-check to the segments you tick (segments are what HubSpot now calls lists). Every ticked segment is re-checked each night. Find a segment searches by name.

Segments do not limit the real-time check. HubSpot adds a new contact to a segment a few seconds after its number arrives, so the real-time check ignores segments.

The nightly re-check already skips numbers checked in the last 27 days, so a segment such as TPS checked more than 26 days ago adds nothing.

These rules apply to the nightly re-check only. A record is re-checked only if every rule allows it. Real-time screening ignores them.

Untick Re-check contacts nightly or Re-check companies nightly to leave that record type out of the re-check.

Filter contacts by a property value skips, or keeps to, records matching a value: pick a Property, a Rule of Skip records that match or Screen only records that match, and the Values to match. A Consent property set to Yes is the usual case. A record with nothing in the property does not match. Companies have the same filter.

Non-UK and invalid numbers do not use a check, so they need no filter. Nothing here or in the segments takes effect until Save rules and segments.

The Workflows box explains the Screen for TPS/CTPS workflow action and gives two common workflows: check before calling, and recheck every 27 days. Use the answer anywhere, later in this guide, shows the first one step by step.

Tick Set 'Do not call' on contacts and companies from screening results. Then pick a property to write for contacts and for companies. HubSpot has no built-in Do not call property, so choose the Do not call property TPSClear creates, or an existing Yes/No property of your own. Saves on click.

A TPS-listed, CTPS-listed or TPS and CTPS-listed result sets it to true. A Clean result sets it to false. Not a valid UK number and Unknown leave it alone. A suppressed number sets it to true, and a number with consent recorded sets it to false. Applies to every check, automatic or not.

A failed check is marked Unknown (check failed), emailed, and checked again. One email goes on the first failure of the day, then a summary the next morning if there were more. Alerts go to the person who installed the app until you add recipients: type an address and click Add. Remove takes one off. Up to ten.

Every check is logged: time, number, result and what triggered it. The log is kept for 24 months. Choose a Period, then click Download report. Current period and Previous period follow your allowance periods. The others are Last 28 days, Last 90 days and Custom dates, which takes a From and a To date. The report downloads as one Excel workbook, for your PECR records. The link works for 30 minutes, so after that download the report again from settings.

The Summary sheet gives the figures for the period: checks, records and numbers screened, numbers by type (mobile, landline, non-geographic, freephone and service, other, and Ofcom drama ranges, taken from the UK numbering plan), TPS and CTPS results separately, how many checks found a different status from the record's previous check, numbers held on more than one record, consent exceptions and the suppression list. The Screened sheet lists every check, with what started it, for a batch its run id, and the status, time and number from the previous check of the same field, even when that check was before the period. The duplicate numbers, your consent exceptions and your suppression list have their own sheets when there are any. When someone asks how you knew a number was safe to call on a given day, the Screened sheet answers per number.

Numbers on the suppression list always come back as Do not call, whatever the TPS says. The Suppression list section shows how many numbers are on it and the newest 100, with the note, who added each one and when. Remove takes a number off. To add numbers, paste them into Add numbers, one per line, with an optional note. UK numbers in any common format are accepted, and any line that is not a valid number is listed back to you. Suppress number on the record card adds to the same list.

Register data is supplied through TPSClear's licensed data partners. The Data source section, on the API tab, tells you which feed your account is on. There is nothing to set.

Name the key, pick an Environment, click Create key. Test keys screen against a development list for free. Live keys screen the real registers and count towards the same allowance as CRM checks.

The key is shown once, in the Copy your new key now panel, until you leave the page or switch tab. TPSClear stores only a hash of it, so a lost key is replaced, never recovered. The row underneath shows the name, environment, last four characters and when it was last used. Revoke ends it.

HubSpot shows the card only on the record views an admin has ticked. If a contact or company has no TPSClear card, go back to Manage locations and tick the view your team uses, including any custom record view.

A record that has not been checked reads Not yet screened. Properties with no number are listed on one line under No number and cost nothing.

Click Re-screen now to check the record on the spot, whatever the automatic settings say. The button reads Re-screening... while it runs, a second or two. Numbers already checked in the last 27 days come back from the cache without spending a check.

The badge is the answer and the line under it is when. The same result is written to the record's Phone TPS Result and Phone TPS Last Checked fields, so lists, workflows and reports see it too. From here on, a number typed, imported or added by another app is checked within seconds.

A number on the Telephone Preference Service. The card says so in red and Phone TPS Result reads TPS-listed. A Corporate TPS listing reads CTPS-listed the same way, and a number on both reads TPS and CTPS-listed on portals installed from October 2026. The check date stays visible so you know how fresh the answer is. Calling a TPS-listed number without consent is a breach of PECR; Record consent is the only thing that changes this badge.

Companies get the same card on the company record, with the company's Phone Number and any other company phone property you screen. Company numbers are checked against both registers, so a CTPS listing shows here. Screen companies automatically in the settings decides whether the real-time check and the nightly re-check cover them.

Someone on the TPS can still be called if they have asked for your calls: a signed order, a ticked box, a contract. Open Actions and choose Record consent, type where the evidence lives in Consent evidence reference, then Confirm consent. The reference is required. Put something a colleague could find later.

The number keeps its register result and gains a Consent recorded badge with the evidence line. On a TPS-listed, CTPS-listed or TPS and CTPS-listed number the Phone TPS Result field becomes OK to call (consent); a Clean number stays Clean. Consent is per number, not per record, so a changed number is checked afresh. Remove takes it off again. TPSClear records what you tell it and when; the consent itself is yours to stand behind.

An opt-out made straight to you beats any register. Open Actions and choose Suppress number, add an optional Note for your colleagues (who asked, and when), then Confirm suppress.

The card shows Do not call. Opted out. with the note. The Phone TPS Result field reads Do not call (opt-out), and with the Do not call property switched on, that checkbox is set too. A suppressed number stays suppressed on every record that carries it. Re-screening does not undo it; only Remove does. The number also goes on the suppression list on the settings page.

A saved contact view filtered to Phone TPS Result is any of TPS-listed, CTPS-listed or TPS and CTPS-listed shows everyone you must not dial. Turn it round for the call list: Phone TPS Result is any of Clean or OK to call (consent). The same filter works in list membership, sequence enrolment rules and reports.

In any contact or company workflow, add the Screen for TPS/CTPS action before the call task. It checks every ticked phone property and writes each one's TPS Result and TPS Last Checked, plus Do not call when that setting is on. Then add an If/then branch on Do not call, which covers every number on the record. Without the Do not call setting, branch on each TPS Result and create the task only when all are Clean. The action runs whether or not automatic screening is on. Needs HubSpot Professional or Enterprise.

Settings cog, Integrations, Connected Apps. On the TPSClear row, open Actions, then Uninstall. The same menu has Go to settings, Contact support and Documentation. Change owner moves the install, and the failure alerts, to another user.

Type uninstall to confirm. The Phone TPS Result and Phone TPS Last Checked fields, and every value in them, stay on your records. Delete the fields by hand under Properties if you want them gone. Reinstalling later picks up the same fields.

Each has a one-step fix on the settings page or the record.

Anything else: support@tpsclear.co.uk with your portal ID. Replies within one working day.