The one outward-acting, irreversible surface — designed send-safety-first: no mis-send · no lost mail. Origination is grounded: no blank compose FAB, but a discoverable recipient-first entry (⓪ who → tell Pingbo → draft) — the button exists, the flow is grounded. Client UX over the built hold-queue.
9:41New message
New message
Who are you reaching?
toDO Dana Okafor+ rajesh@newco.com
cc
bcc
Tell Pingbo what to send — e.g. “ask Dana to release the settlement wire once counsel countersigns this week”
9:41Cacafly — settlement
Reply to Ken WuRe: · same thread
toKen WuccDeesha
Checked against your case-file · never sign blind
✓Matches your 6/23 red line — full-and-final restored↗
✓Tone consistent with the thread↗
!Q7 date conflicts with your May 2 note (you said "after the audit")↗
Re: Settlement — clause 6
Hi Ken,
Thanks for turning this around. Before we release payment, we need clause 6 broadened back to full-and-final — that was our requirement from the start.
I can confirm the Q7 milestone date as proposed. Send the revised draft and we'll countersign same day.
Best, Xiaofei
9:41🪐 Board
9
Sending to KenStays here even if you switch apps · tap anywhere to undo
9:41New message
⤷
Send to a new address?
This goes to rajesh@newco.com — a new contact, not on the original thread. I'll add them to People on send.
9:41🪐 Board
☁ Offline · 1 will send when you reconnect
Needs you
!
legal@oldfirm.com — NDA
Send failed — that address bounced. Draft saved — the board brought it back to you.
↑
Ken Wu — settlement
Sending… · dispatching now (undo window passed)
Waiting
☁
Deesha — Q3 sign-off
Queued · sends when you're back online — saved on this device
✓
Board seat — confirmed yes
Sent 2m ago · ball with them now
⓪Grounded new-message entry (2026-07-08). A discoverable ✎ new message affordance exists (not "hidden in People" only) — but it opens a recipient-first, grounded flow, never a blank editor: Who? (type to add people — multi-select autocomplete over your people; a raw address → new contact, minted on send; cc / bcc hidden by default, expand via the ⌄ chevron, Gmail-style) → Tell Pingbo what to send (its own Draft it → button) → it drafts → the composer (①). Recipients (to / cc / bcc) are picked once here, never re-picked downstream. Half-exit: never sends, never nags — a line draft persists on the line; an origination draft is a single slot ("Continue your draft to X?" on reopen; empty → discarded), no Drafts folder. Honors §353's "no blank compose" while staying intuitive. ① Composer = a sheet; the AI draft is fully editable; the in-editor guard is ambient, not a gate (✓ red-lines · ✓ commitments · ⚠ conflicts, each ↗) — you're never blind, but a clean draft sends on one tap. Swipe-to-send banned. ② Undo-send = a persistent bottom bar (Apple Mail's native iOS pattern, NOT a fading toast) — default 10s, settable 10/20/30/off. Durable timer: leaving / switching apps neither sends now nor cancels — it sends at T regardless, kill-app-safe. Line optimistically moves to Waiting; Undo brings the draft back. ③ A blocking double-confirm fires ONLY when the agent suspects a problem — unified across content-conflict (a ⚠ vs your case-file, e.g. Q7) and recipient-risk (new / external / not-in-thread / large / bcc). No doubt → one tap, no extra step. ④No Outbox folder (email-client anti-pattern) — send-states live INLINE on the board: failed → the line returns to Needs-you (Retry, draft saved — the board catches it, never a folder you must check) · offline → thin banner + per-line · sending → line micro-state · sent → line advances.