# START HERE — handover of the "sales flow" session (2026-10-02 → 2026-10-07)

> **Environment moved (2026-10-07):** work now happens on Shawn's GCP VM **`petav3-dev`** (`/home/zs/peta`,
> branch `dev-shawn`, database `peta_zs_dev`, isolated Redis / queue workers / scheduler) — see `CLAUDE.local.md`,
> which wins over this folder. The Windows / Laragon / WSL notes in §3 below (`petav3` local DB,
> `phpunit.audit.xml`, `C:\Users\zhish\…` memory paths) are **historical**.
>
> **Latest session: [09-session-2026-10-08-claude.md](09-session-2026-10-08-claude.md)** — the owner's decisions
> D1–D5 (three image stages, Record contact on every human box), what was built, and the open items (two
> migrations to apply on `peta_zs_dev`).
>
> **2026-10-13: [10-code-study-and-fixes-2026-10-13.md](10-code-study-and-fixes-2026-10-13.md)** — every file behind
> My Workspace (Sales steps / Action Item), the Sales flow guide (live / flow) and the funnel Journey tab was read
> against this folder; the bugs found, what was fixed, the stale statements in 00–09, and what still needs the owner.
> Read it before trusting 00–09. Owner decisions D6–D11 are now rows in [02](02-decisions.md).

This folder records one long Claude Code session in full, so that a new session can continue without the chat
history. Everything discussed, decided, built and left open is in these files.

| File | What it holds | Read it when |
|---|---|---|
| **00-start-here.md** (this) | The map: what was built, where it lives, the rules for working here | First, always |
| [01-session-log.md](01-session-log.md) | Day-by-day: every owner request and what happened | To understand WHY something is the way it is |
| [02-decisions.md](02-decisions.md) | Every decision: owner's (final) and implementer's (defaults) | Before changing any behaviour |
| [03-open-items.md](03-open-items.md) | Unanswered questions, owner to-dos, the deploy checklist, unfixed bugs | Before starting new work |
| [04-sales-flow-chart-path-design.md](04-sales-flow-chart-path-design.md) | The design behind `SalesFlowChartPath` (journey → flow-chart boxes) | Before touching the bar or chart |
| [05-review-findings-2026-10-07.md](05-review-findings-2026-10-07.md) | 5 confirmed + 4 unverified bugs in the bar/chart — **all fixed 2026-10-13** (see [10](10-code-study-and-fixes-2026-10-13.md)) | History only |
| [06-sales-workflow.md](06-sales-workflow.md) | **The whole sales workflow as built**: every step of 第1/2/3段, who does it, waits and timings, messages M1–M4, DATA 1–5, the daily routine, and where it differs from the original flowchart | To understand the business process itself |
| [07-owner-flowchart-original.md](07-owner-flowchart-original.md) | The owner's original flowchart spec, verbatim (the source file is git-ignored) | To see what was asked for in the first place |
| [08-workflow-readiness-audit-2026-10-08.md](08-workflow-readiness-audit-2026-10-08.md) | Current ten-Slot configuration, automation/human-touch gaps, My Work parity and isolated development runtime | Before claiming the full workflow is ready or changing its operational rules |
| [09-session-2026-10-08-claude.md](09-session-2026-10-08-claude.md) | Claude session of 10-08 → 10-09: Codex's half-finished work, owner decisions **D1–D5**, the packages built, review fixes, test totals, open items | **Before any sales-flow, My Work or Record-contact work** |
| [10-code-study-and-fixes-2026-10-13.md](10-code-study-and-fixes-2026-10-13.md) | 2026-10-13: code-level study of the 7 sales-flow pages, the bugs found and fixed, stale statements in this folder, owner questions | **First, together with 09** |

The older, longer plan this session executed: [`docs/temp/lead-journey-implementation-plan.md`](../lead-journey-implementation-plan.md).
It has a build log at the top (Phases 0–6) and a decisions log in §7.

