TPSClear for Capsule

TPS/CTPS screening for the UK-built CRM.

TPSClear for Capsule integrates via Capsule's API. Verdict on People and Organisations as custom fields. Webhook re-screens on update. UK-grown CRM, UK-grown compliance product.

Status: Building now. Join the waitlist for early access.

TPSClear for Capsule is in build, integrating via Capsule's public API. Capsule is a UK-built CRM with a loyal UK SME following, and TPSClear is a UK-built compliance product built by another UK founder, so this integration matters more to us than the size of the installed base might suggest.

Honest status: not yet a packaged install. The integration runs against the Capsule API for waitlist customers using a personal access token, and we are piloting it before turning it into a one-click install.

People and Organisations

Capsule's data model is People + Organisations + Cases + Opportunities. Phone numbers live on People (multiple, with labels) and on Organisations. TPSClear screens both:

  • People. Every labelled phone value (Work, Mobile, Home, Direct, plus custom labels) gets a verdict, with the rolled-up status mirrored to the Person record so it shows on list filters and tag automations.
  • Organisations. The organisation phone (typically a switchboard or main number) gets a verdict in its own field.

Custom fields per phone field

Capsule's custom-fields system is straightforward, and the integration maps to it directly. On install we provision:

  • TPSClear status (single-choice: Clean, TPS, CTPS, Both, Unscreened) on People and Organisations.
  • Per-phone status custom fields for each phone label you tell us to screen. Capsule allows a flexible label set per record, so the integration discovers the labels in use across your account on first run and provisions matching fields.
  • Last screened (date / time).

Webhook re-screen on update

Capsule supports webhooks (currently called "Webhooks" in the developer settings) on party updates. The integration subscribes to party.updated and filters server-side to events where a phone field changed, then screens and writes back the verdict within a few seconds.

Capsule's API rate limits are generous for the SME use case, but we still rate-limit ourselves on backfill so a one-time CSV import of thirty thousand contacts does not eat your daily allowance.

UK-built CRM, UK-built compliance

Capsule is one of the few CRMs on this list that is genuinely UK-grown. It started in Manchester, it is still run from there, and its customer base skews towards UK SMEs that consciously chose a homegrown product over a US giant. TPS compliance is a UK-specific regulatory regime, and the existing tools that purport to address it on other CRMs are mostly built by US-headquartered firms that learned about the DMA two financial years ago.

TPSClear is operated by Voll Studios Ltd, a UK company, holds the DMA TPS licence directly, and is built by a UK founder who lives with PECR rather than reading about it on Wikipedia. If you are a Capsule customer because of where the product is from, the same logic applies here.

Screenshot: Person record in Capsule with TPSClear custom fields populated and a tag applied for follow-up review.

Tags and lists

Because the verdict is a normal custom field, you can use it anywhere Capsule supports filtering: list views, saved filters, tag rules, and the Lists feature. A common pattern we see is a saved list called "Outbound-eligible" that filters to TPSClear status = Clean, used as the starting point for any outbound sequence.

What you can do today