Troubleshoot calling and AI calling
Resolve provider, number, device, agent, callback, and call-reconciliation problems.
- For
- Workspace users and support owners
- Owner
- Communication operations
- Outcome
- Identify the failure state, recover without duplicate work, or contact support with safe evidence.
- Last verified
- 2026-08-30
- Next review
- 2026-11-28
- Status
- supported
Start from the visible symptom, the affected workspace, and the approximate time. Confirm the current state before repeating an action.
What you can see
- A call cannot start or uses the wrong number or agent.
- Audio, device, consent, language, or provider runtime is not ready.
- The call ended but its final status or disposition is missing.
Check the current state
- Confirm the browser device, microphone, provider account, approved number, region, and consent rule.
- For AI calling, confirm tenant activation, runtime, agent, language, and number mapping.
- Review provider callbacks and final Sakhaa reconciliation.
- Confirm whether the first call started before trying again.
Recover safely
- Disable the failing provider or runtime path while it is repaired.
- Correct one credential, mapping, device, or callback dependency at a time.
- Use diagnostics or an approved test number before customer calling resumes.
Do not call a customer again only to test an uncertain call result.
Contact support
Send the workspace, page, approximate time, safe error code, expected result, actual result, and checks already completed.
- State whether you repeated the action and whether it can create an external side effect.
- Do not send passwords, tokens, API secrets, webhook secrets, message content, or unnecessary customer data.