Skip to content

Plivo (SMS / WhatsApp / Voice) ​

Priya texts Acme Support, calls their hotline, and sends a WhatsApp message, all on the same day. With one Plivo connection in your workspace, each of those reaches the right agent.

This page is for workspace admins who already have a Plivo account. By the end you'll have your keys saved, your numbers tagged by channel, and Plivo pointed at Perfox so messages and calls come in.

What Plivo powers ​

One Plivo connection covers three channels: SMS, WhatsApp (Plivo as your WhatsApp provider) and phone voice. You bring your own Plivo account and Perfox uses your keys when it sends or receives. Your keys are encrypted and stay in your workspace. If the connection is missing or its keys are blank, a send stops with a message that points you back to Connections. It never fails silently. (See Bring Your Own Provider.)

Plivo works in both directions on all three channels. Perfox sends SMS and WhatsApp messages and places calls from your numbers. It also receives inbound SMS, WhatsApp messages and calls once Plivo is pointed at your workspace (see Point Plivo at Perfox).

Connect Plivo ​

  1. Open Admin → Connections. Plivo is under Telephony & Messaging.
  2. Click Connect. The Connect Plivo window asks for:
    • Name and an optional Description.
    • Auth ID and Auth Token from your Plivo console. These are the only required fields.
    • Optional fields, grouped by channel: SIP Domain / SIP Username / SIP Password under Phone, the three DLT fields under SMS (India only), and WABA ID — for template sync under WhatsApp. You can leave the WABA ID blank: WhatsApp Business Account IDs are set per number later, where you view that number's templates (see WhatsApp templates). A WABA ID entered here still works as a fallback for numbers that don't have their own.
  3. Click Create.

You don't type phone numbers here. As the window says, once the connection is saved you open it to find your Plivo numbers and assign each one to Voice, SMS or WhatsApp.

The Plivo editor ​

Plivo is edited on the Connections page itself, not in a pop-up. Click Edit on your Plivo card (or click the card) and it expands:

A Plivo number tagged for Voice and WhatsApp: the Set up voice & SMS button beside the channel tags, and the Required manual step box with the WhatsApp Webhook URL to paste in Plivo's console

From top to bottom:

  • Name, Description, Auth ID and Auth Token. Once saved, the Auth Token shows as dots with a Replace link and Saved and encrypted. Replace it only if it changed. It is stored encrypted and is never shown again. Click Replace only to enter a new token (Keep undoes it); a token you don't touch is never overwritten when you save.
  • Two tabs:
    • Numbers & templates: Numbers (from your Plivo account), where you tag each number with its channels, set it up in Plivo with its own Set up voice & SMS button, and, for WhatsApp numbers, see the manual inbound step and open the number's templates; then Advanced — SIP trunk & DLT (India SMS), a collapsed section with the optional SIP and DLT fields.
    • Integration: the webhook URLs to paste into Plivo.
  • A Save changes button at the bottom. It reads Saved when nothing has changed.

Text fields (name, keys, advanced fields) only save when you click Save changes. The page warns you if you try to leave with unsaved edits. Number tags are the exception: they save on their own (see below).

Your numbers ​

Plivo keeps the list of your numbers, so you never type them in. When you open the editor, Perfox reads every number on your saved Plivo account, however many pages Plivo returns them in. For each one it shows:

  • The number in full international format (+91…) and the label you gave it in Plivo.
  • VOICE and SMS badges. A green badge means that capability is switched on for the number in Plivo.

Click ↻ Refresh from Plivo to read the list again, for example after buying a number.

Perfox can only read your numbers after the Auth ID and Auth Token are saved. If it can't list them, it tells you why:

MessageWhat to do
Add your Plivo Auth ID and Auth Token and save first, then discover numbers.Save the keys, then refresh.
Plivo rejected the Auth ID / Auth Token — double-check them.Re-copy both values from your Plivo console.
Could not reach Plivo to list numbers. Try again in a moment.A temporary problem reaching Plivo. Try again.
No numbers found on this Plivo account.Buy or port a number in Plivo first.

Tag each number with its channels ​

