Convert-Demand Swarm · Lead-Distribution Agent · Routing-Rules- Engine Skill · Build pillar · Published September 24, 2026

How to build a routing-rules engine for multi-location + franchise lead distribution across 50-500 locations

A 4-skill bundle (Define + Match + Route + Track) layered above the existing LeadSimple + Boberdoo + Phonexa + Convoso + RingDNA + LeanData (Salesforce) + Distribution Engine + Lead Liaison + CallTrackingMetrics LeadFlow + Five9 routing + CallRail Lead Center + Invoca Signal AI + HubSpot Routing + Salesforce Lead Routing + Outreach + Salesloft + Drift lead-distribution ecosystem + the Mapbox + Google Maps Geocoding + ArcGIS + HERE + Pitney Bowes geocoding substrate + the HubSpot + Salesforce + Pipedrive + Close + Keap CRM substrate + the Cal.com + Calendly + Acuity + ScheduleOnce booking substrate + the Twilio + MessageBird + Vonage + Plivo SMS substrate. Anchored on FTC Franchise Rule 16 CFR Part 436 + FDD Item 12 territorial rights (exclusive + protected + non-exclusive + reserved) + per-state Franchise Investment Law in 14 named states + per-state franchise relationship laws in approximately 25 additional jurisdictions + TCPA 47 USC 227 + FCC Insurance Marketing Coalition v FCC DC Cir 2025 + 14-state 2-party-consent call- recording + CAN-SPAM + CTIA + A2P 10DLC TCR + CCPA + CPRA + state-comprehensive-privacy + GDPR + NIST AI RMF + ISO 42001 + EU AI Act.

Start with the AI Readiness Assessment Engage the Fractional CMO with AI Swarm Take the 3-question scope quiz

The 4-skill bundle on the lead-distribution agent

Routing-rules engine is one skill on the lead-distribution agent. The skill decomposes into four operationally distinct sub-skills, each with its own success criteria and its own handoff to the next.

1. Define

Operator-defined routing policy in a versioned registry: per-location service-area geometry (radius, drive-time isochrone, ZIP list, custom polygon — same geometry primitives as the FDD-territorial-protection-gating skill, referenced from the same registry version), per- location capacity, language coverage, license-type capability, banner-format match where multiple banners run per region, current load balancing within a multi- location franchisee, hours-of-operation at lead-arrival time. Each rule has explicit precedence and explicit operator-defined fallback.

2. Match

Canonicalize the inbound lead (USPS address via Smarty or Loqate, E.164 phone via Twilio Lookup, geocoded to lat-long via Mapbox + Google Maps + ArcGIS + HERE + Pitney Bowes). Run lead through Define policy rules in precedence order. Identify all candidate locations whose service-area geometry contains the lead. Filter by capacity + language + license + hours. Cross-check every candidate against FDD Item 12 territorial-rights registry version (a lead inside a sibling-franchisee exclusive territory cannot route to a different franchisee). Produce deterministic ordered candidate list with rule-by-rule explanation. Fallback policy applies when no candidate satisfies all rules.

3. Route

Deliver to the destination via the operator-chosen pathway: lead-distribution platform (LeadSimple + Boberdoo + Phonexa + LeanData on Salesforce + Distribution Engine), call-tracking lead surface (CallRail Lead Center + Invoca Signal AI + CallTrackingMetrics LeadFlow + Five9 routing), CRM record creation (HubSpot + Salesforce + Pipedrive + Close + Keap), booking-platform handoff (Cal.com + Calendly + Acuity + ScheduleOnce), SMS notification (Twilio + MessageBird + Vonage + Plivo under A2P 10DLC TCR campaign registration with per-campaign brand- verification status recorded).

4. Track

Per-lead acknowledgment + time-to-first-touch + time- to-qualification + time-to-booking + time-to-revenue per location per franchisee. Realized routing outcomes feed back into the audit trail so the operator can detect Match policy drift (rules producing wrong destinations) and FDD Item 12 territory drift (Item 12 amendments not propagated into the registry). Reconciliation pairs the routing decision with the realized outcome so the next Define-policy review has supervised signal.

The real ecosystem this skill sits above

Lead-distribution + call-tracking lead surface

LeadSimple, Boberdoo, Phonexa, Convoso, RingDNA, LeanData (Salesforce), Distribution Engine, Lead Liaison, CallTrackingMetrics LeadFlow, Five9 routing, CallRail Lead Center, Invoca Signal AI, HubSpot Routing, Salesforce Lead Routing, Outreach, Salesloft, Drift.

Geocoding + address validation

