Workflows
Can You Categorize Leads Automatically?
Yes. You can categorize leads automatically using the information in an enquiry, form or CRM record. Start with categories that tell your team what to do next. A useful label might identify the requested service, an existing customer or an enquiry that needs clarification.
Key takeaways
Define each category in everyday language with positive and negative examples.
Separate the requested service from urgency, owner and sales stage.
Test on labelled examples before allowing categories to trigger customer messages.
Use fixed rules for explicit fields such as the service selected on a form. Use text classification when the enquiry is written in free text. Keep a Needs review category for missing or conflicting information, record the reason for each label and let the team correct it.
- Collect the enquiry
- Check existing records
- Apply clear rules
- Review uncertain cases
- Assign the next action
Choose categories that lead to an action
Use a short, stable list. For a business automation service, useful categories might be Reporting, Document workflow, Lead follow-up, Existing customer support and Needs review. Each should have a definition and an owner.
Avoid mixing different facts in one label. A lead can ask for reporting automation and need a reply today. Keep service interest, urgency and sales stage in separate fields so changing one does not erase the others.
| Enquiry evidence | Suggested category | Next action |
|---|---|---|
| Form explicitly selects reporting | Reporting | Assign the reporting owner |
| Existing customer asks about a failed job | Existing customer support | Route to the agreed support process |
| Message asks about both documents and reporting | Needs review or multiple interests | Person chooses the primary next step |
| Message contains too little detail | Needs review | Prepare a clarifying question |
Apply explicit rules before AI
If the visitor chose a service on a form, use that selection unless it conflicts with other important information. Check whether the CRM already holds an owner or an active support case. Preserve an approved manual label instead of overwriting it on every run.
Write the rule order down. For example, an existing support request may take priority over a keyword that looks like a new sales enquiry. Native CRM branching can handle clear property-based rules. HubSpot’s workflow documentation describes condition-based branches; availability depends on the subscription and permissions.
Use AI for the parts that need interpretation
Free-text messages can mention the same need in different words. A classifier can propose one of your allowed categories and return the phrase that supports its choice. Give it the category definitions and ask it to choose Needs review when the message does not fit.
Treat the enquiry text as data. A sentence inside it that says to ignore the rules must not change the workflow’s instructions or permissions. Validate the returned category against the allowed list before writing to the CRM.
A model’s confidence score is not proof of correctness. Use your labelled test set to decide which cases can pass automatically and which need review. Keep the original message available to the reviewer, with access limited to the team handling it.
Example: classify three incoming enquiries
An illustrative enquiry says, “We copy sales figures into a weekly spreadsheet and email it every Friday.” The workflow proposes Reporting, records that supporting phrase and creates a task for the reporting owner. It does not send a quote.
A second message says, “Our existing reminder stopped yesterday.” The CRM shows an active customer record, so the workflow routes it to support. A third message says only, “Can you help?” That goes to Needs review with a suggested clarification task.
The team can correct any category. Save the old value, new value, reviewer and reason. Feed those corrections into the next rule review rather than quietly changing live behaviour without checking the effect.
Test the labels before they trigger actions
Collect representative examples and have someone label the expected category. Use made-up records or approved, minimized examples during setup. Include ambiguous messages, two services in one request, existing customers, irrelevant messages and a duplicate submission.
Compare the proposed category with the expected one. Count incorrect automatic labels separately from cases sent for review. A system that appears accurate by sending everything to review may save little work. A system that guesses every label may create costly handoffs.
Check a repeated submission against a stable enquiry ID or another agreed duplicate rule. If the same lead arrives twice, update the existing task where appropriate rather than contacting the person twice.
Keep the next action under control
Categorization can create an internal task without automatically sending an email, changing a deal value or promising delivery. Add those actions only after the team agrees the trigger and review rule. A service-interest label alone is not consent to marketing.
Automations For Business can help connect your forms and CRM, define categories, test the routing and keep a manual review path. Bring a few representative enquiry examples and the next action you want for each. The downloadable brief gives you a starting point.
Your ready-to-use checklist
0 of 7 checked
Make the next step clear.
Lead categorization rules and test sheet
Free templateSources and notes
Sources checked on October 27, 2026.
- HubSpot: use branches in workflows
Condition-based CRM routing and subscription requirements.
- Microsoft: condition actions in Power Automate
A documented example of branching a workflow using conditions.