The list header says it plainly: "Tag each number with the channel(s) it serves — many numbers per channel. A workflow sends only from a number it picks; there is no default sender." Each row has three chips: Voice, SMS and WhatsApp.

  • Tag. Click a chip to use that number for that channel. It turns highlighted and shows a tick (for example ✓ Voice). One number can serve several channels, and several numbers can serve one channel. Untagging a number's last channel removes it from your list.
  • What Plivo allows. The Voice chip only works if the number is voice-enabled in Plivo, and the SMS chip only if it is SMS-enabled. Plivo doesn't report WhatsApp, so the WhatsApp chip is always available and you decide which numbers send WhatsApp.
  • In use. A line such as ● used — phone: Support Agent shows which agents currently use the number.
  • Numbers no longer in Plivo. A number you tagged earlier but has since been released in Plivo still shows, so you can untag it.
  • Set up voice & SMS. Each row has its own button, available once the number is tagged with at least one channel (see Point Plivo at Perfox).
  • WhatsApp inbound step. Every WhatsApp-tagged row shows a Required manual step — WhatsApp inbound box with its live status (see Receiving WhatsApp: the manual step).
  • Show templates. WhatsApp-tagged rows have a Show templates button (with the count once templates are loaded, and · needs WABA ID until you've set one). See WhatsApp templates.

Tags save automatically a moment after you click. You'll see Saving number tags… and then ✓ Number tags saved. If saving fails, the message asks you to change the tag again or click Save changes.

Only numbers tagged for a channel appear as options for that channel when you build an agent.

Which number sends: there is no default ​

Perfox never picks a number for you. Every SMS, WhatsApp message and call goes out from the number its agent is linked to: the Send from number on a sender action, the number on the agent's trigger, a number an operator chose, or the from you pass in an API call. That number has to be one your Plivo connection lists (tagged in its number list). For calls, the same number is the caller ID.

If a send has no number linked, or its number isn't on any of your Plivo connections, Perfox refuses it. This happens even if you only have one Plivo account. You'll know about it:

  • Your workspace gets an in-app notification such as "SMS from +91… was refused", saying what to fix and linking to the agent or to Connections. You get at most one notification a day for the same channel, problem and number.
  • When you publish an agent that sends from a number none of your Plivo connections lists, you get an amber warning (publishing still goes ahead).

To fix it, tag the number on the Plivo connection that rents it, or pick a number the agent owns.

More than one Plivo account? You can save several Plivo connections. Every SMS, WhatsApp message and call goes through the connection that owns the sending number, with that account's keys and its own DLT details. Incoming messages and calls are recognised on any of your connections.

If you open a Plivo connection that was set up before number tagging existed, Perfox builds the tags from the numbers that connection already had, so nothing is lost.

WhatsApp templates ​

WhatsApp templates are approved per WhatsApp Business Account (WABA). One Plivo account can hold several WABAs, and Plivo doesn't report which account a number belongs to — so you tell Perfox once per number.

Click Show templates on a WhatsApp number. The window, titled with the number, has:

  • WhatsApp Business Account ID: paste this number's WABA ID from the Plivo console (WhatsApp → Business Account). It's saved with the card. Until it's set, the window explains why it's needed; sending a template by name already works without it.
  • Sync now: reads this account's templates from Plivo. The first time you open a number that has a WABA ID and no templates yet, Perfox syncs it for you. Syncing one account never affects another account's templates. If you have several Plivo connections, templates are read from every one of them, each with its own keys.
  • Shared accounts: if other numbers use the same WABA, the window says so: the same templates send from all of them.
  • The template list: each template with its status (for example approved, pending or rejected), name, a snippet of the body, category and language, and how many values you have to supply when sending. unread means Perfox couldn't read what the template needs — sync again rather than assuming it needs nothing.
  • Preview: click a template to see it the way the customer will: header, body, footer and buttons in a WhatsApp-style bubble. Placeholders such as 1 stay highlighted so you can see what still has to be filled in, and a media header is shown as a labelled slot. Beside it: language, category, what you supply, and which numbers can send it.

Advanced — SIP trunk and DLT (India SMS) ​

Click ▸ Advanced — SIP trunk & DLT (India SMS) to open six optional fields. The section opens by itself if any of them already has a value. They save with Save changes.

FieldUse
SIP Domain, SIP Username, SIP PasswordA Plivo SIP trunk. You don't need these for AI calls in either direction, because inbound and outbound calls both run on your tagged Voice numbers. Leave them blank unless Perfox support asks you to fill them in.
DLT Entity ID, DLT Template ID, DLT Template CategoryIndia SMS rules (TRAI DLT). Paste these from your DLT portal. Perfox attaches them to every SMS it sends to an Indian number, using the DLT details of the connection that owns the sending number.

Registering your SMS templates on the DLT platform (Jio, Airtel, Vodafone Idea) is a regulatory step you complete with the carriers. Perfox can't do it for you. Without valid DLT details, Indian carriers can drop the message.

Point Plivo at Perfox ​

To receive messages and calls, Plivo has to send them to your workspace. Voice and SMS can be set up with one click. WhatsApp inbound is always a manual step, because Plivo offers no way to automate it. You can also paste every URL by hand.

One click: Set up voice & SMS ​

On the Numbers & templates tab, click Set up voice & SMS on the number's row. It's available for any number tagged with at least one channel. Perfox then:

  • creates or updates an Application in your Plivo account that holds your workspace's Answer URL (for calls) and Message URL (for SMS),
  • attaches that Application to the number,
  • checks the number again to confirm it's attached.

The result appears on that row:

ResultMeaning
Voice & SMS set up — … now sends incoming calls to … and incoming SMS to …, and this number points at it.The number now rings your agents and sends its SMS to Perfox.
… was configured, but this number is still bound to something else in PlivoThe Application was saved, but the number is still attached to something else, often a PHLO flow, which Perfox can't change. Open the number in your Plivo console and point it at the Application.
This number is not on this Plivo accountSet it up from the Plivo connection that rents the number.
Plivo rejected the Auth ID / Auth Token — double-check them.Fix the keys and save first.
Not done: WhatsApp inbound… (on a WhatsApp number)Voice and SMS are done, but WhatsApp inbound still needs the manual step below. The URL is shown with a Copy button.

The button covers voice and inbound SMS only. It doesn't set up WhatsApp inbound or delivery-status URLs, so add those by hand.

Receiving WhatsApp: the manual step ​

Plivo has no API for a WhatsApp number's inbound webhook, so no button can set it. Without it, customers' replies to that number never reach Perfox, even though your messages still go out. That's why every WhatsApp-tagged number shows a Required manual step — WhatsApp inbound box with:

  • where to set it: Plivo console → WhatsApp → WhatsApp Numbers → (this number) → Configure Number → Configuration Type: Webhook URL,
  • your workspace's exact Webhook URL, with a Copy button,
  • a status that Perfox works out from real traffic on that number:
StatusMeaning
○ Inbound WhatsApp: not received yetNo customer message has reached Perfox on this number yet. Send "Hi" to the number to confirm the setup.
● Inbound WhatsApp: receiving (last …)Customer messages are arriving. Shows when the last one came in.
⚠ This number sent WhatsApp in the last 7 days … but no customer reply has reached Perfox in 14 days …You're sending but nothing comes back. The Webhook URL is most likely not set for this number in Plivo.

If the status can't be read right now, the box says so and still shows the URL.

By hand: paste the URLs ​

The Integration tab holds the Integration — connect Plivo to Perfox panel. It shows a 📡 Paste into your console block for Phone, SMS and WhatsApp. Each block says where the setting lives in the Plivo console and lists the URLs already built for your workspace, each with a Copy button and its HTTP method.

Every URL uses your workspace's API address:

text
https://<your-workspace>-api.perfox.ai
ChannelURL to paste (method POST)Where in the Plivo console
Voice: incoming callshttps://<your-workspace>-api.perfox.ai/plivo/inbound-answerVoice → Applications → create or edit an Application → Answer URL, then assign the Application to your number under Phone Numbers
SMS: incoming messageshttps://<your-workspace>-api.perfox.ai/webhooks/sms/plivoMessaging → your number / Application → Message URL
SMS: delivery statushttps://<your-workspace>-api.perfox.ai/webhooks/sms/plivo/statusMessaging → your number / Application → Delivery / Status URL
WhatsApp: incoming messageshttps://<your-workspace>-api.perfox.ai/webhooks/whatsapp/plivoWhatsApp → WhatsApp Numbers → (each number) → Configure Number → Configuration Type: Webhook URL. Per number, by hand.
WhatsApp: delivery reportshttps://<your-workspace>-api.perfox.ai/webhooks/whatsapp/plivo/statusYour WhatsApp number's webhook settings → Delivery Reports URL

Copy the URLs from the panel rather than typing them, because a URL on the wrong address never reaches your workspace. The panel shows Loading… until your workspace's address arrives; it never guesses one. You only set up incoming calls in Plivo. For outgoing calls, Perfox supplies the answer URL itself.

How incoming messages and calls are routed ​

An incoming SMS or WhatsApp message is matched to a customer and then to the published agent whose trigger watches the number it was sent to. An incoming call reaches the agent whose Phone trigger watches the number that was called. If no published agent watches that number, nobody replies. Publish an agent with a trigger on the number to fix it (see Channels Overview).

Delivery reports: "sent" is not "delivered" ​

When Plivo accepts a message, it has only been queued. Plivo reports the real outcome later: queued → sent → delivered → read, or failed. Perfox attaches its own status address to every SMS and WhatsApp message it sends, so you get these reports without any extra setup.

The ticks appear on the message in Conversations. A failed send, for example Plivo error 900 (insufficient credits), shows as failed instead of looking like the customer never answered.

Worked example: connecting Plivo for the first time ​

Setup. Asha is the admin at Acme Support. Her Plivo account has two numbers: a support line (voice and SMS) and a WhatsApp line.

Action.

  1. In Admin → Connections, she clicks Connect on Plivo, pastes her Auth ID and Auth Token, and clicks Create.
  2. She clicks Edit on the new Plivo card. Both numbers are listed with their VOICE and SMS badges.
  3. She tags the support line Voice and SMS, and the WhatsApp line WhatsApp. ✓ Number tags saved appears.
  4. She clicks Set up voice & SMS on the support line's row. The row reports that the number points at the Application.
  5. Under the WhatsApp line, she copies the Webhook URL from the Required manual step box into that number's settings in the Plivo console, then sends "Hi" to the number. The status changes to receiving.
  6. She clicks Show templates on the WhatsApp line, pastes its WABA ID, and her approved templates load.
  7. In her SMS agent she picks the support line on the trigger, so replies go out from it.

Result. Priya texts the support line. Plivo passes the message to Acme Support's workspace, the agent with an SMS trigger on that number replies from the same number, and the reply's delivery status appears in Conversations.

What just happened. Saving the keys let Perfox read the numbers. Tagging told it which numbers your agents may use on each channel, and the agent's trigger decided which number replies. The one-click setup and the manual WhatsApp step told Plivo where to deliver incoming traffic.

Troubleshooting ​

SymptomLikely cause
A send stops with a "configure this provider" messageNo Plivo connection, or the Auth ID or Auth Token is empty.
A send is refused and you get a "… was refused" notificationThe agent has no sending number linked, or its number isn't tagged on any of your Plivo connections. Tag it on the connection that rents it, or link a number the agent owns.
The number list says to save your keys firstThe keys aren't saved yet. Save them, then click ↻ Refresh from Plivo.
The Voice or SMS chip is greyed outThat capability is switched off for the number in Plivo.
SMS goes out but replies never arriveThe Message URL isn't set in Plivo, or points to the wrong address.
Calls don't reach the agentThe number isn't attached to the Application (try Set up voice & SMS on its row, and check for a PHLO flow on the number), or no published agent has a Phone trigger on it.
WhatsApp messages go out but customer replies never arriveThe number's WhatsApp Webhook URL isn't set in the Plivo console. Follow the Required manual step under the number; its status shows ⚠ when Perfox sees sends but no replies.
Show templates shows nothingThe number has no WABA ID yet, or the WABA ID belongs to a different account. Paste the number's own WABA ID and click Sync now.
India SMS shows failed or never arrivesDLT fields are missing, or the template isn't registered with the carriers.

What's next ​