> 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/apps/opportunities/lead-management/how-to-dispute-a-lead.md).

# Dispute a Managed Chat lead

The 4 qualifying facts for a lead are: 

* Name
* Procedure
* Phone Number
* Email

If you receive a lead that does not have 1 of these qualifying factors, you are welcome to dispute it. 

To dispute a lead, follow these simple steps:

* Log In to your [Admin Dashboard ](https://admin.doctorlogic.com/)
* On the Left Hand Side, select "**Opportunities**"
* Find the chat lead that you wish to dispute 
* Above the Chat Box, select "Dispute"

#### The Dispute button will only be available for 72 hours after the lead was submitted.

*\*Please Note: Each dispute will need to be verified by our team.\**


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.doctorlogic.com/docs/apps/opportunities/lead-management/how-to-dispute-a-lead.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.