One AI Flow, Two Channels: Voice and Web Chat from the Same Logic

#voip #ai #webdev #chatbot

Most voice bot architectures and web chatbot architectures are built separately. Different codebases, different state management, duplicated logic.

VoIPBin just shipped a prototype that eliminates that separation.

The Insight: Direct Hash Works for Web Too

VoIPBin's Direct Hash was originally designed for voice: instead of provisioning a phone number, you generate a unique hash that maps directly to an AI flow.

sip:direct.<12-hex-chars>@sip.voipbin.net

The same mechanism now works for web clients. A web chatbot widget connects to the same hash, routes to the same AI flow. No separate endpoint. No separate logic.

Build Once, Deploy Everywhere

You design your AI interaction flow once in VoIPBin. That flow can now handle:

SIP voice calls
Web chatbot widget sessions

Same flow definition. Same conversation logic. Zero duplication.

The aicall Architecture

The underlying engine is aicall — originally built to manage async real-time voice. It tracks conversation state, manages the lifecycle, handles turn-taking.

Turns out the same lifecycle management works for web chat. A web conversation has the same fundamental pattern: async messages, stateful context, turn-taking. The voice infrastructure just works.