Understanding BYOC in Telerivet: connectivity completeness & orchestration.

Most communications platforms bundle two things together: the workflows and automation that manage your messaging, and the routes those messages travel on. That bundling shapes everything downstream: how you are billed, what you can change without rebuilding, and what happens to your carrier relationships and channel accounts if you ever move to a different platform.

Telerivet separates the two. The platform handles orchestration. The connectivity layer is yours to own, bring, or provision through Telerivet depending on what your situation calls for. This article explains what that means in practice, how the two paths compare, and what you can build on top of whichever connectivity model you choose.

The two paths: provisioned routes and BYOC

Telerivet-provisioned routes mean Telerivet supplies the connectivity directly. You connect a virtual phone number, a WhatsApp Business Account provisioned through Telerivet's Meta relationship, a Viber Business ID, or a USSD access code through a supported in-network provider. Telerivet manages the carrier and channel relationships, billing flows through a single invoice, and setup is straightforward. You are operational quickly without needing to negotiate your own carrier contracts or manage separate channel accounts.

This is the right path when you are starting out in a new market, when you do not have existing carrier relationships worth preserving, or when operational simplicity matters more than cost optimization at scale.

BYOC (Bring Your Own Connectivity) means connecting routes you already own or manage directly: an SMPP connection to a regional carrier, a WhatsApp Business ID registered to your organization, an Android device running a local SIM as a gateway, or a custom HTTP endpoint connecting a proprietary system. The connectivity assets stay registered to you. Telerivet provides the orchestration layer on top.

This is the right path when you have negotiated carrier rates you do not want to replace, when local carrier relationships carry compliance or regulatory value, when you manage connectivity on behalf of multiple clients whose accounts should remain theirs, or when volume makes the per-message economics of ownership meaningful.

Neither path is a workaround for the other. They are structurally different choices suited to different operational situations, and many organizations run both simultaneously: Telerivet-provisioned routes for some channels or markets, BYOC for others.

For a deeper look at how BYOC works across each channel type, including WhatsApp Business ID portability and custom gateway connections, see What Is BYOC? Bring Your Own Connectivity Explained.

Choosing between the two paths

Situation	Recommended path
Starting out, no existing carrier contracts	Provisioned
Operating in a market where Telerivet offers native route coverage	Provisioned
Want a single invoice and minimal account management	Provisioned
Setting up WhatsApp for the first time, or don't have an existing Meta direct account	Provisioned
Have negotiated local carrier rates worth keeping	BYOC
Already have an active Meta direct WhatsApp Business account	BYOC
Managing connectivity on behalf of multiple clients	BYOC
Operating in a market where local SIM routing is the most practical option	BYOC (Android Gateway)
Have an existing aggregator or proprietary gateway you want to extend	BYOC

What you build on top: orchestration and connectivity completeness

Owning or provisioning your connectivity is the foundation. What Telerivet adds above it is routing intelligence: logic that decides which route handles which message, under what conditions, and with what fallback when a primary route is unavailable.

On-network routing In most markets, sending a message from one carrier's route to a recipient on the same network is cheaper than cross-network delivery. If you operate with multiple carrier routes in the same market, Telerivet can apply routing rules that match the outbound route to the recipient's network: traffic to customers on one network goes through that network's route, traffic to customers on another network goes through the corresponding route. The same principle applies in any market with multiple carriers. The cost savings compound at volume.

Fallback routing If a primary route goes offline or delivery fails, Telerivet can automatically route traffic to a secondary connection without manual intervention. For operations where delivery continuity is critical, such as payment confirmations, emergency alerts, or time-sensitive OTPs, that fallback logic runs in the background without your team needing to notice or act. For more on how this works in practice, see The Art of the Failover.

Channel fallback Routing intelligence is not limited to SMS. A message can be attempted on WhatsApp first and fall back to SMS if the contact is unreachable on WhatsApp. A voice call can trigger an SMS follow-up if the call goes unanswered. The logic operates across channels, not just across carriers within a single channel.

Cost-based routing rules Beyond on-network optimization, routing rules can factor in time of day, message type, contact attributes, or destination network to select the most cost-effective route for each send. This is particularly relevant for high-volume operations running across multiple markets with different carrier economics.

Together, these capabilities are what connectivity completeness means in practice: not just having multiple channels available, but having the routing intelligence to use each one optimally. BYOC gives you ownership of the connectivity layer. The orchestration layer is what makes that ownership operationally useful.

How routes connect to the rest of the platform

Whichever connectivity path you choose, the routes you connect work the same way inside Telerivet. The automated services, campaigns, contact management, and workflow logic you build are independent of the connectivity layer underneath. You can add a route, swap a route, or extend to a new channel without rebuilding your services or campaigns.

This also means the platform's capabilities are not tied to which routes you use. The same service, logic, or poll workflow runs identically whether you are sending through a Telerivet-provisioned virtual number, an SMPP connection to a regional carrier, or an Android phone with a local SIM.

For channel-specific setup guidance:

Best practice tip

If you are evaluating whether to bring existing carrier contracts or channel accounts into Telerivet, map your routes before you configure anything. List what you have: SMPP connections, WhatsApp Business IDs, Viber Business accounts, Android devices with active SIMs, aggregator API credentials. Each of those is a connectable route. The question is not whether Telerivet can work with what you have. It usually can. The question is which combination of provisioned and BYOC routes produces the right balance of simplicity, cost, and coverage for your specific markets and volumes.

Reach out to your customer success lead or contact us to map your connectivity options and design the right routing architecture for your operation.