> For the complete documentation index, see [llms.txt](https://learn.doubletick.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.doubletick.io/bot-studio/default-bots/set-up-stop-bot.md).

# Set Up Stop Bot

Learn how to set up a stop bot on DoubleTick. Allow users to opt out of communications instantly, respecting their preferences and ensuring compliance.

***

## Working of Stop Bot

When it comes to customer communication management, the Stop Bot serves a crucial role in ensuring users have control over their interactions. Instead of bombarding customers with messages they may not wish to receive, the Stop Bot enables them to halt further communication until they're ready to engage again. 

Here's how it operates:

* Upon encountering the keyword "<mark style="color:red;">**STOP**</mark>" in any customer interaction, the Stop Bot immediately halts any further communication attempts.&#x20;
* In practical terms, if a user chooses to opt out of communication by clicking on the "<mark style="color:red;">**STOP**</mark>" button or explicitly entering the keyword "<mark style="color:red;">**STOP**</mark>," the Stop Bot is triggered.
* Subsequently, the bot delivers a predefined custom message set by the administrator. This message acknowledges the user's decision to opt out and provides any necessary instructions or information.
* Following the activation of the Stop Bot and the delivery of the custom message, the user is automatically opted out of further communication. Unless the user explicitly opts back in, they will not receive any additional messages from the system.

***

## Configure Stop Bot

* Navigate to the Bot Studio in the left panel
* Under the default bot, locate and select the **Stop Bot**
* Once on the "**Manage your Stop Bot**" page, click on the edit icon <img src="https://2303112206-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F53n17VnOICC1LtDqlENV%2Fuploads%2FpM9L64mgEhQgB8XFxqTR%2Fimage.png?alt=media&amp;token=35b0ce39-3f76-4258-93cc-346b1f5204ae" alt="" data-size="line">

<figure><img src="https://2303112206-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F53n17VnOICC1LtDqlENV%2Fuploads%2FBrihOyiHGOJWlQ38Tmjg%2Fimage.png?alt=media&amp;token=16cfcd30-76a4-4656-9fc5-c5cf4799a430" alt=""><figcaption></figcaption></figure>

* On Configure bots window, click on the "<mark style="color:green;">**Change Message Button**</mark>" button; If you desire to customize the default message
* Enter the new message and then click on the "<mark style="color:green;">**Set Message**</mark>" button to apply the changes

<figure><img src="https://2303112206-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F53n17VnOICC1LtDqlENV%2Fuploads%2FSJI4CIYzghK51eq8LLym%2Fimage.png?alt=media&amp;token=3765f376-551d-4c9d-bae7-51cadbf73c90" alt=""><figcaption><p>Upon successful configuration, a message will appear "<mark style="color:green;"><strong>Action set successfully!</strong></mark>"</p></figcaption></figure>

* To enable/active the welcome bot click on the toggle switch on the top right coner

<figure><img src="https://2303112206-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F53n17VnOICC1LtDqlENV%2Fuploads%2FkYqCRC8RYxfKXqqY7YCB%2Fimage.png?alt=media&amp;token=7dc575cb-12da-4f1b-84db-2922582b0209" alt=""><figcaption><p><em><mark style="color:green;"><strong>Configuration of the Stop Bot is now complete</strong></mark></em></p></figcaption></figure>

***


---

# 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://learn.doubletick.io/bot-studio/default-bots/set-up-stop-bot.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.