For the complete documentation index, see llms.txt. This page is also available as Markdown.

Enrichment and lead statuses

When you scan or add a lead, Mobly does two things behind the scenes: captures the raw info off the badge or card, then enriches it — pulling extra data about the person and company from our data sources. The mobile app shows a label on each lead so you always know where your lead is in the process. Once enrichment finishes, the label disappears and the lead is ready to work.

Capturing…

The lead is being uploaded from your phone to Mobly. Usually a few seconds. If you scanned a badge or business card, OCR (optical character recognition) also runs during this step, pulling name, email, and phone off the image.

For more on OCR — what it extracts, how offline scanning works, tips for cleaner scans — see How does Mobly's OCR work?.

Enriching…

The lead is on the server and automated enrichment is running — looking up the company, title, LinkedIn, industry, and so on. You'll usually see this label for a few minutes as fields fill in.

Still working…

Enrichment is still running. Data accuracy is a big deal for Mobly, and verifying some fields can take extra time — nothing to do on your end; the automated pipeline keeps going.

In manual queue…

This field didn't populate from our data providers, so a person is working to fill it in. The rest of the lead is still workable — the label just tells you one piece of info is still coming.

Working the lead while enrichment runs

You don't have to wait for enrichment to finish to work the lead. Notes, qualifiers, favoriting, and engagement actions (email, calendar, share content) all work while a status label is showing. The label just tells you the enrichment pipeline hasn't caught up yet.

About the Hub

These status labels are a mobile-app view today. The Hub shows leads as either enriched or not-yet-enriched, without the more detailed lifecycle labels. If a lead looks enriched in the Hub but the mobile app still shows a working label, it's the two views measuring different things — not a sync bug.

Last updated

Was this helpful?