Multi-Location Ad Leads: Route the Work to the Branch That Can Deliver It

Route a service enquiry using the work location, the requested service and the branch that can deliver it. The caller’s address, the ad name or the nearest office may point to the wrong team. A useful routing rule produces an accepted enquiry with a clear customer commitment, rather than merely forwarding a notification.

Ask for the location that determines delivery
A head office may organise work at several sites, and a property owner may live elsewhere. Ask where the work will happen when that information is needed to decide coverage. Keep it distinct from contact and billing addresses.
A broad work area may be enough for the initial decision; obtain further site details through the service process. Retain the information already supplied so the customer does not have to repeat the whole request each time another team becomes involved.
Our service-area targeting guide covers the campaign’s geographic invitation. Routing handles the actual request that arrives, including cases where the customer’s contact address and work site differ.
Build a map that includes capability and availability
For each branch, specify normal coverage, services delivered, conditional work and the route for an exception. A geographic boundary alone is insufficient if only one branch delivers a specialist service or the usual branch cannot meet the requested date.
A practical sequence is to confirm coverage, identify capable branches, check the relevant delivery options and obtain acceptance from the selected team. Keep “outside coverage,” “service unavailable” and “date unresolved” as different outcomes; each requires a different customer response.
Resolve overlapping coverage consistently
If two branches can serve the same area, use an agreed allocation rule or a verified option accepted by the customer. Whichever inbox receives the notification first should not quietly become the deciding rule.
A transfer that changes the date or price is an alternative offer. Confirm those terms before presenting it as a continuation of the original arrangement. Pass on the existing discussion and promises so the receiving team can continue the conversation accurately.
Route three fictional enquiries
Consider a fictional North and South service group with a shared coverage zone. Both branches handle standard work; only South delivers the specialist service in this example.
L301 — capability: the buyer works at a northern head office but needs specialist work at a southern site. South accepts the enquiry with the work site and service details attached. The contact address does not override that fit.
L302 — availability: a northern site needs standard work on a date North cannot supply. Its state is “awaiting delivery alternative.” South becomes an option only after its date and terms are confirmed.
L303 — overlap: a shared-zone site needs standard work. Both branches are eligible, and North has the verified option the customer accepts. North becomes the sole current owner.
These cases need different answers. L301 needs the capable branch, L302 needs a supportable alternative and L303 needs an unambiguous selection. Describing all three as “sent to nearest branch” would hide the decision that matters.
Complete the transfer before calling it accepted
For L301, the receiving team needs the enquiry reference, work site, requested specialist service, customer discussion and promised response time. Acceptance means that South can access those details and has taken responsibility for the next step.
A fictional customer message could read: “Your specialist-service request, reference L301, is now with our South team for the work site you supplied. They have the details already provided and will contact you by the agreed response time. Reply with L301 if the site or requested work changes.” Use the actual branch and arrangement in the live message.
For L302, the accurate message is different: “North cannot provide the date requested. We are checking an alternative with South and will confirm its date and terms before asking you to decide.” It acknowledges the unresolved point without promising delivery that has not been accepted.
Our lead-routing cover guide addresses backup when the assigned person is unavailable. That backup is separate from changing the branch responsible for fulfilment.
Count enquiries, then investigate unresolved routes
A fictional daily review contains six unique enquiries: three accepted by North, two by South and one awaiting an availability decision. That is six opportunities with one unresolved route. Forwarding the unresolved enquiry to another inbox does not create a seventh opportunity or establish acceptance.
Use repeated transfer reasons to improve the rule: missing work-site information, an unavailable service, uncertain capacity or an unclear overlap. Our Google Ads management service can help connect campaign coverage with those fulfilment findings. In this example, L302 still needs an alternative the customer can actually evaluate.
Comments