> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user-documentation/common-error-issues/bot-not-triggering-not-replying-not-starting-at-all-how-to-solve.md).

# Bot Not Triggering : Not Replying : Not Starting At All , How To Solve ?

There are **two possible reasons** why a bot is not triggering in response to a specific keyword:

1. **A human agent is assigned to the chat or contact.**
2. **The trigger keyword condition is incorrect.**

**Resolving Human Agent Assignment**

* Go to the inbox and find the chat.
* Click on the three dots and select **"**<mark style="background-color:green;">**Mark as done**</mark>**"** to unassign the human agent.

**Correcting Trigger Keyword Condition**

* <mark style="background-color:green;">Double-check</mark> the trigger keyword condition to ensure it is correct.
* Common mistakes include using **"contains,"** **"start with,"** or **"end with"** incorrectly.

After addressing these issues, the bot should start working properly.

If the bot is still not triggering, check the conversation to see if an active bot is already present. If you reply to the conversation, the bot will stop by default. To allow the bot to intervene again, mark the chat as **"done."**

This video can be useful when facing issues in bot.

{% embed url="<https://www.youtube.com/watch?v=O2jToSXf1K4>" %}


---

# 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://helpdocumentation.gitbook.io/user-documentation/common-error-issues/bot-not-triggering-not-replying-not-starting-at-all-how-to-solve.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.