Phone call — Keypad v3.2

1 · The header becomes the keypad (PRESCRIPTIVE — call card v3.2, CPO 2026-09-30)

Closed · the key trails the header

Shane Dusang02:41

Connected

Open by pointer · the pad hangs under the card

Shane Dusang02:41

Connected

Type digits, * or #

Shane Dusang · 02:41

A Keypad key (.c3-hkey) sits at the right end of the card header on every call state. Pressing it turns the name area into a digit entry line (.c3-entry). The bar you approved does not change.
Desktop: open, then type. One click, or Enter on the key, then type 0–9, * and #, paste, and Backspace. Mouse users also get a 12-key pad attached under the card. It stays armed until you click somewhere else; clicking the card re-arms it. Needs Spike A (focus into GlobalOverlay).
Mobile: an in-app dial pad docks at the bottom of the screen, where the OS keyboard would sit — * and # on its face, Paste and Done, a haptic on every press, End always visible above it.
No red anywhere. Hold dims the keypad in place instead of closing it; a refused press is never drawn; no failure toast while it is open. Digits show only while it is open, wipe on close, on any auto-close and after 2 min idle, and are never stored or logged.
Opening the keypad closes Transfer, and the other way round (comp-transfer-panel). Card: comp-call-card-v3.

2 · The Keypad key · .c3-hkey · every call state (PRESCRIPTIVE — call card v3.2, CPO 2026-09-30)

Rest

Hover · gray-00 8%

Pressed · gray-00 16%

Open · blue-02 / blue-01

Focus-visible

Focus + pressed

Can't act · .4

S1 · Incoming · dimmed

Shane Dusang

Incoming Call

Tooltip “Keypad available when connected”. Answering only recolours the header and swaps the bar; the name column doesn't change.

S2 · Calling · dimmed

Shane Dusang

Calling...

No timer yet, so line 2 starts at the left edge. Reconnecting and ending look the same.

S4 · Connected v2 · live

Shane Dusang02:41

Connected

Live when canUseKeypad. Also S3 legacy/v1 and the 409 card (SDK DTMF works there), S5 muted, S6 speaker, S13 returned.

S7 · On hold · dimmed

Shane Dusang02:41

On hold

Tooltip “Resume the call to use the keypad”. If the keypad was already open, it stays open and dims in place (KP11).

S10 · Transferring · dimmed

Shane Dusang03:12

Transferring to Karla Sellers...

Also S8/S9 Ask first, S12 the colleague's side, 3+ people and v2 unsafe: “Keypad unavailable for this call right now”.

v3.1 state	Keypad key	Tooltip when dimmed
S1 Incoming (desktop and mobile web; native mobile hides the card)	dimmed	Keypad available when connected
S2 Calling · reconnecting · ending	dimmed	Keypad available when connected
Probe window (≤ 3 s after connect)	dimmed	Checking keypad availability…
S3 legacy/v1 and the 409 card (Hold and Transfer dimmed)	live (SDK DTMF works)	—
S4 v2 · S5 muted · S6 speaker · S13 returned	live when canUseKeypad	—
S7 On hold (keypad closed)	dimmed	Resume the call to use the keypad
S8/S9 Ask first · S10 transferring · S12 colleague's side · 3+ people · v2 unsafe	dimmed	Keypad unavailable for this call right now

Box 40×40 r5, transparent at rest; hit area 48×48 (card-local x 300–348, y 8–56). The key sits at x 304–344, y 12–52 (302–342 on a 390 phone, 232–272 on a 320 phone). Glyph fa-regular fa-table-cells 16 gray-00 (= FontAwesomeIcons.th, which QA ships).
Hover --c3-hkey-hover = color-mix(in srgb, var(--gray-00) 8%, transparent) (gray-06 would vanish on the light tints; it darkens in light and lightens in dark) · pressed --c3-hkey-press, gray-00 16% · open blue-02 / blue-01, hover keeps the fill · focus-visible inset 2px blue-01, focus + pressed gray-03 · can't act opacity .4, no hover, default cursor.
Tooltip (desktop hover and focus; mobile long-press): “Keypad”, “Close keypad” while open; when dimmed, the existing keypadMessage string. Semantics: button “Keypad”, expanded true / false.
Cost: the name column is a constant 220 (272 before; 218 in a 390 phone, 148 on a 320 phone), so long names truncate sooner.

3 · KP2 · The entry line · opened by pointer and by keyboard (PRESCRIPTIVE — call card v3.2, CPO 2026-09-30)

