> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gocromo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Qualify and follow up with leads

> Turn qualification rules and incoming leads into consistent research, routing, and follow-up.

This example shows a sales operations team using Cromo to qualify leads consistently, preserve the reasoning, and prepare the right follow-up.

## Outcome

For every new lead, the team wants to:

* check the lead against its ideal customer profile;
* identify missing information;
* assign a qualification level;
* recommend the next action;
* prepare a personalized follow-up;
* keep a reviewable record.

## Add the business context

Add the following material to a **Sales Operations** Project:

* the ideal customer profile as a Source;
* qualification and routing rules as Knowledge;
* approved outreach guidance as Knowledge;
* a **Leads** table with company, contact, source, owner, stage, score, and next action.

If leads already live in another system, connect it through MCP and keep that system as the source of record.

## Prompt to try

Attach the qualification Knowledge and Leads table, then send:

```text theme={null}
Review the new leads added today.

For each lead:
1. compare the company with our ideal customer profile;
2. identify missing information without inventing values;
3. assign a qualification level of high, medium, or low;
4. explain the decision with citations to our qualification rules;
5. recommend an owner and next action;
6. draft a short follow-up email in our approved tone.

Return a review table first. Do not update records or send messages until I approve.
```

## Review the first result

Cromo should return a reviewable table rather than immediately changing external records.

Check:

* whether every qualification rule is cited;
* whether unknown information remains unknown;
* whether the suggested owner follows the routing policy;
* whether the email uses facts present in the Project;
* whether low-quality leads receive an appropriate next action.

After approval, ask Cromo to write the qualification, owner, and next action to the Leads table.

## Make it reusable

Create a Process Skill named **Qualify a sales lead** with the approved evaluation steps.

Then create a Workflow:

```text theme={null}
Create a workflow named Daily lead qualification.

Every weekday morning, find unqualified leads created since the previous run.
Apply the Qualify a sales lead process, prepare a review table grouped by
recommended owner, and save the result as a dated Project file.

Do not send emails. Mark records that need human review and include the reason.
```

Run it manually with a small set of known leads before activating the schedule.

## Add a Dashboard

Ask Cromo to publish a Dashboard with:

* new leads by source;
* high-, medium-, and low-qualified counts;
* leads missing an owner;
* leads with no next action;
* a table grouped by recommended owner.

## Expected result

| Asset         | Example                                          |
| ------------- | ------------------------------------------------ |
| Knowledge     | Ideal customer profile and qualification policy  |
| Data          | Leads table with stable qualification fields     |
| Process Skill | Qualify a sales lead                             |
| Workflow      | Daily lead qualification                         |
| Dashboard     | Qualification pipeline and unresolved work       |
| Files         | Dated review tables and approved outreach drafts |

## Safety checks

* Keep outbound messages in draft until the team approves the process.
* Never infer contact details, revenue, or company size.
* Review changes to qualification rules before the next Workflow run.
* Limit connector credentials to the operations the Workflow needs.