Lead routing decides who receives a new enquiry and what happens next. A useful rule has a clear condition, an owner and a fallback when the data is missing. Start with a small set of rules that your team can explain and test.
Map the enquiry path
List every place leads arrive: website forms, email, phone calls, referrals and sales imports. Record which system creates the lead and who sees it first. Check whether duplicate entries can arrive through more than one channel.
Keep source information separate from the routing decision. A campaign identifies where an enquiry came from; a routing rule decides who should handle it.
Choose the fields that change ownership
Use fields that reflect how your team works, such as service requested, existing customer status, region or account owner. Do not collect extra personal information just to make the rules more elaborate.
For example, an agency might send website-build enquiries to its web team and paid-ad enquiries to its marketing team. An existing client’s request could go to the current account owner first. This is a sample design, not a claim about AdNxt’s internal sales process.
Write rules in a clear order
- Check whether the contact or business already has an owner.
- Apply any agreed service or territory rule.
- Assign eligible new leads within the right team.
- Send incomplete or conflicting records to a named review queue.
Record which rule wins when two conditions match. Avoid a setup where the last rule silently overwrites the first owner.
Define the fallback and response process
Every enquiry needs a route when a field is blank or a salesperson is away. Give the fallback queue an owner who checks it. Agree what counts as a first response, when reassignment is allowed and how handovers are recorded.
Keep the rule history available. When a salesperson asks why a lead was assigned, the system should show the matching condition rather than require someone to guess.
Test cases before switching on automation
Use sample records that do not send messages to real prospects. Include an existing client, a new lead with complete data, a duplicate, a missing service choice, an absent owner and a record that matches two rules.
For each case, write the expected owner and result before running the test. Check notifications, duplicate handling and reassignment separately.
Measure whether the rules help
Track unassigned leads, reassignment frequency, response time and the share of enquiries that become qualified conversations. Review disputed assignments with the sales team. A faster assignment is not useful if it repeatedly sends a lead to the wrong person.
If you are moving systems, use a CRM migration checklist to preserve ownership and activity history. If records are inconsistent, clean the CRM data before adding more routing rules.
When is custom development worth considering?
Use your CRM’s existing rules when they meet the need. Consider integration work when enquiries arrive from disconnected systems or the team must repeatedly copy and reconcile data. Write down the required inputs and exception routes before requesting a build.