> For the complete documentation index, see [llms.txt](https://docs.yoplanning.support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yoplanning.support/en/general-principles/support-contactez-nous.md).
# Support (Contact Us)
## User guide: how to get help on Yoplanning
### Your first instinct: the Yoplanning AI Assistant
**"AI Assistant" button, bottom left of your Yoplanning interface**
The Yoplanning AI Assistant can single-handedly resolve over 90% of our users' questions. That's why it should always be your first point of contact before reaching out to support: it's available instantly, 24/7, and has in-depth knowledge of how Yoplanning works. Discover everything it can do for you on the [Yoplanning AI Assistant: Capabilities and Usage](/en/general-principles/assistant-ia-yoplanning-capacites-et-utilisation.md) page.
### Formulating your question clearly is the key to getting a helpful answer.
In the vast majority of cases where an answer is unsuitable, the problem lies with the question itself: too vague, incomplete, or lacking context. Here are a few good practices to get a relevant answer the first time:
1. **Describe the problem concretely**: rather than "it doesn't work", explain what you are trying to do, what is happening, and what you expected.
2. **Provide the context**: which feature, which page, which specific action is involved.
3. **Provide specific references**: order ID (REF), email of a customer or relevant staff member.
4. **One question at a time:** If you have several distinct topics, ask them separately to get clearer answers.
### If the AI assistant isn't enough: ask to speak to a human
For more complex or specific situations that the assistant cannot resolve alone, **ask them directly to connect you with support** or escalate your request. They will then forward your message to our team, with the necessary context already gathered, which will expedite the process.
### Would you prefer to write directly to support via email?
#### EMAIL **: **
The same best practices apply:
1. **Use your login email**: When contacting support, make sure you use the email address associated with your Yoplanning account.
2. **Provide precise references:** Include the order ID (REF), the email address of a staff member, or the email address of the relevant customer. Support will have access to your account and will be able to quickly locate your request.
3. **Avoid screenshots**: they are generally unnecessary and do not provide any relevant additional information.
4. **Use videos for complex problems**: If your problem is difficult to explain in writing, record your screen and describe it verbally with [Loom](https://loom.com) (free version available).
### Usage tips and best practices
* **Be specific in your request**, whether you are contacting the AI assistant or email support.
* **Follow up if necessary**: If you have not received a response from support within 48 hours, do not hesitate to follow up.
### Solving common problems
* **No response from support:** After 48 hours without a response, send a follow-up email.
* **Communication problems**: check that the email address used to contact support is the one associated with your Yoplanning account.
### Two types of appointments are possible
Appointment for support, training, and use of Yoplanning. If the AI assistant and our exchanges via email or chat have not been sufficient to resolve your technical problem, make an appointment using the link below.
### [Click HERE to book an appointment with TARA.](https://booking.yoplanning.pro/97197f7e-478f-4cfb-8105-eb6dee1e1ecf/product/95e2e2a5-5faf-4fc2-8744-583497a6809c)
---
# 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://docs.yoplanning.support/en/general-principles/support-contactez-nous.md?ask=&goal=
```
`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.