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 →The built-in check only validates the fields you typed. Here is the test that actually proves a connection works.
Adding a connection runs a field-level check: required fields present, values shaped as expected. It is a form validation, not a live call to your provider — so a connection that passes the check can still fail on the first real send.
Send one real message to a number you control, then read the outcome. That single send exercises credentials, sender authorisation and the route to a destination — none of which the field check touches.
Send a message you can read. Mark it TRANSACTIONAL so suppression rules cannot quietly swallow it.
Find the row for that send. It carries the message ID, the provider and the normalised status.
Delivered means credentials and route are fine. Failed means read the error code. Accepted with no receipt yet means wait and re-read — absence of a receipt is not failure.
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 →Most senders never specify a from address, and that is usually correct. Here is when to override it.
Read this article →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 →