Channels and connections

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.

4 min read · updated 2026-10-13

What the built-in check does

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.

Note. Treat a passing check as "the form was filled in correctly". It is not evidence that the credentials are valid or that the sender is authorised.

The only test that proves it

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.

  1. Send to your own number

    Send a message you can read. Mark it TRANSACTIONAL so suppression rules cannot quietly swallow it.

  2. Look it up in the log

    Find the row for that send. It carries the message ID, the provider and the normalised status.

  3. Read the status honestly

    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.

What a failure is telling you

  • An authentication error means the credentials themselves are wrong, not the route.
  • A rejection naming the sender means the number or sender ID is not authorised for that destination — a registration problem, which is yours to resolve with the provider.
  • A rejection naming the destination means the country or network does not accept this sender type.
  • No error at all and no arrival means the message was accepted and the outcome is still unknown — diagnose it with the "messages accepted but not arriving" article.

Keep reading

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.

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.

Read this article →