> 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/nlp/natural-language-processing-nlp/train-your-nlp.md).

# Train your NLP

Make sure to train your NLP so that your bot understands your users based on your latest model.

## Train the NLP

To train your NLP:

1. On any section of our platform, you will find an **Train NLP** button available in the top right corner, next to **Publish**.
2. Click on **Train NLP**.

<figure><img src="https://2786867680-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LLTwFwbOqJj4dDhg8Ju%2Fuploads%2FT6esPCmHDofVTnAyayRB%2FScreenshot%202024-06-04%20at%2016.53.41.png?alt=media&amp;token=81b9b662-b33a-4f58-94cf-183b9024a342" alt="" width="312"><figcaption><p>Train your NLP.</p></figcaption></figure>

### Why training your NLP

It's important to train the NLP model, especially after making significant changes such as[ adding new intents](/navigation/natural-language-processing-nlp/intents.md#add-a-new-intent) or modifying [entities](/nlp/natural-language-processing-nlp/detect-information-with-entities.md). Here's why:

* Reflect change&#x73;**:** new changes made to the NLP model, such as adding intents or entities, won't take effect until the NLP is trained.
* Testin&#x67;**:** by updating the NLP, you can easily test the impact of these changes on your chatbot's performance. This allows you to fine-tune and validate your bot's behavior.

### Track the NLP update status

To know if your NLP is successfully done training, either:

* After updating NL&#x50;**:** Once you have initiated the NLP training process, you can check the status of the update.
* Click notifications: To check the status, click on the notification icon. This will display the progress and status of the NLP update.
* Monitor progres&#x73;**:** You can monitor the progress and ensure that the update is successfully completed.

<figure><img src="https://2786867680-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LLTwFwbOqJj4dDhg8Ju%2Fuploads%2FHVUWkEZGNKiJ5lUaTpKl%2FCopy%20of%20Copy%20of%20Copy%20of%20Copy%20of%20Copy%20of%20Copy%20of%20Copy%20of%20Copy%20of%20Copy%20of%20Copy%20of%20Copy%20of%20Copy%20of%20Copy%20of%20Copy%20of%20Copy%20of%20Copy%20of%20Copy%20of%20Copy%20of%20Copy%20of%20Copy%20of%20Copy%20of%20Copy%20of%20Copy%20of%20Copy%20of%20Copy%20(2).gif?alt=media&amp;token=1c83659b-e019-4c60-93c4-915dab76a81a" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Do you want to learn how you can improve your NLP model? You can find tips and tricks in [this article](https://docs.chatlayer.ai/tips-and-best-practices/how-to-nlp).
{% endhint %}


---

# 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/nlp/natural-language-processing-nlp/train-your-nlp.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.
