Skip to main content

Call outcomes: call_status and status_reason

call_status — final status bucket of a finished call (empty string until finalized). One axis, one source of truth; quality (call_successful) and technical reliability (health) are separate axes and never leak into the status: status_reason — fine-grained reason, always belonging to exactly one bucket: The Analysis column says whether post-call analysis runs for the call — the summary, the extracted fields and the success verdict. These are the defaults: the list of reasons that skip analysis is an agent setting.

Which carrier answer gives which reason

The reasons of the not_connected bucket come from the carrier’s answer to our INVITE. How fine-grained that is depends on what the carrier’s server publishes: with no code, the reason stays the generic dial_failed and the code itself sits in error_code beside it. A 403 on a peer-to-peer (IP-based) trunk is a failed dial, not a trunk failure. Such a trunk has no credentials, so a 403 means the carrier does not let the call into that destination. The call gets dial_failed, and the 403 is in error_code. On a registration trunk, and when the trunk is not found, a 403 stays trunk_auth_failed. 606 Not Acceptable is deliberately left in dial_failed: the same code arrives both from a carrier out of capacity and from an answering machine rejecting the call. It has no one honest reason, so read error_code for such calls.

How the reason is chosen

The rules apply top down, and the first one that fires wins:
  1. The call never connected — a not_connected reason from the carrier’s answer; for an inbound call where the caller left before the agent answered — caller_abandoned.
  2. The platform decided the outcome — answering machine, call screener or key-press menu, handoff to an operator, silence, the duration limit, an observer incident or a stop for an update.
  3. Not a single recognized callee turn — no_speech; fewer turns or seconds than the configured threshold — too_short.
  4. Otherwise it comes down to who hung up — the flow reached its end (agent_hangup) or the callee hung up first (user_hangup).
busy and user_declined are distinct reasons. busy means busy and user_declined means the subscriber actually declined the call. If you build reports on dial-failure reasons, separate the two values rather than folding them into one.A second consequence for retry logic on your side: whether a reason is permanent depends on the market. user_declined closes a number for good only on the US profile; on other profiles it is transient, and the number returns to dialing having spent an attempt. The campaign launch check refuses an expert rule that retries a permanent outcome (rule_permanent_retry).

What a campaign does with the number after a call

This is how standard campaign logic decides. In expert logic an outcome is handled the same way when no rule matches it or its rule has used up max_matches; an explicit rule — stop_calling, retry_in or wait_for_pass_end — decides instead.
  • A redial is scheduled only while dials are left and the campaign has not ended. If attempts is used up or the next dial would fall after ends_at, the number becomes “Exhausted”.
  • The interval is the campaign interval or the step of the intervals_s ladder for this retry (Campaign fields). The calling window, the do-not-call registry and the frequency caps apply to every redial.
  • Voicemail is redialed whether or not a message was left. How many messages to leave is decided by the voicemail message policy, not by this table.
  • An unknown reason closes the number: if a new value appears in the axis, the campaign will not redial for a reason it does not understand.

What gets confused most often

silence_timeout and no_speech are one situation with two endings. The callee is silent in both; what differs is who hung up. The platform — silence_timeout; the callee first — no_speech. If you count empty calls, add the two together. A callee who hangs up without a word is no_speech, not user_hangup. The second reason is used only where a conversation took place. An inbound caller who hangs up before the agent answers is caller_abandoned. Unrecognized speech counts as silence. Noise, speech too quiet to recognize and a drop before a single recognized word all give the same reasons as silence. silence_timeout is analyzed, no_speech is not. That is not a quirk of the setting: the callee may have talked and then gone quiet, so silence at the end does not mean an empty call. The silence threshold is counted from the agent’s last utterance, reminders included. Every reminder along the lines of “Are you still there?” restarts the count. With a 12-second threshold and two reminders 8 seconds apart, a call with a silent callee runs about 30 seconds, not 12. Once the reminders run out, the call ends one reminder interval after the last one — even when the silence threshold is longer. A retry rule on the answering machine catches both cases. A condition on voicemail_reached also fires when the reason was voicemail_suppressed. The three screener reasons are completed, not not_connected. The line was answered — by the callee’s assistant or a menu — but no person spoke. When a screener connects a person, the call gets the usual reason of the conversation that followed; when it offers to leave a message and the agent leaves one, the reason is voicemail_reached. health_reasons — codes explaining a warning/error health verdict. A call’s verdict is the worst code that fired: any error-level code makes the call error, otherwise warning. The vocabulary is open — new codes are added over time, so treat an unfamiliar one as data, not as a parsing failure. Codes come from four sources. The split matters: health_reasons carries the output of a rule, never its input — status_reason values and the internal codes of call events never appear here. 1. Call events — something went wrong inside the conversation: 2. The call status axis — status_reason values fold into these: Reasons that belong to the callee (no_answer, busy, user_declined, invalid_destination, spam_blocked) dials you cancelled yourself before dialing (cancelled_by_function, cancelled_by_operator) and inbound calls abandoned before the answer (caller_abandoned) contribute nothing: they are not platform defects. 3. Post-call analysis — analysis_skipped, analysis_failed, analysis_interrupted, all warning level, from the terminal state of the analysis. 4. Recording and timing — recording_head_lost (part of the recording does not exist) and slow_turns (the 90th percentile of turn duration is above the configured threshold), both warning.