Skip to main content
A call happens today. Months later, someone asks three questions about it: what was actually said, can you prove the record was not edited, and can an independent party confirm the record existed. Klariqo produces a record that answers all three. This page walks the chain end to end. It runs the same way for an AI call and for a human agent call, on the dialer you already run.

​
The chain, step by step

1

The call is captured

The recording and transcript of the call are captured, whether the call was handled by a Klariqo AI agent or by a human agent on your dialer.
2

The recording is fingerprinted

A SHA-512 content hash is computed over the recording. It is a fingerprint: change a single byte of the audio and the hash changes completely. This is what later proves the audio was not swapped or edited.
3

A vCon is built

The call is assembled into a vCon, the IETF-track standard container for a conversation record (the parties, the dialog, and analysis). See what is a vCon.
4

The record is signed

The vCon is signed with a JWS signature (RS256), carrying Klariqo’s signing certificate. The signature is tamper-evident: any later edit to the record breaks it. See signed vCons.
5

QA and sentiment are attached

The call’s quality and compliance review (pass, needs review, or fail) and its sentiment are attached as signed analysis blocks inside the record. See call QA.
6

A third party witnesses it

An independent witness (JLINC) records the record’s fingerprint plus minimal audit identifiers. It does not receive the transcript, the audio, phone numbers, or the QA content. This is an outside attestation that this exact record existed at that point in time. See third-party witnessing.
7

Anyone can verify it

The signed record can be checked in the public verifier, which reports whether it is valid, altered, unsigned, or not issued by Klariqo. You do not have to take our word for it. See verify a vCon.
8

The record is delivered to you

When the record is final, a signed webhook pushes a pointer to your system, and you fetch the signed vCon from a short-lived link. See compliance export webhooks.

​
What this gives you

An audit-ready, tamper-evident, independently verifiable record of every in-scope call, produced automatically and sitting on top of the dialer you already run. When an auditor, a carrier, or a client asks “what happened on this call,” you hand them a record that proves its own integrity.
This is evidence and provenance, not a legal judgment. A signed, witnessed record proves what the record contains and that it was not altered after signing. It does not by itself prove that a call legally occurred, and it does not make you compliant. You remain responsible for your scripts, your consent practices, your retention policy, and review by your own counsel. See the evidence boundary.

​
See the whole record

Every claim above maps to a part of the record you can inspect and verify yourself.

What is a vCon

The standard container that holds the call record.

Signed vCons

How the signature makes the record tamper-evident.

Verify a vCon

Check any record yourself in the public verifier.

Third-party witnessing

What the independent witness sees, and what it never sees.