> 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 Chrome 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.

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.

**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.
* **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.

### **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 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://help.meltingspot.io/english/coach-ai/configuration/managing-hotspots-and-intents.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.