KP2 · Opened by pointer · pad shown · light

Shane Dusang02:41

Connected

Type digits, * or #

Shane Dusang · 02:41

The name fades out (100 ms), then the entry line fades in (100 ms); nothing moves. Caret + “Type digits, * or #”; line B shows the name and timer.

KP2 · Opened by keyboard · no pad · light

Shane Dusang02:41

Connected

Type digits, * or #

Shane Dusang · 02:41

Enter or Space on the key opens the keypad without the pad; a click on the entry line shows it.

KP2 · Pointer · dark

Shane Dusang02:41

Connected

Type digits, * or #

Shane Dusang · 02:41

KP2 · Keyboard · dark

Shane Dusang02:41

Connected

Type digits, * or #

Shane Dusang · 02:41

Digits #DEE6F2 on #202D31 · pad #272727, keys #383838 · lit key #68666A with a #BCC4D0 inset.

Sent

Sending

Queued

Not sent

Unconfirmed

Digit state	Meaning	Look
Sent .is-sent	v1: the SDK accepted it · v2: own sequence completed and available	gray-00
Sending .is-sending	In flight, shown after 150 ms	gray-00 + a 2px gray-00 underline at y 36–38, glyph width − 2, pulsing opacity 1 → .4 → 1 over 1 s (steady with reduced motion)
Queued .is-queued	Waiting more than 150 ms	gray-00 at opacity .4 (opacity, because dark gray-02/03/04 are all near-white)
Not sent .is-notsent	Cleared by a failure, hold or reconnect	opacity .4 + a 1px gray-00 strike at y ≈ 25
Unconfirmed .is-unconfirmed	v2 unknown: Twilio was called, delivery not confirmed	gray-00 + a 2px dotted gray-02 underline (2 on / 2 off), no pulse

.c3-entry replaces the name column: x 72–292 (220; 218 on a 390 phone, 148 on a 320 phone), y 10–54. The orb and the (blue) key stay where they are. While open, the name tap is suspended; the card still drags (a move over 4 px is a drag; a click on the entry line focuses it).
Line A .c3-digits (y 10–38): --t-heading6 20/28 gray-00, tabular numerals, 2px letter-spacing, no grouping. About 15 digits fit (Inter glyph width UNVERIFIED). On overflow (.is-overflow) they anchor right and older digits fade under a 16px left fade from --c3-hd.
Caret .c3-caret: 2×20 r1 blue-01 at y 14–34, 2px after the last digit or at the start; blinks 500 / 500 ms and resets to on at each press; steady with reduced motion; only while armed (always on mobile). Placeholder .c3-ph: --t-paragraph gray-02, 8 after the caret — “Type digits, * or #” · “Click to type digits” (not armed) · “Tap digits below” (mobile).
Line B .c3-lb (y 38–54): --t-tiny gray-02, one line, ellipsis; bold parts --t-tiny-bold gray-00. The identity form “{Name} · {mm:ss}” truncates the name, never the timer.
After a Stop the next accepted press starts a new run (the echo clears first). A press the queue refuses is never drawn: the pad key doesn't light and line B says why.

4 · KP5 typing on v2 · a lit pad key (PRESCRIPTIVE — call card v3.2, CPO 2026-09-30)

KP5 · “140” sent · “2” sending · “887” queued · light

Shane Dusang02:41

Connected

1402887

Sending · 3 waiting

Hold and Transfer dim in the bar while v2 digits send (the existing isBusy); their tooltips read “Available when digits finish sending”.

KP5 · Dark

Shane Dusang02:41

Connected

1402887

Sending · 3 waiting

Pad key lit · “5” just pressed (v1)

Shane Dusang02:41

Connected

0125

Shane Dusang · 02:41

A click, or the matching physical key, lights the pad key: gray-05 + inset 2px gray-03, held while down (≥ 120 ms), then an 80 ms fade.

#	Line B · first match wins	Copy
1	On hold (the keypad stays open and dimmed)	“On hold · {n} digits not sent” if digits were dropped, else “Resume the call to use the keypad”
2	Reconnecting	“Keypad available when connected”
3	Stopped (failed or canceled), until the next press or close	“Stopped · {n} not sent” in --t-tiny-bold gray-00
4	Unconfirmed, same lifetime	“Last digit may not have played” in --t-tiny-bold gray-00
5	Probe re-running / v2 briefly unsafe ≥ 600 ms	“Checking the keypad…” / “Keypad paused · checking the call”
6	Hint (2.5 s)	“Only 0–9, * and # are sent” · “Enter isn't sent · press # if asked” · “Sent digits can't be taken back” · “Pasted {n} digits” · “Paste has letters · nothing sent” · “Paste up to 32 digits” · “32 waiting · let these send first” · “Not sent · try again”
7	Desktop, not armed, with digits	“Click to keep typing”
8	Sending (v2 only; in flight ≥ 400 ms, or digits queued)	“Sending…” / “Sending · {n} waiting”
9	Otherwise	“{Name} · {mm:ss}”

