> 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/add-ons/managed-chat/qualifying-lead.md). # Qualifying Managed Chat Leads What is a qualifying lead? When it comes to new opportunities, we want to ensure that you and your facility only receive the most quality leads. That's why if your new lead, or opportunity, does not meet these 4 qualities, you will able to dispute it. * Name * Procedure * Phone Number * Email If you receive any lead or opportunity that does not have all of these 4 qualities, you are able to [dispute it](/docs/apps/opportunities/lead-management/how-to-dispute-a-lead.md) for up to 3 business days afterward. To dispute a lead, please log into your DoctorLogic Portal, click on the Opportunities menu item, and then select the specific lead in question. If it says "NOT BILLABLE"-- you're good to go! If it says "BILLABLE", for 72 hours after the lead, the red "Dispute" button will be available. {% content-ref url="/pages/-MAY6adauEHchQnrw4Ju" %} [Dispute a Managed Chat lead](/docs/apps/opportunities/lead-management/how-to-dispute-a-lead.md) {% endcontent-ref %} --- # 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/add-ons/managed-chat/qualifying-lead.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.