Skip to main content
Call Logs, Chat Logs and Analytics

Call Statuses and End Reasons

What each call status and end reason in Call Logs means, why missed calls are hidden, and what to do when a call fails.

Written By voiceaiwrapper

Last updated 26 days ago

Every call in Call Logs has a Status (where the call is right now) and, once it's over, an End reason (how it finished). Together they tell you whether a call went well, never connected, or failed, and where to look to fix it.

This article covers VAW Native calls in detail, because VoiceAIWrapper sets those values itself. On Vapi, Retell AI, ElevenLabs, Bolna and Ultravox Pods (an engine or provider connection), the values come from the provider.

Before you start

VAW Native call statuses

StatusWhat it means
QueuedThe call is set up and waiting to be placed.
RingingThe phone is ringing.
In progressThe call is connected.
ForwardingThe agent is transferring the call to a person.
EndedThe call is over. The End reason says how it ended.

Live calls show a pulsing badge. Ended is the only finished status, so to find failed or unanswered calls, filter by End reason, not Status.

VAW Native end reasons

An end reason in red comes with an error code. Hover over it to see the code and any details.

Normal endings

End reasonWhat it meansWhat to do
Customer ended callThe caller hung up.Nothing.
Customer ended call during transferThe caller hung up while being transferred.Check how long transfers take. See Transfer Calls to a Person.
Assistant ended callThe agent ended the call with its end-conversation tool.Nothing.
Assistant said end-call phraseThe agent said one of its closing phrases.Nothing.
Assistant forwarded callThe agent transferred the call to a person.Nothing.
Exceeded max durationThe call reached the agent's maximum call length.Raise the limit if calls are being cut short. See Call Settings: Recording, Silence Timeout and Maximum Call Length.
Silence timed outNobody spoke for longer than the silence timeout.Raise the timeout if callers need more time to think.
Telephony provider reported completedThe phone carrier reported the call as finished without giving a more specific reason.Nothing, unless the transcript shows a problem.

The call didn't connect

End reasonWhat it meansWhat to do
Customer did not answerThe person you called didn't pick up.Your campaign's redial rules decide when to try again. See Outbound Dialing Rules: Attempts, Redial Wait, Voicemail and Priority.
Customer busyThe line was busy.Same as above.
Caller hung up before connectThe caller hung up while the call was still ringing.Nothing. If it happens often, check for delays in My Phone Number Doesn't Ring.

The call was refused before it started

These calls never reached the agent, so nobody spoke.

End reasonWhat it meansWhat to do
Concurrency limit reachedAll of the Pod's lines were busy, so the call was turned away. A phone caller hears a busy signal.See the missed calls section below.
Insufficient creditsYour organization is out of AI credits.Buy credits. See What Happens When You Run Out of Credits.
Client billing pausedThe agent belongs to a client whose billing is paused.Ask the client to pay or top up.
Number not assignedThe number that was called isn't active or has no agent answering it.Choose who answers the number. See Choose Who Answers a Number.
Rejected by inbound webhookYour phone number's inbound webhook told VoiceAIWrapper to reject the call. The caller heard busy.Expected if your server meant to reject it. Otherwise check your server's reply. See Route Inbound Calls with the Phone Number Webhook.
Campaign not taking callsThe number belongs to an inbound campaign that isn't taking calls right now, for example because it's paused or outside its hours.Check the campaign's status and calling window. See Campaign Statuses and the Campaign Switch.
Agent not foundThe agent was deleted or couldn't be found.Point the number or campaign at an existing agent.
Agent config invalidAn outbound call couldn't start because the phone line for the calling number couldn't be set up. Hover over the reason to see the error.Check the Twilio connection the number belongs to.
Pipeline build failedThe voice engine couldn't put the agent's model, voice and transcriber together.Try again. If it keeps happening, contact support with the call ID.

Something failed during the call

