> For the complete documentation index, see [llms.txt](https://docs-v3.toucantoco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-v3.toucantoco.com/additional-ressources/support-for-app-builders.md).

# Support for App-builders

For any assistance, we offer comprehensive support through <help@toucantoco.com>.

When reaching out to us, kindly provide the following details:

1. A clear description of the issue you are facing.
2. The URL of your project and small-app related to the problem.
3. A step-by-step account of the actions that led to the error.
4. If possible, include screenshots or videos illustrating the issue.

**Business Hours**

Our support operates during the following business hours:

* France: Monday to Friday, 10:00 am to 6:00 pm CET (Central European Time)
* USA: Monday to Friday, 9:00 am to 5:00 pm EST (Eastern Standard Time)

Please note that our support team observes public holidays and will respond promptly during the specified business hours.


---

# 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://docs-v3.toucantoco.com/additional-ressources/support-for-app-builders.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.
