Get started

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

ThunderPhone's current provider table does not list a direct Plivo account connector. The supported framing is Manual SIP configuration, which accepts any SIP trunk. 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. It also tests the route end to end before saving it.

You then import the production number and run round-trip verification. The inbound check confirms that a call can reach ThunderPhone. The outbound probe confirms that the trunk authorizes ThunderPhone to place calls for that number. Only a verified imported number becomes active for assignment to agents.

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

  1. 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.
  2. Open Connections → VoIP in ThunderPhone, create a new connection, and choose Manual SIP configuration.
  3. Enter the SIP domain or URI, authentication if required, port, and transport. Add allowed source IPs when your trunk restricts traffic by source.
  4. Select Generate AI Setup Guide, then apply the resulting trunk-side routing instructions in your Plivo setup.
  5. Run Test & Save Connection. Correct any reachability, authentication, or authorization failure before continuing.
  6. Import the number under Phone Numbers, run its inbound and outbound verification, and assign the appropriate inbound or outbound agent.
  7. 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.

Related reading