End reasonWhat it meansWhat to do
LLM failedThe AI model stopped responding.Try again. If it repeats, choose a different model. See Choose an AI Model.
Voice failedThe voice service couldn't produce speech.Try a different voice. See My Agent Doesn't Speak or Goes Silent.
Transcriber failedSpeech recognition stopped working.Try again. If it repeats, contact support with the call ID.
No customer audioNo sound reached the agent from the caller.Check the caller's microphone or line.
Transport never connectedThe audio connection was never set up.Try again. Check the caller's network on web calls.
Assistant join timed outThe agent didn't join the call in time, so it was never answered.Try again. If it repeats, contact support with the call ID.
Worker died / Worker shutdownThe voice engine handling the call stopped.Contact support with the call ID if you see this more than once.
SIP inbound failed to connect / SIP outbound failed to connectThe phone connection to the voice engine failed.Check your Twilio connection. See Connect Your Twilio Account to VAW Native.
Telephony provider failed to connectThe phone carrier couldn't place the call, for example because the number is invalid.Check the number's format and your carrier account.

Other

Unknown means the call ended without a recorded reason. Contact support with the call ID if it happens often.

A few end reasons appear in the End reason filter but VAW Native doesn't end calls with them yet: Customer did not give microphone permission, Transfer failed, Warm transfer timed out, Manually canceled and Voicemail. VAW Native doesn't detect voicemail yet, so a call that reaches voicemail ends with one of the other reasons above.

Missed calls and "Concurrency limit reached"

Every VAW Native Pod has a limited number of lines, split between inbound and outbound. Inbound phone calls, test calls and web widget calls all share the inbound lines. When they're all in use, a new inbound call is turned away with Concurrency limit reached. These are missed calls.

Missed calls are hidden from Call Logs by default so they don't bury your real conversations. The count above the list says missed calls are hidden when this applies. To see them:

  1. Click the filter button and choose Missed calls.
  2. Pick Include missed calls to show them alongside other calls, or Only missed calls to see just those.

You can also pick Concurrency limit reached in the End reason filter.

When you try a test call while every line is busy, you'll see Concurrency limit reached β€” end an active call or test and try again.

Outbound calls work differently. When all outbound lines are busy, an outbound campaign puts the lead back in the queue and tries again later, and no missed call is logged. A one-off outbound call shows All outbound lines are busy right now. Try again in a moment, or raise the Pod's outbound concurrency limit.

If you see missed calls often, give more lines to inbound calls. See Split Concurrency Between Inbound and Outbound Calls.

VAW Native chat statuses and end reasons

Chats in Chat Logs use their own values.

StatusWhat it means
StartingThe chat is being set up.
ActiveThe chat is open.
EndingThe chat is closing and won't accept new messages. A reply already in progress can still finish.
EndedThe chat is over.
ExpiredNobody ended the chat, so it closed on its own after a period with no messages.
FailedThe chat stopped because of an error. Hover over the end reason to see why.

End reasons for chats are Tester ended the chat, Agent ended the chat, Agent said a closing phrase, Expired, A tool result was uncertain, A reply was lost and Could not start. A tool result was uncertain means a tool may have made a change before the agent stopped, so check that system before testing again.

Statuses on Vapi, Retell AI, ElevenLabs, Bolna and Ultravox

On these Pods, VoiceAIWrapper shows the status the provider reports. The column is called Status on Vapi and Session Status on the others. The values you can filter by are:

PodStatuses
VapiQueued, Ringing, In Progress, Forwarding, Ended, Not Found, Deletion Failed, Scheduled
Retell AIRegistered, Not Connected, Ongoing, Ended, Error
ElevenLabsInitiated, In Progress, Processing, Done, No Answer, Failed
BolnaCompleted, Call Disconnected, No Answer, Busy, Failed, In Progress, Canceled, Balance Low, Queued, Ringing
UltravoxInitiated, Started, Joined, Ended

The End Reason column shows the provider's own wording, exactly as the provider sends it (for example, Vapi's customer-ended-call). Bolna Pods don't have an End Reason column. For what a provider's end reason means, check that provider's documentation.

A call is stuck in progress

VoiceAIWrapper updates a call when the provider reports that it has ended. If a Vapi, Retell AI or ElevenLabs call still shows as in progress after it's over, click the refresh icon next to its status. Its tooltip reads Sync Status. You'll see Call status synced successfully, or Call status already matches if nothing changed. If calls get stuck often, check your webhooks. See Sync Webhooks So VoiceAIWrapper Can Track Calls.