01
Source and routing rules
Map the source, fields, routing rules, and fallback owner.
Automation
Lead Routing Setup
Send incoming leads from an agreed source to the right team or owner using rules you approve.
01 / THE STARTING POINT
Give each incoming lead a clear owner.
Lead routing starts with the information you have when an enquiry arrives. We review which fields can drive assignment, such as territory, service, or account owner, and decide what happens when those fields are missing.
We test the agreed assignment rules using representative enquiries. The handover shows who owns each path, where exceptions land, and how staff can see whether a lead was assigned.
02 / WHAT WE COVER
What you get.
Scope around one lead source and destination with agreed rules. Wider pipeline changes use CRM & Lead Automation.
02
Assignment configuration and testing
Configure the agreed assignment or notification flow and test representative leads.
03
Exception and owner notes
Document the routing rules and where the team can find exceptions.
03 / DIFFERENT STARTING POINTS
Where are you starting?
A focused project or part of a wider plan. We shape the scope around your current situation and the work that matters next.
Enquiries go to a shared inbox
Assign incoming enquiries to the right team by service or location and direct incomplete submissions to a designated queue.
Let’s discuss itThe same lead can arrive twice
Review how your CRM identifies existing records and agree whether a repeat enquiry should stay with the current owner.
Let’s discuss it04 / HOW THE WORK MOVES FORWARD
A clear path.
With room for your input.
Share the lead source, destination, available fields, and how you want to assign enquiries.
- 01
Review the starting point
Look at the examples and existing setup to confirm what the work needs to solve.
- 02
Agree the scope
Confirm the deliverables, access requirements, review points, and what a successful result looks like.
- 03
Do the work and verify it
Complete the agreed work and review the results against the examples or checks defined at the start.
- 04
Hand over the result
Share the agreed files, findings, or changes and explain any next steps your team owns.
05 / YOUR QUESTIONS, ANSWERED
Before we get started.
Have a requirement we haven’t covered?
Let’s talk about it
Can leads be routed by territory or service?
Yes, if the source captures usable fields. We agree rule order and what happens when a lead meets more than one condition.
Can we rotate leads between team members?
We review whether your CRM supports the assignment pattern and agree how to handle inactive users or changes to the roster.
What if a lead cannot be assigned?
We define a fallback owner or queue and test an example so the team can see and resolve exceptions.
How are cost and timing decided?
We prepare a proposal around the agreed deliverables, complexity, dependencies, access, and review requirements. Third-party charges and ongoing work are identified separately.
How do we get started?
Tell us about your business, the requirement, and what you already have in place. We will discuss the fit, clarify the scope, and recommend a practical next step.
LET’S TALK ABOUT YOUR PROJECT
Your next step.
Let’s work it out together.
Tell us about your business and what you want to improve. We’ll help you define a practical starting point.
Business process automation.
A focused project or
a connected plan.