> For the complete documentation index, see [llms.txt](https://docs.bravostudio.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bravostudio.app/need-some-help/production-support.md). # Production support Get an extra hand with your app-building process Speed up your app building process with the help of our support team. We will help you solve any question such as backend recommendations, 3rd party tools integration, Bravorizing, feature set up or any other inquiries. ## Email support Add email support to your Solo plan. Our dedicated support team will assist you with your inquiries.\ \ What's included: * Direct support from Bravo Team. * Response time around 48 hours from 10am to 5pm CET on business days. * Price: 49€/month For more information, please contact [^1] ## What can we help you with? Our Technical Support team can help and provide guidance with the following topics: * Setting up the design file in Bravo Studio. * Creating API requests with the Data Library. * Data Binding: connecting data to the app screens. * Errors with app bundle generation for publication. Due to Bravo's flexibility allowing integration with any 3rd party APIs for app data storage, **we don't support specific backend API or tool integrations or setups**. For assistance, refer to the API documentation and tutorials of the tool being used. These resources typically provide comprehensive information on using the API with your Bravo app. Additionally, the third-party tool may offer support services to address any questions. [^1]: --- # 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.bravostudio.app/need-some-help/production-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.