Skip to main content
Every in-scope call on Klariqo produces a compliance record: a signed, independently verifiable account of the call that sits on top of the dialer you already run. This section explains what is in that record and why you can trust it. If you read one page, read the evidence chain. It walks a call from audio to verified record in one place.

​
What a record contains

1

The parties and the dialog

Who was on the call and the conversation itself: the transcript, a reference to the recording, and the SHA-512 content hash that fingerprints that recording.
2

The analysis

Signed analysis attached to the record: the quality and compliance review of the call, and its sentiment.
3

The signature

A JWS signature over the whole record, carrying Klariqo’s signing certificate, so any later change is detectable.
You can also bind selected fields from your dialer into the signed record, such as a consent reference or the disposition. See add your dialer’s fields.

​
Why you can trust it

Signed

Tamper-evident. Any edit after signing breaks the signature.

Timestamped

An independent trusted timestamp from DigiCert proves the record existed at a point in time, without seeing its contents.

Verifiable

You can check any record yourself, no trust in Klariqo required.

​
The standard underneath

Klariqo records are vCons, the IETF-track standard for a conversation record. Klariqo issues a signed call record; it does not own the standard. See what is a vCon.
A compliance record is evidence and provenance, not a legal judgment. It proves what the record contains and that it was not altered. It does not make you compliant, and you remain responsible for your scripts, consent, retention, and counsel review. See the evidence boundary.