Introduction
Every Bolna Voice AI conversation carries two key fields throughout its lifecycle:| Field | Purpose |
|---|---|
status | Real-time status of the conversation |
error_message | Explanatory message for errors or failed calls |
Anatomy of a Call
The following diagram shows how a call progresses from initiation to completion:completed is the final status of every conversation, indicating all post-call processing (recordings, data extraction) is finished.Call Status Reference
- Successful
- Unanswered
- Unsuccessful
These statuses appear in chronological order during a normal call flow:
| Status | Description |
|---|---|
queued | Call received by Bolna and queued for processing |
rescheduled | Call triggered outside allowed hours and automatically rescheduled (requires call guardrails configuration) |
initiated | Call initiated from Bolna’s servers |
ringing | Call is ringing at the destination |
in-progress | Call answered and conversation is active |
call-disconnected | Call has been disconnected |
completed | All post-call processing finished (recordings, data extraction; may take ~2-3 minutes after disconnect) |
The payloads for all status events follow the same structure as the Get Execution API response.
Example Payload
Completed call payload with "status" and "error_message"
Completed call payload with "status" and "error_message"
Related Pages
Hangup Status Codes
Understand who ended the call and why
Call Latency Metrics
Analyze performance across the voice pipeline
Get Execution API
Retrieve full execution details programmatically