Mapbox, Google Maps Geocoding API, ArcGIS, HERE Geocoding, Pitney Bowes Spatial Analytics, SmartyStreets (formerly), Loqate, Melissa Data, Lob Address Verification, Google Address Validation API for the Match-step canonicalization that precedes territorial- rights cross-check.

CRM + booking + SMS delivery

HubSpot, Salesforce, Pipedrive, Close, Keap (Infusionsoft), ActiveCampaign, Zoho CRM, Copper CRM for CRM record creation. Cal.com, Calendly, Acuity (Squarespace), ScheduleOnce (Oncehub), SimplyBook.me, Setmore for booking. Twilio, MessageBird, Vonage (Nexmo), Plivo, Sinch, Bandwidth, Telnyx for SMS notification under A2P 10DLC TCR.

5-anchor compliance overlay

Anchor 1 — FTC Franchise Rule 16 CFR Part 436 + FDD Item 12 territorial rights + per-state Franchise Investment Law + per-state franchise relationship laws (operationally distinctive)

Lead routing between franchisees is the surface where FDD Item 12 territorial rights are actually enforced or violated. Each franchisee was sold a specific territory geometry: exclusive (no franchisor or sibling-franchisee competition inside), protected (no sibling-franchisee competition but franchisor may operate), non-exclusive (no protection), or reserved (franchisor-only). A lead routed across an exclusive-territory boundary creates an Item 12 violation the affected franchisee can pursue. The FTC Franchise Rule (16 CFR Part 436, amended 2007) requires Item 12 disclosure at sale; per-state Franchise Investment Laws in 14 named states (California Corporations Code Sections 31000 et seq, Hawaii FIL, Illinois Franchise Disclosure Act 815 ILCS 705, Indiana FDA, Maryland Franchise Registration and Disclosure Law, Michigan FIL MCL 445.1501 et seq, Minnesota Franchise Act Minn Stat 80C, New York General Business Law Article 33, North Dakota FIL, Rhode Island Franchise Investment Act, South Dakota FIL, Virginia Retail Franchising Act, Washington Franchise Investment Protection Act RCW 19.100, Wisconsin FIL) layer state enforcement at sale; per-state franchise relationship laws in approximately 25 additional jurisdictions govern post-sale conduct. The Match sub-skill cross-checks every candidate routing destination against the FDD Item 12 territory of record before any routing decision is finalized. Operationally distinctive — routing is the surface where Item 12 lives or dies.

Anchor 2 — TCPA + FCC Insurance Marketing Coalition v FCC + per-state 2-party-consent call-recording

When Route delivery includes outbound callback or SMS to the prospect, TCPA 47 USC 227 + 47 CFR 64.1200 apply. FCC Insurance Marketing Coalition v FCC DC Cir 2025 vacated the FCC 1-to-1 consent rule scheduled for 2025-01-27; the prior consent framework remains in force but regulatory history must be tracked. Per- state 2-party-consent call-recording in 14 named states (California Penal Code 632 + Connecticut Gen Stat 52-570d + Delaware Title 11 Section 1335 + Florida Stat 934.03 + Illinois 720 ILCS 5/14-2 + Maryland Wiretapping Act + Massachusetts Gen L ch 272 16 + Michigan MCL 750.539c + Montana 45-8-213 + Nevada NRS 200.620 + New Hampshire RSA 570-A:2 + Oregon ORS 165.540 + Pennsylvania 18 Pa Cons Stat 5704 + Washington RCW 9.73.030).

Anchor 3 — CAN-SPAM + CTIA + A2P 10DLC TCR

Outbound SMS notification operates under CAN-SPAM Act (15 USC 7701) primary-purpose test for commercial content, CTIA Short Code Monitoring Handbook for short- code traffic, and Campaign Registry (TCR) A2P 10DLC campaign registration for long-code traffic. The Route sub-skill records per-campaign TCR registration ID + per-message brand verification status.

Anchor 4 — CCPA + CPRA + state-comprehensive-privacy + GDPR

Prospect data captured at the lead surface is personal information under California Consumer Privacy Act + California Privacy Rights Act + 18 state-comprehensive -privacy statutes + GDPR in EU jurisdictions. Audit trail preserves data-subject-access-request fulfillment evidence per prospect record.

Anchor 5 — NIST AI RMF + ISO 42001 + EU AI Act + per- vendor LLM zero-retention

AI-driven Match (LLM-assisted geocoding ambiguity resolution when a prospect address resolves to multiple candidate polygons; LLM-assisted service-need classification when free-text inbound form fields drive the license-type filter) operates under NIST AI Risk Management Framework + ISO 42001 + applicable EU AI Act articles + per-vendor LLM zero-retention posture verified before prospect data is sent to a model endpoint.

