Connect MCube calling

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

Connect an approved MCube account, numbers, and call-status callbacks. This guide uses the current supported Sakhaa setup surface and keeps provider-owned approval and availability separate.

Prepare the connection

Number ownership, calling regions, recording, and carrier rules are provider controlled.

Confirm the MCube account, approved numbers, regions, recording rule, and consent rule.
Save the required credentials and callback configuration.
Use diagnostics or an approved test number and confirm final call reconciliation.

Connect and prove health

Open /app/calls/settings/providers in the correct workspace.
Save the provider credentials and webhook configuration only in the protected setup surface.
Use provider diagnostics or an approved test number. Do not call a customer for proof.
Confirm this healthy result: Provider diagnostics pass and call status callbacks reconcile correctly.

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

Monitor and recover

Monitor: Review provider status, numbers, webhook results, dispositions, and reconciliation.
Recover: Keep failed calls visible, repair credentials or callbacks, then run a bounded test.
Rotate: Save and test replacement credentials before the provider revokes the old pair.
Disconnect: Stop scheduled calls and confirm the fallback provider before disconnecting.
Limits: Number ownership, calling regions, recording, and carrier rules are provider controlled.
Fallback: Stop new scheduled calls and use the approved alternate provider or manual callback queue.

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.