# Agentic routing map

```mermaid
flowchart TD
  Visitor[Visitor or external agent] --> Discover[Capabilities / OpenAPI / Markdown]
  Visitor --> Chat[Concierge chat]
  Discover --> Read[Read-only knowledge tools]
  Chat --> Classify[Deterministic service + location routing]
  Classify --> Answer[Grounded answer and suggestions]
  Classify --> Route[Service and geography route]
  Answer --> Counter{Second user message?}
  Counter -->|No| Continue[Continue helpful planning]
  Counter -->|Yes| LeadPrompt[Inline consented lead form]
  LeadPrompt --> Lead[Validated lead or quote record]
  Read --> Menu[Menus]
  Read --> Company[Company / chef / services / locations]
  Read --> Sitemap[Navigation and routing map]
  Lead --> CRM[CRM lead queue + request type + lead events]
  Chat --> Telemetry[Privacy-safe analytics]
  Read --> Telemetry
```

## Deterministic ownership

- Code owns input validation, rate limits, consent, idempotency, persistence, route classification, and lead state.
- Knowledge documents own published business facts and menu wording.
- The model may summarize retrieved knowledge and suggest a next step; it may not invent facts or execute side effects without the validated tool contract.
- SMTP settings remain owned by the existing contact/pricing email path and are not changed by the agentic upgrade.

## Lead routing dimensions

- Service: corporate, private, cocktail, bachelorette, personal chef, or general inquiry.
- Geography: Westchester/Armonk, Manhattan/NYC, Long Island/Hamptons, or needs confirmation.
- Queue: corporate-events, personal-chef, celebrations, cocktail-events, westchester-team, long-island-team, nyc-team, or the general catering-team queue.
- Request type: general lead capture or explicit quote request.
- Source: website chat, public MCP, agent REST, or existing website form.
- Lifecycle: new, qualified, contacted, booked, closed, or rejected.