Inbound lead enrichment & scoring
New form fills are enriched, scored, and routed to the right rep automatically.
Overview
Every inbound lead is enriched with firmographic data, scored against your ICP, and posted to Slack with a routing recommendation, so reps only spend time on qualified leads.
How this workflow works
- Problem it solves
- Reps waste time manually researching every inbound form fill, most of which aren't a fit.
- Expected outcome
- Qualified leads land in a rep's queue pre-enriched and scored within a minute of form submission.
- Setup time
- 1 hour
Steps
- 01Form submittedA new lead comes in through the website form.
- 02Enrich the contactCompany and role data is pulled from an enrichment tool.
- 03Score against ICPAn agent scores the lead against your ideal customer profile criteria.
- 04Route or discardQualified leads are posted to Slack and pushed to the CRM; the rest are logged for later.
Prerequisites
- CRM with API access
- Enrichment tool account
- Slack workspace
This workflow uses
More in Sales & CRM
Reviews (4)
Genuinely changed how our team ships
We put this in front of real work for three weeks before trusting it near main. It's now part of the default flow, and reviewers spend their time on the parts that actually need judgment.
- Fast to set up
- Caught real bugs
- Occasional context loss on very large diffs
Genuinely changed how our team ships
We put this in front of real work for three weeks before trusting it near main. It's now part of the default flow, and reviewers spend their time on the parts that actually need judgment.
- Fast to set up
- Caught real bugs
- Occasional context loss on very large diffs
Genuinely changed how our team ships
We put this in front of real work for three weeks before trusting it near main. It's now part of the default flow, and reviewers spend their time on the parts that actually need judgment.
- Fast to set up
- Caught real bugs
- Occasional context loss on very large diffs
Genuinely changed how our team ships
We put this in front of real work for three weeks before trusting it near main. It's now part of the default flow, and reviewers spend their time on the parts that actually need judgment.
- Fast to set up
- Caught real bugs
- Occasional context loss on very large diffs