> 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.md). # Customer & Technical Support Here are the people who can help you with all things DoctorLogic! ## Contact your Customer Success Manager Contact your CSM with any questions regarding your account, its performance, or any growth accelerators you've signed up for with DoctorLogic. If do not know who your Customer Success Manager is, visit your DoctorLogic dashboard and reference the side information panel or email . ## Submit a Support Request Please email **** to submit a support request if there are direct changes you'd like to have made to your website. ## **Phone Support** To contact our Customer Support team, please call: [469-458-7101](tel:469-458-7101) To contact our Billing team, please call: [469-458-7149](tel:4694587149) Phone support is available Monday – Friday from 9:00 am – 5:00 pm (CST) --- # 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.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.