> 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/benefits-of-a-customer-success-manager.md). # Benefits of a Customer Success Manager When it comes to website performance and success, a customer success manager is an invaluable asset. This role involves providing guidance and support to DoctorLogic customers throughout the customer journey from onboarding through the launch of the site and beyond! With the help of a customer success manager, businesses can improve their website performance by tracking important metrics such as website visits, user engagement, and SEO rankings. The primary goal of a customer success manager is to ensure customers get the most out of their DoctorLogic services. Our skilled customer success managers will provide guidance on optimizing website performance to maximize conversions and drive revenue growth. They’ll also monitor key metrics such as page load times, bounce rate, and SEO rankings to identify areas for improvement. Additionally, they will be able to provide feedback on user experience design and suggest tactics to increase sales or create repeat business opportunities. --- # 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/benefits-of-a-customer-success-manager.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.