> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/support/scope-of-assistance.md). # Scope of assistance ### What level of support do each plan offer and which one should I choose? AppMySite offers different support plans based on the scope of assistance you require. These plans are: * Basic plan- Response times depend on volume of support queries received. Scope of support includes email. * Business plan- Response time is 24 hours. Scope of support includes chat and email. * Enterprise plan- Response time is 8 hours. Scope of support includes chat, email, and call. The Basic Plan is ideal for simple apps, providing general guidance suitable for beginners and small projects. The Business Plans are designed for apps with advanced features and plugins, offering technical troubleshooting and step-by-step support for complex issues. Finally, the Enterprise Plan is recommended for large, mission-critical apps, providing top-tier support, comprehensive assistance, and performance optimization. It's important to note that the response time mentioned in our support plans is specifically for critical issues that may arise due to downtime in AppMySite’s technical infrastructure. For non-critical inquiries, we aim to address them as promptly as possible during our regular 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.appmysite.com/support/scope-of-assistance.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.