---

## 0. For the next AI: how to use this folder (READ THIS FIRST)

1. **Read 00 → 06 in order, then 09** (the latest decisions win over older text). 07 is the original spec, for reference.
2. **These docs are a MAP, not the truth.** The code is the truth: other sessions keep changing this tree. Before
   you state how something behaves, or change it, **open the code files listed below for that task and read
   them.** Also run `git log --oneline 20e1678cb..HEAD` and `git status` to see what changed since this handover.
3. **Read the handbook named for the module.** The main one is
   [leads/funnel-journey/readMe.md](../../modules_handbook/manage/leads/funnel-journey/readMe.md). Follow
   `CLAUDE.md` / `GUIDELINES.md`, and update the handbook in the same change.
4. **Answer the owner in Mandarin, simply** (§3), and check [03-open-items.md §A](03-open-items.md): the owner's
   new message may already answer some of those questions.

**Code to open before each kind of task** (paths are from the repo root):

**The bar / chart (`SalesFlowChartPath`; the [05](05-review-findings-2026-10-07.md) findings were fixed 2026-10-13)**
- `src/Lead/Journey/Support/SalesFlowChartPath.php` (the whole file) and `tests/Unit/Lead/SalesFlowChartPathTest.php`
- `src/Lead/Journey/FunnelJourney.php` (`chipsForLeads`, `toChipArray`, `STEPS`, `flowStage`)
- `src/Lead/Journey/Repositories/FunnelJourneyRepository.php` (`TRANSITIONS`, `ONLY_FROM`, `record`)
- `src/Lead/Journey/FunnelJourneyEvent.php`
- `src/Lead/Journey/FunnelJourneyHooks.php` (`landingRegistered`, `candidateRegistered`, the deal-close hook)
- `app/Http/Controllers/Manage/Leads/LeadsController.php` (`journeyPayload`)
- `resources/js/Components/Leads/SalesFlowProgress.vue`
- `resources/js/Pages/Manage/MyWork/Partials/SalesFlowChart.vue`
- `resources/js/Pages/Manage/Leads/Partials/JourneyCell.vue`
- `resources/js/Pages/Manage/MyWork/Partials/salesFlowGuide.js` (`FLOW_CHART`)
- Read [04](04-sales-flow-chart-path-design.md) as well.

**Sales flow chart, Record contact, My Work responsibilities (10-08, see [09](09-session-2026-10-08-claude.md))**
- Handbook first: `docs/modules_handbook/shared/sales-flow-chart/{readMe,closing,record-contact}.md`
- `src/Lead/Journey/{PreviewJourneyBoard,ProjectJourneyBoard,ProjectJourneyContexts,ClosingJourneyBoard,JourneyWorkQueue}.php`
- `src/Lead/Services/{FunnelFollowUpState,MyWorkResponsibilities}.php`, `src/Lead/Repositories/FunnelFollowUpRepository.php`
- `app/Http/Controllers/Manage/Leads/{FunnelFollowUpController,ActionItemsController}.php`, `src/Lead/Support/FollowUpAccess.php`
- `resources/js/Pages/Manage/MyWork/Partials/{salesFlowOperations.js,SalesJourneyWorkspace.vue,SalesFlowMap.vue}`

**Change the sales-flow rules or timings**
- `config/funnel_journey.php`
- `src/Lead/Journey/Rules/*.php`
- `src/Lead/Journey/FunnelJourneyHandoff.php`
- `src/Lead/Journey/FunnelJourneyRecorder.php`
- `app/Console/Commands/AdvanceFunnelJourneys.php`
- `src/Event/Support/FunnelRuleAudience.php`
- `app/Jobs/Automation/SendFunnelAiCall.php`
- `app/Jobs/Automation/SendAiCallFollowUp.php`
- `app/Actions/PlaceAiVoiceCall.php`

