key, home, house, estate, business, mortgage, real, loan, new, property, rent, agent, buy, apartment, investment, sale, building, hand, lock, housing, owner, purchase, residential, sign, unlock, security, person, key, mortgage, mortgage, mortgage, mortgage, loan, loan, property, property, property, rent, rent, rent, rent, rent, apartment, apartment, investment
Photo by mastersenaiper on Pixabay

Lead Routing

Part of Inbound lead routing

Matching enquiries to the right product or service owner

Map service enquiries to a first responder, resolve overlapping requests and give uncertain enquiries a clear triage route.

This is an editorial pen name used by the publication, not a claim of an independently verified personal identity. Original editorial credit: Desk Qualification.

Why an enquiry lands with the wrong owner

A misrouted enquiry usually fails at one of two points: the workflow's routing criteria did not match the record, or the intended owner was not eligible to receive the enquiry. Treat it as a data problem and a people problem, and check both.

Matching starts with naming the owners. A product owner owns a product in its entirety and is responsible for maximising the value it creates. A service owner is accountable for the quality, performance, benefits and outcomes of a service, providing end-to-end direction, prioritisation, risk management and decision making.

Ownership narrows further than those two roles. A feature owner manages a major capability, a component owner an architecture building block, a platform owner a platform of shared software assets, a portfolio owner a group of related products, and a SAFe product owner the product details. The enquiry goes to the owner whose scope contains it.

Matching is literal. Records must match branch criteria exactly, including spelling, capitalisation, spacing and format, so a value of CA will not match criteria written as California. Product names, service lines and plan tiers all need consistent values in the property the branch reads.

Enrol only the enquiries you mean to route

Routing begins at enrolment, not at the branch. If your branch needs a certain number of properties to contain values, add all of those properties to the enrolment trigger. Records must match the branch criteria before reaching the branch in the workflow.

If five contact properties are required to evaluate a branch, add those five properties to the enrolment trigger. The record then waits until the data is complete rather than being routed on partial information.

List the fields the owner decision relies on and put them in the trigger: the property naming the product, service or region, any property a branch checks for a value, and any field that distinguishes new business from an existing customer's enquiry.

Pick the field that decides the owner

In HubSpot, a value equals branch is based on one property or action output and automatically configures multiple branches from it. Each possible value becomes a path leading to the relevant product or service owner, so a single property can define the whole routing map.

Choose a property whose values are product or service names and whose ownership is unambiguous. If one value can be claimed by two owners, the branch has no way to choose between them, and the mapping has to be settled before the branch is built.

An enquiry that names two products arrives with more than one value, and a value equals branch sends it down the None met branch because it is not an exact match. Use an if/then branch and select the is any of criteria instead.

Work out which owner takes an enquiry that spans two products: a platform owner holds shared software assets, and a portfolio owner holds a group of related products, so one of those scopes may contain both items. Where no single scope covers both, that choice is a business decision, not a branch setting, and it has to be made before the branch is published.

Adding branches to workflows requires Edit permissions for workflows or Super Admin permissions; publishing a workflow requires Publish permissions. A Random distribution by percentage branch needs a Marketing Hub Professional or Enterprise subscription.

Give the enquiry time to settle before it is routed

Where values may not be populated when the record is enrolled, add a five-minute delay at the start of the workflow. The record then reaches the branch with its properties filled rather than empty.

Add a five-minute delay before the branch when the criteria depend on engagement with content from a previous action in the workflow, such as a contact opening a marketing email sent earlier. The delay gives the contact time to engage before the decision is made.

The same five-minute delay applies when branch criteria have dependencies, such as a property update from a form submission, so the record has time to update. For branches based on analytics such as page views, use an eighty-minute delay before the branch to give the analytics sufficient time to refresh.

Straight down the line, or spread across the team?

Once the branch has settled which owner receives the enquiry, the Rotate record to owner action assigns records to paid sales and service users. It works on the record owner property or any custom HubSpot user property.

By default, enrolled records are assigned equally within a selected team or between specified users. For ticket or lead (BETA) records the action offers additional distribution options: load balanced, round robin and random.

Those default distribution rules apply to most record types but do not apply to lead or ticket-based workflows. If there is no eligible user to rotate to, or no team is selected for team-based assignment, no owner will be assigned at all.

Key Requirements for Enquiry Routing Success

Required HubSpot Subscription
Marketing Hub Professional or Enterprise (for random distribution)
Minimum Active Users per Team
At least one user with a paid Sales/Service Hub Pro/Enterprise seat
Permissions Required
Edit permissions (workflow), Publish permissions (to deploy)

Keep the owner pool eligible

When assigning to specific users, each user must be active with an assigned Sales or Service Hub Professional or Enterprise seat. Users with core or view-only seats, or who have not accepted the invite to join the account, are greyed out.

When assigning to a team, the team must contain at least one user with an assigned Sales or Service Hub Professional or Enterprise seat, otherwise the team is greyed out when you set up the action. Only main team members with such a seat are eligible; extra team members are not included.

If the account is opted into the Support Multiple Main Teams for Full Functionality beta, all team members become eligible for assignment. Deactivated users, and users who no longer hold a paid seat, appear in routing rules with a red border and are excluded from assignments.

Expect counts to reset, and watch synced owners

If you add or remove owners from the action after the workflow has been turned on, the assignment counts for that action reset and the random assignments start again. Newly enrolled records rotate evenly across all selected owners or team members, regardless of past distribution.

Where the owner property syncs to Salesforce, the action may not work as expected: Salesforce may try to update HubSpot with the previous owner even after HubSpot clears ownership. When assigning leads with this action, turn off the Sync lead owner with contact or company owner setting.

After changing seats, team membership or the Salesforce sync setting, re-check the routing action, because both who is eligible and how the load is spread will have changed.

More from Lead Routing

Lead Reporting

Monitoring leads that received no response

Find genuine enquiries without a verified reply, separate pending from overdue cases and resolve each exception against the original request.

Lead Routing

Inbound lead routing

Route inbound enquiries to an accountable responder, maintain a monitored fallback and find requests that have not received a reply.