5 · KP6 · KP9 · KP10 · KP11 · KP12 · KP15 (PRESCRIPTIVE — call card v3.2, CPO 2026-09-30)

KP6 · Not armed, with digits

Shane Dusang02:41

Connected

0012

Click to keep typing

A pointer-down outside the card and pad removes focus: capture pauses, the caret goes, queued digits keep sending. A click on the entry line or a pad key re-arms it.

KP9 · Stopped (failure)

Shane Dusang02:41

Connected

1402887

Stopped · 4 not sent

Queued digits become Not sent. No toast while open. The next press starts a new run.

KP10 · Unconfirmed (v2 unknown)

Shane Dusang02:41

Connected

1402887

Last digit may not have played

That digit Unconfirmed, the rest Not sent. Announced assertively.

KP11 · On hold while open

Shane Dusang02:41

On hold

1402887

On hold · 4 digits not sent

Dims in place: line A and pad at .4 (line B keeps its reason at full strength); the queue is cleared and shown as Not sent; card WAITING orange. Resume re-enables it; the keypad stays open.

KP12 · Overflow

Shane Dusang02:41

Connected

001234567890123456

Shane Dusang · 02:41

Right-anchored: the newest digit and the caret at the right edge; older digits fade under a 16px left fade from --c3-hd.

KP15 · Closed with v2 digits pending

Shane Dusang02:41

Sending digits · 3 left

Header back to the name. Line 2 “Sending digits · {n} left”; Hold and Transfer stay dimmed until the queue drains. A failure now fires the existing toast “Keypad input stopped. Check the call before trying again.”

#	State	Desktop	Mobile
KP0	Closed, available	Key neutral	Same
KP1	Unavailable	Key dimmed; tooltip gives the reason	Same (long-press)
KP2	Open, empty, armed	Caret + “Type digits, * or #”; pad only if opened by pointer	Caret + “Tap digits below”; dock up
KP3	Open, empty, not armed	“Click to type digits”	n/a
KP4	Typing, v1	Digits show as sent (queued only faster than 4 a second)	Same
KP5	Typing, v2	Sent / sending / queued; “Sending · 3 waiting”; Hold and Transfer dimmed	Same
KP6	Not armed, with digits	No caret; “Click to keep typing”; sending continues	n/a
KP7	Checking (probe re-runs)	“Checking the keypad…”; pad at .4; presses refused	Dock at .4
KP8	Briefly unsafe, v2	Under 600 ms: no dimming, presses refused with “Not sent · try again”. 600 ms or more: line A and pad at .4 (line B keeps its reason at full strength), “Keypad paused · checking the call”	Same
KP9	Stopped (failure)	Queued → Not sent; “Stopped · {n} not sent”; no toast while open	Same
KP10	Unconfirmed	That digit Unconfirmed, the rest Not sent; “Last digit may not have played”	Same
KP11	On hold while open	Dims in place; queue cleared as Not sent; line B per #1	Dock keys at .4
KP12	Overflow	Right-anchored with the left fade	Same
KP13	Queue cap (32 pending)	Further presses refused; hint	Same
KP14	Hint	Line B for 2.5 s	Same
KP15	Closed, v2 digits pending	Line 2 “Sending digits · {n} left”; Hold and Transfer dimmed until drained	Same
KP16	Idle 2 min	The echo clears (the keypad stays open)	Same

Line 2 with the keypad closed (v3.1, amended): transfer phase › On hold › Sending digits · N left › lock reason › note › Connected.
Auto-close (the queue clears as today, focus is restored, line 2 shows the new phase): the Transfer key · an Ask first or transfer starts · the card becomes the colleague's side · a third participant joins · the probe says unavailable (line B shows the reason for 3 s, then it closes) · the call ends, is declined, missed or replaced · unsubscribe or logout. Stays open: Mute, Speaker, Hold/Resume (dims), reconnect (dims).

