> For the complete documentation index, see [llms.txt](https://docs.chatlayer.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chatlayer.ai/buildabot/tips-and-best-practices/improve-the-not-understood-block.md).

# Improve the Not understood block

## Improve your Not understood user experience

A nice and bot-persona fitted message explaining something like 'Sorry I did not understand that' is the least your bot could do for repair.

Yet, there are several ways to make your Not understood experience even better.

### Use AI to find and generate an answer

* Use GPT to generate an answer.
* Use Knowledge base AI to retrieve an answer from your database.

### Use workarounds to continue the conversation

* Create a [counter ](https://docs.chatlayer.ai/tips-and-best-practices/not-understood-bot-dialog/not-understood-counter)where, after a certain amount of times the user sees a different 'not understood' message than the first message.
* Show the [previous](https://docs.chatlayer.ai/tips-and-best-practices/not-understood-bot-dialog/go-to-previous-bot-dialog) block after the 'not understood' message is shown.
* A specific 'not understood' message per [intent below the NLP threshold.](https://docs.chatlayer.ai/tips-and-best-practices/not-understood-bot-dialog/intent-recognition-below-threshold)
* Create a [google search](https://docs.chatlayer.ai/tips-and-best-practices/not-understood-bot-dialog/not-understood-google-search) for 'not understood' messages.


---

# 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.chatlayer.ai/buildabot/tips-and-best-practices/improve-the-not-understood-block.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.