Seller Lab 1 · A hands-on lab for new LiveKit sellers
Why real-time voice AI is hard
Juniper is a voice agent that answers the phone for a made-up restaurant. Each experiment plays it the same recorded caller twice and changes one setting. You predict what will happen, hear the difference, try it with your own voice, and leave with the question to ask a customer.
What the live runs showed
Same clips, two runs per setting, on LiveKit Cloud
| Experiment | Baseline | Enhanced |
|---|
| 1. Turn detection | Both runs jumped in after “I’d like a table for” and answered at each pause. | Both runs heard the whole sentence as one turn and answered once. |
|---|
| 2. Interruptions | Both runs stopped at each “uh-huh” and picked the sentence back up about two seconds later. | Both runs read on through both “uh-huh”s and stopped only for the vegetarian question. |
|---|
| 3. The coffee shop | Every run heard the next table as part of the call: 11 or 12 words nobody said, like “No way. Did you see the game last night?” And Juniper answered them. | With voice isolation, every run heard only the caller, and Juniper went straight on to ask for a name. |
|---|
| 4. The pausefast vs reasoning model | 0.54 to 0.69 seconds before the answer; the LLM’s first words took 0.12 to 0.17 of it. | 1.77 to 2.23 seconds; the LLM’s first words took 1.32 to 1.82 of it. |
|---|
A cheaper judge
On two saved practice calls, scored twice each, gpt-5.4-mini reached the same verdicts as gpt-5.5. It takes 2 to 4 seconds instead of 4.5 to 6.5, and costs about a tenth as much. So it’s the judge now.
The hosted lab, end to end
The cloud agent joined within 8 seconds. A typed practice call came back scored, with a quote and a time for each point, within 15 seconds of hanging up.