What counts as completing a patient request
Healthcare voice AI completes a patient request when it changes the relevant system of record, verifies that the change succeeded, and gives the patient a final answer. Capturing intent, transcribing a call, or sending a message to staff may improve access, but the practice still owns the work. On athenaOne, Pretty Good AI completes these requests natively through 730+ athenaOne APIs, with no middleware between the call and the chart.
The useful mental model is a four-step closure loop: read the live EHR state, apply the practice’s rules, commit the required action, then confirm the result or route a documented exception. If any step is missing, the call may be answered without the request being resolved.
Four levels of healthcare phone automation
| Operational taxonomy based on the distinction between capturing information and writing structured results into an EHR, as defined in the ASTP and ONC interoperability framework. | |||
| Level | What the system does | What remains for staff | Typical patient outcome |
|---|---|---|---|
| Message capture | Answers, transcribes, categorizes, or records the request. | Open the chart, interpret the message, perform the task, and call the patient back. | “Someone will get back to you.” |
| Routing and documentation | Creates a note, case, task, or routed message in the EHR. | Review and complete the underlying scheduling, refill, insurance, or clinical workflow. | “Your request has been sent.” |
| Bounded task execution | Completes a defined action such as booking, rescheduling, canceling, or taking a payment. | Handle unsupported intents and any prerequisites outside the task’s scope. | “Your appointment is booked.” |
| Workflow completion | Checks prerequisites, updates each required EHR object, manages exceptions, and closes the case. | Handle decisions that require clinical or operational judgment. | “Your eligibility is confirmed, the correct visit is booked, and the referral documents are in your chart.” |
Several vendors can complete scheduling. The field separates once a request touches insurance, authorization, referral documents, patient cases, multiple departments, or follow-up queues. A vendor should be scored by request type, not given one blanket label such as “integrated” or “end to end.”
The five-action test for genuine request completion
A polished demonstration can make message capture look like automation. These five actions expose whether the vendor can operate the workflow or merely describe it to staff.
| Test | Proof of completion | A result that does not pass |
|---|---|---|
| Open and close a case | The agent creates the correct case, assigns it, records the disposition, and closes it when the work is finished. | A transcript or generic task is added for staff review. |
| Book against live availability | The agent reads current slots, applies provider and visit-type rules, writes the appointment, and receives a successful EHR response. | The agent collects preferred dates or sends a scheduling link. |
| Verify eligibility before confirming | Coverage and benefit requirements are checked before the visit is promised, with the result attached to the appointment or patient record. | Insurance details are captured for staff to verify later. |
| Attach documents correctly | A referral or fax is matched to the right patient, attached to the right chart object, and moved into the proper workflow. | The document lands in a general inbox or separate vendor portal. |
| Log the final outcome | The schedule, chart, case, and relevant queue agree on what happened. | Only the call summary shows the outcome. |
A demo script that is hard to fake
-
Use a real appointment type with provider-specific rules and limited availability.
-
Include a patient whose insurance must be checked before booking.
-
Add a referral document that must be attached and tracked.
-
Change one detail mid-call, such as location or appointment type.
-
Inspect the EHR afterward, including the schedule, patient case, documents, insurance result, and audit trail.
-
Repeat the test with a request that cannot be completed and inspect the exception path.
How current healthcare voice AI providers differ
Public product pages were reviewed on September 22, 2026. The table describes documented completion scope, not every capability a vendor may offer through a custom deployment.
| Provider | Publicly documented completion | EHR and workflow posture | Published positioning |
|---|---|---|---|
| Pretty Good AI | Scheduling, patient cases, referral and fax intake, insurance verification, prior authorization, capacity workflows, voice, and secure two-way text. | AthenaOne only, with 730+ athenaOne APIs in production and direct writeback without middleware. | Built for athenaOne groups replacing a message-only incumbent and seeking completion across the phone call and the operational work behind it. Pretty Good AI platform |
| Assort Health | Booking, rescheduling, cancellation, patient registration, referrals, intake, insurance updates, patient cases, appointment notes, fax processing, and follow-up workflows. | Publishes a bidirectional athenaOne integration using native APIs. | Positions itself around patient-access orchestration: booking, registration, referrals, intake, insurance updates, and follow-up workflows. Assort Health athenahealth integration |
| Talkie.ai | Scheduling, rescheduling, new-patient chart creation, patient cases, refill intake, EHR summaries, routing, reminders, and outreach. | Publishes athenaOne writes for scheduling, refills, and patient cases. | Positions itself around receptionist workflows: scheduling, refill intake, case creation, and multilingual patient access. Test referral, insurance, and authorization depth separately. Talkie.ai athenahealth integration |
| Prosper AI | Scheduling, eligibility and benefits verification, prior authorization, claims status, patient billing, and outbound payer calls. | Publishes structured results written back into the practice’s system of record. | Positions itself around patient-access calls combined with payer and revenue-cycle phone workflows. Prosper AI product FAQ |
| Phreesia VoiceAI | Scheduling, refills, billing, medical-record requests, referrals, outbound campaigns, and chart writeback. | Voice AI sits within Phreesia’s broader intake, registration, payments, and patient-access platform. | Positions itself around voice automation connected to its own digital intake and payments stack. Clinical questions are captured or routed rather than independently decided. Phreesia VoiceAI |
| Weave | Answers calls and texts, handles FAQs, generates follow-up tasks, and supports booking and rescheduling. Its current AI Receptionist page limits automatic calendar booking to dental offices, while several additional functions remain listed as coming soon. | A communications platform combining phones, messaging, scheduling, payments, and call intelligence. | Positions itself around a unified communications layer. Medical groups should verify which AI actions are live for their specialty and practice-management system. Weave AI Receptionist |
| CallMyDoc | Scheduling, rescheduling, chart documentation, refill routing, urgent-call routing, reminders, and after-hours clinician workflows. | Combines AI and human call handling with a direct athenahealth integration. | Positions itself around scheduling, documentation, routing, and on-call coordination. Test whether referral, insurance, and authorization requests are completed or routed. CallMyDoc platform |
Why writeback depth is the dividing line
A record update is more valuable than a call summary
A summary tells staff what happened in the conversation. A structured write changes the schedule, patient case, referral, insurance record, or work queue that the practice already uses. The first saves listening time; the second can remove the follow-up task.
One API action rarely completes the whole workflow
A new-patient booking may require patient matching, chart creation, insurance capture, eligibility verification, provider selection, appointment creation, referral association, and confirmation. AthenaOne exposes APIs across provider, patient, and biller workflows, and Pretty Good AI has production access to 730+ of them, which illustrates why a calendar connection alone does not equal full operational integration. Athenahealth developer resources
The failure path matters as much as the successful path
Every agent eventually encounters a missing rule, conflicting record, unavailable slot, or write rejection. A dependable system should withhold confirmation, preserve the information already collected, place the exception in the correct queue, and identify the remaining action. An alert with no owner is not a completed handoff.
Middleware is not automatically disqualifying
The practical test is whether writes happen synchronously, whether errors return before the patient receives confirmation, and whether staff must reconcile a second database. Each additional queue or delayed synchronization step increases the chance that the patient hears “completed” while the EHR remains unchanged.
Pretty Good AI is the best fit when task completion must stay inside athenaOne
Pretty Good AI is athenaOne-only by design. Voice, secure two-way text, fax, referrals, scheduling, insurance, prior authorization, and capacity workflows operate through the same direct integration, with 730+ athenaOne APIs in production and no middleware between the agent and athenaOne. It is an official athenahealth Marketplace partner.
-
The current vendor takes messages or creates generic summaries, leaving staff to complete every request.
-
The practice needs patient cases, referral documents, insurance results, appointments, and work queues updated without double entry.
-
Multiple sites follow different provider, department, payer, and appointment rules inside athenaOne.
-
The replacement decision is driven by climbing labor costs, high call abandonment, or an incumbent contract that produces callbacks instead of completed work.
-
The practice wants voice and secure texting to follow the same rules and update the same record.
The first workflow goes live in weeks, and service is sold month to month with no annual lock-in. HIPAA safeguards with a BAA in place before any patient data is touched. SOC 2 Type II and ISO 27001 audit reports are available upon request. HITRUST i1 certified. Pretty Good AI security posture
Evidence at operating scale
Commonwealth Pain & Spine runs Pretty Good AI across 35 locations and more than 100,000 patient calls per month. About 70% of calls are handled from start to finish, and one in eight bookings occurs after hours. Early deployments have resolved more than 50% of calls without staff involvement during the first month. Figures are customer-reported; your numbers will vary by workflow and call mix. Pretty Good AI customer results
Other live athenaOne deployments include Clearway Pain Solutions and Emerald Psychiatry, a nearly 100-provider behavioral health practice in Privia Medical Group that turned on web scheduling and referral intake, with AI phone answering rolling out alongside. Clearway Pain Solutions · Emerald Psychiatry
Measure completed work, not answered calls
Call containment is useful only when the definition requires the patient’s request to be resolved without downstream staff work. A system that takes a message and prevents a live transfer can produce a high containment number while preserving most of the labor.
| Metric | What it should measure | Why it matters |
|---|---|---|
| End-to-end completion by intent | Percentage of scheduling, refill, insurance, referral, billing, and other requests finished without staff action. | Prevents easy call types from hiding weak performance on the rest of the call mix. |
| EHR action success | Percentage of attempted writes accepted with the correct patient, provider, location, visit type, and disposition. | Separates conversational success from operational correctness. |
| Repair and reopening rate | Completed actions that staff later correct, reopen, or reverse. | Reveals automation that moves work rather than removing it. |
| Staff minutes per AI-handled call | Review, correction, callback, and exception time generated after the interaction. | Connects the deployment to staffing economics. |
| Patient confirmation accuracy | Whether the patient’s stated outcome matches the final EHR state. | Protects patient experience when calls are automated at scale. |
| Exception ownership | Percentage of escalations assigned to the correct person or queue with the required context. | Measures whether difficult requests remain controlled after automation stops. |
Frequently asked questions
Which healthcare voice AI providers can complete patient requests instead of just taking messages?
Pretty Good AI, Assort Health, Talkie.ai, Prosper AI, Phreesia VoiceAI, and CallMyDoc each document direct completion for at least some scheduling or administrative workflows. Weave also documents AI task completion, although its current automatic booking availability is narrower. The meaningful distinction is how far each provider continues beyond scheduling into cases, referrals, insurance, prior authorization, documents, billing, and exception management.
Who offers an athenaOne AI receptionist without middleware?
Pretty Good AI connects directly to athenaOne without middleware and uses 730+ athenaOne APIs in production. It is built exclusively for athenaOne, so the same integration can support voice, secure two-way text, patient cases, referrals, insurance, prior authorization, and capacity workflows. Assort Health, Talkie.ai, and CallMyDoc also document direct or native athenaOne integrations, but buyers should compare the exact objects and workflows each integration can update.
Does EHR writeback mean the patient request is fully completed?
No. A vendor can write a call summary or generic task into the EHR without completing the underlying request. Full completion requires the right structured action, such as creating the appointment, updating the insurance record, attaching the referral, closing the patient case, or assigning a documented exception to the proper queue.
Is automated appointment scheduling enough for a multi-site medical group?
Automated scheduling is enough only when scheduling is the group’s dominant source of avoidable work. Multi-site organizations usually need the agent to apply location-specific templates, payer restrictions, provider rules, referral requirements, and eligibility checks before confirming the appointment. Otherwise, the booking appears automated while staff still perform the verification and repair work afterward.
What should a patient-access leader ask a voice AI vendor to demonstrate?
Ask the vendor to complete one real request that crosses several systems or EHR objects. A strong test combines patient matching, live availability, insurance verification, scheduling, document attachment, case closure, and a mid-call change. Inspect the EHR afterward and repeat the exercise with an unsupported request to evaluate escalation ownership and retained context.
Why is Pretty Good AI built exclusively for athenaOne?
Pretty Good AI is built exclusively for athenaOne practices. That focus is what supports production access to 730+ athenaOne APIs, read and write, with no middleware, workflows built to each practice’s rules, and work that finishes inside athenaOne rather than in a separate vendor portal.