A working example
One call with an administrative and a clinical concern
A patient asks to move a visit to Thursday afternoon and mentions a symptom while explaining why. The assistant can record the requested change for front-desk review. The symptom must follow the practice's clinical escalation instructions, rather than being interpreted by an administrative agent.
Agree the boundary per request type: reviewed office information, pending staff action, or immediate practice-directed clinical escalation.
Make routine office answers reliable
Hours, location, arrival instructions, and contact channels are appropriate starting material when the office approves and maintains them. A callback request can become a concise front-desk item with the reason for contact and a way to return the call.
For an existing visit, a requested new time is not a changed appointment. Staff must check the original visit and the available schedule, then confirm the outcome. The assistant should avoid saying a visit was moved based only on a captured preference.
Route clinical content to the practice
Symptoms, medication, test results, treatment choices, and urgent health concerns are outside a general administrative workflow. The office should provide its own approved instructions for these situations, including what to say when staff are unavailable.
A handoff record should avoid unnecessary sensitive detail. The practice decides what information is required, who may receive it, and which system holds it. A public demo is not a patient portal or clinical triage service.
Review the real front-desk day
Test the questions the office hears repeatedly, then test cases where the caller changes direction: a schedule request becomes a clinical question; a callback request has no reachable number; the office is closed. Check that each outcome has a named owner and accurate caller-facing status.
The RiversideMD demonstration uses fictional office details and prepares example requests. It does not change a visit, send a real staff message, or access a patient record.
Before setup
Questions to bring to the conversation
- 01Approve office answers and assign someone to keep them current.
- 02Define the fields needed for a visit-change or callback request.
- 03Specify who can confirm an actual schedule change.
- 04Write the practice's clinical and urgent-call instructions.
- 05Review an after-hours call that mixes administrative and clinical topics.
Common questions
Clear answers before a pilot
Can a caller reschedule through the website demo?
No. The example prepares a fictional change request. A real office would check the existing visit and confirm any change.
Can the assistant answer symptom questions?
Clinical questions should follow the practice's approved route to qualified staff. The administrative workflow should not diagnose or give treatment advice.
Does a prepared callback note mean staff were notified?
No. Preparation and delivery are separate states. A customer workflow needs its actual destination and delivery behavior verified.
Can we keep our scheduling software?
Possibly. The office and Volimox would review the required permissions and supported actions before agreeing what the agent may do.
See the next step
Explore the office example
Review office answers, visit requests, and staff callbacks using fictional details.
Continue