Which registers does Lyro check a number against?

The UK Telephone Preference Service (TPS) and its corporate equivalent, the Corporate TPS (CTPS) - the two do-not-call registers a UK marketing call has to respect, both checked through the tpsapi.com API behind this toolkit.

Can Lyro check a batch of numbers at once, or only one at a time?

Both. The connected action accepts one phone number or a batch of them in a single check, so a list of captured leads can be screened together instead of one at a time.

What happens when a number comes back flagged as opted out?

Lyro flags it as it enters the pipeline. The action reports the TPS/CTPS status back into the conversation - what happens next, such as excluding the number from a dialler, is up to the workflow it feeds into.

Does this integration work for phone numbers outside the UK?

No. TPSCheck verifies against the UK's TPS and CTPS registers specifically, so it's built for UK marketing calls rather than international do-not-call compliance.

Tpscheck MCP integration

Checks one number or a batch against the UK TPS and CTPS registers, flagging do-not-call opt-outs at the point a lead is captured.

Connect Tpscheck See all integrations

1actions available

What your agent can do with Tpscheck

Every action runs live through MCP. Nothing to build, nothing to maintain.

Checks if one or more UK phone numbers are registered on the Telephone Preference Service (TPS) and/or Corporate Telephone Preference Service (CTPS) lists using the tpsapi.com API.

See all 1 actions

How businesses use Tpscheck + Lyro

Each card is one request a support team gets, and the Tpscheck actions Lyro runs to close it.

Flag a number the moment it's captured
When a UK phone number is captured in a conversation, Lyro checks it against the TPS and CTPS registers before it ever reaches a dialler.
Check Phone Number (TPS/CTPS)Opt-Out Flagging
Screen a batch of leads before a campaign
Ahead of a calling campaign, Lyro checks a batch of captured numbers against both UK registers in one pass instead of one at a time.
Check Phone Number (TPS/CTPS)Batch Number Check
Confirm one number is clear before a callback
Before a callback gets scheduled, Lyro checks that one number against the TPS and CTPS lists so the call itself stays compliant.
Check Phone Number (TPS/CTPS)Opt-Out Flagging
Re-check a number before it re-enters a queue
Before an aging lead goes back into a call queue, Lyro checks the number again against the TPS and CTPS registers in case its opt-out status has changed.
Check Phone Number (TPS/CTPS)Opt-Out Flagging

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Tpscheck actions it has and picks the ones a request needs.

01
Connect Tpscheck
Authorize the Tpscheck account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Tpscheck actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Tpscheck · Lyro

Everything else about Tpscheck

Setup, permissions, and the limits of what Lyro can do inside Tpscheck.

The UK Telephone Preference Service (TPS) and its corporate equivalent, the Corporate TPS (CTPS) - the two do-not-call registers a UK marketing call has to respect, both checked through the tpsapi.com API behind this toolkit.

Every action available in Tpscheck

All 1 actions your agent can call on Tpscheck, straight from the live MCP connection.

Check phone number (tps/ctps)
Checks if one or more UK phone numbers are registered on the Telephone Preference Service (TPS) and/or Corporate Telephone Preference Service (CTPS) lists using the tpsapi.com API.