What is a lead routing decision tree?
A lead routing decision tree is the ordered list of yes/no questions that decides where each new lead goes: is the record ready, does it already have an owner, which territory or segment it belongs to, whether it fits, how fast someone must respond and what happens if nobody does. It makes routing visible before it becomes workflows.
This template is for whoever designs or maintains routing in HubSpot: a RevOps manager, a sales lead or the person who owns the portal. For the reasoning behind each rule and how to set up SLA timers, read the HubSpot lead routing and lifecycle guide.
Get the template: the Lead Routing Decision Tree, a fillable PDF workbook. Enter your name and email and the download starts straight away.
We'll also send occasional HubSpot tips by email. Unsubscribe anytime. See our privacy policy.
Thanks, your download should start now. Download the fillable PDF or the spreadsheet (XLSX).
The spreadsheet has the six questions with a column for your criteria, the five inputs to agree, a territories tab, the build plan and one test case per branch.
What are the questions, in order?
Ask six questions in a fixed order: ready to route, existing owner, territory or segment, fit, response time, then escalation. The order matters. Checking for an existing owner before territory stops a customer's new form fill from landing with a different rep, and checking readiness first keeps junk out of every queue.
- 01 Ready to route?Valid email, country, source, consent, not a duplicateYes Go to 2No Data-quality queue or nurture
- 02 Existing owner?On the contact or its companyYes Keep that owner, go to 5No Go to 3
- 03 Territory or segment match?Region, segment or named accountYes Assign to that team, go to 4No Fallback owner, go to 4
- 04 Meets fit criteria?Your definition of a sales-ready leadYes Lifecycle stage for sales, go to 5No Nurture with a re-entry rule
- 05 Worked within the response time?The SLA for this lead typeYes DoneNo Go to 6
- 06 Owner already reminded?One reminder before escalationYes Reassign or escalateNo Remind, check again
| # | Question | If yes | If no |
|---|---|---|---|
| 1 | Is the record ready to route? (valid email, country, source, consent, not a duplicate) | Go to 2 | Data-quality queue or nurture; fix and re-enter |
| 2 | Does the contact or its company already have an owner? | Assign to that owner; go to 5 | Go to 3 |
| 3 | Does it match a territory, segment or named account? | Assign to that team or owner; go to 4 | Assign to the fallback owner; go to 4 |
| 4 | Does it meet your fit criteria for sales? | Set lifecycle stage for sales follow-up; go to 5 | Nurture with a clear re-entry rule |
| 5 | Was it worked within the agreed response time? | Done; routing ends | Go to 6 |
| 6 | Has the owner been reminded once already? | Reassign or escalate to the sales lead | Send a reminder; check again at the next deadline |
Write your own criteria into each row before you build anything: which fields make a record "ready", what your territories are, what "fit" means and the response time for each lead type.
What do you need to decide before building it?
Five inputs: the required fields for a routable record, the owner field that wins for existing customers, your territory or segment rules, your fit criteria, and response times by lead type. Agree them with sales and marketing in one session; most routing problems are disagreements about these inputs, not about the workflows.
- Required fields: the minimum a rep needs to act, such as email, country, company and source.
- Owner precedence: whether contact owner or company owner wins when they differ.
- Territories: by region, company size, industry or named-account list, with one owner or team for each.
- Fit: the firmographic and behavioral signals that make a lead worth a sales call, written as properties HubSpot can check.
- Response times: per lead type, for example demo requests faster than content downloads, plus who gets escalated to.
How do you build the tree in HubSpot?
Build it as a small set of workflows, one per decision, rather than one huge workflow. Use if/then branches for the questions, owner properties for assignment, the rotate action for round robin within a team, and date properties to stamp assignment and first response so the SLA checks have something to measure.
The rotation step is covered in detail in our HubSpot round robin guide.
- Readiness workflow: checks required fields and duplicates, then sets a "ready to route" property or sends the record to the data-quality path.
- Assignment workflow: enrolls ready records, keeps an existing owner, otherwise branches by territory and assigns or rotates within the team.
- Lifecycle update: sets the lifecycle stage and lead status from the fit check.
- SLA workflow: starts from the assignment time, waits for the response window, then reminds, reassigns or escalates. See the lead SLA workflow.
When we checked HubSpot's documentation in October 2026, rotating leads with workflows needed Sales Hub Professional or Enterprise, and the owners in the rotation needed paid seats. Check your portal before relying on it.
How do you test it before going live?
Create test records for every row of the tree, including the awkward ones: an existing customer, a record missing a country, a lead outside every territory and one nobody answers. Run each through the workflows, check the owner, lifecycle stage and timestamps, and only then switch on enrollment for real leads.
- One test record per branch, named so you can find and delete them afterwards.
- Check the fallback owner receives anything that matches no rule.
- Shorten the SLA wait in a test copy of the workflow to see escalation fire.
- Review the no-owner and data-quality queues every business day for the first two weeks.
Want routing designed and tested for you? We build it as part of our HubSpot RevOps work.
Decision tree checklist
Key takeaway: When the team can see why a lead went somewhere, they can improve the rules instead of guessing at the outcome. Agree the tree first, then build it.
Frequently asked questions
What is a lead routing decision tree?
It is the ordered set of yes or no questions that decides what happens to every new lead: whether it is ready to route, who owns it, how fast someone must respond and where it goes if nobody does. Drawing it first means the HubSpot workflows follow one agreed logic.
Can HubSpot do round robin lead assignment?
Yes. HubSpot workflows have a rotate action that assigns records to a group of owners in turn. When we checked HubSpot's documentation in October 2026, rotating leads with workflows needed Sales Hub Professional or Enterprise, and the owners needed paid seats. Check the current requirements in your portal.
How many branches should a lead routing decision tree have?
As few as your sales team can explain from memory. Most B2B teams need five or six decisions: record ready, existing owner, territory or segment, fit, response time and escalation. Every extra branch is another rule to test and another place for a lead to get stuck.
Sources
HubSpot documentation behind the feature and tier notes above, checked October 2026. HubSpot changes features and tiers often, so check your own portal too.