¶ Demo Run: Dental Appointment Booking (Live)
¶ Summary
| Field | Value |
|---|---|
| Scene | agents/hermes/demo_scenes/dental_appointment_booking |
| Run ID | dental_appointment_booking_20260813T074312Z |
| Started (UTC) | 2026-08-13 07:43:12 |
| Finished (UTC) | 2026-08-13 07:51:00 |
| Duration | ≈ 8 minutes |
| Result | PASS (43/43 steps) |
| Mode | Live interactive (control channel active) |
| Instance | Test Client Dental (test-client-dental.dental.veripath.co.uk) |
| Role shown | RECEPTION (reception.test-client-dental) |
A live, interactive walkthrough: the receptionist booked a real appointment
for Oliver Reed (Filling, NHS Band 2, provider Sarah Holloway, Mon 17 Aug 2026,
09:00) through the native dental booking flow. The symptoms note triggered
rule-based AI triage (priority 1/5), and the new booking appeared in the
triage queue. The run was reseeded before starting, so the mutation was on
fresh demo data.
¶ Step table
| # | Role | Action | Result | Screenshot |
|---|---|---|---|---|
| 1 | RECEPTION | NOTE: welcome | OK | — |
| 2 | RECEPTION | USER: RECEPTION | OK | — |
| 3 | RECEPTION | NAVIGATE {URL} |
OK | — |
| 4 | RECEPTION | KEYCLOAK_LOGIN | OK | — |
| 5 | RECEPTION | VERIFY_VIEW /dental/practices/ |
OK | — |
| 6 | RECEPTION | NAVIGATE /dental/appointments/ |
OK | — |
| 7 | RECEPTION | VERIFY_VIEW /dental/appointments/ |
OK | — |
| 8 | RECEPTION | VERIFY_TEXT Appointments |
OK | — |
| 9 | RECEPTION | SCREENSHOT appointment_list | OK |  |
| 10 | RECEPTION | PAUSE_AND_DISCUSS (appointments list) | OK (timeout, auto-continue) | — |
| 11 | RECEPTION | NAVIGATE /dental/appointments/create/ |
OK | — |
| 12 | RECEPTION | VERIFY_VIEW /dental/appointments/create/ |
OK | — |
| 13 | RECEPTION | VERIFY_TEXT Book Appointment |
OK | — |
| 14 | RECEPTION | TYPE practice → Test Client Dental Practice | OK | — |
| 15 | RECEPTION | WAIT_MS 1500 | OK | — |
| 16 | RECEPTION | TYPE appointment_type → Filling | OK | — |
| 17 | RECEPTION | WAIT_MS 1500 | OK | — |
| 18 | RECEPTION | TYPE provider → Holloway, Sarah | OK | — |
| 19 | RECEPTION | WAIT_MS 1500 | OK | — |
| 20 | RECEPTION | TYPE date → NEXT_MONDAY (2026-08-17) | OK | — |
| 21 | RECEPTION | WAIT_MS 1500 | OK | — |
| 22 | RECEPTION | VERIFY_TEXT Available slots |
OK | — |
| 23 | RECEPTION | TYPE patient_id → Oliver Reed | OK | — |
| 24 | RECEPTION | TYPE nhs_band → Band 2 | OK | — |
| 25 | RECEPTION | TYPE symptoms (sharp pain on hot/cold, dark spot lower right premolar) | OK | — |
| 26 | RECEPTION | CLICK first available slot (2026-08-17 09:00) | OK | — |
| 27 | RECEPTION | SCREENSHOT booking_form_filled | OK |  |
| 28 | RECEPTION | PAUSE_AND_DISCUSS (form ready — submit?) | OK (resumed) | — |
| 29 | RECEPTION | CLICK submit | OK | — |
| 30 | RECEPTION | WAIT_MS 2500 | OK | — |
| 31 | RECEPTION | VERIFY_VIEW /dental/appointments/ |
OK | — |
| 32 | RECEPTION | VERIFY_TEXT Appointment booked |
OK | — |
| 33 | RECEPTION | VERIFY_TEXT Oliver Reed |
OK | — |
| 34 | RECEPTION | VERIFY_TEXT BOOKED |
OK | — |
| 35 | RECEPTION | VERIFY_TEXT AI Priority |
OK | — |
| 36 | RECEPTION | SCREENSHOT booking_created | OK |  |
| 37 | RECEPTION | PAUSE_AND_DISCUSS (booking created) | OK (resumed) | — |
| 38 | RECEPTION | NAVIGATE /dental/triage/ |
OK | — |
| 39 | RECEPTION | VERIFY_VIEW /dental/triage/ |
OK | — |
| 40 | RECEPTION | VERIFY_TEXT AI Triage Dashboard |
OK | — |
| 41 | RECEPTION | VERIFY_TEXT Oliver Reed |
OK | — |
| 42 | RECEPTION | SCREENSHOT triage_queue | OK |  |
| 43 | RECEPTION | NOTE: closing | OK | — |
¶ Narration (as the run told the story)
Welcome — this demo books a real appointment in the practice system, live,
using the native dental booking flow. The symptoms we enter will trigger AI
triage, so the booking lands in the triage queue.Logged in as the receptionist (reception.test-client-dental). Now opening the
appointments list.The appointments list is the demo's entry point — it now works for dental
staff (previously every DENTAL_* role saw "No appointments found."). It shows
appointments across Booked, Attended, Cancelled and DNA. We'll book a new
appointment for Oliver Reed.Opening the native dental booking form at
/dental/appointments/create/.The form is ready: Oliver Reed, Filling (NHS Band 2), Sarah Holloway, Monday
17 August — with the symptoms note that will trigger AI triage. Shall I
submit?The appointment is created — BOOKED, with the success banner — and the AI
Priority score (1/5) shows the rule-based triage ran from the symptoms. Let's
see it in the triage queue.The appointment was created in the live client database (BOOKED + triaged
with a priority score of 1/5). Each run is reseeded, so this repeats cleanly.
¶ Live Q&A
No viewer questions were asked during this run (control channel active the
whole time; two discussion pauses ended by resume).
¶ Development notes
No development notes were requested by the audience this run.
¶ Artifacts
- Steps log:
/opt/hermes-demo/runs/dental_appointment_booking_20260813T074312Z/steps.log - Screenshots:
/opt/hermes-demo/runs/dental_appointment_booking_20260813T074312Z/shots/ - Conversation stream:
outbox.json(9 narration/system messages, no questions or notes)
¶ Observations
- The dependent selects (practice → appointment_type → provider → date) each
auto-submit the GET filter form; slots for 2026-08-17 rendered correctly for
Sarah Holloway, and the POST carried the hidden practice/provider/appointment
type fields (defects from earlier runs remain fixed). - Success banner "Appointment booked for Oliver Reed (Filling, 17/08/2026
09:00)" appeared on the detail page (/dental/appointments/539/), status
Booked, NHS Band 2, AI Priority 1/5. - The new booking appeared in the AI Triage Dashboard queue for Oliver Reed.