Autocloz + MSG91
MSG91 is an Indian provider that Autocloz uses for voice, SMS and WhatsApp from one auth key. For calls, you paste your MSG91 auth key and a Voice flow ID into Settings → Integrations; each call step then asks MSG91 to run that flow for the lead's number. The flow, built in the MSG91 console, decides what the call plays. MSG91 suits teams calling Indian numbers who need DLT-registered sender IDs for texts too. See DLT registration for that side.
What you can do with MSG91
MSG91 plugs into the Call stack — bring your own carrier account, scoped to your workspace.
Flow-driven calls
A call step posts your Voice flow ID and the lead's number to MSG91's v5 voice endpoint. MSG91 runs the flow you built.
One key, three channels
The same MSG91 auth key covers the voice, SMS and WhatsApp adapters, with per-channel IDs on the same card.
No false success
If MSG91 answers 200 with an empty or unreadable body, Autocloz marks the call failed instead of guessing it worked.
How to connect MSG91
Bring your own carrier account — you keep control of the account, the spend and the data boundary.
- 1
Build a Voice flow
In the MSG91 console create a voice flow that plays your message and copy its flow ID.
- 2
Copy your auth key
MSG91 console → API → Auth Keys. The same key is used for SMS and WhatsApp.
- 3
Fill in the MSG91 card
Open Settings → Integrations, pick MSG91, and paste the auth key and Voice flow ID. Add your DID as the sender's number.
- 4
Test with one lead
Put your own number in a one-step call sequence and confirm the flow plays.
MSG91 card fields and where they go
The MSG91 card holds the auth key, a DLT-registered sender ID, the SMS flow/template ID, the WhatsApp template language, a legacy WhatsApp namespace and the Voice flow ID. For calls only the auth key and Voice flow ID matter; the caller ID comes from the number on the call sender. Secrets are encrypted and shown back masked, and the card is scoped to your workspace, so another workspace on the same platform cannot use your key.
- Voice: auth key + Voice flow ID.
- SMS: auth key + sender ID + SMS flow/template ID.
- WhatsApp: auth key + template language.
Compliance for calls to India
MSG91 voice calls are business-initiated, so India's DND rules and your own consent records matter. Autocloz checks its DNC list and quiet hours before each call step, but it does not query India's national DND registry for you. Read DLT registration and the compliance settings before running call steps at volume.
How MSG91 voice calls work in Autocloz
The call adapter sends one request to control.msg91.com/api/v5/voice/call with the authkey header, your flow ID, and the lead's number. MSG91 returns a request ID, which Autocloz stores as the touch's provider reference. An optional callback URL can be set for outcomes. Our 2026-09-28 check confirmed the card's values reach the adapter and it makes the request; we did not place a live MSG91 call.
Because the flow is fixed content, MSG91 calls fit reminders, confirmations and short announcements. They are not rep conversations and they do not appear in the in-browser dialer.
MSG91 across voice, SMS and WhatsApp
The SMS adapter uses MSG91 Flow with your DLT-registered 6-character sender ID and a template ID. The WhatsApp adapter sends approved templates through MSG91's WhatsApp API. Both are covered on their own pages: MSG91 SMS and MSG91 WhatsApp. The legacy WhatsApp namespace field on the card can stay empty.
What MSG91 does not do in Autocloz
- No live rep calling, browser softphone or recordings through MSG91.
- No inbound call handling for MSG91 numbers.
- Call content is limited to what your MSG91 flow plays.
Troubleshooting MSG91
- Calls fail with "MSG91 api_key + extras.flow_id required".
- Fill in Voice flow ID on the MSG91 card.
- Touches fail with "msg91 voice returned 200 with no parseable body".
- MSG91 accepted the request but gave no request ID. Usually the flow ID is wrong or the number is not approved. Check the MSG91 console logs.
Part of the Call stack
MSG91 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 I use one MSG91 account for calls and texts?
Yes. The same auth key drives the voice, SMS and WhatsApp adapters.
Does MSG91 voice work outside India?
That depends on your MSG91 account and number. Autocloz sends the lead's number as stored.
Run MSG91 inside Autocloz
Bring your own account, plug it into the Call channel, and keep a free-forever CRM for 3 users.