AI-generated Answer for niranjan_20946
Short answer: there isn’t a documented “download errors” button for outbound/batch calls in the dashboard. ElevenLabs documents three supported ways to see or extract failure reasons:
- Manual: Call History shows each failed call with a red error explanation. This is the quickest way to view “why” for specific calls, but the Help Center does not document a bulk export from this page. (help.elevenlabs.io)
- API (batch jobs and recipients): Use the Batch Calling API to pull each batch and its recipients (including per-recipient status) and export that data yourself:
- List batches: GET /v1/convai/batch-calling/workspace
- Get batch details (includes recipients[] with status and conversation_id when present): GET /v1/convai/batch-calling/:batch_id
You can then write those results to CSV. (elevenlabs.io)
- Post-call webhooks (recommended for reasons): Enable post-call transcription webhooks for your workspace. Each webhook includes a data.metadata object that contains call timing, phone details, and a termination_reason field. Capture those webhook payloads in your system and export as CSV to get a machine-readable list of failure reasons (e.g., busy/declined/no answer). (elevenlabs.io)
If you need to correlate a recipient in a batch to the full conversation record (for those that connected), use conversation_id from the batch details and fetch conversation metadata via the Conversations API, or rely on the webhook payloads which already include the conversation_id and termination_reason. (elevenlabs.io)
Notes
- ElevenLabs documentation does not list SIP response-code mappings (e.g., 486 Busy Here) or a CSV export button for Call History; if you need evidence of a specific failure at scale, the documented path is to log post-call webhook payloads and/or batch recipient statuses and export them yourself. (help.elevenlabs.io)
Sources:
Where can I locate the reason for my call failing? – ElevenLabs
List workspace batch calling jobs | ElevenLabs Documentation
Post-call webhooks | ElevenLabs Documentation
Get batch call information | ElevenLabs Documentation
Where can I locate the reason for my call failing? – ElevenLabs
broken charm
left cedar