> 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-your-playbooks.md).

# Managing your playbooks

A playbook corresponds to a website or application on which the AI Coach is integrated. You must create a playbook before you can place hotspots or intents on it.

{% hint style="info" icon="eyes" %}
Creating, viewing, and deleting a playbook is done from the **Playbooks** page in your Spot's settings. The conversational context is configured from a separate page: see Configuring your AI Coach.
{% endhint %}

### **Create a playbook**

1. Go to **Settings > Playbooks**.
2. Click **New**.
3. Enter the target site's URL.
4. The playbook's name fills in automatically.
5. A switch lets you also distribute this playbook on the subdomains linked to it (see [here](#domain-and-subdomains)).
6. Click **Create**.

You are redirected to this playbook's page, where you'll find the list of its pages (👉 more information [here](/english/coach-ai/configuration/managing-a-playbooks-pages.md)).

### Domain and subdomains

By default, a playbook only triggers on the exact domain entered at its creation (for example `acme.com`): the AI Coach will only display its pages, hotspots, and intents on that domain.

For it to also trigger on all subdomains of that site (for example `app.acme.com`, `client.acme.com`), enable the **Subdomains** option — available when creating the playbook, and editable afterwards from its settings.

{% hint style="info" %}
A domain that simply shares the same ending, such as `notacme.com`, is never considered a subdomain of `acme.com`. Only true subdomains (separated by a dot) are covered.
{% endhint %}

On the playbook's card, this option is shown by a prefix in parentheses before the domain: `(*.)acme.com` means the exact domain and all its subdomains are covered.

### **View your playbooks**

The **Playbooks** page displays your playbooks as cards. For each one, you'll find:

* its icon (the target site's favicon, or a generic icon),
* the target site's root URL,
* the number of intents and pages configured,
* the last updated date,
* a red badge indicating the number of pending intents.

Click a card to access the list of pages for that playbook.

### **Deleting a playbook**

From a playbook's page, click **Delete playbook**. Enter "DELETE" in the modal to confirm.

{% hint style="danger" %}
Deleting a playbook also deletes all its pages, hotspots, and intents. This action is irreversible.
{% endhint %}

### **What about conversation?**

A playbook works perfectly well without conversation enabled: the AI Coach can display intents without any conversation being configured. If you enable conversation for this playbook, add specific context to it from the **AI Coach** page (👉 more information [here](/english/coach-ai/configuration/configuring-your-ai-coach.md)).


---

# 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-your-playbooks.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.