> For the complete documentation index, see [llms.txt](https://help.meltingspot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.meltingspot.io/english/coach-ai/user-experience.md).

# User experience

This section describes what your users experience once the AI Coach is in place on your product, regardless of any admin configuration.

The AI Coach window appears when hovering over a hotspot, when loading a targeted page, or on the coach's own initiative. It displays a preview card, then the full content when clicked. If two-way conversation is enabled, the window remains permanently visible on all the playbook's pages, and the user can ask their questions whenever they want.

To avoid repeatedly prompting the user about the same content, the AI Coach applies automatic triggering rules (auto-dismiss, temporary muting based on previous actions). By default, these rules are the same for all Spots. However, the admin can customize repetition and delays **intent by intent**, from **Settings > Playbooks**, in an intent's menu > **Conditions** (👉 more information [here](/english/coach-ai/configuration/managing-hotspots-and-intents.md#configuring-reappearance-conditions)).

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>The AI Coach window</strong>: appearance, triggering, moving, and behavior.</td><td><a href="/english/coach-ai/user-experience/the-ai-coach-window.md">The AI Coach window</a></td></tr><tr><td><strong>Triggering the AI Coach</strong>: the two states (beacon / full content), auto-dismiss, and muting rules.</td><td><a href="/english/coach-ai/user-experience/triggering-the-ai-coach.md">Triggering the AI Coach</a></td></tr><tr><td><strong>Conversations with the AI Coach</strong>: what the coach can do, how it adapts, and when it redirects to a fallback.</td><td><a href="/english/coach-ai/user-experience/conversations-with-the-ai-coach.md">Conversations with the AI Coach</a></td></tr><tr><td><strong>Proactive messages</strong>: when the coach steps in on its own initiative, and what it suggests.</td><td><a href="/english/coach-ai/user-experience/proactive-messages.md">Proactive messages</a></td></tr></tbody></table>


---

# 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://help.meltingspot.io/english/coach-ai/user-experience.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.