Skip to main content
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:

​
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:
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

​
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.