> For the complete documentation index, see [llms.txt](https://docs.bito.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bito.ai/help/support-and-questions/getting-support.md). # Getting support Get help or engage with Bito community ## E-mail Please write to us at [**support@bito.ai**](mailto:support@bito.ai) for any issue you might face with Bito. We would love to hear feedback, comments, feature requests, and how Bito improves your development experience. ## Engage with Community Engage with our constantly growing Slack community. {% embed url="" %} ## Bito Github Bito Github is growing. Engage with your fellow developers at ## Response Time We respond to all support requests within **1 business day** (Monday–Friday, 9 AM – 6 PM IST). ## Slack App Support Using Bito inside Slack and need help? * **Bug reports & questions:** email with subject "Slack App – \[your issue]" * **Installation help:** see the [Slack integration guide](/ai-architect/integrating-ai-architect-with-your-tools/integrating-with-slack.md) * **Data deletion requests:** email with subject "Slack Data Deletion Request" ## Security Issues Report security vulnerabilities or concerns to [**support@bito.ai**](mailto:support@bito.ai). We respond within 24 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.bito.ai/help/support-and-questions/getting-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.