# My Workspace (formerly My Work)

> **2026-10-15 — a third My Task tab, 2 Rounds AI Call (owner).** The account manager's grade-B leads: AI
> call 1 → the AI's answer → AI call 2 → a booked human call. Its own page and controller (it loads nothing of Sales
> steps / Action Item): [ai-rounds.md](/docs/modules_handbook/manage/my-work/ai-rounds.md).

> **2026-10-12 — renamed, and two new tabs (owner).** The screen name is **My Workspace** everywhere a user reads
> it (sidebar entry, tab, page title, sales-flow guide copy, "Open in My Workspace"). URLs (`/manage/my-work…`),
> route names (`manage.my-work.*`), PHP/JS identifiers, file names, this folder and test names keep `my-work` /
> `MyWork`. **Calendar** left the Operations sidebar and is now a tab of this strip, and **My Sales** is a new tab —
> see *Calendar tab* and *My Sales tab* below. Older paragraphs that still say "My Work" mean this page.

> **Sales flow — owner decisions D1–D5, 2026-10-08:** My responsibilities and the Sales flow guide's **Live flow &
> actions** follow the owner's three flowchart images — Stage 1 *Registration → Preview webinar*, Stage 2 *After
> Preview → Project webinar*, Stage 3 *After Project webinar → Closing*. The live chart (all three stages, counts from
> `PreviewJourneyBoard`, `ProjectJourneyBoard` and `ClosingJourneyBoard`, optional `flowBoard` prop) is the shared
> [Sales flow chart](/docs/modules_handbook/shared/sales-flow-chart/readMe.md). Every human item records its outcome
> through [Pending / Done](/docs/modules_handbook/shared/sales-flow-chart/record-contact.md). This overrides the
> older descriptions further down where they disagree.
>
> **2026-10-11 — D6 + D10.** **Stage 1 is open (D6):** any sales admin who can see a customer still in Stage 1 may
> record a contact (Pending / Done) on its Stage 1 steps (`preview_invite`, `preview_call`); Stage 2/3 keep D5 (account manager, sales
> owner, task holder, super admin). The rule is `FollowUpAccess::canRecord()` — see
> [Pending / Done → Who may record](/docs/modules_handbook/shared/sales-flow-chart/record-contact.md). **Help team
> (D10):** an entry under Stage 1 in the Steps sidebar listing colleagues' Stage 1 customers who need help — overdue
> calls nobody made, and new customers nobody has contacted for 3 days — see *Help team* below.


> **Labels (owner, 2026-10-12):** the strip's first tab reads **My Task** (the sidebar entry and page header stay
> **My Workspace**, the section's name), and the work tab once called **Assigned tasks** reads **Action Item** — it
> lists open `lead_action_items` assigned to the person (`?tab=tasks`, key unchanged). Elsewhere in this file
> "Assigned tasks" means that tab.

