The Scenario
Your outbound campaign is scheduled to launch Thursday. It's Tuesday morning and the compliance lead just asked whether the 5,000-number prospect list in the "Campaign Q2" Google Sheet has been screened against the TPS and CTPS registers. You assumed someone else handled it. They assumed you did.
The bad version:
- Open the TPSCheck lookup tool, paste the first number, note the result, switch back to the sheet, type it in column B, repeat
- Get through 40 rows in 25 minutes, realize you have 4,960 left, and look for a bulk option that turns out to require a paid API plan you don't currently have set up
- File a request with the developer on your team to wire up a bulk API call, get told it'll take a day, miss the launch window
The campaign can't go out without this check. The fines for calling TPS-registered numbers in the UK aren't hypothetical — they're up to £500,000. That's not a risk your company is willing to absorb, and it's not a timeline that allows for a three-day developer engagement.
The Easy Way: One Prompt in SheetXAI
SheetXAI is an AI agent that lives inside your Google Sheet. It reads the sheet, understands the structure, and through its built-in TPSCheck integration it can check every number in your list and write the compliance results back without any configuration. You just ask.
For each phone number in column A of the "Campaign Q2" tab, check it against the TPS and CTPS registers using TPSCheck and write the registration status, number type, and carrier into columns B, C, and D
What You Get
- Column B: "registered" or "clear" for every row — no blanks, no silent skips
- Column C: line type — "mobile," "landline," or "VoIP" for each number
- Column D: network carrier for valid numbers (e.g., EE, O2, Vodafone, BT)
- Numbers that return an error from the API get "lookup error" in column B rather than a blank, so you can spot and re-run them
What If the Data Is Not Quite Ready
Numbers are stored with formatting characters
Some sheets store numbers as +44 (0)7700 900123 or 07700-900123 rather than the clean format TPSCheck expects. Ask SheetXAI to normalize first:
For each number in column A of the "Campaign Q2" tab, strip all spaces, dashes, and parentheses and rewrite in E.164 format into column A (overwrite), then check each one against TPSCheck and write the TPS status, number type, and carrier into columns B, C, and D
The list spans three tabs merged from different sources
If your campaign list came from separate lead gen sources, the numbers might be split across tabs:
Combine all phone numbers from columns A in the "Source 1," "Source 2," and "Source 3" tabs into the "Master" tab column A, deduplicate, then run a TPSCheck screen on every number and write the registration status, type, and carrier into columns B, C, and D
You need to flag rows for suppression, not just label them
Some campaign tools expect a suppression-ready format — a binary flag or a blank row — rather than a text label:
Check all numbers in column A of "Campaign Q2" against TPSCheck. Write "SUPPRESS" into column E for any number that is TPS-registered or invalid, and leave column E blank for numbers that are clear and valid
Complete cleanup and compliance check in one shot
In the "Raw Prospects" tab: normalize all phone numbers in column A to E.164 format, deduplicate rows where column A matches, check every unique number against TPSCheck, write 'DO NOT CALL' into column B for TPS-registered or invalid numbers and the carrier name into column C for the rest, then create a summary row in F1 showing how many numbers are clear vs. suppressed
The pattern is to ask for the cleanup and the compliance check in the same prompt — SheetXAI runs them as a single pipeline instead of two separate tasks you'd have to coordinate.
Try It
Open your prospect list in Google Sheets, then Get the 7-day free trial of SheetXAI and ask it to screen column A against the TPS register before your next campaign launch. For related workflows, see how to enrich phone numbers with carrier metadata or clean a large contact list in bulk.