Connect your own provider account
Bring-your-own-account keeps the agreement, the sender reputation and the invoice with your CPaaS provider. Here is how to connect one, and what changes once you do.
Read this article →Route across providers with priority and weight
Bind a key to more than one provider and the platform becomes the routing layer — balancing load when all is well, failing over when it is not.
Two dials, two jobs
Routing is controlled by two independent numbers on each channel. They answer different questions, which is why using only one of them cannot express both common setups.
| Dial | What it decides | When it acts |
|---|---|---|
| priority | Which channel takes over when another fails | Only when a channel fails |
| weight | How traffic is split while all channels are healthy | Only while all are healthy |
The distinction is deliberate: weight alone cannot express "keep the backup idle until the primary breaks", and priority alone cannot express "send three for every one".
The rule at send time
- All weights equal → ordered failover. The lowest priority number is tried first and the rest stand by until it fails.
- Weights not all equal → smooth weighted round-robin, so the split follows the weight ratio, with the remaining channels covering failures.
Note. The send response and every receipt name the provider that actually carried the message, so reconciliation never depends on guessing which channel was used.
Turn it on
Connect a second provider
Channels → Add connection, one per provider account you want in the rotation.
Bind the key to both
A single API key can send over several channels. This is what puts the platform in the routing path.
Set priority and weight
Give each channel its failover order and its share of healthy traffic.
Verify with one send
Read the provider field in the response — it tells you which channel carried the message.
Sender numbers rotate inside a channel too
A channel's sender numbers are expanded into virtual channels that join the same rotation, weighted by channel weight × sender weight. Rotating senders is how you work around a provider's per-number concurrency limit without changing your integration.
The rotation is transparent: you keep sending to the same endpoint, and the platform decides which number leaves the building.
Keep reading
Sender numbers and how they are chosen
Most senders never specify a from address, and that is usually correct. Here is when to override it.
Read this article →Verify a connection before you rely on it
The built-in check only validates the fields you typed. Here is the test that actually proves a connection works.
Read this article →