> 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/configuration/managing-hotspots-and-intents.md).

# Managing hotspots and intents

A hotspot targets a specific interface element or applies to an entire page. An intent is the training content attached to that hotspot.

{% hint style="info" icon="eyes" %}
Hotspots and intents are created from the MeltingSpot extension, in point & click mode (👉 more information [here](/english/coach-ai/configuration/placing-intents-point-and-click.md)). This article covers their management from the settings: organization, statuses, audience, processing of pending intents.
{% endhint %}

### **Viewing a page's hotspots**

From a playbook's page list, click a page to display all its hotspots. Filter by status:

* **All**: all intents.
* **Published**: hotspots with published intents.
* **Draft**: hotspots with draft intents.
* **Pending**: hotspots with pending intents.

Search for an intent by content title or description, or a hotspot by its name.

### **A hotspot's card**

Each hotspot is displayed as an expandable card. There you'll find:

* the hotspot's name,
* the list of associated intents, reorderable by drag-and-drop,
* a badge indicating the number of pending intents.

{% hint style="warning" icon="eyes" %}
When a hotspot has several intents, this order isn't just cosmetic: it's also the order in which the AI Coach evaluates them to decide which one to offer the user (👉 more information [here](#which-intent-is-shown-when-there-are-several)).
{% endhint %}

From a hotspot's edit menu:

* **Rename the hotspot**.
* **Change the page** it's on.
* **Edit hotspot** (redirects to the extension, selection mode).
* **Delete the hotspot** — also deletes all its intents.

### Which intent is shown when there are several?

When a hotspot carries several intents, the AI Coach goes through them in the card's order (the drag-and-drop order) and displays the **first one that isn't currently hidden** by its own display rules.

An intent can be hidden for different reasons: its content has already been completed, the user recently closed it, or it's temporarily paused after a "Later". Hiding is specific to each user and changes over time: an intent hidden today may become eligible again tomorrow.

{% hint style="info" %}
If all of a hotspot's intents are hidden for a given user, the AI Coach doesn't force anything but stays discreetly signaled (a "raised hand" icon) on the first one. The user can click on it to open it anyway (👉 more information [here](/english/coach-ai/user-experience/triggering-the-ai-coach.md#muting-rules)).
{% endhint %}

**Intent statuses**

**Draft**: not visible to your users.

**Published**: active, visible to the relevant audience.

**Pending**: created via the extension with a description, not yet linked to content. Awaiting processing by an admin.

Publish or revert an intent to draft via its card's menu: **Publish** or **Convert to draft**.

### **Editing an intent**

From an intent card's menu:

* **Edit intent**: modify or unlink the connected content.
* **Conditions**: set how often the content reappears (see further below).
* **Audience**: if the content is private or secret, manage the groups and members who have access to it.
* **Statistics**: view views and clicks.
* **Change hotspot**: move the intent to another hotspot (redirects to the extension).
* **Delete**: delete the intent.

### Configuring reappearance conditions

From the **Conditions** tab of an intent's edit panel, set how often its content can reappear to a user who hasn't closed it. These settings drive the behavior described in Triggering the AI Coach (👉 more information [here](/english/coach-ai/user-experience/triggering-the-ai-coach.md)).

Two groups of settings:

**Repetition**, how often unclosed content can reappear while the member hasn't acted on it.

* **No limit** (default): the content follows the closing rules below.
* **Only once**: once shown, the content never reappears again for this member.
* **Once per days**: the content doesn't reappear within 24h of its last display.
* **Until content completion**: only available for content with a notion of completion, such as courses, live sessions, and learning paths.

**Dismiss and reappear rules**, for the **Later**, **Close** (before content opening), and **Close** (after content opening) buttons. Set the reappearance delay for each, in hours, in days, or **Never** for permanent hiding.

{% hint style="info" %}
Choosing **Only once** greys out the dismiss and reappear rules. They are no longer used.
{% endhint %}

### **Processing pending intents**

Pending intents are displayed in a separate section of the hotspot's card. For each one:

1. Open the edit drawer to read its description.
2. Link existing content via the search bar, or create new content (tooltip).
3. Click **Save as draft** or **Publish** to turn it into a draft or published intent, respectively.

{% hint style="success" %}
Content suggestions matching the description may appear automatically.
{% 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://help.meltingspot.io/english/coach-ai/configuration/managing-hotspots-and-intents.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.