6 · The desktop pad · .c3-pad · placement (PRESCRIPTIVE — call card v3.2, CPO 2026-09-30)

Below (default) · 1440 × 900 · card at x 1048, y 98 → pad y 234–454

Shane Dusang02:41

Connected

Shane Dusang · 02:41

Flipped above · card at y 720 → pad y 492–712

Shane Dusang02:41

Connected

Shane Dusang · 02:41

To the left · 1440 × 600 · card at y 236 → pad x 848–1040, y 144–364

Shane Dusang02:41

Connected

Shane Dusang · 02:41

Surface: 192×220, gray-07, r7, --elevation-popover, no border (the bar's material, so it reads as part of the card). Grid: padding 8, 3×4, gap 4; keys 56×48 at x 8–64 / 68–124 / 128–184, y 8–56 / 60–108 / 112–160 / 164–212.
Key .c3-pk: gray-06 r5; a centred 40-tall block — digit --t-heading6 gray-00 (28 line), then letters --t-indicator gray-02, uppercase, .08em (12 line). 2 ABC · 3 DEF · 4 GHI · 5 JKL · 6 MNO · 7 PQRS · 8 TUV · 9 WXYZ; 1, 0, * and # keep an empty letter line. * = fa-asterisk 16, # = fa-hashtag 16. Rest gray-06 · hover gray-05 · lit gray-05 + inset 2px gray-03 · can't act: the whole grid at .4. Not in the Tab order; labels “Send 5”, “Send star”, “Send pound”.
Placement: 8 below the card, right edges aligned (card-local x 168–360, y 136–356; at the default spot y 234–454). If it doesn't fit below (viewport − 16) it goes 8 above; if neither fits, 8 to the card's left, bottoms aligned. It follows the card while dragging, never covers or moves the card, has no scrim, and doesn't close on an outside click.
When it shows: opening with the pointer (not with Enter or Space) · a click on the entry line · when the input source is unclear (touch laptops, assistive tech). It closes with the keypad. Motion: in = fade + a 4px slide from the card, 150 ms ease-out; out = 100 ms fade.

7 · Desktop input · arming · paste (PRESCRIPTIVE — call card v3.2, CPO 2026-09-30)

Arming: opening the keypad saves primaryFocus and moves focus to the entry line. Armed = open AND focus anywhere in the card or pad subtree: the caret shows and keys are captured. A pointer-down outside the card and pad (a TapRegion) pauses capture; the keypad stays open and queued digits keep sending. Clicking Mute or another card key never takes focus away.

Input (armed)	Result
A key-down whose character is 0–9, * or # (numpad too; Shift+3 and Shift+8 on any layout)	Queued and sent; the matching pad key lights
Key repeat	Ignored: one physical press is one digit
Backspace	Removes the last queued (unsent) digit. Nothing queued: hint “Sent digits can't be taken back”
Esc	Digits queued: clears them (Not sent, “Stopped · {n} not sent”). Nothing queued: closes the keypad
Enter (entry line focused)	Swallowed, with the Enter hint. On a focused card key it activates that key
Space	Swallowed on the entry line; activates a focused card key
Letters and other characters	Swallowed, with the letters hint (at most once per 2.5 s)
Cmd/Ctrl+V	Paste
Other Cmd/Ctrl/Alt chords	Passed through to the app
Tab	entry line → Keypad key → Mute → Hold → Transfer → End; capture stays live inside the card

Paste: strip spaces and - . ( ) / , + · any other character: send nothing · more than 32 digits: send nothing · otherwise queue every symbol in order, leading zeros included · no pauses (the backend rejects w).
Close (the key, Esc, or an auto-close): the header returns to the name, the pad leaves, focus goes back to the saved element if it still exists — typing notes, open keypad, type digits, Esc, back in notes. Closing with the key does not cancel queued digits (KP15); Esc with a queue does.
Screen reader: the key is “Keypad” / “Close keypad” with expanded · the entry line is a focusable group, “Keypad entry. Digits send as you type”, value “{n} sent, {m} waiting” · each accepted digit is announced politely (“5”, “star”, “pound”) · Stop and Unconfirmed assertively: “Keypad stopped. {n} digits not sent.” · pad keys reachable by screen reader, not by Tab.

8 · Mobile · the dial-pad dock · .c3-dock (PRESCRIPTIVE — call card v3.2, CPO 2026-09-30)

KP2 · 390 × 844 · dock + Paste · light

Shane Dusang02:41

Connected

Tap digits below

Shane Dusang · 02:41

The centred card (y 358–486) doesn't move: its bottom is above dock top − 16 (530).

KP2 · Dark

Shane Dusang02:41

Connected

Tap digits below

Shane Dusang · 02:41

KP5 · typing on v2

Shane Dusang02:41

Connected

1402887

Sending · 3 waiting

Same as desktop: Hold and Transfer dim in the bar while v2 digits send.

375 × 667 · the card nudges up

Shane Dusang02:41

Connected

Tap digits below

Shane Dusang · 02:41

Dock top 403; the card moves from y 269 to 259–387 (dock top − 16 − 128), in step with the dock. Never saved; it returns on close.

320 × 568

Shane Dusang02:41

Connected

Tap digits below

Shane Dusang · 02:41

Card 288; name column 148; keys 91 wide. No Paste when the clipboard has no text.

Route: a root-navigator route (the proven DialogService path, so Android back works) with a transparent barrier: no dim, the page stays readable, a tap on the page closes the dock and does nothing else. The card is above the barrier and fully usable.
Surface: full width, bottom-anchored, gray-07 (the fill runs under the home indicator), 1px gray-06 top hairline, --shadow-float, square corners. Accessory row 40, pad 0 8: “Paste” left (only when Clipboard.hasStrings), “Done” right — .sb-btn--text in blue-01 --t-action, 40 tall, pad 0 8.
Grid: padding 0 16 8, 3 columns, gap 8, 4 rows × 48 → 216. Key width (W − 48) / 3: 114 at 390, 109 at 375, 91 at 320; capped at 400 wide and centred on tablets. Height 40 + 216 + 8 = 264 + the safe area (top y 546 on 390 × 844).
Key .c3-pk--m: r5 gray-06; a 44 block — digit --t-heading5 24/32 gray-00, then the letters line; * and # glyphs 18. Lit on touch-down as on desktop, plus HapticFeedback.lightImpact on iOS and Android (none on the web).
Card nudge: if card bottom > dock top − 16, the card animates to top = dock top − 16 − 128, in step with the dock; never saved; returns on close. Motion: up 200 ms ease-out, down 160 ms. Closes on: Done, the Keypad key, a swipe down ≥ 40 px or a fling, Android back, a tap on the page.
A tablet hardware keyboard follows the desktop key map. Paste reads the clipboard on tap; iOS may show its own “Allow Paste” prompt. [UNVERIFIED] Landscape phones: 264 dock + 128 card don't fit ≈ 390 tall.

9 · Engineering handoff (PRESCRIPTIVE — call card v3.2, CPO 2026-09-30)

Spike A first: can a card Focus / FocusScope inside GlobalOverlay (base_app.dart:183) take primary focus on web, macOS and Windows; does Tab reach it; can the previous focus be saved and restored? If not, desktop input is pointer-only (the pad).
Spike C: one live v2 call with dealer PR #306 deployed — per-digit POST → pending → playing → completed (counts and durations only, never digits); does the phone menu accept them; does the rep hear anything.
Remove #2087's layout (the toggle row, the grid, the message row and the preferredSize growth). Keep canUseKeypad, keypadMessage, setKeypadOpen() (v2's 2 s polling), the probe, PhoneCallDtmfQueue, both transports, neverRetryKey, the toast and the “Send N” labels.
_CallHeader: a trailing _KeypadKey in every state; InteractiveBox reports pointer vs keyboard activation; tooltip = keypadMessage when dimmed. _KeypadEntryLine: a Focus with onKeyEvent — no TextField / EditableText; map by character; drop KeyRepeatEvent; paint the caret; a TapRegion around the card and pad; save and restore primaryFocus.
Tape model: per-session, in-memory {symbol, state}; add() returns accepted or refused; removeLastQueued(), clearQueued(); failed/canceled → notSent, unknown → unconfirmed; cap 32; pendingCount; wipe on close, every clear path and after 2 min idle; redact from toString, logs, crash breadcrumbs and analytics.
Desktop pad: the DraggablePositionedWidget attachment slot (a positioned sibling left out of the clamp size). Mobile dock: a root route with a transparent barrier; the card nudge via stepAside(); haptics (new to the codebase); Paste via Clipboard.hasStrings. Web paste: the native paste event (UNVERIFIED).
Line 2: the “Sending digits · N left” phrase and priority; Hold/Transfer tooltips during sending; suppress the failure toast while open. Local tone (P1) on v2 at send start. v2 batching only if Spike C's median is over ≈ 1 s, with the backend owner's OK.