> For the complete documentation index, see [llms.txt](https://help.getmobly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getmobly.com/help-center/the-mobly-app/capture-and-enrichment/flagging-incorrect-lead-data.md).

# Flagging incorrect lead data

Event badge data isn't always right. Names are misspelled, emails are out of date, titles are stale. When you spot bad data on a lead, you can flag it directly from the app — Mobly takes another pass at enrichment to get the correct information.

## Where to find it

Open the lead's detail screen. Scroll to the bottom. Tap **Flag Incorrect Data · Send to Mobly**.

![Flag Incorrect Data modal](/files/9KEcl4AVqCF8sicbxaBg)

## What you can flag

The form lets you select one or more of seven error types:

* Wrong **name**
* Wrong **email**
* Wrong **phone**
* Wrong **company**
* Wrong **title**
* **Duplicate** lead (this person is already in your records)
* **Other** — a free-text field for things that don't fit the categories

Pick everything that applies and tap submit.

## What happens after you flag

Mobly's enrichment pipeline takes a second pass at the lead, sourcing from premium identity sources to find the correct data. The corrected fields update on the lead record automatically when the re-enrichment finishes.

> **Heads up:** re-enrichment takes a few minutes, sometimes longer for harder-to-match leads. See [How long does enrichment take?](/help-center/the-mobly-app/capture-and-enrichment/how-long-does-enrichment-take.md) for the timing.

## Why bother flagging

Every flag you submit improves identity resolution across Mobly. The flag isn't just for your one lead — it feeds into Mobly's enrichment quality, so the same bad signal is less likely to slip through for the next customer.

## When NOT to flag

* **Typos you can fix directly** — if you can see the right value (e.g., the badge clearly says one thing and Mobly read it as another), edit the field in-app rather than flagging
* **Data that's correct but stale** — if the lead changed jobs and the title is from the old role, flag it (re-enrichment will pick up the new title); but if you have the new title from the conversation, just type it in
* **A lead you're sure isn't in your CRM** — that's a CRM-side issue, not a Mobly data issue

## Related articles

* [How does Mobly's OCR work?](/help-center/the-mobly-app/capture-and-enrichment/how-does-ocr-work.md)
* [How long does enrichment take?](/help-center/the-mobly-app/capture-and-enrichment/how-long-does-enrichment-take.md)
* [How to capture a lead](/help-center/the-mobly-app/capture-and-enrichment/how-to-capture-a-lead.md)


---

# 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.getmobly.com/help-center/the-mobly-app/capture-and-enrichment/flagging-incorrect-lead-data.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.