A healthcare voice AI agent’s intake call usually leaves its transcript, recording, consent, and clinical data in separate services, each with its own format and IDs. We built a telehealth intake agent on LiveKit that writes all of it into one signed, portable vCon, a conversation record

When Jeff Pulver invited me to attend Voice and Conversations on the Net (VON) 2026 on behalf of WebRTC.ventures, I accepted immediately. Three days with people building the next generation of voice communications was an easy yes. While at the conference earlier this week, the enthusiasm for

As Voice AI becomes more prevalent, applications need a way to store conversation data that supports observability, auditing, and long-term retention. The audio recording or a text transcript alone leaves out critical context. Additional details matter too, such as who was in the conversation, what devices were

A production voice agent has a latency budget of roughly 800 milliseconds before a conversation starts to feel slow. That budget is spent across eight sequential stages, typically split across three to five different vendors depending on how the stack is assembled. This post maps that voice
