Ring fromNumber (customer 1); as soon as they answer, ring toNumber (customer 2) and connect the two. Both see one of your numbers as caller ID — a fixed one, or one picked from callingNumberIds (callerIdStrategy ROUND_ROBIN, RANDOM or STICKY). No agent is involved.
While customer 2 rings, customer 1 hears what a normal call sounds like (customer 2's ringing or caller tune, or the operator's message when that phone is off or busy). The conversation is recorded from the moment both are connected (record: false to skip). If customer 1's voicemail answers, customer 2 is connected to it.
The call is a normal call record: follow it with GET /calls/{callLogId} or the call.* webhooks — call_type is connect and connect says what happened on each side. Hang it up with POST /calls/{callLogId}/hangup. Transfer, hold and monitoring do not apply.
Connect calls are off until your account team enables them for your organisation. Subject to the daily/monthly call caps, the allowed number prefixes (both numbers), the do-not-call list, a limit on connect calls in progress, and a platform-wide rate. Requires CRM_ADMIN/ACCOUNT_OWNER/CRM_BOT.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Idempotent replay — the call this Idempotency-Key placed (header Idempotent-Replayed: true)
Not placed: INVALID_NUMBER, SAME_NUMBER, NUMBER_NOT_ALLOWED (prefix), NUMBER_IS_PLATFORM_DID, NUMBER_ON_DNC, CALLING_NUMBER_NOT_FOUND, POOL_SPANS_ACCOUNTS, VOICE_ACCOUNT_INACTIVE, CALLER_ID_NOT_OWNED, CHAT_NOT_FOUND, INVALID_*
Unauthorized
Forbidden — role not permitted, voice API not enabled, or CONNECT_CALLS_DISABLED for your organisation
The Idempotency-Key was used for a different request
Call cap reached, CONNECT_CONCURRENCY_LIMIT, CONNECT_RATE_LIMIT, or too many requests
CONNECT_CALLS_UNAVAILABLE — not available on the voice service yet
VOICE_TIMEOUT — the voice service did not answer in time; the call may still be placed (the body carries callLogId)