> ## 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 in ChatSyncs

> How to connect an SMS gateway (Plivo, Twilio, Vonage, Clickatell) so ChatSyncs can send OTP, marketing, or transactional texts to customers outside WhatsApp.

In ChatSyncs, **Chatbot Manager → \[your bot] → Integrations → SMS** 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. It sits alongside HTTP API, Google Sheets, Autoresponder, and Email
on the same Integrations tab.

Click the button to add a profile, then fill in the **SMS API** modal:

<Frame>
  <img src="https://mintcdn.com/chatsyncs/sAsjFfzcUITpKpey/images/learn/sms-integration/step-01-sms-api-profile-modal.png?fit=max&auto=format&n=sAsjFfzcUITpKpey&q=85&s=c5459a5cebb1e5b6355c0e159c025d61" alt="SMS API 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="780" height="869" data-path="images/learn/sms-integration/step-01-sms-api-profile-modal.png" />
</Frame>

## Supported providers

* **Plivo**
* **[Twilio](/learn/chatsyncs-integrations/sms/connect-twilio-for-sms-with-chatsyncs)**
* **Nexmo/Vonage**
* **Clickatell**
* **[AfricasTalking](/learn/chatsyncs-integrations/sms/connect-africas-talking-for-sms-with-chatsyncs)**
* **Esahal**
* **[HTTP GET](/learn/chatsyncs-integrations/sms/connect-a-custom-sms-gateway-via-http-get-with-chatsyncs)** / **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>