> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/settings/configuration/sms-keywords.md).

# SMS Keywords (Text-to-Give)

Create up to two SMS Keywords in Settings > Configuration > SMS Keywords so supporters can text a word to an Anedot number and get a link to your Action Page.

**SMS Keywords** are Anedot's free text-to-give feature, available for all accounts. A supporter texts your keyword to an Anedot phone number and gets a reply with a link to the Action Page you chose. Each fundraising account can have up to two keywords. You manage them in **Settings > Configuration > SMS Keywords**. This article covers keyword rules, and how to create, edit, and delete a keyword.

## Before You Begin

* To create, edit, or delete keywords, you need **Account Management: Edit Account Details and Configuration** permissions.
* You need at least one active or paused Action Page to link a keyword to.

## Keyword Rules

* Use letters and numbers only, with no spaces, dashes, or other symbols. Keywords can be up to 24 characters and are saved in lowercase.
* Each keyword must be unique on its phone number across all of Anedot, so common words are often taken.
* Some words are reserved and can't be used, including **give**, **donate**, **help**, **thanks**, **refund**, **stop**, and **anedot**.

{% hint style="warning" %}
Don't use dashes in SMS Keywords. Use letters and numbers only.
{% endhint %}

Supporters can text your keyword to either Anedot number. You choose the number for each keyword:

* **(888) 444-8774**
* **(800) 500-5858**

## Create A Keyword

To create a keyword:

1. Go to **Settings > Configuration > SMS Keywords**.
2. Click **New keyword**.
3. Under **Action Page**, select the page supporters should reach.
4. Enter your **Keyword**, for example `CityHelp` or `FoodNow`.
5. Under **SMS number**, choose the number supporters will text.
6. Click **Create keyword**.

The keyword appears under **Action Page keywords**. **New keyword** is unavailable once your account has two keywords.

## Edit Or Delete a Keyword

To edit or delete a keyword:

1. Go to **Settings > Configuration > SMS Keywords**.
2. Find the keyword.
3. Click **Edit**, make your changes, and click **Save keyword**. To delete it instead, click **Delete**, then click **OK** in the confirmation prompt.

## Troubleshooting

* **The keyword won't save:** Check that it uses only letters and numbers, isn't a reserved word, and isn't already taken on that number. Try a more specific keyword.
* **Supporters don't get a reply:** Check that they texted the exact keyword to the number you chose for it. If replies still don't arrive, contact our Support team at <help@anedot.com>.

## Related Articles

* [Configuration](/settings/configuration.md)
* [Share an Action Page](/action-pages/action-page-basics/share-an-action-page.md)


---

# 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://docs.anedot.com/settings/configuration/sms-keywords.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.