**Nav:** Operations suite → **My Assistant** (first entry, above Dashboard) → **My Workspace**, the first main tab
of the `MyAssistantTabs` hub (Wai Kit, 2026-10-31: My Workspace, the Hermes **Chat** and **Revenue Intelligence**
were three sidebar entries and are now one, with Revenue Intelligence last) → `/manage/my-work`. The entry lands
here for anyone with a lead level, and it is also where `useOperationsLanding()` sends anyone who can see leads, so
the Operations tile on the Hub lands here. My Workspace's pills (formerly the `SectionTabs` section `my-work`;
2026-10-06, extended 2026-10-12): **My Task** (this board) | **Calendar** (`/manage/calendar`) | **My Sales**
(`/manage/my-work/sales`, `view-projects`) | **Sales flow guide** (`/manage/my-work/sales-flow`, see *Sales flow
guide* below). The hub resolves the active pill by the longest matching path (My Task's path is a prefix of its
siblings'). The sidebar entry's `prefixes` are `/manage/my-work`, `/manage/calendar`, `/manage/ai-copilot` (lead
levels) and `/manage/assistant` (if offered the assistant), so it stays lit across the whole hub; the **Sales**
entry's prefixes do not include `/manage/my-work/sales`, so it stays dark on My Sales. Every page in the hub reads
**My Assistant** in its sticky header. The boss reads the board for any colleague with `?person={uuid}`.

### Calendar tab (2026-10-12)

Owner: Calendar is a tab beside My Workspace, no longer its own Operations sidebar entry. The page is unchanged
([Calendar handbook](/docs/modules_handbook/manage/calendar/readMe.md)); `Calendar/Index.vue` mounts
`<MyAssistantTabs />` (formerly `<SectionTabs section="my-work" />`) above its masthead **only when the resolved suite (`useSuite()`) is Operations
(`other`)**, where its sticky header reads *My Assistant* like its sibling tabs (the masthead still says *Calendar*). The project (`?suite=project`) and focus (`?suite=focus`) suites have no My Workspace, keep their own
**Calendar** sidebar entry and see the page without the strip. The tab has no permission key — every admin may open
the calendar (owner, 2026-10-06). An admin with **no lead level** cannot see My Workspace, so for them only the
Operations nav keeps a **Calendar** entry (`unless: LEADS_ANY` in `ManageLayout` — `unless` now also takes a list:
hidden from anyone holding ANY of them); without it they would have no way in from the sidebar.

### My Sales tab (2026-10-12)

The Sales Projects **By Deal** list ([sales-projects.md](/docs/modules_handbook/manage/engagement/sales-projects.md),
`Manage/SalesProjects/Index`) for **me only**: deals where the signed-in person holds **any** pipeline role
(`engagement_assignments.admin_id` — the page's existing `assignee` filter, so the numbers equal picking yourself on
the Team performance rail of `/manage/sales-projects`).

- **Route:** `GET /manage/my-work/sales` → `SalesProjectsController@mine` (`manage.my-work.sales`, `permission:view-projects`
  like the Sales Projects index), and `GET /manage/my-work/sales/export` → `@exportMine` (`manage.my-work.sales.export`).
- **How the holder is forced:** `mine()` calls `bookingsView($request, $user, $user)` (the third argument is the holder); `holderScoped()` hands
  every reader a **duplicate** of the request whose `assignee` is replaced by `[viewer uuid]` — the rows, the status
  chip counts, the headline cards, the project / bank option lists and the export all see it, and a posted
  `?assignee=` is ignored. A duplicate rather than `merge()`, so the paginator's links (built from the real request)
  never carry the forced value.
- **What it shows:** the headline cards (Sales Value, Booked / Total Commission, Conversion Rate, Payout), the status
  strip and the booking list — all for me. **Not** shown: the Team performance rail, the Teammate drawer dimension and
  its chip (`filters` echoes no `assignee`, `bookingTeamPerformance` is empty), the Sales hub's stage rail
  (`stageCounts` is `[]`), the By Deal / By Project pivot, and Import / Add Project. Search, status chips, project,
  bank, dates, payout, sort, rows-per-page and pagination all work; their visits stay on `/manage/my-work/sales`
  (`DetailedBookingView`'s `baseUrl` prop; `DataTable` sorts and pages from `page.url`).
- **Chrome:** the prop `mine: true` makes the page mount `<SectionTabs section="my-work" />` instead of `SalesTabs`,
  `#header` **My Workspace**, masthead **My Sales** — *"Deals where you have a role — your bookings, sales value and
  commission."*
- **Row actions** (status select, Assign, booking edit, Add Booking) post to their existing endpoints, which answer
  `back()` — so they land back on My Sales with its query intact.
- **Export:** the Export menu's base is `/manage/my-work/sales`, so the file goes through `exportMine()` — the same
  `bookingListQuery()` with the same forced holder (§14: one query, `per_page` never read). File name `my-sales-…`.
- Pinned by `SalesProjectsIndexTest::test_my_sales_lists_only_the_viewers_deals_whatever_assignee_is_posted`.

## What it does

The default workspace answers **which part of the flow I own, which customers are there,
and what I should do next**. It is about one selected person. A supervisor reads the same
workspace through the existing person picker.

### Sales steps workspace (D1–D5 2026-10-08; simplified 2026-10-09; rebuilt 2026-10-14)

> **2026-10-14 — one number, one list (owner + Shawn).** Eighteen steps × four views (To do · Waiting · Done · Extra:
> 72 numbers) and the "How did the call go?" form were too hard to read. The tab (key `workflow`, label **Sales
> steps**) now answers *"who do I contact today?"*; the design was reviewed as a clickable mock first. It reads:
>
> 1. **Today** (`data-today`) — ONE number: the customers with **New** or **Pending** work across all steps, and
>    nothing else. Page-wide *done today* / *system is handling* / *Later list* pills sat here first and were removed
>    the same day (Shawn: confusing): beside the list's own *To do · Done · Later* counts — which follow the
>    open step — they gave two numbers for one word. `summary` still carries those counts. The how-to sentence under
>    the number went too (Shawn, same day).
> 2. **Your customers by step** (left, 300px; a `<select>` below `xl`) — **All steps**, then every step in its stage
>    panel (sky / indigo / emerald, `STAGE_SKIN` in `salesFlowSkin.js`), each with ONE count (its New + Pending
>    customers, blue when > 0) and, grey, its Later count (*+1,975*). Clicking a step lists only that step; clicking
>    a **stage heading** (*STAGE 2 · After Preview → Project webinar*, with the stage's own count) lists every step of
>    that stage (`rqueue=stage_2`, `STAGE_SCOPES`; the picker has *All of Stage N* too); clicking either again returns
>    to All steps. **Help team** (D10) stays the last entry of the Stage 1 panel (below). From `xl` the panel is
>    **sticky** under the 64px header (`top-20`, its own scroll when taller than the screen); whatever is open is
>    enlarged (`PICKED`: `scale-105`, shadow, 2px ring) and its stage panel outlined (`STAGE_SKIN[n].ring`), so the
>    reader sees what the list shows. Picking from far down the page scrolls back to the list's top.
> 3. **The list** — the selected step (or all) in one of three lists, a segmented control beside the heading.
>    Under the heading (*Stage N* + the step's name) there is no instruction line any more: **Who is in this list?**
>    (`data-step-rules`) opens [`StepRulesModal.vue`](/resources/js/Pages/Manage/MyWork/Partials/StepRulesModal.vue)
>    — short points, read at a glance (Shawn: "一眼就看懂"): **Why they are here** (✓ conditions; for the two
>    *Call before* steps, a mini timeline of how the system hands them over — grey system steps, then *The call
>    comes to you*; for the six suggestion steps a *New for 7 days … then Later* chip) → **What you do** (numbered
>    steps on a brand panel, then the Pending / Done pair, or *No Done button — it completes by itself when the
>    record is saved* for a paid service step) → **They leave this list when** → an amber **note** for the trap
>    (a colleague's registration never comes here) → **How every list works** folded in a `<details>`.
>    Data: `selectedQueue.rules` = `{why[], flow[]|null, do[], leave[], timing|null, note|null, closes:
>    'buttons'|'record'}` from `MyWorkResponsibilities::QUEUE_RULES` via `rules()` (`closes` from
>    `LeadActionItem::SERVICE_QUEUES`; `{fresh}`, `{recontact}`, `{handoff}`, `{neglected}`, `{window}` filled from
>    `FRESH_DAYS` and config), and `list_rules` (`LIST_RULES`). All steps or a stage shows only the last part,
>    open. A new queue needs its `QUEUE_RULES` entry — `MyWorkTest` fails on a step without one or with an
>    unfilled `{placeholder}`. The lists:
>    **To do** (default) · **Done** · **Later**. One card per customer (`ResponsibilityRows.vue`): name (opens
>    the lead modal on Journey) · *Stage N* · an **urgency tag** · the step · its Session / Project · the next step
>    in one sentence · what the AI call heard · the last contact · phone; on the right the **lane** badge and the two
>    buttons **Pending** / **Done** (`FunnelFollowUpButton`, size `md`, one click, nothing to fill —
>    [record-contact.md](/docs/modules_handbook/shared/sales-flow-chart/record-contact.md)) — or, for a paid
>    customer's step that only its real record completes (`member_*`, `project_handoff|preparation|zoom|meeting|close`,
>    D4), that step's own link (*Arrange consent*, *Open in Sales Projects*). Under To do: **The system is still
>    handling these · not counted** — grey rows (at most `SYSTEM_LIST_LIMIT`, 20) whose welcome / AI call /
>    missed-call message is still running. A customer with several steps in the list expands in place
>    (*N more steps for …*); work in another step says so with **Open the Journey**.
>
> **Lanes** — `MyWorkResponsibilities::LANES`, set by `classify()` over the factual `state` the boards share
> (the states, `STATES`, are unchanged):
>
> | Lane | When | Counted |
> |---|---|---|
> | **New** | `todo` / `review` work nobody has tried; a suggestion younger than `FRESH_DAYS` (7) | yes |
> | **Pending** | `scheduled` (an agreed later time, a booked meeting) or the last recorded contact was *No answer* | yes |
> | **Done** | `done`; on the *Done* list when its task closed / its contact was recorded in the last `MyWorkBoard::DONE_DAYS` (30) days | — |
> | **System is handling** | `waiting` — the automation boxes of a tracked journey | no, grey |
> | **Later** | a suggestion (`candidates`) whose reason is older than 7 days | no, Later list |
>
> A suggestion's age (`freshSince()`): an invite — the lead's `created_at`; a webinar follow-up (no-show, attended
> not paid) — its Session's start; a Project invite — the latest attended Preview (`previewAttendance()`, one query).
> So the after-webinar follow-up (flowchart T2 / T4) is **must-do for 7 days**, then fades to Later. Counts are
> **customers** everywhere (a customer with two steps counts once on All steps).
>
> **Urgency** (`urgency()`): 1 — a call before a webinar that starts within `URGENT_WEBINAR_HOURS` (24): *Webinar
> today* / *Webinar tomorrow*; 2 — an overdue / due-today task: *Overdue* / *Due today*; 3 — other New work (a
> fresh suggestion says why: *New lead this week*, *Missed it this week*, *Attended this week*, *Joined a Preview
> this week*); 4 — Pending. The list sorts by it, New before Pending, then date, then task priority (`order()`).
>
> **Help team** (owner decision D10, 2026-10-11) — the last entry of the **Stage 1** panel (and the mobile picker:
> *"Help team — 3 need help"*), one red count of customers. Selecting it (`rqueue=help_team`) shows its rules
> behind **Who is in this list?** (`QUEUE_RULES['help_team']`; the old hint line is no longer shown) and one list in place of the three-list
> control (`hpage`): overdue calls first, then new customers nobody has contacted, each naming its holder / account
> manager, each with Pending / Done (D6). Its entries get the same lanes and urgency. See *Help team* below.
>
> **Every way into a customer opens the lead quick-view modal** (`useLeadModal().openLead`), never the lead
> page (owner, 2026-10-09 — on the Action Item tab too since 2026-10-13: the customer's name, **Task details** and,
> on *Tasks nobody holds*, **Assign on the lead** / **Open the lead** open the modal, the last two on its Action
> items tab; `Index.vue`'s `openCustomer()` = `leadModalTarget()` + `openLead`): the name and **Review the
> Journey** land on Sales → Journey; a step whose server link
> is the lead's own page (e.g. *Arrange consent* → `?tab=portal&ptab=fpa`, a done task → `?tab=actions`) opens
> the modal on that tab (`utils/leadModalLink.js`). The Sales flow roster (`SalesJourneyWorkspace`, shared by
> the company page and a funnel's Journey tab) follows the same rule through `JourneyContactCell` /
> `JourneyWorkCell`. Index.vue: only `?task=` selects **Action Item**; `?lead=` belongs to the modal (a
> refresh reopens it — `useLeadModal`'s close-on-navigate rule no longer closes it on the initial page's
> `navigate` event) and never switches the tab or filters the task list — a task link's customer comes from
> the task itself. Only `JourneyWorkQueue::row()` (the Sales flow roster's *Open task*) builds a
> `/manage/my-work?task=…(&person=…)` link; `MyWorkResponsibilities::taskWork()` links the lead modal on Action
> items (`/manage/leads/{uuid}?tab=actions`). Neither carries `lead`.

**Sales steps** (formerly *My responsibilities*) is the default workspace. It has **no stage tabs**: the three
**image stages** group the steps (each queue's `stage`) and badge each item. A step (queue) narrows the page
to that step, a stage heading to that stage (`stage_N`, 2026-10-14); **All steps** shows everything. Done and
Later are lists, never a fourth stage. The former `STAGES` / `OVERALL_TAB` constants are gone; today's `stages`
payload is only the three headings' counts.

The three workspaces use shared `ShowTabs` with the nested `pills` variant:
**Sales steps** (its All-steps To do count, `responsibilities.summary.todo`), **Action Item** (open-task count —
every open task, future-dated and undated included) and **Schedule & messages** (hidden for now, see below) — both
work tabs carry a count so the reader sees where today's work is without clicking (owner, 2026-10-11). Each of the
first two opens with one plain line saying what it is (`data-tab-hint`):
*Sales steps* = every customer's standard sales steps, found by the system, closed with **Pending / Done**;
*Action Item* = one-off jobs from a colleague, an approved AI plan, or a promise the AI caught in a Phone Call /
Zoom / Showroom F2F recording (`conversation_source`), closed with **Done**. Each row's source chip
(`MyWorkBoard::sourceOf()` → `Index.vue` `sourceLabel`): *AI plan* (`source_action_plan_id`), *AI insight*
(`source_proposal_id`), **AI** (`conversation_source` — the model's own word for that origin,
`LeadActionItem::ORIGINS`; it read *Colleague* until 2026-10-13), *Colleague* (anything else); *Sales flow*
(`funnel_journey_id`) only on the rare hand-off whose journey does not resolve (below).
Only the selected body mounts. `?tab=workflow|tasks|support` survives refresh and sharing;
the host syncs through Inertia's client-side replace so searches and pagination use the
same URL, without refetching the board on each tab switch. A `?task=` link opens Action Item — unless it
names a sales-flow task, which the controller redirects to its step (`tab=workflow&rqueue=…&rview=…`, from
`MyWorkResponsibilities::stepOf()`: a task closed in the last 30 days with a human result → Done; anything else → To do,
where an open one is New / Pending and one closed **without** a human result is *Check the old task*). The colleague picker and unassigned-task entry sit beside
the workspace tabs through `ShowTabs`' optional `actions` slot on desktop, and below them
on smaller screens. They remain visible on the single-tab unassigned-task board.

**Stage banding** — `MyWorkResponsibilities::QUEUES` (queue → stage, title, instructions, completion), in the order
of the owner's images. The titles below are the exact strings shown:

| Stage | Queue → title |
|---|---|
| **1 · Registration → Preview webinar** | `preview_invite` *Invite to a Preview webinar* · `preview_call` *Call before the Preview webinar* (DATA 2) |
| **2 · After Preview → Project webinar** | `preview_no_show` *Call: missed the Preview* (DATA 4) · `preview_unpaid` *Call: joined the Preview, no membership yet* (DATA 4) · `preview_after_call` *Call after the Preview* (DATA 4) · `member_preparation` *New member: consent, questions, WhoPay* · `member_zoom` *New member: book a Zoom call* · `member_meeting` *New member: hold the Zoom call* · `project_invite` *Invite to a Project webinar* · `project_call` *Call before the Project webinar* |
| **3 · After Project webinar → Closing** | `project_no_show` *Call: missed the Project webinar* (DATA 4) · `project_unpaid` *Call: joined the Project webinar, fee not paid* (DATA 4) · `project_after_call` *Call after the Project webinar* (DATA 4) · `project_handoff` *Fee paid: name the salesperson* (DATA 5) · `project_preparation` *Fee paid: consent, questions, WhoPay* · `project_zoom` *Fee paid: book a Zoom call* · `project_meeting` *Fee paid: hold the Zoom call* · `project_close` *Close the sale: Won or Not closed* |

The (DATA n) box is not in the title; it ends the step's completion line ("… Flowchart: DATA 4."), shown with an
item's details. `FunnelFollowUpRepository` writes a recorded follow-up task's body from the title + instructions.

Unpaid work after the Project webinar is **Stage 3** (image 3), no longer Codex's "business Stage 2". Paying a
Membership and attending a Preview are independent facts: an unpaid attendee can need Membership follow-up and a
Project invitation at the same time. Each new Session keeps its own required contact.

**Three kinds of work** (`source`):

- **Responsibilities from facts** (`candidate` / `record`) — for every live (unmerged) and **active** Preview and
  Project funnel (a paused funnel — `is_active = false` — stops its automation, owner 2026-10-02, so it produces no
  Sales-steps work; tasks it already handed out stay their holder's, and a member's contact still falls back to
  the first Preview funnel when every one is paused), the board populations restricted to the person's managed leads
  (`assigned_admin_id`). **Every** context of a managed customer is the account manager's — normal responsibility
  follows `assigned_admin_id` — except a colleague's hand-off: when the journey's owner (`owner_user_id`, the
  hand-off's holder) is somebody else, the `human` context and any context of the Session their open hand-off
  (`human_pending`) is on are skipped (`heldByColleague()`): their task is that work, and a second Pending / Done
  would meet a 409. Until 2026-10-13 a managed customer whose journey owner was a colleague lost every other
  obligation too (e.g. a later no-show) from every board. Preview obligations come from `PreviewJourneyBoard::contexts()` (incl. a later no-show
  after an attended Session, and the contact before an upcoming tracked Session); Project obligations are one per
  customer × Project from `ProjectJourneyBoard::population()`. Fact → queue and state use the boards' own map
  (`JourneyWorkQueue::queueForFact()` / `stateForFact()`).
- **Service steps** (`record`) — a managed lead with an active Membership gets the member steps (preparation from
  `FpaProgress`, then the member consultation from `MyWorkConsultations`); a paid Project opportunity the person owns
  (its sales owner, else the account manager while nobody is named) gets its Stage 3 step from
  `ClosingJourneyBoard::population()` ([closing.md](/docs/modules_handbook/shared/sales-flow-chart/closing.md)) —
  **one item per opportunity** (keyed by the board's unit, `engagement:{id}` or `pending:{lead}:{project}`, since
  2026-10-13: two deals of one customer on one Project at the same step were one item, the later overwriting the
  earlier), except `project_preparation`, which is the customer's FPA and stays ONE item per customer × Project.
  A service step completes only from its record.
- **Tasks** (`task`) — every sales-flow task the person holds as an active assignee: an automation hand-off on one of
  the lead's funnel journeys, or a task with a `responsibility_queue`. A task replaces the inferred entry for the same
  queue, Session and Project (a `human` fact: any contact task of that Session); a service task never replaces its
  step.

**Suggestions** are the `candidates` state: registered / eligible / no-show / attended-unpaid facts with no
standing recorded contact. They carry no invented deadline: **New** for their first `FRESH_DAYS` (7) days, then on
the **Later** list (see *Lanes*). **Customers a colleague registered** (agreed-Session
form, From Preview, admin add, CSV) who are waiting for their webinar sit on the `webinar` node and are **omitted** —
they are not human work (D2). A paid Project context is omitted from Stage 2 (its Stage 3 entry owns it); a recorded
Not closed, a Lost deal or a stopped journey is a Stage 3 *Not closed* entry (Done) with its reason; a deal that moved to
another project (Swing) is a Stage 3 entry Done as *Moved to another project* — never *Not closed* (owner,
2026-10-13); a deal Booked / Converted without a Project fee (the board's `project:won`) is no step — Sales Projects
follows the deal.

**Lists** (`MyWorkResponsibilities::VIEWS`, `listed()`): **To do** = New + Pending, by urgency; **Done** =
finished in the last `MyWorkBoard::DONE_DAYS` (30) days, newest first — the Action Item tab's window, and the same
length as the 30-day re-contact rule, so a suggestion pressed Done stays on Done until it may come back; **Later** =
stale suggestions, newest customers first (lead `created_at`, then id). It read **Done today** (today only) until
Shawn asked why "today" (2026-10-14). Done is history: a step finished in the window and open again (a consultation
to book again) is on both lists.
The default is To do. Counts are distinct customers (`counts()`: `todo`, `pending`, `done`, `system`, `later`);
a customer can appear in more than one stage, so stage totals do not add up to a unique count.

Project follow-up uses the latest visit **within each Slot and Project**: a payment or closed outcome for Project A
does not hide an open Project B follow-up. An unknown selling mapping (and the other Project `review` contexts —
paid through another funnel, muted "next time") is a *Check records* item on the
sales-flow **boards** only: Sales steps omits Project `review` contexts and Preview `review` / `paused` nodes
(`JourneyWorkQueue::queueForFact()` gives them no step). Cancelled or
missed consultations return to an actionable rescheduling step; a past time alone is never "held".

The list (`ResponsibilityRows.vue`, cards) has **one card per customer** (15 per page, its own small pager reloads
only the `responsibilities` prop). `items[0]` is the work the card is listed under and the buttons act on it; *N more
steps* shows the customer's other items in this list, each with its own buttons. `other_work_count` counts the
customer's New / Pending work outside the list — never Later, the system's or finished steps — with **Open the
Journey** (the modal's Journey tab).

**Payload** (`responsibilities`):

```
summary        {managed, todo, pending, done, system, later}       — the whole page (all three stages), customers
queues         [{key, stage, label, instructions, completion, todo, pending, done, system, later}]
stages         [{key: 'stage_1'|'stage_2'|'stage_3', stage, label, todo, pending, done, system, later}] — each
               stage's customers (one customer in two of its steps counts once)
views          [{key: 'todo'|'done'|'later', label: 'To do'|'Done'|'Later', hint, count}] — the selected step
               (or all), before search
selectedQueue  a queue above, or {key: 'all', stage: null, label: 'All steps', instructions: null, …counts},
               or {key: 'stage_N', stage: 'N', label: <the stage's name>, instructions: null, …counts},
               plus `rules`: {why, flow, do, leave, timing, note, closes} for a step / Help team, null for All
               steps or a stage
               or {key: 'help_team', stage: '1', label: 'Help team', instructions: <the hint>, todo: <help count>, …}
list_rules     [string] — "How every list works", the numbers filled in
filters        {queue, view, search}
leads          paginator (pageName `page`) — the selected list
system         rows — the system's grey rows, To do only, at most SYSTEM_LIST_LIMIT (20)
system_total   customers the system is handling in the selected step
help           {count, list} | null — Help team (D10): null unless the viewer is a sales admin on their OWN board;
               `count` = customers; `list` = paginator (pageName `hpage`), only while rqueue=help_team
row            {key, uuid, name, contact, owner, items[], item_count, other_work_count, last_contact_at, context, work}
item           {key, queue, stage, title, context, state, state_label, source, source_label, lane, lane_label, urgency,
                done_at, session, project, owner, due_at, due_label, is_overdue, reason, completion, checklist, work,
                action_context, last_contact, ai_summary, ai_summary_at}
```

**Last contact.** Each item carries `last_contact` — the latest contact anyone recorded on that obligation
(`FunnelFollowUpState`): result, date, who, agreed next date, note, and a Not closed reason. Since 2026-10-11 a
**task** item carries it too (`taskEntry()`), so an account manager sees *"Last contact: Spoke to them · 9 Oct · by
<colleague>"* when a colleague recorded on their customer (D6) — a fact item or a task they hold. A *No answer* on an
automation hand-off does not by itself make the obligation recorded in `FunnelFollowUpState` (with nothing else
recorded it shows only in the task's attempts); once any task of the same obligation is recorded, *Last contact* is
the latest human result across all of its tasks, that No answer included. The row's
`last_contact_at` is the newest human outcome on the customer (kept in the payload; the row shows the item's own
Last contact line instead of a second date); it does not aggregate calls, WhatsApp or Zooms.

**Pending / Done** (`ResponsibilityRows` → `FunnelFollowUpButton`, contract in
[record-contact.md](/docs/modules_handbook/shared/sales-flow-chart/record-contact.md)):

- A task records through its `work.outcome_url` — offered to its holders and to anyone
  `LeadActionItem::canRecordOutcomeFor()` allows: D5 (account manager, sales owner, super admin) and, on an OPEN
  Stage 1 task of a customer still in Stage 1, any sales admin who can see the lead (D6).
- Any other item records through its `action_context`, only for a viewer `FollowUpAccess::canRecord()` allows (D5;
  D6 on a Stage 1 step): a fact while it is To do / Waiting / Suggested (and has a Session, except invitations), a
  service step until it is done. A Stage 3 paid step's context names the Project, not a funnel. On your own board
  you are the account manager, so D6 shows when a leader reads a colleague's board (`?person=`) and on the Help team
  list.
- Whoever records, the obligation counts as recorded on everyone's board (D5). A recorded suggestion shows as
  recorded until it lapses after `funnel_journey.recontact_after_days` (30); then it returns as a suggestion with its
  Last contact, and the recorder's own closed task does not hide it (D3). An agreed next date is a follow-up task.
- On a service step a contact only updates Last contact; a closed recorded service task never shows as a completed
  step (D4). An open task a colleague left (No answer, agreed follow-up) shows its `outcome_url` to anyone D5 allows
  — and on a Stage 1 step to any sales admin (D6), so the next colleague continues it instead of meeting a 409 and
  then a 403.
  A removed opportunity gets no record target.
- **Done** posts *Spoke to them*; **Pending** posts *No answer* (the task stays open). After Done on an invite /
  no-show / after-webinar contact the agreed-Session registration opens when a Session can be offered; it starts no
  automation (D2). Done on a Stage 3 unpaid contact records *Still following up*; *Not closed + reason* is recorded
  only in Sales Projects (the deal → Lost), 2026-10-14.
- Clicking a call or WhatsApp link never completes anything; an unanswered attempt keeps the obligation open.
- **Cannot be reached closes the contact like Spoke to them** (owner; 2026-10-13; no button offers it since
  2026-10-14, but older records and the endpoints keep it): a sales-flow task closed as
  *Cannot be reached* is **Done**, its state label *Cannot be reached* (`LeadActionItemOutcome::RESULTS`). It was a
  *Check records* item in To do with no button. Only a task closed without a human result (no outcome and no
  `done_by`, or a system outcome — Not called in time / No longer needed) stays a To do *Check the old task*.
  `FunnelFollowUpState` reads a recorded Cannot be reached the same way (see record-contact.md).

Normal responsibility follows the current `assigned_admin_id`, not all active REP links — every board context of a
managed customer, except a colleague's own hand-off (see *Responsibilities from facts*). Sales-flow tasks are an
independent projection by their **actual assignee**: they stay on that person's board after reassignment of the
account manager, attendance, payment or another registration. `HandoffQuestions::journeyForTask()` projects each
task's immutable `handoff_context` Session and phase, so a later registration cannot rename an earlier task's Session
or change its questions. Paid Projects follow the opportunity's `zoom_closer_id`, otherwise its closer assignment,
falling back to the account manager. Both viewer and selected-person Lead visibility apply, Project group scope is
preserved, staff accounts are excluded. Viewing creates no task, journey or message.

Query parameters (`ResponsibilitiesQueryRequest::selections()`) are `rqueue` (a step, a stage `stage_1|2|3`, `all`,
or `help_team`),
`rview` (`todo` default · `done` · `later`), `rsearch` (customer name / email — no UI, honoured from links; it filters
the Help team list too), `page` (the list) and `hpage` (the Help team list). A `help_team` the viewer may not have
(not sales staff, or on a colleague's board) falls back to `all`. Step, list and pager controls request only the
`responsibilities` Inertia prop; all preserve `person` / `suite` / `rsearch`, drop `lead` / `task` / `spage` / `rstage`
/ `rstate` and restart the pager. Search runs before customer grouping and pagination; counters describe the step
before name search. **Old links keep working:** `rstage` is ignored — the page shows every stage — while the link's
`rqueue` is honoured (the Sales flow chart's **Open in My Work** sends `rstage=N&rqueue=…`, and no longer an
`rview=optional` for invites); an old `rview` / `rstate` (or `rqueue=waiting|review`) maps through
`LEGACY_STATE_VIEWS`: todo / review / all / scheduled / waiting → To do, done → Done, candidates / optional →
Later.

When a recorded outcome agrees a next contact, the follow-up task inherits the original immutable Session, phase,
handoff kind and Project context and displays the agreed time. A consumed AI `appointment_request` is removed from
that follow-up, while its call identity is kept so a replay cannot create another confirmation task. An agreed date
is not a confirmed Calendar appointment or Zoom meeting.

**Action Item** retains the overdue-first task list, Done history and permissions. A link containing `task`
opens it directly (a bare `lead` is the lead modal's and does not). An ordinary task is ticked **Done** by its holder
on their own board.

**One piece of work, one home** (owner, 2026-10-09). A **sales-flow task** — a Funnel Journey hand-off
(`funnel_journey_id` of a journey of the same lead) or a recorded contact naming its step
(`handoff_context.responsibility_queue`); the one rule is `MyWorkResponsibilities::salesStepTasks()` — is listed in
**Sales steps only**. `MyWorkBoard::tasks()` and `done()` exclude it with `whereNot(salesStepTasks)` (the rule tests
`funnel_journey_id IS NOT NULL` first: `NULL IN (…)` is NULL, and its `NOT` would drop every ordinary task too).
"Tasks nobody holds" still lists unheld sales-flow tasks; Sales steps lists the work somebody holds, plus — on the
**Help team** list — overdue Stage 1 tasks nobody holds (*Nobody holds it*). The AI call
summary that Action Item printed on a hand-off came along: Sales steps items carry `ai_summary` / `ai_summary_at`
(`MyWorkBoard::latestAiSummaries()`), shown above the last contact. A sales-flow task's own "Open task" link in Sales
steps opens the customer's Action items (lead modal). It is **never ticked** (`done_url` is null; `POST …/done`
refuses it): it closes through its **Pending / Done** buttons.

### Help team (owner decision D10, 2026-10-11)

The boss's worry: a round-robin teammate is busy and never contacts a new customer. Any sales admin may view and contact
any colleague's Stage 1 customer at any time (D6); **Help team** is only the shortcut list of who needs help.
`MyWorkResponsibilities::helpTeam()`. Two kinds of row, both narrowed exactly as the recording rule is (a Stage 1
step of a customer still in Stage 1, `FollowUpAccess::stageOneLeadIds()`), on leads the viewer can see, never the
viewer's own (a task they hold, a customer they manage):

1. **An overdue call nobody made** (`helpTasks()`) — open sales-flow tasks dated **before today** (the `overdue`
   bucket, as `SalesWorkQueue::bucketFor()`) whose step is Stage 1. Narrowed **in SQL** to what
   `LeadActionItem::followUpQueue()` can call Stage 1 — a named `preview_invite` / `preview_call`, or an automation
   hand-off (no named step) on a Preview-funnel journey that is not a Zoom, paid or after-webinar contact — then
   confirmed with `followUpQueue()` on the few left. "Nobody called yet": no Reached / No answer / Unreachable on the
   task and no *Last contact* on its step (`FunnelFollowUpState::keyOfTask()`; an agreed follow-up task has no outcome
   of its own, but its step carries the earlier call). Item: the task (*Overdue · date*, the AI call's summary, its
   holders as `work.assignee`); **Pending / Done** post to its `outcome_url` (D6). A task nobody holds is listed too.
2. **A new customer nobody has contacted** (`neglectedLeads()`, owner 2026-10-11) — all in SQL:
   - an account manager who is not the viewer, given the lead by the **current `lead_assignments` span** (the open
     row naming that manager — every round robin, top-rep, pool and manual-distribution move writes one) at least
     `lead_distribution.help_team.neglected_after_days` (env `HELP_TEAM_NEGLECTED_AFTER_DAYS`, default **3**) and at
     most `neglected_window_days` (env `HELP_TEAM_NEGLECTED_WINDOW_DAYS`, default **30**) days ago — on a lead
     **created within the window too**. `leads.last_assigned_at` is written by the same two methods, so it agrees on
     every lead with a span (12,679 of 12,679 on the dev copy); the span is used because it names the manager.
     A manager typed onto a lead without a span (`LeadRepository::assign()`: a colleague creating a lead, the member
     import) has no reliable date and is left out. The created-at test is there because the 2026-10-08 round-robin
     backfill opened ~12,640 spans on one day: by the span alone every old lead would read "assigned 3 days ago";
   - nobody contacted them since: no `lead_reps` row with `last_interaction_at` after the span start (the rollup's
     phone / Zoom / showroom / staff-WhatsApp figures — refreshed every 15 minutes, so a call made in the last quarter
     hour may still list the customer), and no Reached / No answer / Unreachable recorded on the lead since;
   - what they owe is the Stage 1 **invitation** (`preview_invite`) on the first **active** Preview funnel (unmerged,
     by id; with every Preview funnel paused there are no rows of this kind), exactly as its board derives it: no
     registration on a live — not cancelled, not deleted — Session of any unmerged Preview funnel (the Sessions the
     boards read; until 2026-10-13 a registration on a cancelled Session or a merged funnel kept a new customer off
     the list for good), no stopped / lost / hand-off-pending journey on that funnel;
     and recording it would not conflict — no open sales-flow task, no invitation recorded within
     `funnel_journey.recontact_after_days` (D3). Item: *New customer not contacted yet* + *Assigned N days ago*, the
     invitation's instructions; **Pending / Done** post an `action_context` for `preview_invite` on that funnel, which
     `JourneyWorkQueue::owedOpenQueue()` accepts (D6).

- **Order and count** — overdue calls first (most overdue first), then new customers (longest-waiting first), one row
  per customer (`rows()`, the Sales steps row shape), *Owner:* = the account manager, 15 a page (`hpage`). The badge
  counts customers from those queries alone (no assignees, journeys-for-display, AI summaries or board builds); the
  list is built only while it is open. `rows()` answers the Stage 1 question for the page in one
  `FollowUpAccess::rememberStageOne()` batch.
- **Hint** — `MyWorkResponsibilities::helpTeamHint()`: *"Colleagues' Stage 1 customers who need help: overdue calls,
  and new customers nobody has contacted for 3 days. Call them and press Done, or Pending if they did not answer."* (the days follow the config).
- **Who sees it** — the D6 audience (`FollowUpAccess::isSalesAdmin()`: super admins, and active manage-role users
  with `sales-execution`), and only on their **own** board: it is the viewer's list of colleagues' work, and its
  buttons are worked out for the viewer, so it would mean nothing on `?person=` (there `help` is null and a
  `rqueue=help_team` falls back to All steps).
- **No notification, no hand-over.** Recording never makes the colleague the account manager or a rep; the account
  manager sees *Last contact … by <name>* (above). After a colleague's call (even *No answer*) the customer leaves the
  list (somebody has tried); any sales admin may still continue the task from the company board.
- ⚠️ **On the dev copy (2026-10-06 production snapshot)** `funnel_journeys` has 0 rows and there are 0 open sales-flow
  tasks, so kind 1 is empty until journeys run; kind 2 can only list leads created in the last 30 days (395 there).

> ⚠️ **2026-10-12 — Schedule & messages is HIDDEN for now** (owner: temporary, "make page faster"). One switch,
> `config/my_work.php` → `schedule_panel` (env `MY_WORK_SCHEDULE_PANEL`, default **false**):
> `MyWorkBoard::schedulePanelShown()`. Off, `build()` returns only `tasks` — `leads`, `flow`, `today`, `replies`,
> `week` and `candidates` (this tab's data) are not built at all (full page ~3.8 s instead of ~4.8–5.2 s on dev) —
> and the controller's `schedulePanel` prop hides the tab, so a `?tab=support` link opens Sales steps. The panel's
> template stays. Set `MY_WORK_SCHEDULE_PANEL=true` (then `config:cache` where config is cached) to bring it back;
> the tests that read the panel switch it on with `config(['my_work.schedule_panel' => true])`.

**Schedule & messages** contains today's appointments, WhatsApp replies, recent REP leads
and the weekly comparison. Replies initially show five rows with an expand control; recent
REP leads show five with a link to the complete list. These supporting cards do not stretch
the responsibility workspace into an empty dashboard.

The supervisor's **Tasks nobody holds** view retains its existing task list. It offers **no** Done and no Pending / Done
button (the page sends `person.is_me = false` there, and never did); its rows only route a task to its next owner
(*Assign on the lead* / *Open the lead*). Since 2026-10-13 the server no longer works out `outcome_url` for it
either (`taskRows($items, false)`): the record rule cost an Engagement query per hand-off row for a button nobody
saw. A sales-flow task nobody holds is recorded from the Sales flow roster or the Help team list instead.

The page itself **writes nothing**; its buttons post to the existing endpoints. Done posts to
`POST /manage/leads/{lead}/action-items/{item}/done` (`Leads\ActionItemsController@done`). The endpoint's guard is
`LeadActionItem::canToggleFor()`: an ordinary (manual) task is a shared checklist anyone who can see the lead may tick;
an insight, conversation or plan step needs its assignee. "Done only on your OWN board" is the page's rule
(`person.is_me`). A Done on a task that is no longer open (a stale page, two colleagues at once) changes nothing:
`LeadActionItemRepository::done()` re-reads the task under its lock and returns it untouched, so the first close
keeps its `done_by` / `done_at` and the journey hook does not run twice (2026-10-13). A step an approved AI action
plan generated (`source_action_plan_id`) is **left out** of the list, its count, the Done view and *Tasks nobody
holds* while the Action Plans release control (`conversation.action_plans_enabled`) is off
(`MyWorkBoard::withoutClosedPlanSteps()`): its Done and Reopen 404 then, so it could only sit there unclosable
(2026-10-13; before, it was listed and counted with no Done). It returns unchanged when the control is switched on. Contact outcomes post to the [Pending / Done](/docs/modules_handbook/shared/sales-flow-chart/record-contact.md)
endpoints. The "Waiting on a reply" dots use `ReplyOwed::TIERS`' own colour names (`red-solid` · `red` · `amber` ·
`slate`), hottest when fresh.

### From the flow chart to the contact (2026-10-08)

The task card starts with the most urgent work across channels, so an overdue WhatsApp or
Zoom booking is no longer buried below every phone task. `MyWorkBoard::grouped()` exposes
the same globally sorted `rows` as well as the existing type `groups`; the UI uses `rows`.
Order: bucket (overdue → today → later → no date), date, then priority — **High → Medium → Low → none**: a task
with no priority (the lead composer sends `null` when none is picked) sorts after Low, in PHP and in the nobody
view's SQL (`priority is null` first; until 2026-10-13 it sorted ahead of High). Sales steps' `order()` does the
same for its tasks.
Task context and assignees are batch-loaded. The page creates no inferred tasks and does
not call or message a customer on load.

`/manage/my-work?task={task_uuid}` focuses the existing authorized task list on that task's customer and
highlights / scrolls to the task (an older `&lead=` beside it is still honoured; `lead` alone opens the lead modal
and filters nothing). A leader may also pass
the existing `person={user_uuid}`; its existing permission check remains in charge. A
missing task is explained as no longer open on this board, rather than exposing another
person's task or automatically submitting an outcome. **Show all tasks** clears only the
lead/task focus and preserves person and suite. A board with no tasks links back to Sales
flow to review customers without an owner or with readiness gaps; it does not claim the
whole company's work is complete.

The call icon records call intent and prompts the colleague to use their recording handset;
it does not auto-dial. WhatsApp opens the existing conversation search. **Task details**
opens the lead modal on its Action items tab, with the existing edit/assignment permissions. On Action Item, viewing a
colleague's board does not permit completing their work (a sales-flow outcome follows D5, and D6 on a Stage 1
step — see *Pending / Done* above). The Sales flow block applies the
same `LeadVisibility` as tasks. Its **AI collected the answers** label explicitly leaves
human Relationship readiness to be checked.
WhatsApp and Reply links require the actual viewer's `view-whatsapp` or `manage-whatsapp`
permission, including while a leader reads another person's board.

## The one task list (2026-10-06)

Owner: *"/manage/action-items … totally remove this page … should be combine with the my task, and the
backend of the workflow should touch this Action Item module."* Every task already lived in ONE table,
`lead_action_items` — the sales flow's hand-offs, an approved AI plan's steps, a channel insight's, a
colleague's — and the lead's **Action items** tab and My Work both read it. The Action Items page
(`/manage/action-items`) and the Hub's sign-in **My Checklist** modal were a second view of the same table
that showed **AI-plan steps only** (`SalesWorkQueue`'s plan filter), so a sales-flow call task never
appeared there. Both are gone; My Work took over what only they had:

| Was | Now |
|---|---|
| `/manage/action-items` (Dashboard hub tab) | **Removed.** The route redirects to `/manage/my-work`, query kept (`routes/web.php`). The Dashboard tab and the sidebar prefix are gone. |
| Hub sign-in "My Checklist" modal | **Removed** (`DashboardController@index` sends no props; `ActionPlanChecklistPanel` / `Section` / `TodaysChecklistModal`, `utils/actionPlanChecklist.js`, `utils/scheduleBuckets.js`, the `BuildsActionPlanChecklist` trait and `TeamChecklistRequest` deleted). |
| **Completed History** (`/manage/dashboard/checklist/completed`, AI-plan steps only) | The task card's (*Who to contact · what to do*) **To do \| Done** switch. Done = `MyWorkBoard::done()`: tasks of every source but the sales flow's (those are Sales steps' Done; AI-plan steps only while their release control is on) the person is assigned to, closed in the last `DONE_DAYS` (30), newest first, at most `DONE_ROWS` (100); lazy prop `doneTasks` (`Inertia::optional`, fetched on first open). **Reopen** on your own board → `POST …/action-items/{item}/reopen` (same release-control rule as Done). |
| **Team Tasks** (`/manage/dashboard/checklist/team`, super admin) | The **person picker** — every in-scope manage-role staff member (`assignableAdminOptions`, the pool a task can be assigned to), not only sales — plus a leader's **Tasks nobody holds** (`?person=nobody`, `MyWorkBoard::unassigned()` / `unassignedCount()` / `nobodyHolds()`): open tasks, on leads the viewer can see, that **no active assignee can still open** — nobody assigned, only people who left, or people who lost the lead (the old Team Tasks' "stranded" rule: one `LeadVisibility` query per distinct assignee). Each row says who it still names and why; "Assign on the lead" (the lead modal's Action items tab, whose **Reassign** button changes only the assignees) works on every row: whoever may open this view (super admin / `view-leads-all`) may reassign any task (`LeadActionItem::canReassignFor`, owner decision 2026-10-13); rewriting the task stays its author's (`canEditFor`). Ordered overdue-first BEFORE the 300-row cap (`UNASSIGNED_ROWS`), with "showing the N most urgent of M" past it. The button beside the picker shows the count (red when > 0). Only somebody who may pick (super admin / `view-leads-all`). |
| Agree / Disagree rating on AI steps | Stays on the lead's Action items tab (`ActionItemFeedbackControl`). |

**Only leads the person can still see.** `MyWorkBoard::tasks()` (and `done()`) add `LeadVisibility::apply`
for the person — the rule the retired page used — so the board never offers a Done that answers 403. In
practice it rarely bites: a task's assignee is an active rep of its lead
(`LeadActionItemRepository::mirrorAssigneesAsReps()`), and a former account manager who still holds an open
task stays one (`LeadRepRepository::standingKind()`). It takes a task off when the person has lost their lead
level, or for a Customer Journey task, which makes nobody a rep (`assignees_become_reps => false`) once the
assignee's scope no longer covers the customer.

**Refusals read as a message, not an error page.** `Leads\ActionItemsController@done` / `@reopen` turn a
Customer Journey task (`ConflictHttpException`) and a superseded plan step (`ActionPlanConflictException`)
into a flash + `back()` for an Inertia visit — My Work posts with Inertia, and a 409 there opens the raw
error dialog — and keep the 409 for plain AJAX (the lead tab prints it inline) (`refuse()`). My Work also
offers neither Done nor Reopen on a Customer Journey task (`MyWorkBoard::journeyManaged()`): it closes there.

**Lazy props.** `board`, `responsibilities`, `people` and `unassignedCount` are closures, so opening the Done view
(`only: ['doneTasks']`) builds the Done list and nothing else.

`SalesWorkQueue` keeps `forViewer()` / `totals()` / `openStepCount()` / `openStepsByAssignee()` for the Zoom
AI Agent, Revenue Intelligence and the Copilot; its page-only methods (`completedItemsQuery`,
`teamItemsQuery`, `teamLeadPage`, `provenanceByPlan`, …) were deleted. Two links that pointed at the page:
the Zoom AI Agent's "See the list" → `/manage/my-work` for a person counting their own steps, and
`/manage/leads?action_open=yes` (every lead with work outstanding) for a Super Admin, whose count is the
TEAM's; the Operations "Not followed up" tile (it counts RECORDINGS, not tasks) → `/manage/zoom/actions`.

⚠️ **Deploy together.** My Work and the sales flow are new; production still has the Action Items page.
Ship this in the same deploy as My Work, or production has no task list in between.

## Sales flow guide (second tab, 2026-10-06; rebuilt 2026-10-08)

Owner: *"another tab is show the workflow design, so sales team can always refer back how is the workflow."*
`GET /manage/my-work/sales-flow` (`MyWorkController@salesFlow`, `manage.my-work.sales-flow`, the same
any-lead-level gate as the board) renders `Pages/Manage/MyWork/SalesFlow.vue` with five pill tabs (`?guide=`):

- **Live flow & actions** (`live`) — the owner's three flowcharts with today's counts and the customers behind every
  count (`SalesOperationsBoard` → `SalesJourneyWorkspace`, optional `flowBoard` prop, `j*` URL params). Without a
  `jproject` the Project funnel is the first **active** one (else the first; 2026-10-13 — a paused funnel stops its
  automation), its Preview the Project funnel's `candidate_source_funnel_id`; `jproject` may name any unmerged
  Project funnel, and the filters' **Reset** clears it with the others (2026-10-13). See the
  [Sales flow chart](/docs/modules_handbook/shared/sales-flow-chart/readMe.md).
- **How the three stages work** (`flow`) — the same charts without counts (`SalesFlowStageCards` + `SalesFlowMap`),
  Overview / Details, with each Human / REP box linking to its My Work responsibility
  (`/manage/my-work?tab=workflow&rstage=N&rqueue=…` — My Work honours the `rqueue` and ignores the `rstage`). The
  boxes and cards are `salesFlowOperations.js`, drawn from
  the owner's page `storage/app/workflow/PropertyLab Flow.html`.
- **每天怎么做** (a sales admin's day + when to press Pending or Done), **页面** (which CRM page for what; a row
  links only for a viewer who may open it, so nobody is sent to a 403) and **名词** — static copy in
  [`Partials/salesFlowGuide.js`](/resources/js/Pages/Manage/MyWork/Partials/salesFlowGuide.js) (`ROUTINE`,
  `CONTACT_BUTTONS`, `CONTACT_NOTES`, `PAGES`, `TERMS`), in Chinese with the CRM's English button and page names — staff
  copy, not the Academy, so the bilingual `bi()` rule does not apply. This tab is the **only** copy of the guide.

`salesFlowGuide.js` still exports **`FLOW_CHART`**, the older 23-box dagre chart. It is no longer on this page: it
draws **one lead's map** on the lead's Sales → Journey tab (`Partials/SalesFlowChart.vue` given `flow` from
`SalesFlowChartPath::forLead()` — passed boxes green, the current one blue, reached-but-not-done orange; see the
[Funnel Journey handbook](/docs/modules_handbook/manage/leads/funnel-journey/readMe.md) §6). So **a change to
`FLOW_CHART` is a change to the server too**: its box ids and stage bands must stay equal to
`SalesFlowChartPath::NODES` (`tests/Unit/Lead/SalesFlowChartPathTest.php`). Moving the per-lead chart onto the image
renderer is an open item.

## How it works

- **Route** `GET /manage/my-work` (`manage.my-work.index`, `permission:viewLeadsAny`) →
  [`MyWorkController@index`](/app/Http/Controllers/Manage/MyWorkController.php) →
  `Pages/Manage/MyWork/Index.vue`. The controller decides WHOSE board: the viewer, or — when the viewer
  is a super admin or holds `view-leads-all` — the manage user named by `?person=`. A uuid that is not a
  manage user (a customer's) falls back to the viewer's own board. `people` (the picker) is
  `assignableAdminOptions()` (`ResolvesAssignableManagers`): every ACTIVE user holding a manage role (built-in or
  custom) in the viewer's group — not only sales staff, so every task holder's board can be reached.
- **Service** [`Src\Lead\Services\MyWorkBoard`](/src/Lead/Services/MyWorkBoard.php) builds only `tasks()`
  while the Schedule & messages tab is off (the default); with it on, seven blocks (`tasks`, `leads`, `flow`,
  `today`, `replies`, `week`, `candidates`), all READ from existing definitions — nothing here invents a rule. `rows` preserves cross-channel urgency order. The compatibility
  `groups` remain `TASK_GROUPS` (type → group), with unknown types in *Other*. Staff leads
  (`is_staff`) are skipped everywhere.
- **Responsibilities** [`MyWorkResponsibilities`](/src/Lead/Services/MyWorkResponsibilities.php)
  supplies the default workspace separately. Its filtering is in
  [`ResponsibilitiesQueryRequest`](/app/Http/Requests/Manage/MyWork/ResponsibilitiesQueryRequest.php);
  its UI is [`ResponsibilitiesBoard.vue`](/resources/js/Pages/Manage/MyWork/Partials/ResponsibilitiesBoard.vue)
  (the Today number, the step map with the Help team entry, the three-list control) with its cards in
  `ResponsibilityRows.vue`. It reuses the chart populations. One paginated list (`page`), plus the system's grey rows.
- **Visibility.** The person's LEADS and REPLIES blocks are by ownership: their leads because they are a
  rep, their replies because the thread belongs to a lead they are a rep of — the same set whatever their
  level. Their TASKS (open and Done) are by ownership AND `LeadVisibility::apply()` for the person
  (2026-10-06, see *The one task list*): a task on a lead they can no longer open is not offered, because
  its Done would 403. The leader's *Tasks nobody holds* view applies the VIEWER's visibility instead.
- **Cost.** With the Schedule & messages tab on, `SalesEngagementReport::build()` runs twice per page view (this
  week, last week; never while it is off); each call loads the paid pipelines in scope. Fine for one person; do not loop it over a team here — the CEO's
  Sales Engagement page already does that once for everyone.
- **Why it is first in the nav and the landing.** The owner's objective is that a salesperson knows what
  to do before they see a chart. `ManageLayout`'s Operations nav lists My Workspace above Dashboard, and
  `useOperationsLanding()` puts it first for anyone with a lead level. Sign-in itself still lands on the
  Hub (`ResolvesPortalHome::homeFor()`) — the Operations tile then lands here.
- **Tasks the sales flow hands out (2026-10-04, updated 2026-10-08).** Human contact is required after an AI
  conversation, even when it collected useful answers. Silent invitation timeouts and missing AI answers
  also hand off work; attendance and payment do not count as the human outcome. The
  the [funnel journey](/docs/modules_handbook/manage/leads/funnel-journey/readMe.md) writes an ordinary action
  item for the person who should call (`lead_action_items.funnel_journey_id`). Since 2026-10-09 it is listed only
  in **Sales steps** (one piece of work, one home — not on the Action Item tab), its "why" and "ask" on their own
  lines. It is never ticked Done: it closes through **Pending / Done** on Sales steps and the sales-flow rosters —
  Done = *Spoke to them*, Pending = *No answer* (the task stays, moved to tomorrow); since 2026-10-14 nothing else
  is asked. (Pending / Done on the Action Item card remain only for a hand-off whose
  `funnel_journey_id` does not resolve to a journey of the same lead, which `salesStepTasks()` cannot place.) A closing result moves the lead's journey to *Colleague
  called*. Its holders and the people D5 allows may record it (a Stage 1 hand-off: any sales admin too, D6)
  ([Pending / Done](/docs/modules_handbook/shared/sales-flow-chart/record-contact.md)). A hand-off nobody could be picked for is NOT on anyone's board — it shows as a
  rose icon in the Leads list's Journey column, and on a leader's *Tasks nobody holds* view, until somebody is
  assigned; switching on the company **Round Robin** (Setting → Lead Distribution) is what prevents that.
- **Sales flow block (2026-10-04).** Shown once the person owns somebody in a tracked funnel: their leads by who
  holds the ball — *With the automation* · *Waiting for my call* (count only; they are the Call tasks above) ·
  *AI collected the answers* · *Called* · *After the webinar* — each with its count and its most recent six
  (`MyWorkBoard::flow()`, keyed on `funnel_journeys.owner_user_id`).
- **What is NOT here yet:** the REP's Zoom booking and the paid Stage 3 steps are here now (2026-10-08); what is
  still open is listed in [`docs/temp/7-10-temp/03-open-items.md`](/docs/temp/7-10-temp/03-open-items.md).

## Related files

- [app/Http/Controllers/Manage/MyWorkController.php](/app/Http/Controllers/Manage/MyWorkController.php) — whose board, the picker, the props.
- [src/Lead/Services/MyWorkBoard.php](/src/Lead/Services/MyWorkBoard.php) — the Action Item list (`tasks()`, `done()`, `unassigned()`; `sourceOf()`, `withoutClosedPlanSteps()`) and the Schedule & messages blocks (`TASK_GROUPS`, `LEAD_ROWS`, `REPLY_ROWS`).
- [resources/js/Pages/Manage/MyWork/Index.vue](/resources/js/Pages/Manage/MyWork/Index.vue) — the shared workspace tabs, responsibilities, tasks, schedule/messages and weekly figures; person picker for a leader.
- [resources/js/Pages/Manage/MyWork/SalesFlow.vue](/resources/js/Pages/Manage/MyWork/SalesFlow.vue) — the Sales flow guide tab; its static words in [Partials/salesFlowGuide.js](/resources/js/Pages/Manage/MyWork/Partials/salesFlowGuide.js); the charts and live workspace are the [Sales flow chart](/docs/modules_handbook/shared/sales-flow-chart/readMe.md) renderer (`Partials/SalesFlowMap.vue`, `SalesJourneyWorkspace.vue`, `salesFlowOperations.js`, …). `Partials/SalesFlowChart.vue` is only the per-lead map now.
- [src/Lead/Services/MyWorkResponsibilities.php](/src/Lead/Services/MyWorkResponsibilities.php) — Sales steps (`QUEUES` with their stage, `STATES`, `LANES` + `FRESH_DAYS` + `URGENT_WEBINAR_HOURS` (`classify()`, `urgency()`), `VIEWS` + `VIEW_HINTS` (To do · Done · Later), `LEGACY_STATE_VIEWS`, `SOURCE_LABELS`); [app/Http/Requests/Manage/MyWork/ResponsibilitiesQueryRequest.php](/app/Http/Requests/Manage/MyWork/ResponsibilitiesQueryRequest.php); UI [Partials/ResponsibilitiesBoard.vue](/resources/js/Pages/Manage/MyWork/Partials/ResponsibilitiesBoard.vue) + [Partials/ResponsibilityRows.vue](/resources/js/Pages/Manage/MyWork/Partials/ResponsibilityRows.vue) (the cards; vitest `ResponsibilitiesBoard.test.js`) + [Partials/StepRulesModal.vue](/resources/js/Pages/Manage/MyWork/Partials/StepRulesModal.vue) (the "Who is in this list?" window, `QUEUE_RULES` / `LIST_RULES`); [Partials/ResponsibilityItem.vue](/resources/js/Pages/Manage/MyWork/Partials/ResponsibilityItem.vue) is the sales-flow roster's item; lead-page link → modal tabs in [utils/leadModalLink.js](/resources/js/utils/leadModalLink.js); stage colours (`STAGE_SKIN`) in [Partials/salesFlowSkin.js](/resources/js/Pages/Manage/MyWork/Partials/salesFlowSkin.js).
- [src/Lead/Services/FunnelFollowUpState.php](/src/Lead/Services/FunnelFollowUpState.php) — recorded contacts per obligation (Last contact, D3 re-contact window).
- [src/Lead/Support/FollowUpAccess.php](/src/Lead/Support/FollowUpAccess.php) — who may record a contact (D5 + D6: `canRecord()`, `isSalesAdmin()`, `isOpenQueue()`, `stageOneLeadIds()`); Help team is `MyWorkResponsibilities::helpTeam()` (`HELP_TEAM`, `HELP_TEAM_HINT`).
- [resources/js/Layouts/ManageLayout.vue](/resources/js/Layouts/ManageLayout.vue) — the Operations nav entry (prefixes `/manage/my-work` + `/manage/calendar`; the fallback Calendar entry for admins with no lead level); [resources/js/composables/useOperationsLanding.js](/resources/js/composables/useOperationsLanding.js) — first landing candidate.
- [resources/js/Components/SectionTabs.vue](/resources/js/Components/SectionTabs.vue) — the `my-work` strip (My Task · Calendar · My Sales · Sales flow guide); mounted by `MyWork/Index.vue`, `MyWork/SalesFlow.vue`, `Calendar/Index.vue` (Operations suite only) and `SalesProjects/Index.vue` (My Sales only).
- My Sales: [SalesProjectsController](/app/Http/Controllers/Manage/Engagements/SalesProjectsController.php) `mine()` / `exportMine()` / `holderScoped()` / `bookingsView(…, $holder)`; [Pages/Manage/SalesProjects/Index.vue](/resources/js/Pages/Manage/SalesProjects/Index.vue) (`mine` prop) and [Partials/DetailedBookingView.vue](/resources/js/Pages/Manage/SalesProjects/Partials/DetailedBookingView.vue) (`mine` + `baseUrl` props); routes `manage.my-work.sales` / `manage.my-work.sales.export` in `routes/web.php`.
- [routes/web.php](/routes/web.php) — `manage.my-work.index`.
- Borrowed definitions: [src/Lead/Services/SalesWorkQueue.php](/src/Lead/Services/SalesWorkQueue.php) (buckets), [src/Whatsapp/Support/ReplyOwed.php](/src/Whatsapp/Support/ReplyOwed.php), [src/Ceo/Services/SalesEngagementReport.php](/src/Ceo/Services/SalesEngagementReport.php), [src/Lead/LeadRep.php](/src/Lead/LeadRep.php).
- Tests: [tests/Feature/Manage/MyWorkTest.php](/tests/Feature/Manage/MyWorkTest.php) — an agent sees only their own work and cannot read a colleague's board; a leader can pick a name; a customer's uuid is refused; a task on a lead the person can no longer see leaves their board; the Done view lists the last 30 days newest first; a leader sees the tasks nobody holds and an agent cannot; the sales flow guide tab opens for any agent; responsibilities follow the image-stage banding; one page for all
stages (an old `rstage` is ignored, its `rqueue` honoured), Extra is its own view newest-first (labelled "Extra"), the
To do / Waiting / Done views, and old `rstate` links map to a view; **Help team** lists a colleague's overdue Stage 1
customer nobody called (not mine, not one due today, not an already-called one), its button records, and it is hidden
on a colleague's board and from staff outside the sales team; it lists a new customer nobody contacted 3+ days after
assignment (not one given yesterday, not one a rep already talked to) and its invitation records, and one whose only
Preview registration was on a cancelled Session. 2026-10-13 regressions: two deals on one Project are two
`project_close` items; a task with no priority sorts after High; a conversation task's source is `conversation`; a
second Done keeps the first close; AI-plan steps leave the lists while Action Plans is off; a colleague's agreed
follow-up moves to To do on its date; a managed customer's later no-show stays with the account manager while a
colleague holds the hand-off; a paused funnel gives no Sales steps and is not the guide's default Project funnel;
*Cannot be reached* is Done and `?task=` lands on the view that lists the task. Also [tests/Feature/Lead/FunnelFollowUpTest.php](/tests/Feature/Lead/FunnelFollowUpTest.php) (recorded contacts on My Work, D3–D6) and [tests/Feature/Lead/MyWorkConsultationsTest.php](/tests/Feature/Lead/MyWorkConsultationsTest.php).
