> 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/set-up.md).
# Set up
Before you can display the AI Coach on your product, two steps are required.
The first is technical: a developer on your team integrates the script provided by MeltingSpot into your site or application. Without this script, no hotspot or AI Coach window can be displayed, even if the configuration is ready.
The second is editorial: you install the MeltingSpot extension, which lets you navigate your product pages in Edit mode and place your hotspots and intents visually, without touching any code.
These two steps are independent and can be done in any order. In practice, you can prepare your entire configuration from the extension even before the script is installed — your users won't see anything until the script is in place.
Installing the AI Coach on your product: the script to integrate, via the Deploy your coach button
---
# 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/set-up.md?ask=&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.