Autocloz + Plivo SMS
Plivo SMS is listed in Autocloz, and the Plivo card in Settings → Integrations accepts your Auth ID, Auth Token, from-number and an optional PowerPack UUID. In the current build a Plivo SMS sender does not use those saved values: the credential resolver does not recognise Plivo's Auth ID field, so the send is routed to Autocloz's stub provider and fails with "real SMS provider not registered". It is never reported as sent. For working SMS now, use Twilio SMS or MSG91 SMS.
Status: limited today. Measured on 2026-09-28: Plivo SMS configured through Settings fails with the stub-provider error. It does not reach Plivo.
What you can do with Plivo SMS
Plivo SMS plugs into the SMS stack — bring your own sms provider, scoped to your workspace.
Values stored
Auth ID, Auth Token, from-number and PowerPack UUID are saved, encrypted, per workspace.
Adapter exists
A Plivo SMS adapter posts to Plivo's Message API with basic auth once it receives credentials.
Honest failure
Unsent texts show as failed with the reason in the Unibox and campaign reports.
How to connect Plivo SMS
Bring your own SMS provider — you keep control of the account, the spend and the data boundary.
- 1
Copy Plivo credentials
Auth ID and Auth Token from the Plivo console overview.
- 2
Save the Plivo card
Settings → Integrations → SMS → Plivo, with a from-number.
- 3
Expect a stub failure
A test shows "stub provider, real SMS provider not registered".
- 4
Use another provider
Point SMS steps at Twilio, Telnyx, Sinch, Vonage or MSG91 senders.
Planning around the gap
Nothing else in Autocloz depends on Plivo. Email, LinkedIn, calls on other carriers and WhatsApp through Meta all work independently, so you can keep a sequence running by moving its SMS step to a working provider or removing it until Plivo is fixed.
How a Plivo SMS attempt shows up
The lead's timeline and the Unibox show a failed SMS touch with the message "stub provider, real SMS provider not registered. Connect Twilio or Telnyx in Settings → Senders to send real SMS." Campaign reports count it as failed. Because the stub never contacts Plivo, there is no charge on your Plivo account. The SMS template itself is kept, so it can be reused on another provider's sender.
SMS rules that apply on every provider
Whichever provider you move to, SMS steps run after the same checks: quiet hours (20:00 to 09:00 by default), the workspace DNC list across all channels, and consent when the sender requires it. Templates are capped at 320 characters. See the SMS marketing compliance guide.
What goes wrong with Plivo credentials
Autocloz reads provider credentials by looking for common field names such as account_sid, account_id, api_key and auth_token. Plivo's card uses auth_id for the account identifier. Because no known identifier is found, the resolver decides the sender has no credentials and hands the message to the stub, which fails loudly by design rather than faking a send.
The PowerPack UUID field is stored for shared-shortcode routing but has no effect until the mapping is fixed.
Choosing an SMS provider while Plivo is unavailable
For US traffic, Twilio and Telnyx both work from their cards; register 10DLC with them. For India, MSG91 handles DLT-registered sender IDs and templates. All of them share the same SMS step, quiet hours and DNC checks on the SMS channel.
What Plivo SMS does not do in Autocloz
- No working Plivo SMS from the card alone.
- No Plivo inbound webhook.
- No PowerPack routing in effect.
Troubleshooting Plivo SMS
- Every Plivo SMS fails with the stub-provider error.
- Known credential-mapping gap; use another provider for now.
Part of the SMS stack
Plivo SMS is one of the providers behind the SMS channel. All providers share the same two-way threading, STOP-keyword DNC and quiet-hours enforcement.
Explore the SMS featureRelated integrations
Frequently asked
Will my saved Plivo settings work later?
They stay stored. When the mapping is fixed they will be read without re-entry.
Which provider is closest to Plivo in Autocloz?
Twilio or Telnyx for global SMS, both working from their Settings cards. For India, MSG91 with DLT templates.
Can I use my Plivo numbers with another provider?
No. A number belongs to the carrier that issued it. Port it or use the other carrier's numbers.
Is PowerPack routing supported?
Not today. The field is stored but not used.
Does the failure affect my other SMS senders?
No. Only senders whose provider is Plivo fall to the stub. Twilio, Telnyx, Sinch, Vonage, Voximplant and MSG91 senders are unaffected.
Run Plivo SMS inside Autocloz
Bring your own account, plug it into the SMS channel, and keep a free-forever CRM for 3 users.