A real-time AI avatar gives a voice agent a face, and it also puts a third-party media service between your text-to-speech and the user. In a Pipecat pipeline, the avatar service receives your synthesized speech, renders the face, and sends back the audio the user hears. When
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
WebRTC and SIP both carry live voice to an AI agent. Voice AI platforms list them side by side, so teams building an AI receptionist often expect to pick one or the other for connecting callers to the agent. In practice, each protocol serves a different way
