CRM & sales / GUIDE + WORKSHEET
Stop leads from sitting without an owner
Design lead routing with fallback ownership, reassignment, and an exception queue that catches incomplete or ambiguous enquiries.
THE STARTING POINT
Every new enquiry needs either a responsible person or a visible queue with a responsible person behind it. Define routing rules, a fallback for missing information, and a way to detect unaccepted assignments. Treat reassignment and duplicate enquiries as explicit workflow states.
Route only on information you can trust
List the fields used to route enquiries, such as service requested, territory, existing account, or language. Check whether they are actually present and reliable at arrival. If routing depends on a field filled later, create a temporary review queue rather than leaving ownership blank. Give conflicting conditions a defined precedence that staff can explain.
Make assignment different from acceptance
An automation can fill an owner field while the owner is away or unaware. Define how the assigned person sees the enquiry and confirms the next action. Monitor work with no activity or overdue acceptance according to your team's agreed service expectations. Reassignment should preserve the prior owner and reason so people do not contact the same prospect independently.
Review the exceptions as a process
Look at the unmatched queue regularly and group causes: missing service, ambiguous region, no available owner, or existing customer conflicts. Improve the form or rule that creates repeat exceptions. Do not keep adding narrow routing rules without an owner for their maintenance. Test the fallback whenever territories, staffing, or services change.
WORKED EXAMPLE / ILLUSTRATIVE
A fictional enquiry with no region
The form captures a valid request but omits a region. The system can still acknowledge receipt and assign review ownership; it should not invent a territory or quietly drop the lead.
| Condition | Assignment | Verification |
|---|---|---|
| Existing account matched | Current account owner | Confirm owner is available |
| New enquiry, known service | Service routing rule | Next action recorded |
| Missing or conflicting fields | Named review queue | Reviewer resolves and reassigns |
MAKE IT USEFUL
Routing exception map
Document both the usual route and the cases that do not fit.
Your notes stay in this page and are not sent to Smithers. Download or copy them before leaving; refreshing clears them.
Before you put it to work
- Never leave fallback ownership blank.
- Test unavailable owners.
- Preserve reassignment history.
- Review repeat exceptions at their source.
A notification is not proof that someone has taken responsibility. Monitor the next action, not just message delivery.
IF THIS LOOKS FAMILIAR
Your tools. Your particular mess.
The worksheet is yours to use. If the difficult part is making it work with the systems you already have, that's the kind of thing we help with.