A demo can sound excellent while leaving you with a full callback list. The voice is natural. The answers are quick. Then somebody asks how the appointment reaches the schedule, and the answer becomes less specific.
Use a common test script to get past that problem. Ask each supplier to complete the same ordinary clinic tasks, including the awkward ones. Inspect the resulting record instead of scoring the conversation alone.
This scorecard is an original Moxcares evaluation worksheet, free to use with any supplier—including Moxcares. It is not a vendor ranking, certification or hands-on product review.
Agree what you are buying before scoring a demo
A phone-answering service, a patient-engagement layer and a full practice platform may overlap without having the same scope. Write down your required starting point: existing EHR, current schedule, locations, visit types, languages, opening hours and the staff member who receives exceptions.
Then choose the outcomes you need. “Answer calls” is one requirement. “Book an appropriate appointment and send the approved next step” is a larger requirement. Neither is automatically the right choice for every clinic.
Mark a required workflow as a must-have before seeing the demo. Otherwise an attractive extra can distract from the task that caused you to start shopping. Our AI receptionist comparison explains several different product scopes; this worksheet is for testing the shortlist you create.
Run these 12 tests with synthetic patients
Ask for a sandbox or an approved demonstration environment. Do not put real patient details into a sales demo. Use a fictional patient who changes their mind, misses a question and needs a person at least once.
| Test | Scenario | Evidence to inspect |
|---|---|---|
| 1. New booking | An appropriate new patient asks for a visit. | Correct patient, visit type, provider, location and confirmed slot. |
| 2. Rescheduling | An existing patient needs a different day. | Old and new appointments have the intended final states. |
| 3. Cancellation | A patient cancels without rebooking. | Cancellation is recorded and any next action is visible. |
| 4. Waitlist offer | A matching slot opens; one patient accepts. | Offer, acceptance and booking are distinct; no duplicate confirmation. |
| 5. Enquiry follow-up | A website enquirer has not yet booked. | Owner, contact preference and next action are retained. |
| 6. Staff handoff | The patient asks for a person. | A named team receives context and a follow-up task. |
| 7. Booking exception | The requested visit is outside the rules. | The system does not invent availability or silently close the task. |
| 8. Unfinished intake | A patient skips a required question. | The missing answer is visible and has an appropriate next step. |
| 9. Intake summary | A patient reports a changed medication list. | Patient-reported information is preserved for human review. |
| 10. EHR handoff | An intake summary must reach the existing chart workflow. | Correct destination, identity match, review owner and failure visibility. |
| 11. Arrival | A booked patient checks in. | Arrived, intake readiness and roomed states remain distinct. |
| 12. Contact preference | A patient declines further messages. | The preference changes future outreach and is visible to staff. |
For a multilingual requirement, repeat the important scenarios in a language your patients use with someone qualified to assess the exchange. A list of supported languages does not show whether the booking instructions are understandable.
Score the result without inventing a magic number
The download uses five outcomes: Untested, Completed, Staff step required, Not supported and Not applicable. These labels describe the test result. They are not an overall quality grade.
“Completed” means the agreed workflow reached its intended end state and you saw evidence. If the system took a message and a receptionist later booked the visit, record the staff step. That might still be a worthwhile service—but it is a different operating model.
Keep untested separate from unsupported. A supplier may be able to demonstrate a capability later. Until then, record the gap rather than giving credit for a roadmap promise. Keep not-applicable separate too; removing an irrelevant test is different from passing it.
Do not total all rows into a universal winner. A failed must-have may matter more than five optional passes. Compare required workflows, staff effort, unresolved questions and full quoted scope.
Watch the failed path as closely as the successful one
Ask what happens when availability changes mid-conversation, the destination system is unavailable or identity is uncertain. The system should leave the patient with an accurate next step and the team with visible work to resolve.
For an EHR handoff, inspect the destination and review queue. Ask which steps are supported in your exact environment, which depend on staff and which require additional configuration. Avoid accepting “works with EHRs” as the whole answer.
A clinical request should follow the practice’s approved escalation process. An administrative assistant should not turn a patient’s symptom description into an autonomous diagnosis or a promise about clinical urgency.
Have reception and clinical staff try the test script. AHRQ’s workflow toolkit includes usability evaluation and process-mapping tools. The scorecard here is a practical demo aid inspired by that workflow-first approach; it is not an AHRQ-endorsed instrument.
Add the operating questions that a demo cannot settle
Ask for the written scope: onboarding tasks, usage allowances, supported actions, implementation responsibilities, support arrangements and any optional modules. Check call or message charges, provider or location fees and staff work that sits outside the quote.
Review data access, retention, roles and the contractual arrangements appropriate to your practice before a live pilot. A convincing demonstration does not establish the security or legal suitability of a deployment. Keep those questions alongside the workflow result, rather than treating a marketing badge as the answer.
Our software cost guide helps organize the quote. The useful comparison is the cost of the workflow you intend to operate, with the work left for your team made explicit.
Use the same scorecard again after the pilot
Bring back the original test cases once the system is configured. Record what actually completed and why exceptions occurred. Add a clinic-specific scenario if the standard set missed something important.
Moxcares offers a patient-engagement layer around an existing EHR and a separate end-to-end practice platform. Ask us to demonstrate the path you plan to buy, including human review and the handoff into your current setup.
You may adapt this worksheet for your practice, client workshop or teaching session. If you share it publicly, a link to this article helps others find the current version and its instructions. No endorsement or favorable review is required.
Keep reading
Put a real workflow on the demo agenda
Bring your existing EHR, one patient scenario and the handoff you want to improve. We will walk through the supported workflow and staff responsibilities.
Explore keeping your EHR