Skip to main content
Most customers connect VICIdial for compliance and QA: Klariqo reviews your calls from their recordings, after the call, and turns each one into a signed, independently verifiable compliance record. This is the default way to connect, and the lightest. Klariqo reads your recordings after the call. It does not register as a SIP agent, place calls, or transfer calls.
Want Klariqo’s AI voice agent to handle calls on your dialer, as well or instead? That is a separate, heavier setup. See Connect VICIdial for voice AI.

​
What you do not need

Connecting for compliance and QA skips the entire voice setup:
  • No SIP phone extension.
  • No SIP port (5060) whitelisting.
  • No remote agent.
  • No transfer dialplan.
  • No server restart or SIP reload.

​
What Klariqo needs

Klariqo reads your call recordings through VICIdial’s built-in non-agent API. To set that up, you provide:
1

Your VICIdial URL

The web address of your VICIdial admin and API, for example https://dialer.yourcompany.com.
2

An API user for recordings

A VICIdial user with API access and permission to view reports and lead information. Klariqo uses this account to list recordings, retrieve them, and read each call’s caller number and direction for the record.Klariqo uses read functions only, and no write access is needed:
  • agent_stats_export and recording_lookup to find and fetch recordings.
  • lead_field_info and lead_all_info to read caller and lead fields. These need the user’s “GET LEAD INFO” permission.
  • phone_number_log to confirm whether each call was inbound or outbound.
3

Reachability

Klariqo must be able to reach your VICIdial API and download the recording URLs it returns. If your system restricts API or recording access by IP, allow the Klariqo IP we give you during setup.
4

Recording authorization

Confirm that these calls were lawfully recorded and that you are authorized to submit them for review.
5

Agents to review (optional)

Give the agent IDs you want reviewed. If you leave this open, Klariqo reviews the agents that were active in each review window.
Before any review starts, use the Test connection button in your Klariqo dashboard. It checks that the API authenticates, that both read functions work, and that a recording actually downloads, and it shows exactly which step failed if anything is blocked.

​
What each record captures

Every reviewed call becomes a record that carries the caller’s phone number, the agent who handled it, the timestamp, the duration, and the call direction. Klariqo reads these values directly from your dialer’s own call logs, and attaches them to the QA score and the signed record. Direction is resolved per call, never assumed, because it affects consent obligations:
  • Inbound calls are positively confirmed from your inbound call log.
  • Outbound calls are positively confirmed when your VICIdial has an index on the phone_number column of its call-log tables. This is a one-line change your database administrator can make, and it is recommended by VICIdial’s own documentation. Without it, on high-volume systems Klariqo marks an unconfirmed call unknown rather than guessing, so the record stays honest.
If a line carries only one direction (for example an inbound-only queue), tell us during setup and Klariqo labels it accordingly. If a line carries both, add the index above for full outbound confirmation.

​
What you get

Human-agent QA

How Klariqo reviews human-agent calls against your scorecard.

Compliance records

How each reviewed call becomes a signed, timestamped record.

Add your dialer's fields

Bind the lead fields you choose, such as a consent reference or disposition, into each signed record.
Klariqo reviews recordings you provide and warrant you have the right to review. QA and signed records support evidence, provenance, and audit-readiness. They do not make you compliant, do not prove consent by themselves, and do not replace review by your counsel.