Campaign call failures

Open a campaign's results page to see each recipient's current status. When a recorded provider error is available, a short explanation appears beside the status. The call history includes the provider code. Retrying means another attempt is pending according to the campaign's retry policy; a failed attempt does not necessarily mean the recipient is permanently failed.

Select a recipient's Status to inspect the attempt history, most recent first. Known errors show a short explanation and next step. Unknown errors say Unknown error. Contact your account manager. Inline summaries stay on one line. Expand Technical details for the recorded provider message, which is capped at 2,000 characters and scrolls within a bounded area. Details include the recorded failure message, time, Twilio error code, HTTP or SIP response when available, attempt ID and Twilio Call SID. Twilio can reject call creation before assigning a Call SID.

• 21215: destination calling is disabled. Review Voice Dialing Geographic Permissions in the connected Twilio account and enable the destination you intend to call. See Twilio error 21215.
• 21216: call blocked by Twilio. Review Twilio's destination and account requirements. If the block appears incorrect, contact Twilio support with the destination and business use case. Enabling a country's geographic permission does not necessarily resolve this block. See Twilio error 21216.
• Assistant preparation failed. No call was placed. Use the attempt ID when contacting Octocom support.

Details are recorded for new attempts. Older attempts may only have an outcome, and Twilio does not always supply an error code. The attempt history contains failure diagnostics, rather than full server logs or stack traces. For an issue that still needs investigation, share the attempt ID and Call SID with support.

Copilot and integrations

Ask Copilot to inspect a campaign's failed calls. The list_campaign_recipients MCP tool includes each dial's failureDetails by default. Set includeDials: true when reading attempts explicitly.

REST integrations can use:

GET /rest/v1/campaigns/{campaignId}/recipients?page=1&pageSize=100
X-API-Key: YOUR_API_KEY

The campaign must belong to the API key's organization. The response contains recipients, dials, collectedData and total. pageSize is limited to 500. Set includeDials=false to omit attempts and collected data.

Each dial's failureDetails is either null or an object with source (preparation, origination or status-callback), recordedAt (ISO timestamp), code, message, httpStatus and sipResponseCode. Codes are strings, and unavailable codes/statuses are null. Documentation links are generated from the Twilio error code.