Telephony bridge
Twilio media streams bridged to a realtime speech model over websockets, with a FastAPI service holding call state. Callers can interrupt at any time and the system stops talking.
Answer every call, capture structured patient details, hand off to a person the moment anything is clinical.
Reference engagements illustrate how Elicon would approach a project of this kind — the problem, the architecture and the decisions. They are examples, not accounts of past client work.
THE SITUATION
A clinic group that loses patients to busy lines in the morning and voicemail at night. The engagement builds a real-time voice intake system that answers every call, fills a validated intake form as the caller speaks, and transfers to a person — with the form and transcript on screen — the moment anything looks clinical, urgent or unclear.
Phone-only intake creates morning queues, missed calls after hours, and inconsistent data that causes rework downstream.
APPROACH
ARCHITECTURE
Twilio media streams bridged to a realtime speech model over websockets, with a FastAPI service holding call state. Callers can interrupt at any time and the system stops talking.
Behind the conversation sits a form, not a transcript. Each field has a validator and a confidence level; the model fills the form conversationally and the form refuses bad data.
A parallel classifier watches every turn for urgency, clinical questions, distress and repeated misunderstanding. Any trigger warm-transfers to a person with the partial form and transcript already on screen.
Completed intakes write into the practice management system with idempotent keys. Ambiguous patient matches queue for a person to confirm rather than creating duplicates.
DECISIONS
A free-form assistant that produces a summary sounds impressive and creates cleanup. A validated form produces records billing can use.
TRADE-OFFConversations are slightly more directed than an open assistant.
In a clinical context the costs are not symmetric. A needless transfer wastes a minute; a missed urgent caller is unacceptable.
TRADE-OFFAutomation is deliberately lower than the technology allows, and the threshold is agreed in writing during scoping.
Repeating everything to a person is the worst experience in phone automation.
TRADE-OFFDeeper integration with the phone system than a simple forward.
STACK
Work of this shape usually runs as AI Product Launch →
SIMILAR PROBLEM?
One conversation with an engineer is usually enough to tell whether this is a few weeks of work, a few months, or something you shouldn't build at all.
Talk to an engineer →