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 →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.
Default behaviour
Leave from out of the request and the platform injects a sender from the connection's configured list. When a connection holds several senders, they are rotated with smooth weighted round-robin, and the caller is not told which one carried the message.
For most integrations this is the behaviour you want: you do not have to track which number is currently healthy.
When to specify from explicitly
An explicit from always wins over the automatic choice. Reach for it when the number is part of the message's meaning rather than its infrastructure.
- A support line the recipient is expected to reply to.
- A number already published on a website or an invoice.
- A per-region or per-brand number where the sender itself carries information.
Reply matching does not depend on the sender
Opt-out suppression is keyed on tenant plus recipient number, not on the sending number. Rotating senders will not route around a STOP, and changing the sender does not reset anyone's consent state.
Keep reading
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.
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 →