In this guide
A new enquiry lands in your CRM. A notification goes to the sales channel. Three people see it, but nobody replies because each assumes someone else has picked it up.
The missing piece is not another notification. It is a rule that names the person responsible for the next action.
CRM lead routing means assigning an incoming enquiry to the right person or queue using agreed criteria. For a small team, a useful setup also answers two questions: when should that person act, and who takes over if they cannot? Here is a workflow you can adapt before buying another tool.
Choose the owner before choosing the automation
Start with the enquiry types your team actually receives. A request for a quote, an existing customer's account question and a supplier pitch should not all enter the same sales rotation.
Write down the few facts that genuinely change who should respond. These might be the requested service, an existing account relationship, a territory or a language requirement. If the form does not collect a fact reliably, do not build a critical rule around it.
Avoid creating a separate branch for every possibility. Start with the common cases and send anything unclear to a named person for review. A shared queue can be useful, but it still needs someone responsible for checking it.
Check existing ownership before assigning a new person
If the enquirer already has an active conversation with your team, look at that record before creating another one or rotating the enquiry. Otherwise, two salespeople can contact the same person with different answers.
Agree when existing ownership should be retained and when reassignment is justified. An account owner leaving the business is different from an existing customer submitting another form.
Check the actual automation settings rather than assuming an assigned owner is protected. HubSpot's record-rotation action includes a setting that controls whether existing ownership is overwritten. Its documentation also warns that synchronising ownership with Salesforce can create unexpected behaviour. [1]
Keep a note of which system is responsible for ownership when tools sync with each other. Test that a second system does not quietly restore an old owner after your routing rule runs.
Find the broken handoff in your revenue journey.
Write the routing rules in order, including a fallback
A useful starting order is: check for an existing relationship, apply any specialist requirement, then distribute the remaining enquiries among eligible people. That is a suggested design, not a universal CRM setting.
Rule order matters in Salesforce assignment rules. Salesforce evaluates entries in order and stops after a match. Its documentation recommends a final entry without criteria to catch records that earlier entries did not assign. [2]
Whatever platform you use, decide what happens when information is missing or nobody is eligible. The fallback should lead to a monitored queue or a designated person, not an invisible backlog.
Do not assume equal distribution means equal capacity. Someone handling complex proposals may have fewer open leads but less time available. Start with a simple assignment method your team understands, then change it if observed workload warrants it.
Add a response target and an accepted handoff
An owner field does not prove that anyone has acted. Create a next action with a due time and make the target clear to the person receiving it.
Choose a target the team can staff. State whether it runs only during business hours, which time zone applies and what happens on holidays. An automatic acknowledgement is not a human response, so measure those separately.
When the target is missed, send the task to the agreed backup or manager. Avoid repeatedly rotating the same enquiry without anyone accepting it. The receiving person should confirm ownership, and the previous owner should be able to see the change.
Use this routing-rule template in a team discussion. Replace every bracketed field before implementation.
Enquiry type: [what this rule covers] Required information: [fields needed to route it] Existing relationship: [retain owner or request review] Primary owner or pool: [named person or eligible team] Next action: [specific action, not just read notification] Due: [target, business hours and time zone] If information is missing: [fallback owner or queue] If the owner is unavailable: [backup] If the action is overdue: [escalation recipient and action] Handoff complete when: [new owner acknowledges the task] Process owner: [person who reviews exceptions]
Use AI to help with interpretation, not to hide uncertainty
A straightforward form with a service dropdown may only need fixed rules. AI can be useful when enquiries arrive as free text: it might suggest a category, summarise the request or prepare a draft reply.
Treat that suggestion as a suggestion. If the request is ambiguous, the category is missing or the proposed route conflicts with an existing relationship, send it for human review. Do not let a guessed budget or inferred intent decide that someone is not worth contacting.
Keep access limited to the information needed for the task. Review the tools and data arrangements before sending customer information to an AI service. You can test the routing design with synthetic records first.
Also check which features your current subscription supports. HubSpot's documented rotation action has subscription and paid-seat requirements. Confirm availability before making it the centre of your process. [1]
Test the awkward cases before going live
Create clearly labelled test enquiries and follow them through the whole journey. Do not stop at checking whether an owner field changed.
For each test, confirm the assigned owner, the due action, the notification and the fallback. Check that test emails and tasks stay with your test recipients. Keep the current manual process available until you know the new one works.
- A new enquiry contains all the required information.
- An existing customer submits the form again.
- An enquiry is missing the field used by the routing rule.
- The expected owner is away or no longer active.
- The enquiry arrives outside the agreed working hours.
- The next-action deadline passes without a response.
- A connected tool fails or tries to change the owner.
Review unanswered enquiries, not just assignment counts
For the first review, open the records themselves. Which enquiries have no owner? Which have an owner but no next action? Which have an overdue task? Those lists tell you where the process needs attention.
Track the time to the first human response separately from the time to assignment. Record whether the team reached the person, what happened next and why a lead was closed. Remove spam and test records from your reporting.
Look at exceptions before adding more branches. If the fallback queue keeps filling with the same type of request, improve the intake question or clarify who handles that work. If reassignment keeps happening because everyone is busy, the issue may be staffing rather than routing.
You do not need an elaborate system to begin. Pick one enquiry source, agree the owner and backup rules, and test the handoff. Expand only once the people using it can explain what happens when something goes wrong.
A useful routing workflow does more than fill in an owner field. It gives someone a specific next action, sets a realistic response target and makes missed handoffs visible. Agree those responsibilities first, then configure the CRM around them.