Bring your own carrier (BYOC)
Bring your own carrier (BYOC) is a telephony setup in which a business connects an existing carrier account or SIP trunk to a separate communications platform instead of buying all calling service from that platform.
The carrier remains responsible for routing calls to and from the telephone network, while the connected platform handles the application logic, such as an AI phone agent's conversation and actions. The connection commonly uses SIP. Inbound calls are routed from the carrier to a platform endpoint, and outbound calls travel from the platform through the business's carrier connection.
Businesses choose BYOC to preserve existing phone numbers, carrier contracts, geographic coverage, routing policies, or account relationships. It can also help a company keep telephony administration separate from the software that answers calls. BYOC does not automatically make a setup simpler or less expensive; the result depends on the carrier agreement, configuration, call destinations, and support model.
Implementation requires both sides of the call path to agree on routing and authentication. A team may need to configure a SIP URI or trunk, permitted source addresses, credentials, caller ID behavior, codecs, and failover rules. Imported numbers may also require verification before outbound use. The exact process varies by carrier and platform.
For AI phone calls, ownership boundaries matter during troubleshooting. Audio quality, caller ID, call completion, and transfer behavior can depend on both the application platform and the carrier. Teams should document who controls each route, where call records are available, and which party responds when a call fails before reaching the agent.
In practice on ThunderPhone
ThunderPhone supports production numbers through supported direct VoIP connections or manual SIP configuration for any SIP trunk. Verified imported numbers can be used for inbound and outbound calling. Inbound demo U.S. numbers are available for testing, but they are inbound-only and are not intended for production. Provider-specific onboarding status can change, so it should be rechecked when planning a connection.