Each environment sends phone one-time codes through providers you connect. There is no Authdog-managed SMS sender. Until a provider that can deliver is connected, SMS sign-in and SMS multi-factor authentication cannot send a code.

Configuration belongs to one environment. Connect a test account in development, then repeat in production with production credentials. Providers do not copy between environments.

## Choose a provider

| Provider | What it sends | Credentials |
| --- | --- | --- |
| **Twilio** | SMS. Also WhatsApp, when a from number is set | Account SID, auth token, and a Messaging Service SID or from number |
| **Vonage** | SMS only | API key, API secret, and a from number or sender ID |
| **MessageBird** | SMS only | Access key and originator |
| **WhatsApp** | WhatsApp only, through a Twilio WhatsApp sender | Account SID, auth token, and the WhatsApp from number |
| **Amazon SNS** | Nothing. Authdog stores the credentials and does not publish the SMS | Access key ID, secret access key, and region |

The provider you connect becomes **Active**. Any others you already connected stay on the environment as fallbacks. Authdog tries the active provider first. After a hard failure it tries the fallbacks, in the order you set.

## Connect a provider

In the [Authdog console](https://console.authdog.com):

1. Select the project and environment.
2. Open **Notifications > Providers**.
3. Select the **SMS** channel.
4. Choose a provider and select **Connect**.
5. Enter the fields below, then select **Connect provider**.
6. Select **Test**, enter a number in E.164 (for example `+15551234567`), and confirm the message arrives.

**Test** walks **Failover order** and stops at the first provider that accepts the message. It sends the text "Your Authdog test message." A **WhatsApp** row sends that text on WhatsApp. Twilio, Vonage, and MessageBird rows send it as SMS. A successful test does not prove every connected provider works.

Secret fields are masked on a later edit and are never loaded back into the browser. Leave a password field blank to keep the stored secret.

> **Caution**
>
> **Manage** does not fill the account SID, API key, region, originator, or sender back in. Saving with those fields empty replaces the stored configuration. Enter them again before you save.

## Twilio

| Field | Required | Value |
| --- | --- | --- |
| **Account SID** | Yes | Starts with `AC`. From the [Twilio console](https://console.twilio.com) |
| **Auth token** | Yes | Stored encrypted |
| **Messaging Service SID** | One of these | Starts with `MG`. Used for SMS |
| **From number** | One of these | E.164, for example `+15551234567` |

SMS needs a Messaging Service SID or a from number. If both are missing, the send fails.

WhatsApp sign-in can use this same Twilio connection, but only when **From number** is the WhatsApp-enabled sender. A Messaging Service SID alone does not send WhatsApp. Authdog prefixes that number with `whatsapp:`.

## Vonage

| Field | Required | Value |
| --- | --- | --- |
| **API key** | Yes | From the Vonage account |
| **API secret** | Yes | Stored encrypted |
| **From number / sender ID** | Yes | E.164 number, or an alphanumeric sender ID the account may use |

The sender has to be one Vonage will accept for the destination country. An alphanumeric sender ID that works in one country is rejected in another. If you leave the sender empty at send time, Authdog uses `Authdog`, which many countries reject.

## MessageBird

| Field | Required | Value |
| --- | --- | --- |
| **Access key** | Yes | A live access key. Stored encrypted |
| **Originator** | Yes | The sender recipients see, such as `Authdog`, or an E.164 number the account owns |

If the originator is empty at send time, Authdog uses `Authdog`. Use a sender MessageBird will accept for those destinations.

## WhatsApp

WhatsApp codes are a sign-in method of their own. They are not SMS, and Vonage or MessageBird cannot send them.

Connect **WhatsApp** with the Twilio account that owns the sender:

| Field | Required | Value |
| --- | --- | --- |
| **Account SID** | Yes | Starts with `AC` |
| **Auth token** | Yes | Stored encrypted |
| **WhatsApp from number** | Yes | The WhatsApp sender, in E.164, for example `+15551234567` |

The number must already be a WhatsApp sender in Twilio. Authdog does not register it for you. A missing from number fails the send even when the same account's SMS tests succeed.

You can skip this card and use **Twilio** instead, as long as that connection has a **From number**. Enable **WhatsApp** only if you want WhatsApp codes. **SMS** and **WhatsApp** are independent toggles.

A WhatsApp-only connection does not send SMS codes. SMS sign-in still needs Twilio, Vonage, or MessageBird.

## Amazon SNS

The **Amazon SNS** card saves an access key ID, secret access key, region, and an optional sender ID. Authdog does not publish SMS through SNS, so that provider never delivers a code. **Test** fails on it and continues to the next fallback. If SNS is the only provider, nothing is sent.

Use Twilio, Vonage, or MessageBird for SMS.

## Failover order

When two or more providers are connected, **Failover order** appears above the cards. Drag a row to choose who sends first. The first row is **Primary**. The rest are **Fallback**. Cards use the same idea: **Active**, **Fallback**, or **Available**.

Authdog tries them in that order and stops at the first success. A provider error, a rejected sender, or a missing from number is a hard failure, so the next row is tried. Reordering saves immediately.

SMS sign-in skips a **WhatsApp** row. WhatsApp sign-in uses only **Twilio** and **WhatsApp** rows, in the same order. Putting WhatsApp first does not make it the SMS sender.

## Turn the method on

Connecting a provider does not enable the sign-in method.

1. For passwordless SMS, open **Authentication > Methods** and enable **SMS**.
2. For WhatsApp codes, open **Authentication > Methods** and enable **WhatsApp**.
3. For a second factor, open **Authentication**, enable **Multi-factor authentication**, and enroll a test user with SMS before you enforce it.
4. Request a code on the hosted sign-in page and confirm a session is created.

SMS as a second factor is not the passwordless **SMS** method. See [Multi-factor authentication](/docs/mfa).

If the provider test succeeds and the sign-in code never arrives, check that the method is enabled on this environment. A provider connected in development does not send for production.

## Security

- Create a send-only credential for Authdog. Do not reuse an account-owner key.
- Store secrets only through the console. They are encrypted server-side and are not returned by provider queries.
- Rotate a credential in development first, then replace the production value and run **Test**.
- Disconnect a provider you no longer use. Disconnecting deletes that environment's configuration for it.
- Do not log one-time codes. SMS and WhatsApp codes can be intercepted, so prefer an authenticator app when you need a second factor.

## Related

| Read | To learn how to |
| --- | --- |
| [Multi-factor authentication](/docs/mfa) | Use SMS as a second factor |
| [Notifications](/docs/console/notifications) | Tell providers apart from alert channels |
| [Email providers](/docs/email-providers) | Configure the email channel on the same screen |
| [Deployments](/docs/deployments) | Keep development and production providers apart |
| [Twilio](/marketplace/twilio/setup) | Connect the Twilio card |
| [Vonage](/marketplace/vonage/setup) | Connect the Vonage card |
| [MessageBird](/marketplace/messagebird/setup) | Connect the MessageBird card |
| [WhatsApp](/marketplace/whatsapp/setup) | Enable WhatsApp codes |
| [SMS code](/marketplace/sms-otp/setup) | Enable passwordless SMS sign-in |