**Round robin, account manager, reps, visibility**
- `src/LeadDistribution/LeadRotation.php`
- `src/LeadDistribution/Support/RoundRobinTurn.php`
- `src/LeadDistribution/Repositories/LeadRotationRepository.php`
- `app/Jobs/Lead/AssignRoundRobinManagerJob.php`
- `src/Lead/Lead.php` (the `booted` hook)
- `app/Services/LeadDistribution/TopRepOwnership.php`
- `app/Services/LeadDistribution/LeadDistributionService.php`
- `src/Lead/LeadRep.php`
- `src/Lead/Repositories/LeadRepRepository.php`
- `app/Console/Commands/RollupLeadReps.php`
- `src/Auth/Support/LeadVisibility.php`

**My Work and tasks**
- `app/Http/Controllers/Manage/MyWorkController.php`
- `src/Lead/Services/MyWorkBoard.php`
- `resources/js/Pages/Manage/MyWork/Index.vue`
- `app/Http/Controllers/Manage/Leads/ActionItemsController.php`
- `src/Lead/Repositories/LeadActionItemRepository.php`
- `src/Lead/LeadActionItem.php`

**Calendar or sidebar or Dashboard access**
- `resources/js/Layouts/ManageLayout.vue`
- `app/Http/Controllers/Manage/Calendar/CalendarController.php`
- `resources/js/composables/useOperationsLanding.js`
- `routes/web.php` (calendar group, the `action-items` redirect)

**Deploy**
- `scripts/deploy-update.sh`
- `app/Console/Kernel.php`
- [03 §C](03-open-items.md)

**A prompt the owner can paste into a new session:**

```text
Read docs/temp/7-10-temp/00-start-here.md and follow its "For the next AI" section: read 00 to 06 in order,
then open the code files it lists for the task before doing anything. Check git log/status since 20e1678cb.
Reply in Mandarin, simply. My task now: <describe the task>
```

---

## 1. The 60-second picture

**The owner's goal**, from the boss: *every sales admin or agent, on login, sees clearly what to do; the boss can
track it.* The owner's flowchart (`storage/app/workflow/PropertyLab Flow.md` / `.drawio.svg` / `.webp`) has three
stages:

1. **第 1 段** — landing sign-up → Preview webinar.
2. **第 2 段** — after the Preview webinar → Project webinar.
3. **第 3 段** — after the Project webinar → Booked / Not closed.

The full step-by-step flow, as built: **[06-sales-workflow.md](06-sales-workflow.md)**. Each stage runs an "AI-call loop" (WhatsApp → AI call → answered? → … → a human). People hand-offs happen at fixed
points; DATA 1–5 are what each call learns.

**What now exists** (ALL in commit `20e1678cb` on branch `dev-shawn`, pushed; not deployed; no PR yet):

