Skip to main content
Third-party witnessing adds an outside attestation to a compliance record. Klariqo signs the vCon, then an independent witness records that the record existed. The witness is JLINC. It records the record’s fingerprint plus minimal audit identifiers. It does not receive the transcript, audio, phone numbers, or QA content.

​
What the witness records

1

The record is finalized

A call covered by an active scorecard is assembled into a vCon with its dialog, analysis, and recording fingerprint.
2

Klariqo signs the record

The vCon is signed with a JWS signature (RS256). Any later change to the signed record breaks verification.
3

The witness records the fingerprint

JLINC records the record’s fingerprint plus minimal audit identifiers. This creates an independent attestation that this exact record existed at that point in time.
4

The content stays private

The witness does not receive the transcript, the audio, phone numbers, or the QA content.

​
What witnessing proves

Witnessing helps answer a narrow but important question: did this exact record exist outside Klariqo’s own system at a point in time. It does not replace the signature. The signature shows the record was signed by Klariqo’s key and was not altered after signing. The witness adds an independent record of the fingerprint.

Signed vCons

Understand what the Klariqo signature proves.

Verify a vCon

Check whether a signed record is valid or has been altered.

​
What witnessing does not prove

Third-party witnessing is evidence and provenance, not a legal judgment. It does not prove consent, approve a script, decide a dispute, or make you compliant. You still own your scripts, consent practices, retention policy, and counsel review. The witness helps show that a specific signed record existed, without exposing the call content to the witness.