> For the complete documentation index, see [llms.txt](https://help.doctorlogic.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.doctorlogic.com/docs/contact-support/how-to-submit-a-support-ticket.md). # How to Submit a Support Ticket ### In order to submit a request for a website change, please email . Please include your practice name or URL for us to identify your account quickly. Please specify what change you would like made, and if relevant, include a specific URL of the page you want to be modified or a screenshot of the area you'd like adjusted. Common change requests: * Adding a staff member's bio * Adjusting your homepage content * Adding a new menu item * Adding a new patient form * Changing a photo on the site There are a few changes that can easily and quickly be made in real-time through your Customer Admin portal. For more information, please see: This includes changing content through on-page editing, adding a new blog article, publishing new reviews, and more! --- # 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://help.doctorlogic.com/docs/contact-support/how-to-submit-a-support-ticket.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.