Consent and TCPA certification for VICIdial

When teams ask us for this

You need the certificate on the record you dialled

A certificate in a spreadsheet proves nothing about the call you actually made. On the lead, it sits with the number, the disposition and the recording.

You buy from sources that certify consent

TrustedForm and Jornaya certificates arrive with the lead. Mapped into a custom field, they stay with it for as long as the record does.

You are preparing for an audit or a complaint

The question is always "show me consent for this number on this date". That is a lookup on the lead, not an archaeology project across three systems.

You already run per-trunk TCPA scrubbing

This is the other half. Scrubbing decides whether you may dial; the certificate evidences why you were entitled to.

Consent platforms certify that a lead consented, and issue a certificate proving it. The certificate is only worth having if it stays attached to the record you dialled. Point your consent platform's delivery at your VICIfast box and the certificate URL lands on the VICIdial lead itself - not in a spreadsheet somebody has to reconcile later.

Integrations on demand. There is no connector to switch on. Our team wires it as a scoped piece of work, quoted per setup.

Platforms in this category

ActiveProspect (TrustedForm, LeadConduit) · Jornaya (LeadiD)

Between them they are most of the consent-certification market. This is also the category nobody else in VICIdial hosting writes about, which is odd, because it is the one with a regulator attached.

How it works

ActiveProspect's LeadConduit is the usual path. A delivery step takes a customisable endpoint URL, credentials and field mappings, and their own documentation names the destinations as "a CRM, dialer, and data warehouse" - the dialer is explicitly in scope.

When a certified lead reaches LeadConduit, it captures the TrustedForm certificate URL with the lead automatically. You map that field into a destination field, the same way you map a phone number.

On the VICIdial side, non_agent_api.php takes custom_fields=Y, which lets per-campaign custom fields be written in the same call as the standard ones. So the certificate URL arrives with the lead rather than after it.

The result: an agent dials a number, and the consent record for that number is on the same row.

Setup, in order

Create the custom field on the campaign that will hold the certificate URL.
Confirm the field's length. Read the gotcha below before you do anything else.
Add the delivery step in LeadConduit, pointed at your box.
Map the certificate URL field to your custom field, alongside the standard lead fields.
Send one certified test lead and open the stored URL. It must resolve.

Gotchas

This is the one that will bite you. VICIdial's API truncates values at 255 characters and strips apostrophes, double quotes and ampersands before writing. A TrustedForm certificate URL is long. If it is truncated, what you have stored is not a certificate - it is a string that looks like one and resolves to nothing.

A truncated consent record is worse than no consent record, because it will pass a glance and fail an audit. Verify the round trip on a real certificate before you trust the field, and if it does not survive, store an identifier and keep the full URL where it will fit.

Capturing consent is not the same as honouring it. The certificate proves the lead consented at a moment in time. It does not scrub against DNC, it does not enforce your calling windows, and it does not know about a later revocation. Keep dnc_check on regardless.

Jornaya works the same way but is not identical. The certificate format and the retrieval path differ. Do not assume a field mapping built for TrustedForm transfers.

Questions we get asked

Does this make me TCPA compliant?

No, and nobody can sell you that. It puts the consent record where your dialled numbers are, which is one part of a defensible position. DNC scrubbing, calling windows, revocation handling and your retention policy are the rest.

Can I retrieve the certificate later from the lead?

Yes, provided the URL survived intact. VICIdial truncates field values at 255 characters, and a truncated certificate URL resolves to nothing while still looking like proof - so verify the round trip before you rely on it.

What if my consent platform is not ActiveProspect or Jornaya?

The shape is the same: a delivery step, a field mapping, a URL on the lead. Tell us the platform and we will look at it.

Do you store or process the consent data?

No. It lands on your server, in your database, on your lead record. We never hold a copy.

What does it cost to set up?

Scoped work, quoted per setup, and usually the quickest of these to wire because it is one field mapped carefully rather than a routing change.