> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/integrations/twilio.md).

# Twilio SMS

Connect Twilio to send supported event SMS notifications and reminders.

## Connect

An admin opens **Settings → Integrations → Twilio SMS** and enters the **Account SID**, **Auth token** and **Sending number**. Use an international number such as `+14155551234`.

Saving reads the Twilio account to verify the credentials. It does not send an SMS. Confirm that the number, messaging permissions and destination coverage are suitable in Twilio.

## Configure a message

Choose an SMS-capable template and attach it to the event's intended audience and timing. Ensure the booking captures a usable recipient phone number. Review email fallback when the editor offers it.

Use [Meeting reminders](/scheduling/reminders.md) for timing and [Meeting messages](/scheduling/messages.md) for lifecycle behavior.

## Test delivery

Make a controlled booking with an approved test recipient. Check the message and Twilio delivery result. A template preview does not send.

If no message arrives, check recipient formatting, trial-account restrictions, sending-number capability, destination rules, credits and the reminder's pending/cancelled state.

SMS billing comes from your Twilio account. A successful credential check is separate from carrier acceptance and delivery.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.distro.so/integrations/twilio.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.