Agent Troubleshooting

Common agent problems and how to fix them.

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.

Most agent problems come from one of three places: the instructions, the agent's settings, or the route from your carrier. This page lists the common symptoms, the likely causes and the fix for each. For problems that span the platform, such as latency or dropped calls, see the Troubleshooting section.

The agent is not answering calls

Likely causes: the agent is not live yet, no number on your SIP trunk is routed to it, or your carrier is not sending the calls to Xebit.

  1. Open the agent in the dashboard or admin console and check it is live and saved.
  2. Check a number on your SIP trunk is routed to this agent.
  3. Check its hours: outside them it behaves as configured, which may not mean answering.
  4. Ask your carrier or SBC team to confirm calls for that number reach Xebit. See Carrier and SIP Trunk Issues.

The agent does not understand the caller

Likely causes: vague instructions, a language setting that does not match the caller, or heavy background noise.

  1. Make the instructions more specific about what callers usually say.
  2. Check the language settings match your callers, including any second language they switch to.
  3. Add examples for the situations the agent struggled with.

The agent gives wrong answers

Likely causes: the instructions do not cover the topic, contradict themselves, or leave the agent to guess.

  1. Replay the call with its transcript to find exactly where it went wrong. See Call Recordings.
  2. Add a line covering that situation.
  3. Be explicit: tell the agent what to say, not only what to do.

The agent is not booking appointments

Likely causes: the booking workflow is not enabled on the agent, your scheduling system is not reachable, or it has no free slots.

  1. Check the availability and booking actions are enabled on the agent. See Workflows.
  2. Open a failed call and check the event log for the action's response.
  3. Check your scheduling system has free slots at the times callers ask for.

More in Appointment Troubleshooting.

The agent is not handing over

Likely causes: transfer rules are not set, the destination is wrong, or the instructions never say when to hand over.

  1. Check the agent's transfer settings and the destination.
  2. State the triggers in the instructions, for example "If the caller asks for a manager, hand over immediately."
  3. Make a test call that hits a trigger.

Remember that a person can always join a live call from a browser. See Multi-Protocol Audio Bridge.

The agent replies in the wrong language

Likely causes: the language setting is wrong, or the instructions are written in a different language from the caller's.

  1. Update the agent's language settings to match your callers.
  2. If callers use several languages, say so in the instructions, for example "Reply in the language the caller uses."

More in Language Issues.

Call results are not reaching your systems

Likely causes: the CRM connector or webhook is not set up for this agent, or your endpoint is failing.

  1. Check the agent writes to your CRM, or that a webhook is set up for its events.
  2. Check your endpoint returns a success status.
  3. If customers expect a confirmation message, check your own messaging system is triggered by the webhook. Xebit does not send SMS, WhatsApp or email to customers.

More in CRM Sync Errors and Webhook Failures.

The agent talks over the caller

Likely cause: the instructions push it to reply quickly or to keep talking.

  1. Add a line such as "Let the caller finish before you reply. Never interrupt."
  2. Save and make a test call to check it feels natural.

Callers who feel interrupted hang up. This small change usually fixes it.

The agent sounds robotic

Likely causes: instructions written as a formal script, or a voice that does not suit the language.

  1. Rewrite the instructions the way you would actually speak to a customer.
  2. Try a different voice.
  3. Test after each change.

Still need help?

Write to hello@xebit.ai or use the contact page, with:

  • the agent's name;
  • the number on your SIP trunk involved;
  • a description of the problem;
  • the call ID, or the date and time of an affected call.

On Xebit VoiceKit, also include your release version, and share logs as your security process allows.