Lead routing · Territory exclusivity · Franchise + multi-unit

Territory says franchise X. Capacity says 110%. SLA says 5 minutes. Route correctly the first time.

You run lead distribution across 50-1,500 franchise or multi-location units. Your franchise agreement gives territory A exclusively to franchise X. Right now X is at 110% capacity. The lead has a 5-minute SLA promise from the ad creative that brought it in. Routing to X breaks the SLA. Routing elsewhere breaks the exclusivity contract. Per-territory + per-capacity + per-SLA + per-lead-quality + per-franchise-policy routing closes the four-way constraint and emits the attribution event so per-market budget reconciles to outcome.

Audit your routing decisions (Tier 1)Explore Fractional CMO operation

Published May 30, 2026

Why your routing tool is producing the wrong decisions

Marketing automation platforms (Mautic, SuiteCRM, EspoCRM) 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. LeanData focuses on Salesforce-internal routing. FranConnect ships franchise-management workflow with lead distribution as a configuration screen rather than a real-time engine with attribution emission. Each is good at its primitive. None composes into the unified engine your operation actually needs.

You glue three or four together. The CRM assigns the lead by ZIP. A second tool checks capacity but only within one CRM hierarchy. A third tool tries to enforce SLA but has no awareness of franchise exclusivity. The attribution event that should fire on routing decision never fires because the decision is split across tools. Per-market budget reconciles to brand-level rollups that hide the per-location performance distribution.

The gap is the unified routing engine that consumes the full constraint set (territory + capacity + SLA + lead-quality + franchise-policy) and emits the routing decision + the attribution event from one place.

We’ve built unified routing for franchise networks. Here’s what we know.

You already have most of the inputs. The CRM holds capacity. The ad platforms emit per-channel SLA promises. The franchise-management system holds the exclusivity contracts. The lead-scoring system emits per-lead-quality. The gap is the routing decision that composes all four into a single per-lead decision in under a second, and the attribution event that records the decision for downstream per-market budget reconciliation.

We have built this for franchise + multi-location networks across verticals. We know which fallback shapes hold up when SLA + exclusivity + capacity collide (the three-fallback pattern: backup location if exclusivity permits, central dispatch queue, manager escalation). We bring the per-franchise-policy onboarding playbook and the per-vertical lead-quality-score weights.

How we get from gluing four tools to one unified routing engine

Step 1 — Tier 1 AI Readiness Assessment (2-3 weeks). We audit your current routing surface across every inbound channel. We sample 30-60 days of routing decisions against the constraint set (territory + capacity + SLA + lead-quality + franchise-policy) and measure how often each constraint was honored. Output: the unified routing-rules specification, the per-franchise-policy onboarding template, the per-channel SLA + lead-quality alignment, and the attribution-event schema.

Step 2 — Tier 2 AI Swarm Setup Sprint (4-8 weeks). We build the routing 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. Your engineering team receives the running system, all source code, all credentials.

Step 3 — Tier 3 Fractional CMO with AI Swarm ( 6-month minimum, 1-2 days/wk). We operate the routing engine in production. Extend the per-franchise-policy overlay as new franchise agreements ship. Tune the per-location capacity- prediction model against queue-pattern shifts. Roll up a monthly per-route attribution report showing per-market acquisition cost reconciled to per-location outcome. Coordinate SLA renegotiations with your operations + sales leadership.

What changes for you

You stop having the same conversation with franchise owners about exclusivity violations. The routing engine honors the contract by default; exceptions fire the documented fallback rules your team has already approved.

You stop missing SLA promises when the right franchise is at capacity. The fallback rules route to the backup location or central dispatch queue rather than the wrong franchise.

You can answer the question your CFO asks every quarterly review: which paid-search campaigns produced revenue at which receiving franchise locations. The per-route attribution events roll up per market per week.

You can onboard a new franchisee with the per-territory + per-franchise-policy spec in 30 minutes rather than a two-day routing-rules configuration sprint per new location.

Frequently asked

How is per-territory routing different from per-franchise territory exclusivity, and why does it matter?

Per-territory routing asks: which locations geographically serve this prospect. Per-franchise territory exclusivity asks: which franchise has contractual right to leads from this geography. Corporate-owned multi-location networks have per-territory routing without exclusivity — multiple corporate locations may compete for the same prospect with the engine choosing on capacity or SLA. Franchise networks 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 routing engine needs both.

How does per-SLA dispatch interact with per-location capacity when the SLA cannot be met?

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 (but only if territory exclusivity permits), route to a centralized dispatch queue whose reps cover overflow, or auto-escalate to a manager with a notification. The fallback rules are operator-side configuration; the engine enforces them. SLA + capacity together produce the routing decision that 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 in the right territory or contracted franchise.

What does Completions commit to on Tier 3 if we run the routing engine in production?

Tier 3 process commitments include: routing decision at sub-second p95 latency per inbound lead; per-territory exclusivity rule maintained on a documented quarterly cadence as franchise agreements evolve; per-location capacity-prediction model updated daily as queue patterns shift; per-SLA fallback rules reviewed weekly with your operations + sales leadership; per-route attribution event emission on every decision with full lead-source + receiving-location + receiving-rep + SLA-promised trace. We commit to the operating discipline. Per-channel + per-territory routing precision is tuned per stack and recorded as engagement KPIs.

What attribution events does the routing engine emit, and why does that matter for marketing budget?

Every routing decision emits a typed event with: original source (organic search vs paid search vs paid social vs marketplace 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, you see lead count and a brand-level CRM-stage rollup. You cannot tell which paid-search campaign produced revenue at which franchise location. Per-market budget allocation defaults to the brand-level rollup and misallocates against per-location performance.

Who owns the per-territory map, the per-franchise-policy metadata, and the credentials post-engagement?

Your team owns the per-territory geofence map, the per-franchise-agreement metadata (exclusivity contracts, call-cap thresholds, blackout windows), the per-location capacity feed, the per-channel SLA promises, the CRM credentials, and the ad-platform credentials. Completions owns the orchestration knowledge: the routing-decision runbook, the per-location capacity-prediction tuning history, the per-franchise-policy onboarding playbook. At engagement end we transition operational ownership back to your team over 30-60 days with documented handover.

How does the routing engine connect to the rest of the marketing + sales + attribution stack?

The engine subscribes upstream to every inbound channel (web form, phone, chat, marketplace, partner referral), to the change-event-emission stream (lead-state changes), to your CRM (capacity + queue state), and to the sentiment-intent-classification urgency stream (high-urgency leads route with adjusted SLA). It publishes downstream: per-route attribution events to the attribution-event-emission pipeline, routing decisions to the CRM as the assigned-rep field, and SLA-clock starts to the per-location response-time dashboard. Four upstream feeds, three downstream consumers, one routing contract.

Start with the audit

Tier 1 AI Readiness Assessment (2-3 weeks): we audit your current routing surface, sample 30-60 days of routing decisions against the constraint set, and produce the unified routing-rules specification + per-franchise-policy onboarding template + attribution schema. If you decide to build, Tier 2 ships the routing engine. If you decide to operate it with us, Tier 3 runs the engine in production. You choose the next step at each gate.