We confirm scope and price in writing. The main factors are:
- Number of lead sources and teams.
- Rule complexity, from simple sharing to multi-level routing.
- CRM capabilities and plan.
- Alerts and escalation needs.
- Testing and reporting.
CRM plan upgrades or automation tool subscriptions are paid to those vendors and are separate from our fee. A small team with one source needs a short, simple rule set. A multi-city team with several products needs more design time.
Tell us how leads arrive and who handles them, and we will reply with a plan and a quote.
Speed targets should be realistic and agreed. A rule that demands a response in five minutes from a team that works field visits will only create false alarms. We set targets with the team, based on working patterns and lead value, and we use different targets for different sources. A hot enquiry from a phone call button may deserve a faster response than a general newsletter signup.
Fairness over time needs a look as well. Round-robin sounds equal, but if some people are on leave, on calls or handling larger deals, workloads drift. We include simple checks that show leads per person, contact rates and open tasks, so managers can see imbalance and adjust weights. This avoids resentment and keeps the system trusted.
Quality of leads varies by source, and assignment rules can reflect that. Leads from a high-intent source, such as a quote request, might go to the most experienced sellers, while low-intent sources go to a nurturing sequence before any person calls. We discuss these choices with you, as they involve judgments about your market that only you can make.
Documentation closes the work. A one-page rule sheet explains each rule in plain language, who owns the CRM settings and how to request a change. When a new person joins or a territory changes, the document guides the update. We also keep a short change log, so that a surprise in lead flow can be traced to a rule edit.
Rules should be reviewed regularly. Markets change, teams change and products change, and a routing design that suited last year may no longer fit. We recommend a quarterly review of response times, assignment fairness and conversion by owner, with small adjustments rather than large rewrites. Gradual refinement keeps the system helpful and understood.
Data quality decides whether rules work. If the city field is free text, “New Delhi”, “Delhi” and “Dilli” are three different values, and a territory rule will miss two of them. We standardise key fields with drop-downs or lookups, clean existing records and add a fallback for leads with missing values. A small amount of data discipline makes routing far more reliable.
Duplicates need handling too. If the same person submits a form twice, or arrives through two channels, the rules should recognise the existing lead and avoid creating a second owner. We configure duplicate checks before assignment, so that a repeat enquiry adds a note and a task to the current owner, not a conflict between two salespeople.
Communication with the team matters. When rules go live, we hold a short briefing on how they work, what to do when a lead arrives, what to do if a lead is wrongly assigned and how to request changes. People accept automation more readily when they understand its logic and know that mistakes can be corrected quickly.
Finally, we build in transparency. Each lead record shows which rule assigned it and when, so questions can be answered with facts. If a customer complains about a delay, you can see when the lead arrived, who received it and when contact was made. This record supports coaching and process improvement instead of blame.
Mobile alerts deserve a final mention. Salespeople are often away from desks, so alerts should reach their phones with the lead’s name, source and a tap-to-call or tap-to-chat link. We test that notifications arrive on the devices your team actually uses, and that they do not flood people with messages that are not relevant to them.
