Skip to content

CPaaS / Your calling setup

AI voice agents
for Plivo.

AI-answered calls on your Plivo numbers, via forward or API.
Get API Key Read the docs
CPaaSNo import needed to start
PyAI / WorkspaceActual product
Actual PyAI Console showing the Agents API integration panel with sample workspace data
The actual PyAI Console API panel, shown with sample data. Connect it to your own calling workflow.Explore Omni

Keep the parts that already work

Two ways in.
Choose by call type.

Keep Plivo for what it is good at (dependable, no-frills routing) and add the AI layer at PyAI. Forward the numbers you want AI-answered to a PyAI number, or build the AI call path directly on PyAI's OpenAI-compatible voice APIs.

Path 1: Forward calls to PyAI

Keep everything exactly where it is. PyAI provisions a number (or takes your SIP trunk), you point your calls at it, and a PyAI agent answers with your greeting, your knowledge, and your tools. Your platform keeps billing you for lines; the AI layer lives at PyAI.

  1. 01In the PyAI console, provision a number (Phone) or bring your own SIP trunk.
  2. 02Build the agent: pick a voice, write the greeting, connect your knowledge and tools, then call it yourself to test.
  3. 03Set the forward on your side using the hint below, aimed at the PyAI number.
  4. 04Place one real call. The agent answers; the recap and QA land in PyAI and any tools you connected.

On Plivo: Plivo Console: edit the number's application to answer with a Dial to the PyAI number, or set forwarding on the carrier.

Path 2: Integrate via API

No importer needed to start: build the AI leg directly on PyAI and keep Plivo for transport, or adopt PyAI end to end when you are ready.

  • OpenAI-compatible voice APIs: speech-to-text, text-to-speech, and the full Omni voice agent behind one key.
  • AMD for outbound list screening (human vs voicemail) works with any provider that can stream audio, billed per answered call.
  • Managed PyAI numbers exist for the calls you want fully on the new stack.
Explore the Omni SDK path

See the workspace behind it

Make the setup
your own.

Write the instructions, choose a voice and connect the knowledge and tools for the job. Then test the conversation before connecting it to your callers.

Explore Agents

Follow the real Console with a sample workspace, narrated by Aria, our Natural English voice.

Product tour
Actual Console UI · sample workspaceAria Natural · PyAI Speak

Start at the right depth

A useful first call.
Room to build from there.

Call forwarding, API integration and completed-call import are separate paths. Choose the one that fits the workflow you want to run first.

Start with forwarding

Send a selected call type to PyAI and keep your Plivo setup for the rest. Configure the agent, set the transfer path and test a real call before widening the route.

Add the API when it fits

Own more of the call flow or connect speech to your application. Hear and Speak support OpenAI-compatible shapes; Omni uses its native realtime protocol through the official SDK.

Keep import status clear

A native Plivo importer is not available. Start with forwarding or a direct API workflow, and keep the rest of your calling setup in place.

Before you connect the first call

Your platform.
A clearer way in.

Choose the calling path first, then check the current product and import requirements for your setup.

All integrations Explore Telephony
Do I have to leave Plivo to use PyAI?

No. Most teams start with call forwarding: Plivo keeps the lines and the bill, and PyAI answers the calls you point at it. If and when it makes sense, you can also build directly on PyAI's APIs or import completed calls.

What does the AI voice agent actually do on a call?

It answers in your voice and greeting, holds a real conversation at human pace, uses your knowledge base and tools, and can transfer to a human, collect details, or end the call politely. Afterward you get the recap and, with Trace, a compliance scorecard.

Is call import from Plivo available?

There is no native Plivo importer today, and you do not need one to start: forwarding sends the calls you want AI-answered to PyAI. Importer candidates are prioritized by customer demand, so ask.

What does this cost?

You pay PyAI for the calling and call intelligence you run (per-minute calling, Recap or AMD usage); integrations carry no extra fee. Your existing platform bills you as usual for the lines you keep.

Put a voice agent on your Plivo calls.

Sandbox keys never bill. Test the workflow, then fund a live key when you are ready for production traffic.

Get API Key Explore the Agent builder