> For the complete documentation index, see [llms.txt](https://gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.com/docs/help/contact-support.md). # Contact support There are two ways to get in touch with GitBook's support team: * Submit a support request from the GitBook app. Click the **question mark** icon in the sidebar, click **Contact us**, then click **Send us a message**. * Email directly. Before reporting an issue, check [GitBook's status page](https://www.gitbookstatus.com/) for any outages affecting the app or the third-party services it relies on. For issues you may be able to resolve yourself, see Troubleshoot the GitBook app. #### What to include Include all the relevant details so the team can help you as efficiently as possible: * If your request relates to specific content, include a link to it. * Describe the steps you're taking, what happens when you take them, and what you expect to happen instead. * If you're running into an error message, include the error message in full. * Screenshots — or a short video showing the steps you're taking — are extremely helpful. For app issues, the team may ask for a network capture. See Report a bug. #### When you'll get a response GitBook aims to respond to every message within one business day. At busy times this might not be possible, but the team always gets back to you as soon as they're able. Support isn't real-time — you'll be notified when there's a reply. The support team works Monday to Friday, from 9 am to 5 pm GMT (+/- 3 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://gitbook.com/docs/help/contact-support.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.