> 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/support-plans.md). # Support plans ### What support plans are included with my subscription? Your Agency subscription includes access to a support plan that determines the level of assistance you receive. Support is provided only to agency owners—not directly to their customers. #### Step 1: Go to the “Support” section * Click on **Help** from the side menu #### Step 2: Review your support plan * Your current support plan will be shown (Basic, Business, or Enterprise) * Each plan offers different response times and support features {% hint style="warning" %} The Basic plan includes access to email support and the knowledge base. {% endhint %} #### Step 3: Access available support channels * Depending on your plan, you may see options like: * Email support * Live chat * Knowledge base * Call scheduling #### Step 4: Upgrade support if needed * If you need faster response times or dedicated support, upgrade your support plan from the same section by clicking on the Upgrade button from the "Help" menu. --- # 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/support-plans.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.