LiveKit 指南：如何打造可投入生產環境的 AI 語音智能體

Given the number of solutions today (including LiveKit), and how easy it's gotten to code with AI, pretty much anyone can get a demo voice agent running in a matter of minutes. In fact, tens of thousands of developers (and some non-developers) get agents up and running on LiveKit each month.

However, this guide isn't just about helping you get a voice agent up and running. It's meant to share the years of experience our solution architects and forward deployed engineers have gained helping clients turn their POCs into live production agents that serve millions of minutes of AI voice agent conversations.

AI voice agent production readiness comes down to 3 questions#

In the next sections, we'll walk you through some recommendations for tackling each bucket of requirements and some tips our engineers have learned implementing AI voice agents.

1. Is the agent smart and natural-sounding enough to converse with our users?
2. Will we be able to figure out how it's doing in production?
3. Did we build it in a way that we can reliably and cost-efficiently scale it?

7 ways to build a smart and natural-sounding voice agent#

1. Optimize the agent's first response as much as possible#

When I took tennis lessons in college, my coach said that if you want to be great, you should spend most of your practice time on one stroke: the serve. It's the only shot you control from start to finish, and it sets up the rest of the point.

Your voice agent's first response works the same way. Getting the first few seconds of a call right is the number one concern one of our forward deployed engineers hears from teams going to production. And it's well-supported by data we've seen in the field. After measuring, one company found that around 3 out of 4 calls ended at their agent's greeting step.

Our recommendation comes down to a couple of things:

Measure the first turn on its own. Track the time from pickup to the agent's first word as its own metric, separate from your p50 and p95 turn latency. When we dug into one team's slow openings, the models weren't the problem. Before the agent could speak, it was waiting on an HTTP call to choose its opener that alone took almost an entire second. Moving it out of the way was some of the cheapest latency we've ever found.

Load only what the agent needs to say hello, and fetch the rest while it talks. Split your context into two buckets. Bucket one holds the minimum needed for a good greeting, often just the caller's name. Pass it in with the call, through job metadata, room metadata, or a SIP header, so the agent never waits on a lookup. Meanwhile, bucket two holds everything else, and it starts loading while the agent greets the caller.

Tip

Keep the first sentence short and the important part first.

2. Handle turn-taking and interruptions like a human does#

It's immensely frustrating to chat with an AI voice agent (or a human, for that matter) if they keep interrupting you at the wrong moments or continue rambling on about something that isn't relevant to you. To counter this poor experience, most teams bringing an agent to production use a turn-taking model like LiveKit's turn detector, paired with adaptive interruption handling so a quick "uh-huh" doesn't cut the agent off.

It's one line: turn_detection=inference.TurnDetector(). It's also the default, so AgentSession turns it on even if you leave the line out, and it adds adaptive interruption handling whenever your speech-to-text model supports it.

Unfortunately, a set-and-forget turn-taking model isn't always perfect for every use case. Our solution architects and forward deployed engineers recommend testing long mid-sentence pauses, short answers like "yes" or "no," and interruptions in every language you support before you launch. If you spot any gaps, override only the setting that fixes what you heard and leave everything else at its default:

For the full list of options and which symptom each one fixes, see the turn-taking tuning guide or Configuring turn detection and interruptions in LiveKit Agents.

Tip

If you don't have a native speaker on hand to test pauses, LiveKit Agent Simulations with voice are a helpful place to start.

3. Avoid unnatural dead air#

It's pretty normal for a human customer service agent to be on the phone with you and take a second to think about an answer, look something up, or take action. But when they do pause, you're generally confident they're still on the line, and they're usually clear about what they're doing.

