> 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/placing-intents-point-and-click.md).

# Placing intents (point & click)

Once Edit mode is activated (👉 more information [here](/english/coach-ai/set-up/meltingspot-extension.md)), place your hotspots and create your intents directly on your product's pages.

{% hint style="info" icon="key" %}
Intents created from the extension are always created with a "pending" status: you write a description, and the content is then associated from the settings (👉 more information [here](/english/coach-ai/configuration/managing-hotspots-and-intents.md)).
{% endhint %}

### **The Edit mode toolbar**

The toolbar contains:

* the MeltingSpot logo,
* a **Pages** button, which lists the playbook's pages. Clicking on one of these pages redirects you to the page's base URL, in Edit mode,
* a central area ("intent zone") that adapts based on the page's content,
* navigation arrows between hotspots.

#### **Page without a hotspot**

**New intent** button with two options: **Add to a new hotspot** or **Add to the entire page**.

#### **Page with hotspots**

The area displays the content of the first hotspot:

* its name in a blue box (red if the targeted element can no longer be found),
* the list of its intents (resource icon if the intent is published, grayed out if it's a draft, and a dotted circle if it's pending),
* **Edit hotspot** button,
* button **+**: new intent on this hotspot, on a new hotspot, or on the entire page.

### **Creating a new intent**

#### **Launching selection mode**

On launch, the cursor changes and a highlight frame follows the mouse, with the message **Click to place the intent**. Normal clicks are intercepted during this mode.

#### **Targeting**

* **Element**: click on the element. Its CSS selector is captured.
* **Full page**: no targeting, the intent is displayed on the entire page.

#### **Writing the description and configuring the hotspot**

1. **Write the intent's description**: describe what this content should cover.
2. **If working with a new hotspot:**
   1. **Place the hotspot** (if new): a toggle lets you select the hotspot type (full page or element). For an element, you see the CSS selector's detail,
   2. **Strictiness**: a bar lets you set the precision level of the CSS selector,
   3. **Highlight with a coach icon** lets you add or not a small icon at the hotspot's location.
   4. A **Replace hotspot** button lets you go back into selection mode
   5. The **hotspot's name**.
3. **Link to page**: choose an existing page or click **New page** (static URL corresponding to the current page).

{% hint style="info" icon="eyes" %}
For an intent on an already existing hotspot, only the description is required.
{% endhint %}

Click **Save** to create the intent in "pending" status. You then need to go to the Spot settings to publish it.

{% hint style="info" icon="key" %}
If you close after starting a description, a confirmation will ask if you really want to leave without saving.
{% endhint %}

### **Editing an existing hotspot**

Navigate to the hotspot and click Edit hotspot. To target a different element, click Replace hotspot: selection mode restarts, then a confirmation validates the change.

{% hint style="info" icon="eyes" %}
Renaming, changing the page, and deletion are also managed from the Spot settings (👉 more information [here](/english/coach-ai/configuration/managing-hotspots-and-intents.md)).
{% endhint %}

### **Exiting Edit mode**

**X** button on the toolbar or the settings panel, or the extension popup.

{% hint style="info" icon="key" %}
If a change is in progress, a confirmation will ask if you really want to leave without saving.
{% 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/placing-intents-point-and-click.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.