Delayed Responses
Find and fix awkward pauses before the agent answers: instructions, language settings, slow workflow actions and provider trouble.
Showing instructions for Xebit VoiceCloud.Showing instructions for Xebit VoiceKit, on your own infrastructure. Switch with the selector at the top. Updated 22 October 2026.
On the default speech to speech path the agent answers in under 500 ms, so a pause the caller notices means something is waiting. Usually it is one of your own systems behind a workflow action, an instruction set that has grown too long, or a language mismatch. Observability shows response time on every turn, which tells you exactly where the pause happened.
Find the slow turn
- Sign in to the Xebit VoiceCloud dashboard at
voice.xebit.ai. - Sign in to the Xebit VoiceKit admin console on your own host.
- Open an affected call and replay it. The event log beside the transcript shows what happened in the gap.
- Check the per turn response time for the call in Observability. See Observability.
Then match what you see to one of the sections below.
A pause on every turn
- Language setting: if the agent is set to one language and callers speak another, every turn suffers. See Language Issues.
- Instructions: very long instructions with many nested conditions slow the agent down. Keep them short and direct. See System Prompt.
- Your components: if you run a cascade with your own speech to text and text to speech, each one adds its own time. See Latency Problems.
A pause when the agent looks something up
What it usually means: a workflow action is calling one of your APIs, such as a calendar, a loan system or a CRM, and that API is slow to answer.
- Find the action in the event log and how long it took.
- Speed up the API, or return less data from it.
- Add a filler phrase to the instructions, such as "one moment, let me check that", so the caller hears something while the action runs.
- If the data does not change during the call, pass it in before the call starts instead of fetching it mid conversation. See Prompt Variables and Agent Workflows.
A pause on certain questions
What it usually means: the instructions do not cover that question clearly.
- Open the agent's settings and add a clear answer or rule for that kind of question.
- Start a test call and ask it again.
A pause at the start of every call
- Keep the opening line short and fixed.
- Avoid lookups or conditions before the first sentence. Pass what the greeting needs, such as the customer's name, as a variable.
- Test again with a test call.
Delays getting worse over time
If response times have crept up across many calls without any change on your side, check Observability for an open incident. Model and speech provider slowdowns show up there, with the agents they affect. If there is none, contact us.
Still need help?
Email hello@xebit.ai or use the contact page, with the call ID of a call that had delays.
Support is included in your Xebit VoiceKit licence.