Franchise marketing · the capacity signal CRM routing never asks for

Your CRM routes a lead to the right territory. It never asks if that location can take the job.

Franchise CRM lead routing decides by territory — zip code, drive time, franchise boundary. It almost never knows whether that location is booked out two weeks. The dispatch platform already has that number; the CRM’s routing rule never asks it.

The desire, and the question routing never asks

Nobody searching “franchise CRM software” wants routing logic. They want the lead to reach a location that can actually take the job soon — not the nearest one, the nearest one that is not two weeks out.

1. 1. The routing decision — territory. Zip code, drive time, franchise boundary. Every franchise CRM answers this question well; it is the well-known half of the purchase.
2. 2. The missing question — capacity. Technician queue depth, next open slot, whether the location is booked out. The field-service platform has this number in real time; the CRM’s routing rule never reads it.
3. 3. The close — territory-correct and available. Read the open-slot count before finalizing the route. Territory-correct-but-booked-out routes to the next viable location in the same group, where the franchise agreement allows it, instead of sitting in a queue at a location that cannot get to it soon.

A lead routed exactly by the territory map and left waiting two weeks is not a routing success. It is a routing rule that answered the only question it was built to answer.

Which platforms close the gap

• CRM and marketing automation, by scale — the platform that owns the routing rule.
• Field-service software, by scale — the platform that owns the capacity number the route needs.
• Speed to lead: the channel most CRMs never measure — the same CRM, a different signal it does not receive.

Some links on the recommendation pages are partner links: the vendor pays us if you sign up, your price does not change, and each button says which.

How to build it yourself, end to end

Five steps. Each names the vendor touchpoint from the picks above.

1. 1. Read the open-slot count from the field-service API. A rolling count of upcoming availability per location, not just whether the location exists in the territory.
2. 2. Set a capacity threshold, not a hard cutoff. “Booked past N days” is more useful than a binary open/closed flag — most locations are never fully idle or fully full.
3. 3. Define the fallback route inside the franchise agreement’s own rules. Which adjacent location can legitimately take an overflow lead is a franchise-agreement question, not a technical one — confirm it before building the rule.
4. 4. Route on territory first, capacity second. Capacity should reroute an overflow, not override territory by default — the franchisee whose territory it is still gets first right of refusal.
5. 5. Report the reroute rate per location. A location rerouting a large share of its own leads is either understaffed or overpriced relative to demand — a fact worth surfacing to franchise operations, not just routing around silently.

Step 3 is the one to get right before building anything — a technically correct reroute that violates the franchise agreement is a bigger problem than the slow lead it solved.

Or have it scoped and built

Wiring a CRM’s routing rule to a dispatch platform’s capacity data, inside the franchise agreement’s own boundaries, is an integration project, not a subscription — the readiness assessment is where the routing rule and the fallback logic get scoped against your actual franchise agreement before anything is built.