# Twilio

Use Twilio in Redbelt to receive permitted text messages on your own enrolled phone. Redbelt provides the sending service; you do not need to create a personal Twilio account.

## Before you start

Open **Customize → Plugins → Twilio**. Check package availability, then follow the phone-enrollment steps below. Redbelt's configured sending service and workspace policy must permit the action. Adding the package alone is not phone enrollment or consent. Enable the plugin for the selected agent or task and review any requested [action approval](/threads/approvals/).

![Use Twilio plugin in Redbelt](/screenshots/current/plugin-twilio.png)

Plugin details under **Customize → Plugins**. The button shows the current installation state.

## Enroll before requesting a reminder

1. Open the Twilio plugin page and find **Receive Texts on My Phone**.
2. Review the enrollment and consent information, then enroll your own eligible U.S. mobile number.
3. Follow [SMS Enrollment and Consent](/sms-enrollment/) for the full user-facing requirements and opt-out process.
4. Prepare a concise appointment reminder with an explicit date and time zone.
5. Review the destination and message before requesting a send. Inspect the result rather than assuming enrollment itself sent anything.

> Prepare an appointment reminder for my enrolled phone. Ask me for the date, time, and time zone, and include a request to review the agenda beforehand. Show me the message before sending it.

## Understand the limits

Adding the plugin does not grant SMS consent. The send operation requires an approved, enabled destination under Redbelt's enrollment rules; it is not an unrestricted way to text arbitrary numbers.

SMS use follows your workspace's allowance and spending settings, including any permitted overage. Enrollment and a successful provider request are different states. An unavailable sending service or exhausted allowance can prevent delivery even when the plugin is installed.

Opting out prevents further permitted sends under the enrollment rules. A message already in transit may still arrive. Use the existing consent article as the authority for enrollment wording and availability; do not infer live provider approval from this guide or the plugin's Add button.

## Tool Reference

Thread and workflow availability are listed separately. A tool must also be enabled for your task and allowed by its account and administrator policy. [Configure workflow app actions](/workflows/apps/) using only actions offered by the current picker.

### Available Tools

| Tool              | Required Fields | Thread | Workflow |
| ----------------- | --------------- | ------ | -------- |
| `twilio.send_sms` | `body`          | Yes    | Yes      |

Required fields above are the schema minimum. The target, selected operation, or account can impose additional requirements.

**`twilio.send_sms`** — Send a transactional SMS using the connected Twilio account’s configured default sender.
Optional fields: `to`.

## Troubleshoot

If sending is unavailable, check enrollment, destination approval, workspace SMS settings, and administrator configuration. Do not work around an unenrolled or disabled destination.

Provider details: [Twilio messaging documentation for administrators](https://www.twilio.com/docs/messaging).
