Demonstration
One Veteran. One Conversation. Connected Care. This is a synthetic scheduling demonstration, not a live VA appointment service.
Recorded demonstration
Open the full recording (MP4, 3 min 36 sec). Follow the caller’s request, Avery’s replies and the MCP tool activity in the conversation panel. All caller details in this recording are synthetic.
A verified scheduling journey · November 16, 2026
| Step | What happened | Enforcement / evidence |
|---|---|---|
| 01 · Greet | Synthetic caller describes a Primary Care request | LiveKit/voice application |
| 02 · Verify | Caller identity and session/case binding verified | Trusted host; not model-provided authority |
| 03 · Retrieve | IBM selected patient summary and call knowledge tools | Scoped structured MCP reads |
| 04 · Search & select | IBM selected search_call_appointments and select_call_appointment; two verified options returned |
Selected option is not yet a booking |
| 05 · Confirm | Host read back exact option; caller confirmed in a later turn | Current consent and policy checked independently |
| 06 · Book & wrap up | IBM selected book_call_appointment; protected synthetic commit and host CRM write |
Independently verified one appointment, one CRM note; receipt BOOKED_SIMULATED |
Five distinct IBM-selected tool types are evidenced. Automatic host-written CRM work should not be falsely attributed to a separate agent tool call.
Proof beyond a spoken answer
The acceptance report for CASE-047 records a successful real-time generated-audio call using backend revision 00037 and frontend revision 00022. Independent persisted-record reads confirmed the synthetic appointment and CRM interaction. CASE-047 is consumed historical evidence; do not replay the write to re-demonstrate it.
Read RTC acceptance and retained failures · Machine-readable proof JSON
Reproduce safe local behavior
{"name":"get_scheduling_encounter","arguments":{"case_id":"DEMO-CARD-5000335-001"}}
Use the synthetic Cardiology and Primary Care fixture IDs listed in Developer Guide, then try UNKNOWN-CASE. These read-only tests establish deterministic MCP behavior, not a new voice booking.
What to show judges in five minutes
- One-sentence problem and solution.
- The MCP server and host authority boundaries.
- The accepted tool sequence and the persisted synthetic booking receipt.
- A real local MCP fixture read and unknown-case denial.
- Evidence, limitations and source/reproduction references.
No production VHA write access or clinical decision authority is claimed.