Integrations/Compliance / DNC

TrustedForm

In final testing

TrustedForm (by ActiveProspect) issues a certificate that documents how and when a consumer gave consent on your form. lead2inbound captures the certificate URL you attach to each lead, stores it as part of the consent evidence trail, and shows you how many of your consented leads carry one.

1 Lead in2 Dial3 Prequalify4 Route to buyer5 Track

What it does in the flow

This sits at step 1, lead in — alongside consent capture. TrustedForm, a product from ActiveProspect, generates a certificate on your webform that records how and when a consumer gave consent: the page they were on, what they saw, and when they submitted. When your form or vendor attaches that certificate URL to a lead (the consent.trustedform_cert_url field on the canonical lead shape), lead2inbound captures it and stores it durably as part of that lead's consent evidence trail, timestamped alongside the consent text version, source URL, and the rest of the consent metadata.

In the dashboard's compliance view — and in the stats compliance section — we then report what share of your consented leads carry a certificate URL (paired with a source URL). That gives you a real coverage number for the strength of your consent evidence, rather than a guess.

Current status

To keep our honesty rule intact, here is exactly what works today and what is still in testing — nothing here claims more than the code does.

Today Works now

Certificate-URL capture and durable storage on every lead, plus evidence reporting — the share of your consented leads that carry a certificate URL, surfaced in the dashboard compliance view and stats.

Coming In final testing

Automated certificate verification and retention via ActiveProspect's API — claiming and confirming each certificate directly with TrustedForm. Built and in final testing; not live yet.

To be precise about the boundary: today lead2inbound captures and stores the certificate URL and reports coverage. It does not yet call ActiveProspect to verify, claim, or retain the certificate on your behalf — that automated path is in final testing. We'd rather draw that line clearly than let you assume verification is happening when it isn't.

FAQ

What does lead2inbound do with a TrustedForm certificate today?

We capture the certificate URL you attach to each lead (the consent.trustedform_cert_url field) and store it durably as part of that lead's consent evidence trail, timestamped. In the dashboard's compliance view we report what share of your consented leads carry one.

Does lead2inbound verify or retain the certificate with ActiveProspect?

Not yet. Automated certificate verification and retention through ActiveProspect's API is in final testing. Today we capture and store the certificate URL and report coverage — we do not call ActiveProspect to claim, verify, or retain the certificate for you.

Does a missing certificate stop a lead from being dialed?

No. Certificate coverage is reported for visibility, not enforced as a hard gate. Whether a TrustedForm certificate should ever become a dial-eligibility requirement is a decision for your TCPA counsel — the measurement exists so that call can be made against real numbers.

Related integrations

Keep the consent evidence with the lead.

Attach a TrustedForm certificate URL to each lead and we'll store it and show you your coverage — part of the same compliance trail that gates every dial.

Get started