# Klariqo

## Docs

- [Klariqo: the compliance layer for call centers](https://docs.klariqo.com/index.md): Klariqo is the compliance layer for call centers: it turns calls on the dialer you already run into signed, independently verifiable compliance records.
- [How Klariqo works](https://docs.klariqo.com/start-here/how-klariqo-works.md): How Klariqo sits on top of your existing dialer to review calls for quality and compliance and turn each call into a signed, independently verifiable record.
- [Trust and honesty boundaries](https://docs.klariqo.com/start-here/trust-and-honesty.md): What Klariqo proves, what it does not, and where your responsibility sits: evidence and provenance of a call, not legal compliance, consent, or approval.
- [Glossary](https://docs.klariqo.com/start-here/glossary.md): Key Klariqo terms defined in one place: vCon, compliance record, content hash, JWS signature, verifier, trusted timestamp, scorecard, QA result, and more.
- [Compliance records](https://docs.klariqo.com/compliance-records/overview.md): What a Klariqo compliance record is, what it contains, and why the signed, timestamped, independently verifiable record is trustworthy without trusting us.
- [The evidence chain](https://docs.klariqo.com/compliance-records/evidence-chain.md): How a phone call becomes a Klariqo compliance record step by step: recording, content hash, transcript, QA analysis, JWS signature, and a trusted timestamp.
- [What is a vCon](https://docs.klariqo.com/compliance-records/what-is-a-vcon.md): How the IETF vCon conversation-record format turns a phone call into a structured, signed compliance record with parties, dialog, analysis, and attachments.
- [Signed vCons](https://docs.klariqo.com/compliance-records/signed-vcons.md): How a JWS RS256 signature over a Klariqo vCon makes the record tamper-evident, what integrity and self-asserted origin prove, and what they do not prove.
- [Verify a vCon](https://docs.klariqo.com/compliance-records/verify-a-vcon.md): Verify any Klariqo compliance record yourself in seconds: check the JWS signature, content hash, and trusted timestamp, right in your browser.
- [Verify a record's trusted timestamp](https://docs.klariqo.com/compliance-records/verify-the-timestamp.md): Confirm a Klariqo compliance record existed at a point in time, checked against DigiCert, a global trust authority Klariqo does not control. No account, no login.
- [The evidence boundary](https://docs.klariqo.com/compliance-records/evidence-boundary.md): What a Klariqo compliance record can prove and what it cannot: evidence and provenance of a call, not a legal compliance judgment or consent decision.
- [Call QA](https://docs.klariqo.com/call-qa/overview.md): How Klariqo reviews every in-scope call for quality and compliance against your own scorecard, on AI voice calls and human-agent VICIdial calls alike.
- [Scorecards](https://docs.klariqo.com/call-qa/scorecards.md): How Klariqo scorecards define the required elements and prohibited claims each call is reviewed against, with critical checks that gate compliance status.
- [QA results](https://docs.klariqo.com/call-qa/qa-results.md): How to read a Klariqo QA result: call status, overall score from 0 to 100, compliance status, and what unscored calls like voicemail mean for reporting.
- [AI-call QA](https://docs.klariqo.com/call-qa/ai-call-qa.md): How Klariqo reviews each AI voice call against your active scorecard after the call ends, and attaches the QA result to the signed compliance record.
- [Human-agent QA](https://docs.klariqo.com/call-qa/human-agent-qa.md): How Klariqo reviews human-agent VICIdial calls from the recording against the same scorecard, and attaches QA results to the signed compliance record.
- [Dialer integrations](https://docs.klariqo.com/dialer-integrations/overview.md): How Klariqo sits on top of the dialer you already run, starting with VICIdial for compliance and QA, plus optional voice AI setups for VICIdial and Twilio.
- [Connect VICIdial](https://docs.klariqo.com/dialer-integrations/connect-vicidial.md): Connect Klariqo to your VICIdial for compliance review and call QA using recording access only, with no SIP setup, agent changes, or dialer downtime.
- [Add VICIdial fields to your records](https://docs.klariqo.com/dialer-integrations/field-enrichment.md): Choose which of your VICIdial lead fields bind into each signed compliance record, such as a consent reference, disposition, or lead source, with honest provenance on every field.
- [Connect VICIdial for voice AI](https://docs.klariqo.com/dialer-integrations/connect-vicidial-voice.md): Run Klariqo's AI voice agent on your VICIdial as a remote SIP agent: a heavier customer-side setup your VICIdial administrator configures end to end.
- [Voice AI connection troubleshooting](https://docs.klariqo.com/dialer-integrations/troubleshooting.md): Confirm Klariqo's voice AI is registered on your VICIdial and fix common SIP connection issues: registration failures, one-way audio, and codec mismatches.
- [Twilio (bring your own)](https://docs.klariqo.com/dialer-integrations/twilio.md): Bring your own Twilio number to Klariqo's voice AI by pointing the number's voice webhook at a Klariqo endpoint, for inbound and simpler outbound setups.
- [Compliance export webhooks](https://docs.klariqo.com/compliance-export-webhooks/overview.md): Push every finalized Klariqo compliance record to your own system with a signed webhook the moment it is ready, and fetch the signed vCon from the link.
- [Set up an endpoint](https://docs.klariqo.com/compliance-export-webhooks/set-up-an-endpoint.md): Register a webhook endpoint in the Klariqo dashboard, receive your signing secret, and pass the verification challenge before real records are delivered.
- [Verify webhook signatures](https://docs.klariqo.com/compliance-export-webhooks/verify-signatures.md): How to verify a Klariqo compliance export webhook using the Standard Webhooks scheme and your endpoint secret before you trust or store the delivery.
- [Compliance record envelope](https://docs.klariqo.com/compliance-export-webhooks/record-envelope.md): The shape of the compliance_record.ready event Klariqo sends when a signed record is ready: call metadata, event id, and the expiring signed vCon URL.
- [Fetch the signed vCon](https://docs.klariqo.com/compliance-export-webhooks/fetch-the-signed-vcon.md): Retrieve the signed compliance record from the short-lived link in a compliance export webhook, then verify its JWS signature before you store it.
- [Security overview](https://docs.klariqo.com/security-privacy/overview.md): How Klariqo protects compliance records with signing, encryption, and trusted timestamps, and what remains your responsibility around the dialer you already run.
- [Data in a compliance record](https://docs.klariqo.com/security-privacy/data-in-a-compliance-record.md): What data a Klariqo compliance record may contain (parties, transcript, recording hash, QA), and what the trusted timestamp authority never sees or receives.
- [Public verifier privacy](https://docs.klariqo.com/security-privacy/public-verifier-privacy.md): The Klariqo public verifier runs entirely in your browser: records, keys, and hashes you check never leave your machine and nothing is uploaded to Klariqo.
- [AGENTS](https://docs.klariqo.com/AGENTS.md)

## Optional

- [Klariqo home](https://klariqo.com)
- [Blog](https://klariqo.com/blog/)