| Feature | Where to see it | Code entry points | Handbook |
|---|---|---|---|
| **Funnel journey**: which flowchart box each lead is in, per funnel; hooks + a 5-min scanner hand unfinished work to a person as a task | Leads list → Journey column; lead → Sales → Journey tab | `src/Lead/Journey/*` (`FunnelJourney`, `FunnelJourneyEvent`, `Repositories/FunnelJourneyRepository` = TRANSITIONS/ONLY_FROM, `FunnelJourneyHooks`, `FunnelJourneyRecorder`, `FunnelJourneyHandoff`, `Rules/*`), `app/Console/Commands/AdvanceFunnelJourneys.php`, `config/funnel_journey.php` | [leads/funnel-journey/readMe.md](../../modules_handbook/manage/leads/funnel-journey/readMe.md) (the main reference, ~670 lines) |
| **Per-funnel opt-in** ("Sales flow" = Preview / Project) | Events → Funnels → Edit | `EventFunnel::JOURNEY_*`, `journey_kind` | [events/funnels/readMe.md](../../modules_handbook/manage/events/funnels/readMe.md) |
| **Hand-off outcome form** "How did the call go?" (DATA 2/4), "will join next time" mute | Lead → Action items; My Work → Log the call | `HandoffOutcome`, `Components/Leads/HandoffOutcomeModal.vue`, `LeadActionItemOutcome` | funnel-journey §4b |
| **DATA 1–5 Call questions + answers**, readiness amber | Funnel page → Call questions; lead → Journey → "What they told us" | `FunnelQuestionSet`, `FunnelJourneyAnswer`, `Support/HandoffQuestions`, `src/Lead/Support/ReadinessColumns.php` | funnel-journey §4c |
| **After-webinar rules** (attended/paid conditions, Preview-attendee-only AI call, per-rule M4), **AI-call pacer** | Funnel → Automation tab | `src/Event/Support/FunnelRuleAudience.php`, `SendFunnelAiCall`, `RETELL_CALLS_PER_MINUTE` | [events/funnel-automation/readMe.md](../../modules_handbook/manage/events/funnel-automation/readMe.md), [events/funnel-whatsapp/readMe.md](../../modules_handbook/manage/events/funnel-whatsapp/readMe.md) |
| **From Preview** candidate list (review, then register on a Project session) | Project session → Registrations → "From Preview" | `src/Event/Services/PreviewCandidates.php`, `PreviewCandidatesController` (`/manage/events/{id}/registrations/candidates`) | funnel-journey §3e |
| **REP after payment** ("book the 1-1 Zoom" task) | My Work | `Rules/AssignRepWhenPaid`, `FunnelJourneyHandoff::pickRep` | funnel-journey §3d |
| **Lead reps** (many staff per lead + time each; the ONE REP source; top REP = most engaged) | Lead header "Reps:" + Manage; Leads REP column / sort / `top_rep` / `rep` filters | `src/Lead/LeadRep.php`, `Repositories/LeadRepRepository`, `app/Console/Commands/RollupLeadReps.php`, `RepsController`, `Components/LeadRepsModal.vue` | [leads/readMe.md](../../modules_handbook/manage/leads/readMe.md) ("Lead reps" bullet) |
| **Account manager follows the Top REP** (only people on the round-robin list; score = talk seconds + 10 s per staff WhatsApp message; moves only when ahead by >20% and ≥5 min — D7/D8, 2026-10-11) | automatic, every 15 min, and at once on every payment (D9) | `app/Services/LeadDistribution/TopRepOwnership.php`, `app/Actions/Payment/RecomputeTopRepOnPaymentAction.php` | leads/readMe.md |
| **Company Round Robin** (one editable list, repeats = weight; names the manager of every new lead) | Setting → Lead Distribution → Round Robin (`/manage/lead-distribution/round-robin`) | `src/LeadDistribution/LeadRotation*.php`, `Support/RoundRobinTurn.php`, `Repositories/LeadRotationRepository.php`, `app/Jobs/Lead/AssignRoundRobinManagerJob.php`, `RoundRobinController`, `Pages/Manage/LeadDistribution/RoundRobin.vue` | leads/readMe.md (round-robin bullet), funnel-journey §3b |
| **Zoom actual duration** everywhere (not booked length; "Not held") | every Zoom time in the app | `zoom_meetings.actual_seconds` etc., `ZoomMeeting::SECONDS_SQL`, `app/Console/Commands/SyncZoomActualDurations.php` | [zoom/readMe.md](../../modules_handbook/manage/zoom/readMe.md) ("How long a meeting ACTUALLY ran") |
| **My Work** (shown as **My Workspace** since 10-12) = the ONE task list. *Now:* **Sales steps** (default, `MyWorkResponsibilities`) + **Action Item** (ordinary tasks, `MyWorkBoard`; To do / Done; "Tasks nobody holds"); Today / replies / My leads / This week sit in the hidden Schedule & messages tab | `/manage/my-work` (first sidebar entry) | `MyWorkController`, `src/Lead/Services/{MyWorkBoard,MyWorkResponsibilities}.php`, `Pages/Manage/MyWork/Index.vue` | [my-work/readMe.md](../../modules_handbook/manage/my-work/readMe.md) |
| **Action Items page retired** (→ redirect to My Work); Hub "My Checklist" modal removed | `/manage/action-items` → My Work | `routes/web.php` redirect; deleted `Manage\ActionItemsController` (NOT `Manage\Leads\ActionItemsController`, which still owns every task write) | my-work/readMe.md "The one task list" |
| **Sales flow guide** tab (the ONLY copy of the guide): *now* Live flow & actions (`?guide=live`) + How the three stages work (`?guide=flow`) + the text tabs | `/manage/my-work/sales-flow` | `Pages/Manage/MyWork/SalesFlow.vue`, `Partials/salesFlowOperations.js` (the three charts), `Partials/SalesJourneyWorkspace.vue`, `Partials/salesFlowGuide.js` (text; its `FLOW_CHART` + `SalesFlowChart.vue` now draw only the per-lead map) | my-work/readMe.md "Sales flow guide" |
| **Where a lead is on the flow**: 3-stage bar + highlighted chart + list pills | Lead page/modal top; Journey tab; Leads list Journey column | `src/Lead/Journey/Support/SalesFlowChartPath.php`, `Components/Leads/SalesFlowProgress.vue`, `LeadsController::journeyPayload()`, `FunnelJourney::chipsForLeads()` (`lead_flow`) | funnel-journey §6; [04 design](04-sales-flow-chart-path-design.md); **fixed 2026-10-13: [05](05-review-findings-2026-10-07.md)** |
| **Journey board** (funnel page tab) + **Sunday "Sales flow board"** report + Leads journey filters + `journey_overdue` flag | Funnel page → Journey tab; CEO → Reports; Leads filters | `src/Lead/Journey/JourneyBoard.php`, `src/Report/Definitions/SalesFlowWeeklyReport.php`, `LeadQueryRequest`, `AttentionFlags` | funnel-journey §6c, [ceo-dashboard/reports/readMe.md](../../modules_handbook/manage/ceo-dashboard/reports/readMe.md), [leads/pay-attention.md](../../modules_handbook/manage/leads/pay-attention.md) |
| **Time with Leads** | CEO → Employee Performance → Time with Leads | `TimeWithLeadsController`, `src/Ceo/Services/TimeWithLeadsReport.php` | [ceo-dashboard/employee-performance/readMe.md](../../modules_handbook/manage/ceo-dashboard/employee-performance/readMe.md) |
| **Calendar for every admin** (*since 10-12 a tab of the My Workspace strip; the sidebar entry stays only for admins with no lead level*); **Dashboard menu super-admin only** | sidebar | `ManageLayout.vue`, `CalendarController`, `Activity::toCalendarArray`, `ZoomMeeting::toCalendarArray`, `useOperationsLanding.js` | [calendar/readMe.md](../../modules_handbook/manage/calendar/readMe.md), [agents/readMe.md](../../modules_handbook/manage/agents/readMe.md) |
| **All admins read all leads** (sales roles get view-all incl. Sales Dashboard commission) | — | migration `2026_10_05_100001_grant_view_all_leads_to_sales_roles` | [people/roles/readMe.md](../../modules_handbook/manage/people/roles/readMe.md) |
| 4 WhatsApp templates submitted to Meta (Pending on 10-05) | Messages → Templates | — | [03-open-items.md §B](03-open-items.md) |