6-workstream pre-engagement-baseline reporting cycle

Routing accuracy and per-lead cycle time are what the data shows after the engine is built, not numbers Completions promises in advance. The first 30 days of every Tier 2 Setup Sprint or Tier 3 Fractional CMO engagement establishes the baseline.

Define coverage. Per-location service- area geometry completeness, per-location capacity + language + license + hours coverage, Define registry version pointer freshness, operator-defined fallback policy completeness.
Match quality. Per-lead canonicalization success rate, per-lead geocoding success, per-rule evaluation completeness, per-lead candidate-list ordering deterministic-reproducibility, per-lead FDD Item 12 cross-check completion rate.
Route quality. Per-destination delivery success rate per pathway, per-CRM-vendor + per-call- tracking-vendor + per-booking-platform + per-SMS-vendor delivery, per-A2P 10DLC TCR campaign registration freshness.
Track quality. Per-lead acknowledgment + time-to-first-touch + time-to-qualification + time-to- booking + time-to-revenue capture per location per franchisee, realized-outcome audit-trail completeness.
5-anchor compliance posture freshness. FTC Franchise Rule + FDD Item 12 + per-state FIL across 14 named states + per-state franchise relationship laws + TCPA + FCC Insurance Marketing Coalition v FCC + per- state 2-party-consent call-recording across 14 states + CAN-SPAM + CTIA + A2P 10DLC + CCPA + CPRA + state- comprehensive-privacy + GDPR + NIST AI RMF + ISO 42001 + EU AI Act + per-vendor LLM zero-retention posture.
Audit-trail completeness. Per-lead canonical-routing-decision record, per-rule evaluation record, per-FDD Item 12 cross-check record, per-fallback decision record, per-realized-outcome reconciliation entry.

Frequently asked questions

What does a routing-rules engine for multi-location + franchise lead distribution actually solve?

A 50-500 location operator receives inbound leads from form fills (landing pages, Google Ads lead forms, Meta lead ads, LinkedIn lead gen), inbound calls (CallRail + Invoca + CallTrackingMetrics + WhatConverts), inbound bookings (Cal.com + Calendly + Acuity + ScheduleOnce), and event ingestion from partner referral programs. Each lead has to land at the correct location — by service area, by language, by license type, by capacity, by current load, by sibling-franchisee territory rights, by hours of operation. Off-the-shelf round-robin within a CRM treats every location as interchangeable; that breaks at multi-banner franchise scale because franchisee A in Austin cannot receive a lead whose service address sits inside franchisee B exclusive or protected territory. The routing-rules engine encodes the operator-defined matching policy, runs it deterministically per lead with full audit trail, and produces evidence the franchise-development team and franchisor counsel can defend.

Why is FTC Franchise Rule + FDD Item 12 territorial-rights cross-check the unique compliance frame for this skill?

When the operator is a franchisor, every lead routing decision is a decision about which franchisee earns the revenue. FDD Item 12 territorial rights define what each franchisee was sold: exclusive territory (no franchisor or sibling-franchisee competition inside), protected territory (no sibling-franchisee competition but franchisor may operate), non-exclusive (no protection), or reserved (franchisor-only). A lead routed across an exclusive-territory boundary creates an Item 12 violation that the affected franchisee can pursue. The FTC Franchise Rule (16 CFR Part 436, amended 2007) requires Item 12 disclosure at sale; per-state Franchise Investment Laws in 14 named states (California Corporations Code Sections 31000 et seq, Hawaii Franchise Investment Law, Illinois Franchise Disclosure Act 815 ILCS 705, Indiana Franchise Disclosure Act, Maryland Franchise Registration and Disclosure Law, Michigan Franchise Investment Law MCL 445.1501 et seq, Minnesota Franchise Act Minn Stat 80C, New York General Business Law Article 33, North Dakota Franchise Investment Law, Rhode Island Franchise Investment Act, South Dakota Franchise Investment Law, Virginia Retail Franchising Act, Washington Franchise Investment Protection Act RCW 19.100, Wisconsin Franchise Investment Law) layer state enforcement on top; per-state franchise relationship laws in approximately 25 additional jurisdictions govern post-sale conduct. The Match sub-skill therefore cross-checks every candidate routing destination against the FDD Item 12 territory of record before any routing decision is finalized.

How does the Define skill encode operator routing policy?

