> For the complete documentation index, see [llms.txt](https://docs.mercuri.cx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mercuri.cx/features/ai-assistants/faqs.md).

# FAQs

<details>

<summary><strong>How do I train the AI Assistant on the provided data?</strong></summary>

<figure><img src="/files/ms781YiQBJlNb91xxtET" alt=""><figcaption></figcaption></figure>

After adding your knowledge sources (Sitemaps, URLs, and FAQs), you can train the AI Assistant in two ways:

* From the agent card menu by clicking the **three-dot menu → Train Agent**
* From the agent card menu by clicking the **three-dot menu → Edit**, navigate to the **Settings** tab, and click **Train Agent**

<figure><img src="/files/YyVvX7Ax2zZbQsNvSZpc" alt="" width="563"><figcaption></figcaption></figure>

The AI Assistant will then process and train on the provided data so it can use that information while responding to users.

> ⚠️ Whenever you update the knowledge base or FAQs, it is recommended to retrain the agent to apply the latest changes.

</details>

<details>

<summary><strong>How do I set the AI Assistant to Test or Live mode?</strong></summary>

<figure><img src="/files/C6d7kx8RDWn2Fg1QmsXr" alt=""><figcaption></figcaption></figure>

After training the AI Assistant, you can change its mode(Test / Live) from the agent card menu.

1. Go to the **AI Assistants** section
2. Locate the required agent card
3. Click the **three-dot menu** on the card

From here, you can select:

* **Set to Test** – The AI Assistant will only respond to the configured test phone numbers
* **Set to Live** – The AI Assistant will start responding to all users on the connected channels

> ⚠️ It is recommended to first test the AI Assistant in **Test Mode** before switching it to **Live Mode**.

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mercuri.cx/features/ai-assistants/faqs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.