Also touched (doc updates in the same commit):
- [operations/readMe.md](../../modules_handbook/manage/operations/readMe.md)
- [payments/payment-automation/readMe.md](../../modules_handbook/manage/payments/payment-automation/readMe.md)
  (receipts for payments with no payment link)
- [engagement/perimeter.md](../../modules_handbook/manage/engagement/perimeter.md) and
  [engagement/sales-projects.md](../../modules_handbook/manage/engagement/sales-projects.md)
- [membership/memberships/readMe.md](../../modules_handbook/manage/membership/memberships/readMe.md)
- [leads/readiness-verdict.md](../../modules_handbook/manage/leads/readiness-verdict.md)
- [shared/notify/readMe.md](../../modules_handbook/shared/notify/readMe.md) (new events)
- [shared/voice-agent/readMe.md](../../modules_handbook/shared/voice-agent/readMe.md) (pacer, refusals)

On 10-02 (before the plan) the funnels, leads, engagement, membership and payments handbooks were corrected against
the code; that work is in the owner's commit `08698166e`.

**The tests that pin this work:**
- `tests/Feature/Lead/FunnelJourneyTest.php`
- `tests/Unit/Lead/SalesFlowChartPathTest.php` (also pins `NODES` / `EDGES` to `salesFlowGuide.js`)
- `tests/Feature/Lead/JourneyBoardTest.php`
- `tests/Feature/Lead/LeadRepsTest.php`
- `tests/Feature/LeadDistribution/RoundRobinTest.php`
- `tests/Feature/Manage/MyWorkTest.php`
- `tests/Feature/Calendar/CalendarAccessTest.php`
- `tests/Feature/Manage/Events/PreviewCandidatesTest.php`
- `tests/Feature/Event/FunnelAutomationReminderTest.php`
- `resources/js/Pages/Manage/MyWork/Partials/SalesFlowChart.test.js`

