Call Drops
Work out why calls end before the conversation is finished: callers hanging up, unreachable numbers, carrier rules or a platform incident.
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.
A dropped call is one that ends before the conversation is finished. Most are the caller hanging up, and the fix is in the agent's opening. Some are the number or the carrier. A sudden rise across many calls is often an incident, which Observability will already be tracking. Start by finding out which kind you have.
First checks
- Sign in to the Xebit VoiceCloud dashboard at
voice.xebit.aiand open the calls list. - Sign in to the Xebit VoiceKit admin console on your own host and open the calls list.
- Filter to the affected calls and look at their dispositions. Caller hung up and failed to connect point in different directions.
- Check Observability. Dropped and abandoned calls are one of the things it watches, and if they spiked in one window the SRE agent will have opened an incident with the cause. See Observability.
Calls showing as caller hung up
What it means: the person ended the call before it was complete.
- Play the recording and read the transcript. Note how far in the call ended and what was said just before.
- Was the opening too long or unclear? People decide in the first few seconds. Shorten it.
- Did the agent miss something the caller said? Check the agent handled the question, then update its instructions. See Agent Prompting.
Calls ending after a few seconds
What it usually means: the person thought it was a spam call.
- Have the agent say who it is and which business it is calling from in the first sentence.
- Give a reason the person will recognise, such as their appointment or their account.
- Check the caller ID your carrier presents is a number people associate with you. It is set on your trunk, not in Xebit. See Carrier and SIP Trunk Issues.
- Start a test call to hear the new opening.
Calls dropping on the same number
What it usually means: the number is unreachable or the person has poor coverage.
- Check the disposition history for that number in the calls list.
- Try calling it yourself to confirm it is reachable.
- If it is not, remove it from the campaign's list so retries are not wasted on it. See Import Contacts.
Many dropped calls across a campaign
- Number format: every number must be in E.164 format: a plus sign, the country code and the number, with no spaces or brackets.
- Calling window: calls at inconvenient hours get dropped more. Check the campaign's calling window.
- The agent: an agent that sounds unclear or scripted loses more people. Review a sample of calls.
- Carrier rules: some carriers end calls after a set time, cap calls per number or block patterns that look like bulk dialling. Ask your carrier if calls end at the same point every time.
- Pacing: if you dial faster than your concurrency allows, calls wait. See Rate Limits.
- Capacity: check node and GPU capacity and your model provider's limits during the campaign. Per node metrics in Observability show where it was tight.
Still need help?
Email hello@xebit.ai or use the contact page, with the call IDs of a few dropped calls.
Support is included in your Xebit VoiceKit licence.