Put your voice AI on the phone, not just in a demo
Klicko is the connective layer between real phone calls, browser calls, and any voice AI platform — whether it speaks SIP or expects a raw audio stream. Build the AI. Let Klicko handle the telephony.
SIP-based voice AI
If your voice AI platform already speaks SIP, Klicko treats it as a first-class routing target — inbound calls can ring it directly, and it can originate outbound calls the same way a carrier does.
- Normal SIP registration and call flow, nothing proprietary
- An allow-listed set of call metadata headers on request
- Automatic fallback if the platform is unavailable
Real-time streaming media
For platforms that expect a raw audio stream rather than SIP, Klicko bridges the live call to a bidirectional real-time streaming connection — audio in, audio out, with call metadata and DTMF passed alongside it.
- Standard telephony audio formats, no custom decoder needed
- Backpressure-aware, bounded buffering — never an unbounded memory grower
- Sequenced, timestamped frames so nothing arrives out of order unnoticed
Four call flows, one integration
Inbound number → voice AI
A customer calls a published number; Klicko routes it straight to your AI agent, with the same reliability and observability as any other inbound route.
Voice AI → outbound PSTN
Your AI platform originates outbound calls through Klicko exactly like any authenticated connection — reaching real phone numbers through your existing carrier relationships.
Browser caller → voice AI
A web or app user calling in over browser-based calling can be routed to the same AI agent used for phone traffic — one routing policy, either origin.
AI → live agent hand-off
When the AI needs a human, the call transfers to a queue, extension or PBX destination you control — the caller never has to redial.
The parts of telephony your AI team shouldn't have to own
- Jitter buffering, resampling, and codec conversion between telephony audio and your model's expected format
- Reconnect and backpressure handling so a slow AI response never grows memory unbounded
- Call admission, concurrency limits and usage metering for AI-handled minutes
- Recording of AI-handled calls with the same retention and access controls as everything else
- Normalized disconnect reasons and CDRs, so AI-driven calls show up in the same reporting as everything else
Voice AI integration, answered directly
Does my voice AI platform need to support SIP?
No. Klicko supports both SIP-based voice AI platforms and platforms that only expect a raw, bidirectional audio stream over a real-time connection. If your platform can accept and emit standard telephony audio over a WebSocket-style connection, Klicko can bridge a live call to it directly.
Can a call move from AI to a human agent mid-call?
Yes. A call handled by voice AI can be transferred to a queue, extension, or any other routing target you've configured, without the caller hanging up and redialing.
Is AI-handled call audio recorded the same way as regular calls?
Yes — recording, retention policy and access auditing apply the same way regardless of whether the far end of the call is a human, a PBX, or a voice AI platform.
How is usage for AI-handled calls billed?
AI-handled minutes are metered and settled through the same real-time reservation and ledger system as every other call, so they show up in your existing usage reporting rather than a separate system.