> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chatsyncs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# SMS Integration

> Connect an SMS gateway (Plivo, Twilio, Nexmo/Vonage, Clickatell, AfricasTalking, Esahal, or generic HTTP GET/POST) under Control Panel → Settings & Integration to send OTP, marketing, transactional, or notification text messages. Use this when a customer wants their bot to fall back to SMS or send OTPs outside WhatsApp.

<Frame caption="Control Panel → Settings & Integration → API Integration → SMS API, with the New button highlighted.">
  <img src="https://mintcdn.com/chatsyncs/vqDfXbzggyAX9oqx/images/learn/control-panel-sms-integration/step-01-sms-integration-list.png?fit=max&auto=format&n=vqDfXbzggyAX9oqx&q=85&s=f8bc53c63d8f80d1377a1fa28ec3527e" alt="Settings & Integration page with API Integration selected, SMS API selected in the sub-list, and its profile table (empty) with a New button highlighted" width="1258" height="533" data-path="images/learn/control-panel-sms-integration/step-01-sms-integration-list.png" />
</Frame>

**Control Panel → Settings & Integration → API Integration → SMS API** connects an SMS gateway
so your bot or automations can send plain text messages — useful for OTPs and any customer who
isn't reachable on WhatsApp.

Click **New** to add a profile:

<Frame>
  <img src="https://mintcdn.com/chatsyncs/Ma-dImppMzscCHUd/images/learn/control-panel-sms-integration/step-02-sms-profile-modal.png?fit=max&auto=format&n=Ma-dImppMzscCHUd&q=85&s=815676288bcaf40d71e39d6448bb82d3" alt="SMS Profile modal with Profile Name, Auth ID, Auth Token, Sender/From fields and a provider list: Plivo, Twilio, Nexmo/Vonage, Clickatell, AfricasTalking, Esahal, HTTP Get, HTTP Post" width="529" height="544" data-path="images/learn/control-panel-sms-integration/step-02-sms-profile-modal.png" />
</Frame>

## Supported providers

* **Plivo**
* **Twilio**
* **Nexmo/Vonage**
* **Clickatell**
* **AfricasTalking**
* **Esahal**
* **HTTP GET** / **HTTP POST** — for any gateway that isn't natively listed but exposes a simple
  URL-based API

## Required fields

| Field                  | Example                        |
| ---------------------- | ------------------------------ |
| **Profile Name**       | `Twilio OTP`                   |
| **Auth ID**            | Your provider's account/API ID |
| **Auth Token**         | Your provider's secret token   |
| **Sender/From Number** | `+14155550100`                 |

## Use cases

* **OTP messages** — e.g. a login verification code, when the customer can't receive WhatsApp
  right now.
* **Marketing SMS** for customers who opted into SMS but not WhatsApp.
* **Transactional SMS** — order or appointment confirmations.
* **Notifications** — internal alerts sent as SMS to a staff phone.

## Frequently asked

<AccordionGroup>
  <Accordion title="How do I send an OTP over SMS instead of WhatsApp?">
    Connect an SMS gateway under **SMS Integration** (e.g. Twilio), then have your flow send the
    OTP through that profile instead of a WhatsApp template.
  </Accordion>

  <Accordion title="My SMS provider isn't in the list — can I still connect it?">
    If it exposes a simple **HTTP GET** or **HTTP POST** endpoint for sending messages, choose
    that provider type and supply the endpoint details instead of a named integration.
  </Accordion>

  <Accordion title="What credentials do I need from my SMS provider?">
    Typically an **Auth ID**, **Auth Token**, and the **Sender/From Number** the messages will
    appear to come from — check your provider's dashboard for these.
  </Accordion>
</AccordionGroup>