Lead assignment rules should send an enquiry to the person able to act on it. Service fit, territory and availability matter, but the rule must still have an owner when no exact match exists.
The decision sequence
Begin with a real buyer or team task and keep the relevant source record. The worksheet below is meant to expose a decision that someone can check, rather than replace specialist review or claim a Megvi client result.
| Decision point | What to check |
|---|---|
| Define precedence | Decide whether existing-account ownership overrides new territory or service rules. |
| Use reliable fields | Only route on location or service when the form values are clear and stored in the CRM. |
| Add fallbacks | Specify what happens for unknown service, absent owner, leave periods and duplicate leads. |
| Monitor outcomes | Track unassigned records, reassignment, first-response time and qualified conversations. |
Worked example
Illustrative UAE agency: CRM enquiries for ecommerce SEO go to a specialist queue; a returning customer goes to the existing account owner. If that owner is away, the queue gets a timed escalation. A general “marketing” enquiry goes to triage rather than being silently assigned to the wrong specialist.
What could change the decision
A complex rule with stale staff availability can perform worse than a simple staffed queue. Keep a visible exception report.
Review before using it
Submit synthetic leads for each service and territory, including unknown values and unavailable owners. Confirm owner, notification and escalation.
Next useful step
For new leads without an existing owner, compare distribution models in Round-Robin vs Account-Based Lead Assignment. For help with a live implementation, see Megvi’s CRM development service. Bring the current page, workflow or evidence record and the decision you need to make.