- Scene: agents/hermes/demo_scenes/dental_appointment_booking
- Result: STOPPED by viewer (user) at 14:03Z — during the first live test of the raise-hand feature
- Duration: ~12 min (13:51:54 → 14:03:00)
Booking flow completed end-to-end cleanly: receptionist login → appointments
list (25 rows) → create form (practice 43 / FILLING / provider 115 / Mon 17
Aug, 19 slots) → Oliver Reed selected → Band 2 + symptoms → submit → appointment
726 created BOOKED with success banner + AI Priority → triage queue shows
Oliver Reed top of Needs Triage. All screenshots captured. No JS/driver issues.
- Viewer raised the hand at 14:00:41 (after the triage navigation). The
presenter did NOT see it: the closing narration was posted without a
control-channel check first (check-before-every-browser-action was followed,
but not check-before-narration). The raise sat unnoticed until after the fact.
- Viewer raised again at 14:02:43. The presenter acknowledged ~17s later via
--discuss ("I see there is a question someone would like to ask — go ahead"),
which clears the hand. 17s is too slow: the presenter was mid-diagnostics
instead of reacting to the channel.
- Viewer pressed Stop at 14:03:00 (again at 14:03:42) — during the
acknowledgment pause, before asking anything. No chat questions, no mic
events this run.
- Check the control channel before every presenter action — browser
actions AND narrations/answers. The skill's "check before EVERY browser
action" must extend to control_respond calls.
- On
HAND: RAISED, react IMMEDIATELY (it is a priority signal): finish the
current browser action at most, then acknowledge. Do not batch additional
steps/narrations first.
- Acknowledgment delay target: < 5s from raise to the spoken "I see there is
a question…".
- If the viewer stops during a test, ask them what they wanted to ask
(terminal) and record it in viewer-qa per §3c — a raised hand carries an
unanswered question even if the run dies.
- The run itself (booking flow) remains a clean PASS mechanically — the
failure was purely in the presenter's conversational responsiveness.
- viewer-qa knowledge base: nothing to append (no question was ever asked).