The Define sub-skill encodes operator-defined routing policy in a versioned registry: service-area geometry per location (radius, drive-time isochrone, ZIP code list, custom polygon — the same geometry primitives the FDD Item 12 territorial-protection-gating skill uses, referenced from the same registry version), capacity per location (current open capacity + booking-window availability), language coverage per location, license-type capability per location (what services the location is licensed to perform — relevant for regulated trades like healthcare, legal, accounting, real estate, contracting), banner-format match where the operator runs multiple banner formats per region, current load balancing within a franchisee that owns several locations, hours-of-operation availability at lead-arrival time. Each policy rule has an explicit precedence and an explicit operator-defined fallback when the rule does not produce a match.

How does the Match skill turn a raw lead into a routing decision?

The Match sub-skill canonicalizes the inbound lead (address USPS-canonicalized via Smarty or Loqate, phone E.164-canonicalized via Twilio Lookup, geocoded to lat-long via Mapbox + Google Maps Geocoding + ArcGIS + HERE + Pitney Bowes), runs the lead through the Define policy rules in precedence order, identifies all candidate locations whose service-area geometry contains the lead, filters by capacity + language + license + hours, cross-checks every candidate against the FDD Item 12 territorial-rights registry version (a lead inside a sibling-franchisee exclusive territory cannot route to a different franchisee), and produces a deterministic ordered list of candidate destinations with the rule-by-rule explanation. When no candidate satisfies all rules, the fallback policy applies (route to corporate triage, route to nearest-available franchisee, route to operator review). The audit trail captures every rule evaluation per lead so a franchisee dispute or a franchisor counsel inquiry can be answered from the record.

How does Route handle the actual delivery, and how does Track close the loop?

Route delivers the lead to the destination location via the operator-chosen pathway: lead-distribution platform (LeadSimple, Boberdoo, Phonexa, LeanData on Salesforce, Distribution Engine), call-tracking lead surface (CallRail Lead Center, Invoca Signal AI, CallTrackingMetrics LeadFlow, Five9 routing), CRM record creation (HubSpot, Salesforce, Pipedrive, Close, Keap), booking-platform handoff (Cal.com, Calendly, Acuity, ScheduleOnce), SMS notification (Twilio, MessageBird, Vonage, Plivo under A2P 10DLC TCR registration). Track captures lead acknowledgment, time-to-first-touch, time-to-qualification, time-to-booking, and time-to-revenue per location per franchisee. Realized routing outcomes feed back into the audit trail so the operator can detect Match policy drift (rules producing wrong destinations) and FDD Item 12 territory drift (Item 12 amendments not propagated into the registry).

How does Completions report on this without fabricating KPI commitments?

Pre-engagement baseline is established in the first 30 days. Reporting cycles cover the six workstreams: Define coverage (per-location service-area geometry completeness + per-location capacity + language + license + hours coverage + Define registry version pointer freshness + operator-defined fallback policy completeness), Match quality (per-lead canonicalization success rate + per-lead geocoding success + per-rule evaluation completeness + per-lead candidate-list ordering deterministic-reproducibility + per-lead FDD Item 12 cross-check completion), Route quality (per-destination delivery success rate per pathway + per-CRM-vendor + per-call-tracking-vendor + per-booking-platform + per-SMS-vendor delivery + per-A2P 10DLC TCR campaign registration freshness), Track quality (per-lead acknowledgment + time-to-first-touch + time-to-qualification + time-to-booking + time-to-revenue capture per location per franchisee + realized-outcome audit-trail completeness), 5-anchor compliance posture freshness (FTC Franchise Rule + FDD Item 12 + per-state FIL across 14 named states + per-state franchise relationship laws + TCPA 47 USC 227 + FCC Insurance Marketing Coalition v FCC + per-state 2-party-consent call-recording across 14 states + CAN-SPAM + CTIA + A2P 10DLC + CCPA + CPRA + state-comprehensive-privacy + GDPR + NIST AI RMF + ISO 42001 + EU AI Act + per-vendor LLM zero-retention posture), audit-trail completeness (per-lead canonical-routing-decision record + per-rule evaluation record + per-FDD Item 12 cross-check record + per-fallback decision record + per-realized-outcome reconciliation entry).

Engage Completions

Multi-location and multi-unit franchise operators distributing inbound leads across 50-500 locations face a recurring problem: off-the-shelf round-robin routing breaks against FDD Item 12 territorial rights and ignores the license + language + capacity + hours constraints that determine which location can actually serve the lead. Completions architects the routing-rules engine as a 4-skill bundle layered above the existing LeadSimple + Boberdoo + LeanData + Five9 + CallRail + Invoca + HubSpot + Salesforce + Mapbox + ArcGIS + Cal.com + Twilio ecosystem. Start with the Tier 1 AI Readiness Assessment (2-3 weeks), build with the Tier 2 Setup Sprint (4-8 weeks), or engage Tier 3 Fractional CMO with AI Swarm (6-month minimum).