Plivo (bring your own number)

A Plivo number can connect to ThunderPhone through the platform's manual SIP path. You keep the number and trunk with Plivo, then configure the SIP route that carries calls between that trunk and a ThunderPhone agent. After the connection and number pass verification, the number can support inbound and outbound calling.

What the Plivo connection does on ThunderPhone

Plivo connects over SIP. In ThunderPhone's VoIP setup, Plivo has its own tile that opens the manual SIP form with Plivo-specific steps, and the saved connection is a manual SIP configuration; there is no API-key Plivo account connector. In practical terms, ThunderPhone does not need a provider-specific workflow to handle the call: it needs the trunk's SIP domain or URI and, where required, authentication and network settings.

The connection form supports an optional username and password, port, transport, and allowed-source-IP list. ThunderPhone can generate provider-specific instructions for the configuration that belongs on the trunk side. Before saving, Test & Save Connection checks that the SIP domain resolves to a public address and, for TCP or TLS, accepts a connection on the chosen port (UDP gets the DNS check only). It cannot place a call yet, because the connection has no numbers.

Once connected, import the number. Importing verifies it: ThunderPhone places a short test call from the number, through your Plivo trunk, to a ThunderPhone number. That proves the outbound path, including your credentials, trunk selection and whether the carrier accepts the call; the number becomes active only after it passes. It does not call your number, so it does not test inbound routing. To prove that, call the number from any phone and confirm the assigned inbound agent answers.

This scope is intentionally narrow. The SIP connection transports calls; it does not imply a native synchronization of contacts, messages, or other Plivo account data. Use an attached agent tool, REST workflow, or signed ThunderPhone webhook separately when a call needs to trigger work in another system.

Typical call flows

Support intake on an existing number

A customer calls the Plivo number already associated with the business. The SIP trunk routes the call to the assigned inbound agent. The agent follows its deployed prompt to identify the request, answer supported questions from attached knowledge, and collect the details a human team needs. This is a common pattern for customer-support triage.

Missed-call recovery

A separate workflow can decide when to place a callback through the verified number. The outbound agent follows its prompt, confirms why the customer called, and collects the next action. ThunderPhone's REST surface can place outbound calls, while webhook events can report call completion to your server. The Plivo SIP connection remains the telephony route rather than the business-workflow engine.

Scheduled notifications

For a defined contact list and calling window, a ThunderPhone outbound campaign can place calls using the imported number. The agent handles the conversation and follows its configured voicemail behavior. This can support outbound notification campaigns, subject to the consent, notice, and calling rules that apply to your organization.

Setup outline

Identify the Plivo SIP trunk and production number you want to use. Confirm the trunk can receive calls for the number and authorize the outbound direction you need.
Open Connections → VoIP in ThunderPhone, select New connection, choose Connect a provider you already use, then pick Plivo.
In the Plivo console, create an outbound trunk with a new credential. Enter its Termination SIP Domain (<trunk-id>.zt.plivo.com), username and password, plus port and transport if needed. Add allowed source IPs when your trunk restricts traffic by source.
Create an inbound trunk whose Primary URI is the ThunderPhone SIP endpoint shown on the form followed by ;transport=tcp, then set each number's Application Type to SIP Trunk and pick that inbound trunk. The form links Plivo's guide, and Generate AI Setup Guide can write step-by-step instructions.
Run Test & Save Connection. If it fails, correct the Termination SIP Domain, port or transport, or the network path to it, before continuing.
Import the number under Phone Numbers → Add number → Import existing numbers. Its verification call tests the outbound path; if it fails, correct the outbound credential or trunk settings and verify again. Then assign the appropriate inbound or outbound agent.
Call the number from any phone to confirm inbound routing; if it does not reach ThunderPhone, check the number's Application Type, the inbound trunk's Primary URI and any source restriction. Then test realistic calls, including caller silence, voicemail, routing, and any human handoff, before sending production traffic.

Telephony charges and number costs depend on your Plivo account and trunk configuration. Keep that provider setup separate from ThunderPhone's agent usage and configuration.