↓ Skip to main content

AICC

Self-hosted, AI-native call center that makes realtime voice models first-class participants alongside human agents. A single Go binary on top of FreeSWITCH.

Repository: rasonyang/ai-native-callcenter

A Realtime Voice Bot on One Mac, and Why the Third Call Breaks It

A Realtime Voice Bot on One Mac, and Why the Third Call Breaks It

AICC answers calls with anything that speaks the OpenAI Realtime protocol. In the first post in this series that meant a hosted model, or Cascade Realtime Gateway, which runs ASR → LLM → TTS behind the protocol but still calls hosted providers for each stage. The question this post answers: can one Mac run the whole cascade itself, every model local, and still answer inside the deadlines AICC’s client enforces?
An AI-Native Call Center in Four Open-Source Projects

An AI-Native Call Center in Four Open-Source Projects

Call a support line and the call usually goes like this. A recording reads you a menu. You press 3, then 1, then 0 because nothing fits. You wait in a queue. An agent picks up and asks for the order number you already keyed into the menu. Behind that call there is more pain, just not the caller’s: The agent’s desktop softphone has to be installed, configured and kept registered. When a laptop sleeps, the agent is silently unreachable. The PBX is either on the public internet, where it is scanned all night, or behind a session border controller that costs real money. If a voice bot has been bolted onto the front, it is wired to one vendor’s API, and it hands the caller to a person with none of what was said. Each of those pains sits on a different boundary of the call path: the public edge, the switch, the model, and the agent’s browser. I built one open-source project per boundary. This post is the map; later posts take one problem at a time.