Connect Bolna AI calling

For: Company admins and integration owners
Owner: Integration operations
Outcome: Test, monitor, recover, rotate, and disconnect Bolna AI calling safely.
Last verified: 2026-08-30
Next review: 2026-11-28
Status: supported

Connect a controlled Bolna runtime, agent, number, and callback path. This guide uses the current supported Sakhaa setup surface and keeps provider-owned approval and availability separate.

Prepare the connection

Tenant activation, provider agents, numbers, consent, and runtime limits apply.

Confirm tenant activation, the approved Bolna agent, number, language, and consent rule.
Map provider agent and number identifiers to the intended Sakhaa workspace.
Use the approved test plan and confirm callbacks and field mappings.

Connect and prove health

Open /app/calls/settings/providers in the correct workspace.
Save the provider api credentials and agent identifiers only in the protected setup surface.
Use the provider test plan and an approved test number. Do not call a customer for proof.
Confirm this healthy result: The runtime, agent, number, callback, and field mapping checks pass.

Use synthetic data and an approved test identity. Do not use customer traffic only to prove a connection.

Monitor and recover

Monitor: Review runtime status, agent mapping, number mapping, callbacks, and recent failures.
Recover: Disable the failing runtime path, preserve call evidence, and repair one dependency at a time.
Rotate: Rotate provider credentials and rerun the full runtime readiness test.
Disconnect: Pause AI calling and scheduled work before removing agents, numbers, or credentials.
Limits: Tenant activation, provider agents, numbers, consent, and runtime limits apply.
Fallback: Pause AI calling and route approved follow-up to a human owner or the reviewed non-AI calling path.

Support boundary

Sakhaa supports the CRM configuration and product behavior. The provider controls account approval, billing, quotas, and external service availability.

Record the provider, workspace, approximate time, safe error code, expected result, and actual result.
Do not include passwords, access tokens, API secrets, message content, or unnecessary customer data.