TL;DR
- A Klariqo Call Record (KCR) is a signed, tamper-evident, independently timestamped record of a single call, generated on the dialer you already run.
- It bundles four things: QA on 100% of calls, a signed record (built on the open vCon standard), PII redaction, and an independent trusted timestamp.
- It's the call-event version of a TrustedForm certificate: the branded artifact a buyer can require from every vendor and check across every call.
- You verify it against standards, not our word. The signature proves the record is unaltered; an independent trusted timestamp proves when it existed.
- What it is not: a KCR does not make you compliant, and it is not a compliance certification. It is evidence. The compliance program stays yours.
A call recording tells you a call happened. It does not tell you the recording is unaltered, and it does not let anyone but you vouch for it. That gap is the difference between a file and evidence.
A Klariqo Call Record (KCR) is Klariqo's signed, tamper-evident, independently timestamped record of a single call, scored for compliance and generated on the dialer the call center already runs. Think of it as the call-event equivalent of a web-form consent certificate like TrustedForm: a standardized, checkable artifact you can require from every vendor and audit across 100% of calls.
What's in a KCR
A KCR is the object. The things below are the layers that make it trustworthy.
- QA on 100% of calls. Every call is scored against the rules you write, not a 1 to 2 percent sample. On a campaign running 10,000 calls a day, a 2% sample is 200 calls, and the one a plaintiff sues over is almost never in it. A KCR scores all 10,000. The blind spot that traditional QA leaves is the whole point of the product.
- A signed record. The audio is fingerprinted with a SHA-512 hash and the record is digitally signed, so any change to the audio or transcript breaks the signature. This is built on the open vCon standard (an IETF-track format for conversation records); Klariqo implements it, we did not invent it.
- PII redaction. Sensitive data in the transcript and audio is automatically detected and redacted, so the record can be shared without spilling personal information. Redaction is automatic detection, not a zero-leak guarantee.
- An independent trusted timestamp. Each record carries an RFC 3161 trusted timestamp from an independent authority, the same standard behind legal e-signatures. It proves the record existed at that moment and could not be backdated after a dispute started.
All of it is generated done-for-you on the dialer the call center already runs, VICIdial included. Nobody rips out their stack to produce a KCR.
A KCR vs a recording vs a QA score
The three get confused, so here they are side by side.
| Raw call recording | A QA dashboard score | Klariqo Call Record (KCR) | |
|---|---|---|---|
| Coverage | Whatever was recorded | Often 100% now | 100% of calls |
| Who holds it | You, or the vendor | Inside the QA vendor's platform | You own it |
| Tamper-evident | No, a file can be edited | The score, not the audio | Yes, breaks on any edit |
| Independently verifiable | No | Only inside that vendor's system | Yes, with an independent timestamp |
| Portable to a regulator | The file, unproven | Export a report they must trust | A signed record anyone can check |
The last two rows are what matter. Plenty of platforms now score 100% of calls, so coverage alone settles nothing. What a KCR adds is a signed record you own and can hand to a buyer or a regulator, who can then check it themselves without trusting Klariqo or logging into anyone's dashboard. A dashboard score is the vendor's word. A KCR is evidence.
How you verify a KCR
You do not take our word for it. That is the entire idea.
The signature proves it is unaltered. Every KCR is sealed with a digital signature over the call audio and transcript. Change one byte and the signature breaks. That is what makes it tamper-evident: anyone checking the record can tell whether it was touched after the fact.
An independent trusted timestamp proves when. On top of the signature, each record carries an RFC 3161 trusted timestamp from an independent authority, the same standard behind legal e-signatures, the technology under Adobe and PDF signing, eIDAS in the EU, and ESIGN and UETA in the US. It proves the record existed at that moment and could not be backdated or reconstructed after a dispute began.
What the signature and the timestamp prove is integrity and timing, that the record is unaltered and when it existed. They do not prove the conversation was lawful or that consent was valid. That distinction is deliberate, and it is where honest vendors stop.
You check a KCR by its KCR_ID, a short shareable handle that opens that call's record and its proof at verify.klariqo.com. Hand a buyer the KCR_ID and they verify the call themselves, with standards their own lawyers already recognize.
A KCR is more than the raw format
A KCR is built on the open vCon standard, but it is more than the format. It wraps that signed record in 100% QA, PII redaction, and an independent trusted timestamp, generated for you on the dialer you already run. The standard is the engine. The KCR is the finished car.
That is what makes it something you can require by name. A buyer writes one line into a vendor agreement, "every call ships a KCR," and it means something specific and checkable, the same way lead buyers require a TrustedForm certificate on every lead.
What a KCR is not
Being the compliance company, we are precise about this.
- A KCR does not make you compliant. Compliance is your program: your consent, your scripts, your calling hours. A KCR is the evidence that proves what happened on the call, so you can meet your burden of proof if you are ever challenged.
- A KCR is not a compliance certification. We do not certify anyone. We provide authentic, defensible evidence and provenance. Final legal admissibility is your counsel's determination, not ours.
- A KCR does not prove the upstream consent was valid. It proves what was said, that it is unaltered, and when. Whether the consumer validly consented is a separate question your lead source owns.
A record that oversells what it does is worthless the first time a lawyer reads it. A KCR is built to survive that reading.
FAQ
What is a Klariqo Call Record (KCR)? A branded, signed, tamper-evident record of a single call. It contains the audio's cryptographic hash, a timestamp, the transcript, a QA score, and a digital signature, and anyone can confirm it was not altered.
What's inside a KCR? Four layers: QA on 100% of calls, a signed record built on the open vCon standard, PII redaction, and an independent RFC 3161 trusted timestamp. All generated on the dialer the call center already runs.
How is a KCR different from a call recording? A recording is a file, and a file can be edited with nothing in it to prove otherwise. A KCR adds a cryptographic hash, a digital signature, and an independent trusted timestamp, so anyone can confirm the record is unaltered and when it existed.
Is a KCR the same as a vCon? No. vCon is the open standard the signed record is built on. A KCR is Klariqo's finished product: the vCon plus 100% QA, PII redaction, an independent trusted timestamp, and done-for-you setup.
How do I verify a KCR? The digital signature proves the record is unaltered: change one byte and it breaks. An independent RFC 3161 trusted timestamp, the standard behind legal e-signatures, proves when the record existed and that it could not be backdated. You check both by the KCR_ID at verify.klariqo.com.
Does a KCR make me compliant? No. A KCR is evidence, not compliance. It proves what was said on the call, that the record is unaltered, and when. Your consent, scripts, and calling practices are your program.
What is a KCR_ID? A short, shareable handle for a single KCR that opens that call's record and its proof at verify.klariqo.com. It is the piece a buyer mandates from a vendor: hand it over, and they verify the call themselves.
See one for yourself
The fastest way to understand a KCR is to make one. Upload a call, watch it become a signed, verifiable record, and check it yourself at klariqo.com/try.
By the Klariqo team. Last updated: July 10, 2026. A KCR provides authentic, audit-ready evidence and provenance; it is not legal advice or a certification of compliance.