A visitor reads four pages about the Phoenix location, leaves, comes back three days later, submits the generic contact form. The form fires to the sales pool. The Phoenix franchisee finds out two hours after a Cleveland rep already called the lead.

The form fires to the sales pool. The pre-form context that should have routed it to Phoenix never enters the CRM.

The pipeline, end to end

1. Position on the lead-scoring-routing agent. The agent owns the 3-skill enrichment-scoring- routing pipeline. Firmographic enrichment ( /firmographic-enrichment) adds who-they-are. Behavioral enrichment (this skill) adds what-they-did + where-they-researched. BANT scoring consumes both inputs + scores the lead on budget + authority + need + timeline. The agent routes the scored, enriched lead to the right franchisee with full context attached.
2. Per-page location-tagging. Every page in the location-aware section of the operator site carries a location_id tag (Phoenix page = location_id_phoenix; Cleveland page = location_id_cleveland). Generic non-location pages tag with a sentinel (location_id_global). Tags surface in the page metadata + analytics layer + session telemetry stream.
3. Session telemetry capture (first-party + server- side). The session telemetry layer captures page views + per-page dwell time + page sequence + return-session count + scroll depth + exit page per visitor. First- party cookie identifies same-browser continuity. Server-side capture runs all logic on the operator- controlled server + survives third-party cookie deprecation + handles privacy consent enforcement centrally.
4. Visitor identification (pre-form). Anonymous visitor identification at the company- level runs via reverse IP lookup (the Lead Forensics + Leadfeeder + Albacross + RB2B + Warmly pattern) + identifier-graph match where the visitor previously identified at the same first-party identifier on a consented surface. Person-level identification waits for the form-submit unless consent unlocks an identifier-graph match (Bombora + Demandbase + Clearbit-style person-level reveal).
5. Location-intent signal extraction. The extractor scores every location the visitor encountered by aggregate dwell-time + page-count + return-session-count + recency-decay. Top location + secondary location surface in a per-visitor location-intent profile. Multi-location visitors (visitor researched Phoenix + Tampa) get a multi- modal profile.
6. Multi-session stitching. Cross-session + cross-day + cross-device continuity via first-party identifier graph. Day-1 4-page Phoenix session + day-4 form-fill stitch into one visitor record on form-submit. Form-fire reverse- lookup confirms the company-level match where IP changed across sessions.
7. Firmographic enrichment combination. On form-submit (or pre-form via consented reveal), firmographic enrichment fires from the loop-22 substrate. Company name + size + industry + technographics + leadership data + ICP score join the visitor record. Combined record carries who- they-are + what-they-did + where-they-researched.
8. BANT scoring on the enriched record. BANT scoring runs on the enriched lead record (loop- 36 callback). Behavior signals weight the timeline + need components (return-session frequency signals timeline urgency; per-location dwell signals need specificity). Firmographic signals weight the budget + authority components. BANT score attaches to the CRM record.
9. Per-franchisee routing decision. Routing layer consumes location-intent profile + BANT score + firmographic profile + per-franchisee territory rules. Top-intent franchisee routes the lead unless territory rules override. Multi-location visitor edge case (Phoenix 0.55 + Tampa 0.45) resolves via form-provided ZIP + secondary cues. Lead enters CRM record assigned to right franchisee.
10. Pre-form context attachment to CRM record. The 4-page Phoenix research + 11-minute aggregate dwell + 3-day return signal + reverse-IP company match + firmographic profile + BANT score + sourced talking-points attach to the lead record on creation (cross-link to /crm-record-creation). Franchisee opens the record + sees the full pre-form story.
11. Per-franchisee territory rules + privacy boundaries. Per-franchisee territory rules enforce (geographically-defined territory boundaries + cross-franchisee customer rules). Per-franchisee privacy boundaries prevent franchisee X from seeing franchisee Y operational details that are not customer-relevant. Per-state privacy regimes propagate (CCPA opt-out + GDPR consent + state- level identity signals).
12. Cookie-deprecation resilience. Third-party cookie deprecation does not break the pipeline. First-party cookie handles same-browser continuity. Server-side enrichment runs at form- submit on the operator server. Reverse IP lookup handles company-level pre-form identification. Consented identifier-graph handles person-level where available. iOS Mail Privacy Protection + state consent laws all factor in.
13. Measurement. Per-location holdout test (50 percent of multi- location form-fills get enrichment-routed; 50 percent get generic round-robin). Conversion-rate delta measured per location + per franchisee + per lead-source. Routing accuracy measured (percentage of leads routed to the location matching the per- location intent signal). Enrichment-driven lift feeds back into the BANT-scoring weights via the loop-36 measurement loop.