Voice carriers

Autocloz + Plivo

Plivo appears in Settings → Integrations as a global voice and SMS carrier, and the card accepts your Plivo Auth ID, Auth Token, from-number and PowerPack UUID. In the current build those saved values do not reach the Plivo adapter: the credential resolver does not recognise the Auth ID field, so the call step falls back to Autocloz's stub provider and every Plivo call fails with a "real provider not registered" message. For working calls today, connect Telnyx or Voximplant.

Status: limited today. Measured on 2026-09-28: a call or SMS on a Plivo sender configured only through Settings → Integrations fails with the stub-provider error. It is never shown as sent.

Bring your own accountWorkspace-scoped, no cross-org leakFree-forever CRM core

Start free See pricing

What you can do with Plivo

Plivo plugs into the Call stack — bring your own carrier account, scoped to your workspace.

Settings are stored

Auth ID, Auth Token, from-number and PowerPack UUID save to your workspace, encrypted, so they are ready when the mapping is fixed.

Loud failure

A Plivo send that cannot run is recorded as failed with a readable reason in the Unibox and reports, following Autocloz's no-silent-fallback rule.

Adapter written

A Plivo Voice adapter exists that calls Plivo's Call API with basic auth and an answer URL, once it receives credentials.

How to connect Plivo

Bring your own carrier account — you keep control of the account, the spend and the data boundary.

1
Find your Plivo Auth ID and Token
They are on the Plivo console overview page. The Auth ID usually begins with MA.
2
Save them on the Plivo card
Open Settings → Integrations, Voice or SMS tab, Plivo, and paste the Auth ID, Auth Token and a from-number.
3
Expect a stub failure for now
A test send will show "stub provider, real provider not registered". That is the known gap, not a wrong key.
4
Pick a live carrier for the step
Point your call step at a Telnyx, Twilio, Voximplant or MSG91 sender until Plivo is fixed.

Checking what happened to a Plivo send

Every attempted Plivo call or text creates a touch on the lead with outcome failed and the stub message as the reason. The Unibox shows it, and campaign analytics count it as failed rather than sent, so your numbers are not inflated. Because the stub runs before any request, Plivo is never charged. Once another carrier is connected, you can move the step to that sender and retry the failed leads from the campaign.

Plivo card fields: Auth ID, Auth Token, from-number, PowerPack/App UUID.
Channels listed: voice, SMS, WhatsApp, numbers. Wired in code: voice and SMS.
Current result from the card alone: stub failure on both.

Why Plivo calls fail today

Autocloz resolves a sender's credentials in two places: a secret pasted on the sender itself, then the provider card in Settings → Integrations. The resolver maps well-known field names such as account_sid, account_id and api_key. Plivo's card uses auth_id, which is not on that list, so the resolver finds no usable credential and hands the send to the stub. The stub records a failure instead of pretending to call.

Plivo's voice API also needs an answer URL that returns Plivo XML. The card does not collect one, so even with the resolver fixed, a URL would still be needed for calls to connect with content.

Plivo WhatsApp is not wired

The Plivo card lists WhatsApp among its channels, but WhatsApp is not in its wired channels, and there is no Plivo WhatsApp adapter. Use the official Meta WhatsApp Cloud API for WhatsApp.

What Plivo does not do in Autocloz

No working Plivo calls or SMS from the Settings card alone (see above).
No Plivo WhatsApp, no in-browser softphone, no inbound call webhook, no recordings.
No number buying inside Autocloz.

Troubleshooting Plivo

Every Plivo touch fails with "stub provider, real Call provider not registered".: This is the credential-mapping gap. Use another carrier for now; your Plivo settings stay saved.
You see WhatsApp on the Plivo card.: It is listed as a channel Plivo offers, not one Autocloz sends through. Connect Meta instead.