Lead routing: which rules do you actually need?

A route may be commercially attractive yet unsuitable for a specific enquiry. First check hard conditions such as market, product, region, customer type and required fields. Only suitable destinations continue.

This separation prevents priority or price from overriding an invalid match. It also makes rejection explainable: the destination was outside its service area, lacked required data or did not accept the customer profile.

A daily, weekly or segment cap is not a static number. The system needs to know how many valid deliveries already count in the relevant period, which time zone applies and whether a limit is tracked separately by region or product.

Schedules are part of availability too. A route can be skipped outside opening hours, queued or offered later according to agreement. Define that choice upfront so speed and quality do not depend on chance.

When several routes are suitable and available, priority decides which one is attempted first. This can be a fixed order, round robin, weighting, price or a combination. Use one dominant logic per group and document exceptions.

A complex score with many small factors may look sophisticated but is difficult to control. Start with rules that reflect a commercial contract or operating agreement. Add complexity only when evidence shows it improves outcomes.

Routing selects the destination. Delivery determines how the enquiry arrives through API, email or another connection and how the response is interpreted. Keep these responsibilities separate so a temporary technical issue does not silently change commercial logic.

Agree whether a failed attempt retries, stops or moves to the next suitable route. Preserve every attempt with its time, response and outcome so the team can distinguish a wrong match from a technical delivery failure.

Test more than the happy path. Use a full cap, closed schedule, duplicate enquiry, missing field, rejecting API and two simultaneous leads competing for the last available slot. These cases determine whether the system remains fair under pressure.

A useful audit trail shows which rule matched, which limit was reached and which delivery followed for every candidate. Operations, sales and finance can then inspect the same decision without reconstructing the system.