> For the complete documentation index, see [llms.txt](https://support.pipefile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pipefile.com/reminders-and-notifications/sms-reminders.md).

# SMS reminders

Text recipients their request link, reminders and status updates in addition to email.

{% hint style="info" %}
Available on the **Professional** and **Enterprise** plans, and during the free trial. [Upgrade your plan](https://pipefile.com/dashboard/settings/account/upgrade).
{% endhint %}

With SMS, Pipefile texts recipients who have a phone number on the request. Texts go out alongside emails, not instead of them. A recipient with only a phone number gets texts only.

## Add a phone number

On plans with SMS, every recipient card on a new request has a **Phone Number (Optional)** field. A recipient needs a name and either an email address or a phone number. See [Create and send a request](/requests/create-and-send-a-request.md).

Visitors to your [lead forms](/intake/lead-forms.md) and [profile page](/intake/profile-page.md) can also give a phone number. They must tick **Text me about this request** to agree to texts, or remove the number, before they can continue.

## What gets texted

| Event                                                   | Text                                                                                  |
| ------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| You send the request                                    | The subject and the request link, followed by a second text: "Reply STOP to opt out". |
| A reminder goes out (automated or **Send reminder**)    | "Reminder" with the subject and the request link.                                     |
| You approve, reject or mark a checklist item incomplete | The item name, the result and the request link.                                       |
| You mark the request completed                          | A short completion message.                                                           |
| You reopen the request                                  | "Request Reopened" with the subject and the link.                                     |

Reminder texts follow the request's reminder schedule, the same as reminder emails. See [Reminders and notification sequences](/reminders-and-notifications/reminder-sequences.md).

Texts are sent in the request's language. See [Send requests in another language](/requests/translations.md).

## Write your own texts

A [notification sequence](/reminders-and-notifications/reminder-sequences.md) has an **SMS** version of each message. Switch to **SMS** at the top of the sequence editor to write them. Your **Initial Request**, **Reminders** and **Completed** texts replace Pipefile's wording; review texts always use the standard wording above. The same `{{ variable }}` placeholders work as in email. Pipefile adds the request link to the end of the initial and reminder texts for you.

Keep texts short. Long messages are split into several texts by the carrier.

## Opt-outs and failed numbers

* **Replying STOP** stops all texts to that number. If the recipient has no email address on the request, they're unsubscribed from it.
* **A number that can't receive texts** (invalid, landline, or delivery failed) is marked unreachable, and Pipefile stops texting it. Email continues if the recipient has an address.

To reach someone whose texts stopped, add or correct their email address on the request.

<details>

<summary>I added a phone number but the recipient got no text</summary>

Check that your plan includes SMS: on plans without it, the phone field doesn't appear and no texts are sent. Then check the number is a mobile number, and that the recipient hasn't replied STOP to an earlier Pipefile text. If texts still don't arrive, email `support@pipefile.com` with the request link.

</details>


---

# 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 by asking a question.

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

```
GET https://support.pipefile.com/reminders-and-notifications/sms-reminders.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 `automate deployments from our CI pipeline` 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.