> 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/general/how-to/how-to-dispute-a-1-star-review.md). # How to dispute a 1-star review Receiving a 1-star review can be incredibly frustrating. You work hard to provide a service and may sometimes receive negative feedback on your Google Business Page or Yelp Page. If that does happen, here are some tips to guide you. Public Response: The best approach is to respond to the review in a polite, professional manner. Acknowledge the customer's concerns and apologize for any inconvenience they experienced. Offer to make it right by providing a refund, second consultation free of charge to discuss their concerns or a credit for future service, if applicable. Finally, invite them to contact you directly so that you can further discuss their experience. Posting a response shows that you care about your patients' experience and will acknowledge any issues they experienced. If the 1-star review was inaccurate or created by spam, you can report it. **Instructions for Google:** **Instructions for Yelp:** --- # 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/general/how-to/how-to-dispute-a-1-star-review.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.