Autocloz + Sinch
Sinch is listed for voice, SMS and WhatsApp in Autocloz, but the three channels are not in the same state. Sinch SMS works from the Settings → Integrations card with a service plan ID and API token. Sinch voice does not: the call adapter needs an application key and secret that the card does not ask for, so calls fail with a named error. Voice calls through Sinch are text-to-speech callouts that read your script, not a rep talking in the browser. For live rep calling use Telnyx or DIDLogic.
Status: limited today. Measured on 2026-09-28: Sinch call touches fail with "Sinch account_sid (app key) + auth_token (app secret) required" when configured only through the card. Sinch SMS reaches Sinch's API.
What you can do with Sinch
Sinch plugs into the Call stack — bring your own carrier account, scoped to your workspace.
TTS callouts
The Sinch Voice adapter uses the ttsCallout method: Sinch dials the lead and reads the step text in the locale you set, en-US by default.
Regional endpoints
The card's API region (us, eu, br, sg or au) picks which Sinch endpoint the SMS adapter calls.
Named failures
Missing Sinch values produce a failure that lists them, visible in the Unibox and campaign reports.
How to connect Sinch
Bring your own carrier account — you keep control of the account, the spend and the data boundary.
- 1
Collect Sinch credentials
From the Sinch dashboard take your SMS service plan ID and API token, and a Voice application key and secret if you plan to test calls.
- 2
Fill in the Sinch card
Open Settings → Integrations, pick Sinch, and paste the service plan ID, API token, from-number and region.
- 3
Test SMS first
Send one SMS to your own phone from a Sinch sender. This path works with the card values.
- 4
Keep calls on another carrier
The voice adapter cannot read an application key and secret from the card yet, so use Telnyx or Twilio for the call step.
Sinch card fields and what each one feeds
The Sinch card has five fields. Service plan ID and API token feed SMS. From-number is the sender for SMS and the caller ID for callouts. Region picks the SMS host. WhatsApp bot ID is stored but not read by the current WhatsApp adapter. None of the five is the Voice application key and secret, which is why calls stop. Nothing on the card is shared with other workspaces, and secrets are shown back masked.
Voice, SMS and WhatsApp through Sinch, channel by channel
SMS: the adapter posts batches to {region}.sms.api.sinch.com with your service plan ID and bearer token. That matches what the card collects. See the Sinch SMS page for sending details.
Voice: the adapter posts to calling.api.sinch.com with basic auth made from an application key and secret. The card has no fields for those, and the resolver does not derive them, so calls stop before the request.
WhatsApp: the adapter uses Sinch's Conversation API, which needs a project ID and an app ID. The card offers a WhatsApp bot ID instead, so WhatsApp sends also stop. The Sinch WhatsApp page has the detail.
When a Sinch callout makes sense
Because Sinch voice here is a text-to-speech callout, it fits reminders or short notices rather than sales conversations. A rep cannot pick up the call in the browser, and there is no inbound call webhook or recording import for Sinch. Every call step still passes the compliance gate for quiet hours and DNC first.
What Sinch does not do in Autocloz
- No working Sinch voice calls from the card alone.
- No browser softphone, no inbound calls and no recordings through Sinch.
- No number purchase inside Autocloz.
Troubleshooting Sinch
- Call touches fail with "app key + app secret required".
- Expected with the current card. Use another carrier for calls.
- SMS fails with an authentication error.
- Check the token belongs to the same service plan ID, and that the region matches where the plan lives.
Part of the Call stack
Sinch is one of several carriers you can run behind the Call channel. They share the same dialer, CDR logging, recordings UI and compliance gates.
Explore the Call featureRelated integrations
Call Control v2 + WebRTC softphone, signed-URL recordings, Ed25519 webhook verification.
View integrationIn-browser Voice SDK calling + low international SIP rates; CDR poll for retroactive ingest.
View integrationIndia-native voice with per-agent OAuth, presence sync + recording import.
View integrationFrequently asked
Can a rep talk to a lead over Sinch?
Not in Autocloz. Sinch calls here are text-to-speech callouts.
Which Sinch channel works today?
SMS, using the service plan ID and API token on the card.
Run Sinch inside Autocloz
Bring your own account, plug it into the Call channel, and keep a free-forever CRM for 3 users.