> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/pro/help.md).

# Help

Help for Equipme Pro: frequently asked questions from all areas, glossary of provider terms and how to contact equipme support.

* [Frequently asked questions (FAQ)](/pro/help/faq.md): the most frequent questions from all areas of Equipme Pro
* [Glossary](/pro/help/glossary.md): provider terms from A to Z
* [Contact support](/pro/help/support.md): who helps with which issue and what information support needs

**In the app:** The **"Help"** button in the header bar opens help with an AI assistant that answers your questions based on this guide.

{% hint style="info" %}
Questions about your customers' view – such as how a Hosted customer orders, approves or manages their assets – are answered in the customer guide (see customer guide). It is also suitable as material for onboarding your customers.
{% 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://hub.equipme.io/pro/help.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.