## 2. Git state (2026-10-07 02:09)

- Branch **`dev-shawn`** = master `ad0a6aa26` + **`20e1678cb`**, pushed to `origin/dev-shawn` (fast-forward, no force).
- The working tree was clean right after the commit. Other sessions may have changed files since; check `git status`.
- To ship: open a PR `dev-shawn` → `master` (the owner has not asked yet), then follow
  [03-open-items.md §C](03-open-items.md). Memory: never squash-merge `dev-chen` PRs; for `dev-shawn`, ask the owner.
- What happened during the commit (GitHub Desktop's branch switch left conflicts; it was fixed by fast-forwarding):
  see [01 → 10-07](01-session-log.md).

## 3. How to work with this owner (MUST follow)

These rules come from `CLAUDE.md`, `GUIDELINES.md`, `CLAUDE.local.md` and the memory folder
`C:\Users\zhish\.claude\projects\c--Users-zhish-work-petav3\memory\` (index `MEMORY.md`). Read those too.

**Communication**
- **Reply in Mandarin (简体)** with English technical terms. The owner calls himself a newbie (小白): keep it simple and
  short, and put numbers in tables. Code, comments and docs stay in English.

**Shared working tree and database**
- **Several sessions run at the same time** on the same working tree and the same local DB. If a file you edited lost
  your changes, or broke, **tell the owner** instead of silently redoing it.
- **Never `git stash`** — a stash once swept another session's work. **Never `npm run build`** — the owner keeps
  `npm run dev` running. **Never `migrate:fresh` the `petav3` DB.** Commit or push **only when asked**.

**Tests**
- Use `phpunit.audit.xml` → DB `petav3_audit_testing`, for example
  `php -d memory_limit=2G vendor/bin/phpunit -c phpunit.audit.xml <file>`.
- Never run two phpunit processes on the same DB at once.
- Other local test DBs: `petav3_testing`, `petav3_testing_claude`, `_claude_2`, `_claude_3`, `_claude_4`.
- Tests are proportionate (CLAUDE.md): a bug fix gets ONE regression test; a style change gets none.
- Page-render tests need `npm run dev` (`public/hot`). Without it they 500; that is not a regression.
- Pre-existing red tests are not yours: `useSalesCoachChat` (2), `DraftLiveQaAnswerTest`, CEO chat 403, the
  FunnelAutomation placeholder email, the Zoom Evaluation vitest, Customer Journey `coverageGaps`. Isolate-run on a
  clean HEAD to prove a regression.

**Documentation**
- **Update the handbook in the same change** (`docs/modules_handbook/…`). For the catalogue, start at
  `docs/modules_handbook/shared/project-catalogue/start-here.md`.

**Sending**
- **HARD RULE: never send a WhatsApp, place an AI call or run a blast** without the owner asking for THAT send.
  Template submission to Meta was explicitly asked.

**Production**
- The production read-only DB account (`PETAV3_READ_DB_*` in `.env`) is SELECT-only. Never commit its credentials.
  Use it to check facts, never to write.
- **Local-only files** are listed in `.git/info/exclude` and must never be `git add -f`'d: `config/db_sync.php`, the
  `SyncDatabaseFromProduction` command, `PinsUtcSessions`, its test, `docs/operations/local-database-sync.md`,
  `phpunit.claude.xml`.

**Local machine**
- Laragon + PHP 8.4, https://petav3.test.
- MySQL is often OFF ("connection refused" = Laragon MySQL not started; ask the owner, or start it as described in
  the memory file `local-dev-environment.md`).
- Horizon / queue runs in WSL2, usually not running, so nothing is queued or sent locally unless WSL is up.
- Keep `bootstrap/cache/config.php` cached (the Apache putenv race): re-run `php artisan config:cache` after any
  `.env` edit.
- The local `petav3` DB is a production copy, last synced 2026-10-06 with `/sync-prod-db`. It has **no funnel
  journeys** (production has none yet).

**Workflows**
- Ultracode was on in this session (multi-agent workflows for build, review and verify). The owner accepted the
  token cost and has hit usage limits several times; say so if a workflow stops early.

## 4. Glossary (as the owner uses the words)

**Funnels and stages**
- **Preview webinar** — funnel "Trust Nurturing - Property Investment"; sells memberships.
- **Project webinar** — funnel "Property Closing"; sells a project fee (e.g. ViiA RM 299).
- **第 1 / 2 / 3 段** — the flowchart's three stages: before the Preview / after the Preview / after the Project.
  In code: the chart's *band*. Do not confuse it with `FunnelJourney::flowStage()` (`flow_stage`), which is wrong for
  paid-before-verdict leads. Since 10-08 (D1) the live charts and My Work band work by the owner's three **images**
  (`jstage` 1·2·3, `MyWorkResponsibilities::QUEUES`); the unpaid follow-up after the Project webinar is Stage 3.
- **Journey** — one row per (lead, funnel) in `funnel_journeys`, with its `step` (the box), `stage`, owner and an
  append-only log (`funnel_journey_events`).

**People**
- **Account manager** — `leads.assigned_admin_id`, ONE per lead. Named by the Round Robin; follows the Top REP (D7/D8, re-checked at payment — D9).
- **REP** — anyone handling the lead (`lead_reps`, many). The top REP = most engaged. After payment, the account
  manager IS the REP who books the 1-1 Zoom.

**Messages and data**
- **M1** — the welcome WhatsApp.
- **M2** — "让 AI 打给你", sent to people who unticked the AI call.
- **M3** — missed-call WhatsApp with a callback button.
- **M4** — the after-webinar missed-call WhatsApp (`ai_caller_missed_after_v1`).
- **DATA 1–5** — what each call learns: 1 = AI call before the webinar; 2 = colleague before; 3 = AI after; 4 =
  colleague after; 3+4 / 5 = the REP's call after payment (Preview / Project).

**Outcomes and screens**
- **Booked** = the booking fee is paid to the developer (closing). **Converted** = SPA signed.
- **From Preview** — the Project session's candidate list of Preview people, reviewed before registering.
- **My Work** — every person's one task list and home page.
- **Sales flow guide** — its second tab, the team's reference.
