TPS/CTPS screening for Dynamics 365 Sales and Customer Engagement.

TPSClear for Dynamics 365 is in build as a Microsoft solution package, with an AppSource submission planned once the UK pilot orgs have signed off. This page covers what the integration is designed to do and how it slots into a Dataverse-backed Dynamics estate. Nothing below is on AppSource yet.

Where the verdict surfaces

The solution package writes a TPS/CTPS status field to the three records UK sales teams actually work with in Sales Hub:

• Lead. Status surfaces on the form, the Sales Accelerator queue, and the LinkedIn Sales Navigator card.
• Contact. Status carries across qualification and shows on the contact form and on associated views.
• Account. Switchboard and direct-dial fields on accounts get their own status alongside the per-contact verdicts.

Custom columns we provision

The solution adds the following columns under the tpsclear_ publisher prefix:

• tpsclear_tpsstatus
• tpsclear_ctpsstatus
• tpsclear_combinedstatus (option set: Clean, TPS, CTPS, Both, Unscreened)
• tpsclear_lastchecked (datetime, UTC)

Power Automate is the screening engine

The re-screen pattern is a Power Automate cloud flow shipped with the solution. It is triggered by a Dataverse row update, filters on the relevant phone columns, calls the TPSClear API through a custom connector we publish, and writes the verdict back to the row. Admins who want to customise the flow (different phone columns, different cadence) can clone it and edit it without losing the connector configuration.

For orgs that prefer plug-ins over Power Automate, a synchronous plug-in registered on the relevant message is on the roadmap. It is not in the first release; the Power Automate path is the supported one.

Customer Service module compatibility

Customer Service Hub uses the same Contact and Account tables as Sales Hub, so the verdict appears wherever those tables are surfaced, including in the agent experience and in case records. The package does not modify Case directly; if a case has a phone number on it that you want screened, you can copy the verdict via a column-level synchronisation rule.

D365 connector approach

We are publishing a certified custom connector for the TPSClear API. That gives you:

• A single registered connection that admins manage centrally, rather than per-flow API keys scattered across the environment.
• Throttling and retry handled by the connector platform, which matters when you backfill against a 200,000-row environment.
• DLP-compatible classification, so you can include or exclude the connector from data-loss-prevention policies the same way you do with Microsoft connectors.

Common UK use cases

Dynamics 365 has a stronger footprint in regulated UK sectors than the other CRMs on this list, and that shapes how the integration is being designed.

• Financial services compliance. Banks and insurers using D365 for outbound retention or renewals need a TPS verdict that auditors can trust. The custom connector logs every screen with a timestamp and a reference number, which becomes part of the treatment-record evidence trail. We talk about why this matters in ICO PECR fines and cases.
• Public sector. Local authorities and NHS trusts running D365 Customer Service for citizen contact need to make sure campaign or survey calls do not hit CTPS-registered corporate lines at suppliers and partners. The verdict on the Account makes that straightforward.
• Field service and retail. Where outbound is mostly appointment confirmation rather than marketing, screening still matters because regulator complaints often start with a confused recipient who reports the call regardless of intent.

What you can do today

• Join the waitlist for early access to the solution package.
• Build the integration today via Power Automate against the public TPSClear API. The flow we will ship is the same flow you would build by hand; we are just packaging it.