Prerequisites
- A Plivo account with at least one purchased phone number
- Plivo Auth ID and Auth Token (from your Plivo console)
What is Plivo?
Plivo is the telephony provider Swiftsell uses for AI voice agent calls. When a caller dials your Plivo number, Plivo routes the call to Swiftsell, which hands it off to the configured voice agent.Step 1 — Get your Plivo credentials
- Log in to your Plivo Console.
- On the dashboard, note your Auth ID and Auth Token.
- Go to Phone Numbers in the console and note the phone number you want to use (in E.164 format, e.g.,
+14155552671).
Step 2 — Add the phone number to Swiftsell
- In Swiftsell, go to Settings → Phone Number.
- Click Add Phone Number.
- Enter:
- Plivo Auth ID
- Plivo Auth Token
- Phone Number (E.164 format)
- Click Save.
Step 3 — Configure the Plivo webhook
For Plivo to route incoming calls to Swiftsell, you need to set the answer URL in Plivo.- In the Plivo Console, go to Phone Numbers → Your Numbers.
- Click on the phone number you’re configuring.
- Under Inbound Call Settings, set the Answer URL to the webhook URL shown in Swiftsell (Settings → Phone Number → Webhook URL).
- Set the method to POST.
- Save the changes in Plivo.
Step 4 — Assign to a voice agent
After the phone number is saved in Swiftsell, assign it to a voice agent:- Go to Voice Agents and open (or create) the agent that should handle calls from this number.
- In the agent’s configuration, select the phone number from the Phone Number dropdown.
- Save the agent.
Managing multiple numbers
You can add multiple Plivo phone numbers to Swiftsell — each with its own Plivo credentials if they’re on different Plivo accounts. Each number is assigned to one voice agent at a time.Troubleshooting
| Problem | Check |
|---|---|
| Calls not reaching the agent | Confirm the Answer URL in Plivo matches the webhook URL in Swiftsell |
| Authentication errors | Verify the Auth ID and Auth Token are correct |
| Agent not responding | Confirm a voice agent is assigned to the phone number |
| Poor audio quality | This is typically a Plivo infrastructure issue — check Plivo’s status page |
Related pages
- Voice Agents Overview — understand the full call flow
- Create a Voice Agent — set up an agent to handle calls