How to Build a Real-Time Voice Agent

Abstract

A voice agent looks like a chatbot with a microphone. Architecturally, it's a real-time distributed system with extremely unforgiving constraints: less than 500ms of end-to-end response latency across a multi-model pipeline, intelligent and natural-sounding conversation, and reliability when scaling to thousands of concurrent calls.

This talk walks through the architecture of a production voice agent end to end: the streaming pipeline that chains speech-to-text, turn detection, an LLM, and text-to-speech into a single system, and the design decisions that make it work under real traffic. We'll dig into where the latency budget actually goes, why colocating and serving your own models can beat just calling inference APIs, and why autoscaling stateful, long-lived audio connections is harder than it looks. 


Speaker

Rishabh Bhargava

Director of ML @Together AI

Rishabh Bhargava is Director of ML at Together AI, where he leads the Voice AI team building low-latency speech models and real-time inference for production voice agents. Previously, Rishabh was co-founder and CEO of Refuel.ai, which built purpose-built LLMs and a platform for enterprise-scale data workflows and was acquired by Together AI in 2025. Across 10+ years in AI/ML infrastructure, he has shipped ML systems at Primer.ai and Datacoral (acquired by Cloudera). He did his graduate work in CS at Stanford and is based in San Francisco.

Read more

From the same track

Session

Live Resharding Without Regret: Lessons from Building Valkey's Atomic Slot Migration

Sharding is easy. Resharding under heavy load is notoriously difficult. How do you move gigabytes of state across live database nodes without dropping keys, blocking the main event loop, or breaking client abstractions?

Speaker image - Jacob Murphy

Jacob Murphy

Open Source Maintainer @Valkey & Software Engineer @Google Cloud's Memorystore Team

Session

Architecting Nubank's Global Financial Infrastructure

Instant payment frameworks are transforming global finance, but few institutions have faced the infrastructure scale required by Brazil's Pix network.

Session

Inside the Disaggregated Architecture Serving LLM Inference

Every LLM request is really two very different jobs. Reading your prompt (prefill) is compute-intensive, while generating the response token by token (decode) is dominated by memory bandwidth. For years, the industry ran both phases on the same hardware and accepted the compromise.