A Fair Lead-Routing Rule When Several Staff Share Enquiries

When three employees answer calls, WhatsApp messages and website forms, “whoever sees it first” sounds efficient until a valuable enquiry receives two replies while another gets none. A routing rule is not a leaderboard. It is a promise that every request will have a named owner, a deadline and a fallback if that person is unavailable. The best design is small enough to explain during a five-minute staff meeting and explicit enough to settle disagreements without asking the owner to adjudicate every lead.

The operational problem

Begin by separating the intake channel from the ownership decision. A message arriving on the shop phone is not automatically owned by the employee holding that phone; likewise, a website enquiry submitted after closing should not be assigned to whoever happens to open the inbox first. Define eligible staff, service categories, operating hours and the meaning of “accepted”. Do not route based on assumptions about customer value unless the business has a legitimate, documented reason. Unexplained priority rules invite bias and can leave ordinary customers waiting.

A workable procedure

Create a simple routing matrix. Rows should describe enquiry type—new purchase, service request, existing order, complaint or partnership proposal. Columns should name the primary owner, backup owner, first-response target and escalation point. If all staff can handle all requests, use round-robin assignment during staffed hours; if expertise differs, route by service category first and rotate fairly within each eligible group. The rule must define what happens when the assigned person is on leave, already handling a customer or fails to acknowledge the assignment.

Example from a small business

Imagine a Rajkot repair shop with two technicians and one front-desk employee. A request about repair status goes to the front desk, while a new diagnostic request goes to the technician rota. The front desk remains responsible for acknowledging receipt even when a technician will provide the technical answer later. At 4:30 p.m., a new request is assigned to the on-duty technician; if it is not acknowledged within the agreed window, the backup receives it. This prevents the customer from becoming the messenger between staff members.

Failure modes to watch

Watch for “soft ownership”: everyone believes someone else is replying. Another common defect is an assignment that changes silently when a staff member forwards a message. Forwarding is not a transfer unless the recipient accepts it. Staff should also avoid assigning themselves every high-value enquiry while leaving routine requests to colleagues. A monthly sample of assignments can reveal whether routing is being bypassed, whether certain categories are consistently delayed and whether the rota is realistic for actual staffing levels.

How to review the result

Track four operational measures rather than rewarding raw lead counts: percentage of enquiries with a named owner, acknowledgement time, reassignment frequency and requests that miss the response target. Segment results by enquiry type and working hours; otherwise an employee handling complex complaints may look slower than someone answering simple price questions. Review a small sample of missed targets with staff before changing the rules. The purpose is to identify capacity or process problems, not to turn every customer interaction into a competition.

Implementation note

A workable routing rule fits on one page and has an owner, backup, acknowledgement rule and exception path. Test it for two weeks with a small sample of incoming enquiries. Ask staff which assignments were confusing, then amend the matrix rather than relying on informal exceptions. Publish the final version beside the shared inbox procedure and revisit it whenever opening hours, staffing or service categories change.

Conclusion

A workable routing rule fits on one page and has an owner, backup, acknowledgement rule and exception path. Test it for two weeks with a small sample of incoming enquiries. Ask staff which assignments were confusing, then amend the matrix rather than relying on informal exceptions. Publish the final version beside the shared inbox procedure and revisit it whenever opening hours, staffing or service categories change.