Inbox guides — working conversations

Who these guides are for: EMPLOYEES who work the shared inbox every day, and their ADMINISTRATORS (the routing rule is a team-wide setting).

Three guides, each written only from real, qualified evidence of the actual app:

  1. The customer drawer: deals, follow-ups and internal notes — record a deal, set a follow-up with an exact due time, and write internal notes that can never reach the customer; what refusals look like and how to recover.
  2. Hand a conversation to a teammate: claim, transfer and release — the one-holder-at-a-time model, the guard-rail messages, and the same journey on a phone.
  3. Finding your conversations: search, All-mine and assignment routing — what search matches, the honest "no conversations match" message, the All-mine filter, and the admin routing rule.

All three share one evidence source: the completed ZC-3132 INBOX-CRM-CONT lane, run O4 (23 October 2026, 17 of 17 tests passed, single clean run) of the three zc3068-* real-browser specs, recorded in the lane ledger C:/CT-ZCODE3132/lane-inbox-cont-ledger.json.

Screenshots live in assets/ with per-image provenance and SHA256 checksums in assets/ASSETS-MANIFEST.json. They come from an isolated synthetic test business; the examples are simulated test data, not live customer traffic. Areas without qualified evidence (for example teammate mentions, snoozing and queue-state transitions) are intentionally absent, not forgotten.


Evidence standing (kept for honesty). At authoring time Chief acceptance of the lane was open (historical status, preserved). Independent review CT-INBOX-REVIEW3143 has since accepted the inbox local candidate at HEAD 85bf2a878df1e2430354910e9718c3ed62a2c05b — a bounded local-candidate acceptance covering these journeys. Main PR #336 is Chief-reported source integration, not independently verified Main-built or live evidence here; the candidate / Main-source / live distinctions are kept throughout. The guides claim only what the recorded passing run shows.