Call routing for multi-location businesses

Resolve location before department

Use a location registry with branch name, service area, public number, timezone, hours, departments, languages, appointment system, overflow destination, temporary closure status, and registry owner.

Collect only routing evidence

Do not ask callers to navigate the organization chart. Location, existing relationship, and requested service usually provide enough evidence to select the next queue.

Maintain a location routing registry

Capture caller name, callback number, city or postal code, preferred branch, existing-customer branch, reason for call, service needed, appointment or order reference, language need, branch selected, rule used, local time, destination, and fallback result.

Handle closures and ambiguous locations

When service areas overlap, offer the documented choice or send the case to the routing owner. Temporary closures use the declared alternate branch; unknown locations enter a central review queue; a failed branch transfer returns to the central fallback.

Keep branches in control of exceptions

A central answerer may select a branch using approved geography and service rules. They may not claim inventory, local capacity, pricing, or appointment availability unless the branch source is current and authorized.

Test calls that cross boundaries

Test a caller near a boundary, an existing customer who moved, a closed branch, and a service offered at only one site. Include calls placed outside the destination’s local hours.

Find leakage between locations

Track first-route accuracy, branch corrections, transfers between branches, no-answer fallbacks, registry gaps, closure-rule use, and caller repeats. Review patterns by originating number and selected location.