Lead routing assigns leads or enquiries to people or teams responsible for handling them.

Start with an enquiry whose assigned destination you cannot explain. Read the request beside the rule, identify the intended handler and make any unresolved assignment visible. Then check what actually happened, including whether the receiving person was notified.

Write the rule beside the input

Name the information a rule uses and the person or team it selects. If location determines the destination, identify where that location came from. Leave a missing location unresolved rather than guessing it from an unrelated detail.

HubSpot documents manual owner selection as well as workflow assignment. Its workflow guidance permits branching by different criteria and requires a Professional or Enterprise subscription. Those are conditions of the documented product feature, rather than requirements for every routing process.

Trace a fictional equipment-hire enquiry

Imagine a rental team receiving this invented request: “I need a projector for an event.” The team has chosen to assign enquiries by event location, but the message gives no location. Its chosen fallback is central review, where someone asks for the missing detail.

Fictional routing plan and checks
Input or conditionChosen handlingEvidence to check
Event location missing.Central reviewer asks for location; branch remains unresolved.Request and unanswered location question.
Event location stated as North.Select the North branch under this fictional plan.Stated location and actual assigned handler.
Selected branch cannot receive the assignment.Return the unresolved assignment to central review.Failed assignment and named reviewer.

For the original message, central review is a handling responsibility while branch assignment remains pending. Once the requester supplies a location, review the rule again. The request still leaves equipment availability and any booking to be confirmed separately.

Decide what happens when assignment is unresolved

If more than one rule matches, write down which decision should take priority and check how your actual setup resolves the conflict. Do not assume that the order on a planning sheet is the order the software executes.

Give unresolved assignments a named review responsibility. State what the reviewer needs to resolve, such as a missing location or an unavailable destination. In the rental plan, “central review” needs an actual responsible person; a queue label alone does not identify who will inspect it.

Check assignment and notification separately

Use a clearly marked test enquiry to compare the expected handler with the actual assignment. Then inspect any notification and ask the intended recipient to find the request. Record these checks separately from a response to the requester. This is a proposed check, not a test performed here.

For example, HubSpot explicitly says that assigning a record through import does not notify the assigned user. That exception concerns import, not every assignment method.

When reviewing configuration, ask whether an existing owner should be retained or replaced. HubSpot’s Rotate record to owner action has an explicit option to overwrite an existing owner.

After changing a rule or destination, recheck the affected cases and retain the rule version with the result. If the recorded owner differs from the intended handler, trace the assignment rather than silently changing the record and losing the explanation.

Keep routing separate from qualification. Choosing someone to handle an enquiry does not answer whether the business can meet the request or whether sales accepts it for follow-up. For the rental team, the next useful fact is the event location, not an invented readiness score.

HubSpot: Assign ownership of records

HubSpot: Assign and rotate record owners using workflows