Open for Plivo

Plivo remains the controlling side of the call. Your Plivo application keeps owning numbers, XML response logic, and CDRs. Open is a SIP destination your XML can Dial or your Zentrunk can route to. When a call should be handled by AI, Plivo forwards the SIP INVITE to Open, and the AI picks up over the same SIP/RTP session your application already speaks.

For inbound, the simplest path is to return a Plivo XML response with a Dial element targeting the Open SIP URI on the calls you want AI'd. If you're on Zentrunk SIP Trunking, you point the trunk's outbound rule at Open instead — same effect. Either way, the IVR, recording, and analytics you already use on Plivo stay intact because Plivo is still in the path.

For outbound, Open opens a SIP session against your Zentrunk termination URI using the digest credentials Plivo issues per endpoint. Calls show up in your Plivo CDRs the same way human-dialed calls do, with whatever caller ID Plivo has approved on the trunk. You can run AI-driven outbound — payment reminders, lead callbacks, surveys — from Open while staying invoiced by Plivo.

What the AI does on the call: it listens, reasons over your knowledge base and the tools you've connected (CRM, ticketing, calendar, payments), and acts. It looks up an order, creates a ticket, schedules a callback, sends a payment link, or warm-transfers to a human via SIP REFER with the live transcript and detected intent attached. Every call is recorded and trace-logged.

Billing stays predictable. Plivo bills you at-cost for carrier minutes; Open never marks them up. Open charges per resolved conversation, not per agent or per seat.