Commercial pillar · Lead routing · Multi-location + franchise
Routing rules engine for multi-location and franchise operators: territory + capacity + SLA in one engine
Mautic, SuiteCRM, EspoCRM, Distrobird, Chili Piper, LeanData, and FranConnect each ship a partial routing primitive. Marketing automation does rule-list routing. Chili Piper does meeting-handoff routing. LeanData does Salesforce-internal routing. FranConnect does franchise-config routing. Operators with 50-1,500 receiving locations and franchise territory exclusivity contracts glue three or four of these together. The unified engine that combines per-territory + per-capacity + per-SLA + per-lead-quality + per-franchise-policy + per-route attribution emission is operator-side wiring.
Published May 30, 2026
Six rule classes that compose into one routing decision
Per-territory match. Which locations geographically serve the prospect address. Pre-computed per-ZIP-per-location geofence; per-state per-DMA per-metro variants.
Per-location capacity match. Which eligible locations have available rep bandwidth right now versus full queue. Live signal from queue depth + active rep count + recent contact-attempt rate.
Per-SLA dispatch. Which routing satisfies the per-lead promised response-time. Predicted first-touch must be below SLA threshold; SLA misses trigger fallback routing.
Per-lead-quality scoring. High-fit leads route to highest-converting reps + locations rather than round-robin. Lead-quality score consumed from upstream marketing-attribution and intent-signal layers.
Per-franchise-policy overlay. Territory exclusivity contracts, per-franchise call-cap thresholds, per-franchise blackout windows, per-franchise lead-class eligibility. Overlay applied after geographic + capacity + SLA narrowing.
Per-route attribution event emission. Every routing decision emits a typed event with original-source + campaign + channel + lead-quality + receiving-location + receiving-rep + SLA-promised + predicted-first-touch into the attribution pipeline.
Territory vs franchise exclusivity are not the same concept
Per-territory routing answers: which locations geographically serve this prospect. Per-franchise territory exclusivity answers: which franchise has contractual right to leads from this geography.
Corporate-owned multi-location operators have per-territory routing without exclusivity — multiple corporate locations may compete for the same prospect with the engine choosing on capacity or SLA. Franchise operators add the exclusivity overlay: the contract says franchise A owns the 85008 ZIP; the lead routes there regardless of franchise B having lower queue load.
Engines that treat territory as a single concept conflate the two and produce wrong routing for franchise operators. Engines that treat franchise exclusivity as a single concept miss the capacity-and-SLA layer underneath. The unified engine carries both.
Why per-route attribution emission matters for marketing budget allocation
Every routing decision emits a typed event into the attribution pipeline. Downstream reporting joins acquisition cost (paid-search spend, paid-social spend, marketplace fees, partner referral fees) to per-location outcome (CRM stage transitions, revenue, customer-lifetime-value).
Without the routing engine emitting these events, the marketing team sees lead count and a brand-level CRM-stage rollup. They cannot tell which paid-search campaign actually produced revenue at which receiving location. Per-market budget allocation defaults to the brand-level rollup and misallocates against per-location performance.
Frequently asked
What does a routing rules engine for multi-location and franchise operators do?
The routing rules engine consumes every inbound lead (web form, phone call, chat, marketplace inquiry, partner referral) and emits a per-lead routing decision that names the receiving location + receiving sales rep + receiving SLA-clock + downstream attribution event. The decision is computed against six rule classes. First: per-territory match — which locations geographically serve the prospect address. Second: per-location capacity match — which of the eligible locations has available rep bandwidth right now versus full queue. Third: per-SLA dispatch — which routing satisfies the per-lead promised response-time. Fourth: per-lead-quality scoring — high-fit leads route to highest-converting reps + locations rather than round-robin. Fifth: per-franchise-policy overlay — territory exclusivity contracts, per-franchise call-cap thresholds, per-franchise blackout windows. Sixth: per-route attribution event emission — which marketing source + channel + campaign generated the lead routes to which receiving location, so downstream reporting joins acquisition to outcome per location. Six classes, one engine, every inbound lead.
Why do Mautic, SuiteCRM, EspoCRM, Distrobird, Chili Piper, LeanData, and FranConnect not solve this in one place?
Each ships a partial primitive. Mautic + SuiteCRM + EspoCRM are open-source marketing-automation + CRM platforms; they emit leads but their routing is rule-list + round-robin without per-territory or per-capacity awareness. Distrobird focuses on inbound dial-routing for SDR teams. Chili Piper focuses on calendar-meeting handoff routing. LeanData focuses on Salesforce lead-routing inside the Salesforce ecosystem. FranConnect ships franchise-management workflow including lead distribution but treats routing as a configuration screen rather than a real-time engine with attribution emission. Operators who run multi-location or franchise networks at 50-1,500 receiving units glue three or four of these together. The glue layer that unifies per-territory + per-capacity + per-SLA + per-lead-quality + per-franchise-policy + per-route attribution into one engine is operator-side wiring. The unified engine is the whitespace.
How does per-territory routing differ from per-franchise territory exclusivity?
Per-territory routing answers: which locations geographically serve this prospect. Per-franchise territory exclusivity answers: which franchise has contractual right to leads from this geography. Multi-location operators (corporate-owned stores) have per-territory routing without exclusivity — multiple corporate locations may compete for the same prospect with the engine choosing on capacity or SLA. Franchise operators add the exclusivity overlay: the contract says franchise A owns the 85008 ZIP code; the lead routes there regardless of franchise B having lower load. The exclusivity overlay is per-franchise-agreement metadata that the routing engine consumes alongside the geographic match. Engines that treat territory as a single concept conflate the two and produce wrong routing for franchise operators. Engines that treat franchise exclusivity as a single concept miss the capacity-and-SLA layer underneath. The engine needs both.
How does per-SLA dispatch interact with per-location capacity?
A lead with a 5-minute SLA cannot route to a location whose queue depth predicts a 12-minute first-touch. The engine computes per-location predicted-first-touch from queue depth + active-rep count + recent contact-attempt rate + per-rep average response-time. Predictions above SLA trigger one of three fallbacks: route to a backup location whose capacity satisfies SLA, route to a centralized dispatch queue whose reps cover overflow, or auto-escalate to a manager with a notification. SLA-and-capacity together are what produce a routing decision that actually meets the promised response time. SLA alone routes to a location that will miss it. Capacity alone routes to a fast location that may not be the right territory.
What attribution events does the routing engine emit and why do they matter for marketing attribution?
Every routing decision emits a typed event with: original-source (organic search vs paid search vs paid social vs marketplace referral vs partner referral vs direct), original-campaign-id, original-channel, lead-quality-score, receiving-location-id, receiving-rep-id, SLA-promised, predicted-first-touch, actual-first-touch (joined later), and outcome (joined later from CRM stage transition). The event stream flows into the attribution pipeline where downstream reporting joins acquisition cost to per-location outcome. Without the routing engine emitting these events, the operator marketing team cannot tell which paid-search campaign actually produced revenue at which receiving location — they see lead count and a CRM-stage rollup at the brand level and miss the per-location attribution that drives per-market budget allocation.
What is the typical engagement model for building the routing rules engine?
Tier 1 AI Readiness Assessment ($10k, 2-3 weeks) audits the current routing surface across every inbound channel + every receiving location and produces the unified routing-rules specification. Tier 2 AI Swarm Setup Sprint ($25-50k, 4-8 weeks) builds the engine end-to-end: per-channel ingestion connectors, per-territory match logic, per-location capacity-prediction model, per-SLA dispatch, per-lead-quality scoring, per-franchise-policy overlay, per-route attribution event emission. Tier 3 Fractional CMO with AI Swarm ($15-25k/month, 6-month minimum, 1-2 days/wk embedded) operates the engine in production + extends policy overlays per new franchise agreement + tunes capacity-prediction per location + coordinates SLA renegotiations with operations. Operator team owns the per-territory map, the per-franchise-policy metadata, the receiving-location capacity feed, and the attribution event store. Completions owns the orchestration knowledge.
Engage Completions
Start with the AI Readiness Assessment (Tier 1, 2-3 weeks, $10k). Hand off to Tier 2 AI Swarm Setup Sprint ($25-50k, 4-8 weeks). Continue under Tier 3 Fractional CMO with AI Swarm ($15-25k/month, 6-month minimum, 1-2 days/wk embedded).