How to route leads to the right person

01

Create a routing table

List each entry point and the information needed to route an inquiry, such as service requested, location, language or existing customer relationship. For every combination, name a primary owner and a backup, then set a response target. Give incomplete or unusual requests a human review queue instead of guessing.

Agree on precedence when rules overlap. For example, an existing account owner may take priority over a location rule. Document who can change assignments and how the team handles out-of-hours arrivals.

02

Require an accepted handoff

The handoff should include the original request, arrival time, source, relevant conversation history, contact preferences and next action. Use a shared record rather than asking a prospect to repeat information. Restrict access to the information staff need for their work.

Set a deadline for the recipient to accept ownership. If they do not accept it, send the record to the backup and flag it for review. The original owner remains responsible until acceptance; a notification alone is not confirmation.

03

Review routing failures

Each day, inspect unassigned inquiries, unaccepted transfers and actions past their deadline. Record the reason: missing information, absence, wrong rule or insufficient capacity. Resolve the individual inquiry first, then update the rule if the same problem recurs.

Compare the count of inquiries received with those assigned, accepted and attempted over the same period. Reconcile differences against duplicates, invalid records and suppressed contacts. Review quality and contact outcomes as well as speed before deciding a routing change worked.

04

Put the rules into practice

Run a short sample of recent inquiries through the proposed table before using it live. Include an existing customer outside the usual service area, an incomplete form, an urgent request and an inquiry arriving during an absence. If two rules claim the same record, write down which one wins and who can override it.

Track overrides with a reason and review them with the people receiving the work. Frequent overrides may show that the table needs a new rule or that required information is missing at intake. Set a review date and publish the current table where all owners can find it.

05

Make routing rules auditable

Give each rule a priority number, a named owner and an effective date. For a sample request, record which rule matched, who accepted the inquiry and the time of acceptance. If the record bypasses the table through a manual assignment, keep the reason and approver so a manager can distinguish an exception from a broken rule.