IVR & Call Routing Without the XML

Webhook-driven call control

• Inbound webhook — When a call comes in, Kadeno POSTs to your webhook URL with the caller number, called number, and call ID.
• JSON response — Your server responds with call instructions: play a message, collect a keypress, transfer to another number, or connect to an AI agent.
• Real-time events — Kadeno sends events throughout the call lifecycle (answered, digit pressed, ended) so your logic can react in real time.
• Transfer anywhere — Route to a SIP endpoint, another PSTN number, an AI agent, or a WebSocket audio stream.

What you can build

• Phone menus — "Press 1 for sales, 2 for support." Collect DTMF digits and branch your routing logic server-side.
• Time-based routing — Route to your team during business hours, to voicemail after hours, to an AI agent on weekends.
• AI-first with human fallback — Start every call with your AI agent. Detect when the caller asks for a human and transfer to a live agent.
• Multi-number routing — Assign different numbers to different campaigns or departments. One API handles them all.
• Call queuing — Hold callers in a queue with hold music, notify your team via SMS, connect when an agent is available.

Flat-rate, no surprises

Why Kadeno for IVR

• No proprietary language — TwiML and VXML are dead ends. Kadeno uses plain JSON over HTTP — testable, versionable, and debuggable like any API.
• Any language, any framework — Your webhook handler can be Node, Go, Python, or anything that can respond to an HTTP POST.
• AI-ready — Routing logic that starts simple can grow to include AI agents, transcription, and sentiment detection without changing your phone numbers or API integration.