AI agents also need some time to think, look something up, or take action (especially if they're working with legacy systems), but how you tune the agent to handle and minimize dead air can make a big difference.

The three most common ways to do that are:

Use fast AI models that get the job done. Throwing in the LLMs you're familiar with (like the latest ones from OpenAI or Anthropic) isn't always the right choice. In fact, in many cases, our solution architects recommend against using them. For example, Gemma 4 31B on LiveKit Inference can often get to the right answers and tool calls with far less thinking time and latency than more general-purpose models. A couple of our clients shifted from GPT-4.1 to Gemma and saw a 300–500ms savings at p50 while still having the agent pass all evals. You can compare models yourself on the LiveKit Inference latency benchmarks.

Time to first token on identical requests, from the Gemma 4 launch benchmarks (July 2026). Lower is faster.

Call long-running tools asynchronously. Our forward deployed engineers work with companies of all shapes and sizes, and many of them run into a system that takes seconds to respond. When you know a lookup is going to take a while, you can make the tool asynchronous so the agent keeps the conversation going while the work runs. Done well, it can multitask better than a human. Here's how a call plays out with an async lookup:

See sequence digram

Be careful about prompt size and caching. One of the cheapest fixes for slow responses that our solution architects and forward deployed engineers help with is optimizing the size of the prompt and caching it properly. For context, the difference between a small prompt (~2k tokens) and a large prompt (>15k tokens) can be up to ~500ms at p50 and a full second at p95. Caching can be as simple as reordering a prompt: one of our internal tests found a 38% latency improvement just by moving the static content to the top of the system prompt.

4. Help your agent listen to the customer without getting distracted by background noise#

It's pretty clear to a human whether the person on the other end of the call is talking or it's background noise from Love Is Blind: Sweden on their TV. To an agent, it's not always clear, and we've seen cases where an agent has a very confused conversation with someone's background TV or accidentally cancels out the user's voice altogether. There are a number of ways to guard against this in production, and we've documented them in LiveKit noise cancellation: what it is and how it works.

Tip

One of the things we see with teams going into production is that they didn't test the agent in background noise scenarios. You can run your scenarios with background noise on LiveKit using lk agent simulate audio --scenarios scenarios.yaml --background-noise.

5. Give your voice agent the right accent for your region and expressions for the context#

There's something uncanny about a voice agent that delivers every line in a deadpan monotone and never takes a breath, or a voice agent for a Mexican bank speaking with an accent from Spain. These issues tend to show up late when you're delivering a multilingual agent meant to span many regions.

Getting a voice agent to be expressive on LiveKit is easy if your TTS provider supports it. Turn on expressive mode and the LLM adds emotion, pacing, and non-verbal sounds inline, matched to the moment:

Try it yourself: tell the agent some good news or some bad news, then toggle expressive mode off to hear the same agent flat.

Tell it some good news, or some bad news, and listen to how the delivery changes.

Getting the right accent can be a bit trickier. The first place our team generally recommends you focus your testing is picking a voice built for the locale. It sounds obvious, but it's important to know whether your vendor supports all the locales you need so you can switch automatically when needed for a bilingual agent.

If you need tighter control, such as a different voice per language, see Build a multilingual voice agent that automatically switches languages.

Tip

In some cases, matching the entire STT, LLM, and TTS pipeline to the right language and locale helps. For example, a phone number spoken in British English can be transcribed differently from one spoken in American English, which affects how the agent reads the number back.

6. Intelligently clean up spelled-out information#

The key here is "intelligently." Nothing is worse than panic-spelling "M as in Michael, I as in icicle, C as in cat?" It shouldn't take five minutes of back-and-forth with your agent to get the right information pulled up.

Our team's approach usually has three parts:

Hear the spelling correctly without cutting the caller off. Spelling is full of pauses, and an agent that treats every gap as the end of a turn will jump in after "M-I-C." LiveKit's turn detector understands that a caller mid-spelling isn't done talking, and you can give it a little more patience (a higher min_delay) for the moments that need it.

Clean it up with a dedicated step instead of the main prompt. Don't make your main prompt do this job. LiveKit's prebuilt tasks (GetNameTask, GetEmailTask, GetPhoneNumberTask, GetAddressTask, and more) are built for exactly this: they turn "john dot doe at g mail" into john.doe@gmail.com and remember what the caller already said so they never ask twice. Additionally, you can add an agent tool that fuzzy-matches against your records for some cases.

Read it back once in a form the caller can check. In many cases, one clean confirmation beats three rounds of guessing, so our team often recommends having the agent read it back letter by letter, saying "dot" and "at" out loud: "That's j o h n dot d o e at gmail dot com, right?"

And for anything numeric, like account numbers, PINs, or confirmation codes, let callers use the keypad. LiveKit agents accept keypad presses and spoken digits interchangeably, so nobody has to read a 12-digit number out loud.

7. Keep your agent on script#

In March 2026, someone posted that Chipotle's chatbot would happily write Python. They asked it to reverse a linked list before placing an order, and the bot explained the algorithm, wrote working code, then politely asked what they wanted for lunch.

It's pretty funny until it's your brand (and your AI inference budget). Voice agents face the same thing: within the first day of launch, callers may start asking off-topic questions, pushing for exceptions, or trying the classic "ignore your previous instructions." And voice can be a bit trickier than text. In edge cases, your agent can slip in ways callers hear: reading a function call aloud, switching languages mid-sentence, or rambling through a 30-word answer to a yes-or-no question.

Here are four ways we've helped teams tackle this:

Write the prompt for the model you're running. Every model goes off the rails in its own way, so a prompt that works on one won't always carry over to another. In our experience, fast models like Gemma do best with explicit, prescriptive rules ("do this, never do that"), while larger general-purpose models do better when you describe the goal and let them work out the steps. Whichever you use, name the specific things it must never say out loud. For subtler slips, such as switching languages, use LiveKit Observability to trace the turns where the slip happens, track how often it happens, and tighten the prompt around those turns.

Tip

Be careful with examples in your prompt. Models tend to over-rotate on them, repeating the example phrasing word for word or forcing every conversation into the example's shape.

Validate in code instead of the system prompt (when it makes sense). The more rules you put in the prompt, the more chances the model has to get one wrong. Anything that has a right answer belongs in a tool. Verifying a date of birth is a good example: LLMs are notoriously bad at dates, so instead of asking the model to compare "March 3rd, '85" to a record, have it call a verify_date_of_birth tool and let your code return a yes or no. The same goes for eligibility checks, account lookups, and business rules.

Say less. LLMs are trained to be thorough, which is fine in a chat window but feels endless on a call. Not to mention every extra word costs money. On one forward deployed engagement, our engineers compared the agent with the competitor it was replacing and found it averaged about five more words per turn. Trimming wordy recovery steps turned out to be the biggest lever on total call length.

For high-stakes calls, let a second model keep watch. In some rare cases where you need a conversation to be very fast but you can't sacrifice the intelligence of a smart model, our forward deployed engineers recommend an observer pattern: a fast model handles the conversation, while a smarter model listens in the background and quietly steers the agent's next turn if needed. The observer doesn't block speech, so callers never hear the checking happen. There are major tradeoffs to consider, though. For example, the observer can only correct the next turn, not the current one; running two models costs more; and the added complexity is usually a stopgap, not a long-term design.

3 ways to set yourself up for success observing your voice agent in production#

Shipping your agent to production, even to a small slice of traffic, can be both an exciting and nerve-wracking experience. No matter how many scenarios you've tested or best practices you've followed, once you launch, you're bound to find opportunities for improvement from a latency, intelligence, or conversational flow perspective.

The teams that have the smoothest first week in production decide ahead of time what they're allowed to record and what "good" looks like, and they have everything set up so they can quickly root-cause a problem when a call doesn't go perfectly.

1. Decide what you're allowed to record before you record it#

Make sure what you're recording follows your data residency, PII, and data retention requirements.

Double-check your observability region (if needed). If you're using LiveKit Cloud for observability, your project's data region decides where traces, logs, metrics, transcripts, and recordings are stored. Today that's the United States (the default) or the European Union (Frankfurt). It's set when you create the project.

Turn on PII redaction (if necessary). LiveKit can remove personal information from transcripts, audio, and telemetry before it's stored: spoken details become a beep, and text becomes a redaction marker. It's off by default and included with LiveKit Observability at no extra cost.

2. Hypothesize what "good" looks like before you launch (and make sure you're set up to measure it)#

Voice agents can be complex systems, and it's easy to get "lost in the logs" after deployment. To help focus your first days in production, we recommend focusing on a few things.

How fast it feels. Our engineers typically look at end-to-end latency at p50 and p95, plus the first turn of the call. LiveKit Observability reports e2e_latency on every agent turn. You can inspect it call by call in Agent Insights (it's the latency under each agent reply in the screenshot above), see p50/p95/p99 in audio simulations before you launch to get a rough idea, and export it to the tools you already use to track percentiles across all your production calls.

Whether it does the job. Pick an outcome that matches what you built. The goals for an outbound agent, a customer service agent, and an AI interviewing agent differ, so there isn't a one-size-fits-all answer. Whatever you choose, our FDEs suggest making it something you can count, rather than something you can only judge from transcripts. If success means handing a qualified lead to a person, the transfer_to_human tool call is your conversion event. Track what happens after the handoff too, such as whether the lead arrives warm or cold.

Tip

If you do use an LLM to grade calls, keep the scale small. We've found models are inconsistent graders on a 0–100 scale, but they tend to do better on a 0–7 or binary scale.

3. Make sure you can find and cluster edge cases from your transcripts#

It's common when developing voice agents to fall into testing the same conversations over and over until they're all consistently successful, but in nearly every case we've seen, you'll inevitably find edge cases when you go to production.

Our forward deployed engineers usually start by having an LLM sort the first few days of transcripts into clusters, then work through the clusters of edge cases one at a time, by priority.

3 ways to build a reliable and cost-efficient voice agent in production#

1. Assume every model will fail at some point#

Every model provider has outages; it's not an "if," it's usually a "when." When deploying at production scale, we recommend including fallbacks for each model. If you're using an STT-LLM-TTS pipeline, that means a fallback for each stage. In the LiveKit Agents framework with LiveKit Inference, this is usually a quick line or two. And don't stop at the STT-LLM-TTS pipeline: consider your tools as well if they make LLM calls.

Tip

Before launch, "break" your primary provider on purpose in staging: give it a bad API key or block its hostname, then run a few test calls, including one where you break it mid-conversation. If what you hear is silence instead of a slightly different voice, your fallback isn't done.

2. Make sure your backend is set up to handle scale#

It's logical to think you need to run a massive load test before launching, but our forward deployed engineers, who have helped enterprises deploy hundreds of voice agents at scale, usually say it isn't necessary.

LiveKit Cloud scales with you, so a load test of the media and agent layers can end up being a waste of budget. Instead, they recommend testing each of the pieces you own and making sure they're set up correctly and with the right limits: your backend databases can handle many connections, your APIs can handle the request volume, and, if you're not using LiveKit Inference, your model providers are set up for your concurrency expectations.

3. Know what a conversation costs before you scale it#

It's tempting to build your voice agent with all the freshest models you're familiar with in your daily life, but when you scale that up to tens or hundreds of thousands of minutes a month, costs add up. And when you go back to switch out models, you might need to add new tools, guardrails, or prompts, because every model has its own quirks.

Don't let this list keep you from shipping#

We packed a ton of advice into this guide. Every recommendation here comes from real deployments: conversations with enterprise teams, weeks spent digging through call data, and fixes that made a measurable difference in production. But it's also specific. Some of it will matter a lot for your use case, and some of it won't matter at all.

So don't treat this as a checklist you have to finish before launch. Pick the few items that matter most for your agent, get it in front of real traffic, and let actual calls tell you what to fix next. The best voice agents we've seen weren't perfect on day one. They shipped, learned quickly, and kept getting better.

If you hit something you can't solve along the way, we'd love to help. Our developer success engineers, solution architects, and forward deployed engineers help teams take voice agents from POC to production every day. Talk to our team or explore the LiveKit Agents docs to get started.