Agent Not Responding
Find out why an agent is not placing calls, not answering, or going quiet mid call, and fix it.
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.
If an agent is not placing outbound calls, not answering inbound calls, or going quiet in the middle of a conversation, the cause is almost always one of a short list: the campaign, the trunk routing, capacity, or the agent's instructions. Work through the section that matches what you see.
Before you start
- Sign in to the Xebit VoiceCloud dashboard at
voice.xebit.ai. - Sign in to the Xebit VoiceKit admin console on your own host.
- Check Observability for an open incident. If a provider or a module is having trouble, the SRE agent will usually have opened one already, and no change to the agent will help. See Observability.
Agent not placing outbound calls
- Is the campaign running? Open the campaign and check it has been started and is not paused. See Run a Campaign.
- Is the agent assigned? Confirm the campaign uses the agent you expect.
- Are there contacts to call? Check the campaign's list has contacts that have not been called yet or are due a retry.
- Is it inside the calling window? Calls only go out in the hours and days you set.
- Is your trunk up? Outbound calls leave over your own SIP trunk. If your carrier is rejecting calls, they will show as failed to connect. See Carrier and SIP Trunk Issues.
- Does the account have minutes left? Check this month's usage against your 5,000 minute commitment. If it is used up, a top up adds minutes in 5,000 minute blocks at the same rate. See Pricing.
- Are you at your concurrency limit? Extra calls wait until a slot frees up. See Rate Limits.
- Is there capacity? There is no per minute billing on Xebit VoiceKit, but calls need capacity. Check node and GPU capacity, your model provider's limits and your licence band. Per node metrics in Observability show where it is tight.
Agent not answering inbound calls
- Are the numbers routed to the agent? The numbers live on your SIP trunk. Check your carrier or SBC sends calls for those numbers to Xebit, and that Xebit routes them to this agent. See Inbound Agent.
- Is the agent live? An agent that is still being configured or tested should not be taking real calls. Check it is set up and enabled.
- Are the agent's hours restricting calls? Check the hours in the agent's settings and what happens to calls outside them.
- Does a test call work? Start a test call from the agent's settings. If the test works but real calls do not reach the agent, the problem is in routing, not the agent.
Agent goes quiet mid call
- Read the transcript and replay the call. Find the last turn before the silence and check the event log at that moment.
- Was it waiting on your system? If a workflow action was calling one of your APIs, a slow or failed response leaves the agent with nothing to say. Fix the API, and add a filler phrase to the instructions such as "let me check that for you". See Delayed Responses.
- Did the situation fall outside the instructions? If the caller raised something the instructions do not cover, add how to handle it. See Agent Prompting.
- Test it. Start a test call and recreate the conversation.
Agent gives wrong or irrelevant answers
- Check the instructions are clear and specific, and that facts the agent needs (prices, hours, policies) are written in them or passed in as variables. See Prompt Variables.
- Look at off script answers flagged in Observability, especially after a recent change to the instructions.
- Test the questions that went wrong, change the instructions, and test again. See Agent Testing.
Still need help?
Email hello@xebit.ai or use the contact page, with the agent's name and the call ID of an affected call.
Support is included in your Xebit VoiceKit licence.