HubSpot lead routing: how to make sure no lead waits

Start with what the form collects

Routing can only use what you know. If you want to send Finnish leads to one person and enterprise leads to another, the form has to ask for the country and the company size, or HubSpot has to know them already.

• Use dropdowns for routing fields. “Finland”, “finland” and “FI” are three different values to a workflow. A dropdown gives you one.
• Ask only what you’ll use. Every extra field costs submissions. If a field doesn’t change who gets the lead or what they say, drop it.
• Use hidden fields for things the visitor shouldn’t have to choose, such as the page or campaign the form sits on.

Agree what each stage means

Before you automate anything, agree with sales what a lead is. HubSpot’s lifecycle stages (subscriber, lead, marketing qualified lead, sales qualified lead, opportunity, customer) and the lead status property only help if everyone reads them the same way. Write down when a contact moves from one stage to the next and who moves it. The workflows then follow those rules, rather than inventing them.

The routing workflow

A typical setup is one contact-based workflow, triggered by a submission of the forms that should go to sales:

1. Check for an existing owner. If the contact, or their company, already has an owner, notify that person and stop.
2. Branch by the routing rules. An if/then branch on country, company size or the service they asked about.
3. Assign the owner. Either set a specific owner, or use the rotate action to share leads evenly within a team.
4. Set the lifecycle stage and lead status, so reports and views reflect the new lead.
5. Create a task for the owner, due today, with the form answers in the task description.
6. Notify the owner by email or in the HubSpot app, with a link to the contact.

Catch the leads that slip

Routing fails quietly: someone’s on holiday, a notification lands in a busy inbox, a task gets buried. Add a safety net to the same workflow:

1. Add a delay, for example four working hours.
2. Branch on whether the lead has been contacted, using the last contacted date or the lead status.
3. If not, notify the team lead, or reassign the contact to the next person in the rotation.

Use the workflow’s execution times so the delay only counts working hours, and so leads that arrive on Friday evening don’t trigger an escalation on Saturday morning.

Measure it

Build a simple report: new leads per week, by owner, and the time from form submission to first contact. If one person’s leads consistently wait, the routing rules or the workload need adjusting. If no leads wait, the system is working, and nobody had to remember anything.

Common mistakes

• Routing every form to sales, including newsletter sign-ups, until sales stops reading the notifications.
• Free-text routing fields, so half the leads fall through the branches into a default owner.
• No owner for the default branch. Every branch, including “none of the above”, needs someone.
• Forgetting people who leave. When someone leaves the team, update the rotation and reassign their open leads.