Telnyx (bring your own number)

The Telnyx connection lets you use phone numbers from your own Telnyx account with a ThunderPhone agent. Telnyx continues to provide the number and telephony connection; ThunderPhone provides the agent configuration that handles the conversation. After a number is imported and verified, it can support inbound and outbound calling.

What the Telnyx connection does on ThunderPhone

ThunderPhone provides a guided Telnyx setup as well as a path for connecting an existing account. The guided flow covers account creation, a Telnyx v2 API key, and connection testing, and it provisions what it needs on the Telnyx side before saving the connection. The same connect-import-verify flow is also available through the REST API, where credentials can reference an existing Telnyx SIP connection.

Connecting an account is only the first part. You then import the numbers you want to use and run a round-trip verification. That check confirms that inbound calls can reach ThunderPhone and that the number is authorized for outbound calling. A verified number can be assigned to an inbound agent, an outbound agent, or both.

This is a telephony connection, not a business-data integration. The Telnyx connection carries calls. Agent behavior comes from the ThunderPhone prompt, attached knowledge, and tools. Post-call automation can be handled separately through REST or signed webhooks.

Typical call flows

Inbound front desk

A customer calls a Telnyx number the business already publishes. The Telnyx connection routes the call to the assigned ThunderPhone inbound agent. The agent follows its deployed prompt, answers questions from attached knowledge where configured, collects the reason for the call, and follows the routing rules you define. This is a practical foundation for a virtual front-desk receptionist or after-hours answering flow.

Outbound follow-up

ThunderPhone places a call through the verified imported number and runs the assigned outbound agent. The prompt can define the purpose, required questions, and next step. If voicemail answers, the agent can decide what to do, hang up, or leave a configured message. Common applications include lead follow-up and outbound notification campaigns.

Call escalation

An inbound agent can gather context before routing the caller. When a production number is eligible to place an outbound SIP leg, ThunderPhone can use an attended warm transfer: the caller waits while the agent privately briefs the recipient, then connects the parties after acceptance. Transfer behavior should be tested with the actual number and trunk configuration before launch.

Setup outline

  1. Open Connections → VoIP in ThunderPhone and choose the guided Telnyx setup or the existing-account path.
  2. Create or copy a Telnyx v2 API key and paste it into the connection form; the flow provisions the required connection on the Telnyx side.
  3. Select Connect & Test so ThunderPhone can verify the credentials and connection before saving.
  4. Open Phone Numbers, choose Add number → Connect VoIP provider, and import the production numbers you want to use.
  5. Run verification for each imported number. Fix any failed inbound reachability, trunk assignment, or outbound authorization check and retry.
  6. Assign the inbound and outbound agents, test the intended flows, and deploy any draft agent changes before sending production traffic.

Keep provider credentials current. When a key changes, test the replacement credentials before updating the saved connection. Telephony charges and number costs remain dependent on your provider setup.

Related reading