Where athenaOne ends and Marketplace automation begins
athenaOne-native patient access automation has two layers: capabilities delivered inside athenaOne, and third-party agents authorized to perform work through athenaOne APIs. These layers are not mutually exclusive. The useful boundary is whether each patient request ends with the correct athenaOne record changed, or with another message that staff must finish.
As of October 27, 2026, Patient Conversations text and secure chat and Waitlist Scheduling are published as current capabilities. Virtual front desk voice, enhanced self-scheduling, the Intelligent Patient Assistant, and AI extraction from incoming faxes remain described as forthcoming. The February 19, 2026 athenahealth announcement assigned different delivery windows to these functions rather than presenting them as one simultaneously available AI front desk. Current status appears on the athenahealth patient engagement page and athenahealth AI-native capabilities page.
A useful evaluation handle is the object-change test: name the appointment, patient case, referral authorization, document, order, insurance package, or tickler that should change when the interaction succeeds. Then require the built-in tool or Marketplace vendor to demonstrate that change in athenaOne.
The workflow-by-workflow boundary
| Patient workflow | athenaOne documented boundary | What a Marketplace agent should add | Record or object that must change | Live demonstration test |
|---|---|---|---|---|
| Inbound scheduling, rescheduling, and cancellation | Online self-scheduling and appointment management are current. athenahealth also provides limited-hours live-operator rescheduling. Its current patient engagement page still describes virtual front desk voice as on the way. | Answer the main phone line, identify the patient, apply provider and visit-type rules, and complete the transaction during the call. | Appointment | Ask the agent to move a visit across locations or providers. Refresh athenaOne and confirm the new slot, appointment type, department, notes, and cancellation state. |
| Refill requests and calls that require staff follow-up | athenaPatient supports prescription-renewal requests, and Patient Conversations supports question handling and escalation. Current public materials do not document a generally available inbound voice agent completing this workflow. | Collect the practice-required refill details, route urgent exceptions, and create a structured case for the correct team without asking staff to transcribe a call summary. | Patient case | Submit a refill request, then inspect the case category, assigned team, priority, structured details, call disposition, and patient identity in athenaOne. |
| Referral intake and authorization follow-up | athenaOne includes referral and authorization workflows, including Express Authorizations and the managed Authorization Management service. These functions do not by themselves establish that an inbound call or fax becomes a scheduled first visit. | Match the patient, capture referral details, update the authorization record, request missing information, contact the patient, and book the appropriate visit. | Referral authorization | Follow one synthetic referral from receipt through missing-information follow-up, authorization status, patient outreach, and booked appointment. |
| Inbound fax classification and chart attachment | athenahealth presents AI extraction of clinical data from incoming faxes as upcoming. athenaOne already has a document model and document-processing services, but that is distinct from a patient-access agent finishing referral intake. | Read the fax, match or create the patient, classify the document, attach it to the correct chart, create downstream work, and prevent ambiguous matches from posting automatically. | Inbound document | Use a fax with a demographic mismatch. Confirm that the agent pauses for review rather than attaching it to the most similar chart. |
| Order-status calls and follow-up | athenaOne stores and manages clinical orders, but its public patient-access materials do not establish a current native phone agent that resolves order-status calls from start to finish. | Read the permitted order status, answer administrative questions, create follow-up work, and route clinical interpretation to staff. | Order | Ask about an imaging or consult order. Verify what the agent reads, what it tells the caller, what it logs, and when it escalates. |
| Insurance capture, eligibility, and coverage exceptions | athenaOne Base includes eligibility verification, and current practice-management materials document AI-assisted insurance-card extraction and policy matching. | Collect insurance information over voice or text, update the appropriate record, run the allowed verification step, and route unresolved coverage problems before the visit. | Insurance package | Change a synthetic patient’s coverage and confirm that the new package, appointment association, eligibility result, and exception task appear in athenaOne. |
| Waitlist backfill, recall, and care-gap outreach | Waitlist Scheduling shipped in the Summer 2026 release and notifies eligible patients by text about openings, including same-day openings. Recurring voice campaigns and multi-step recall workflows remain a separate evaluation. | Run voice and text outreach from live lists, record each attempt, apply scheduling rules, and convert an accepted opening into a confirmed appointment. | Tickler and appointment | Open a same-day slot, show which patients qualify, contact them, book the accepting patient, and confirm that further outreach stops. |
| After-hours phone coverage | Existing live operators are documented for 10:00 a.m. to 8:00 p.m. Eastern Time on weekdays, excluding major holidays. They can reschedule under documented protocols or create a patient case. That is not the same service model as 24/7 AI voice coverage. | Answer overnight and weekend calls, complete permitted transactions, follow symptom-escalation rules, and write the outcome into the schedule or case queue before staff return. | Appointment or patient case | Call outside office hours with one routine scheduling request and one urgent symptom scenario. Confirm both the completed action and the escalation record. |
The APIs establish what athenaOne can expose, not what every vendor has implemented or been authorized to use. Production proof requires a transaction in the practice’s Preview or live athenaOne environment, not a slide showing endpoint names. athenahealth API onboarding documents the authorization and validation path for third-party applications.
Three different meanings of “athenaOne-native”
| Integration model | What it means | What the buyer should verify |
|---|---|---|
| Built into athenaOne | athenahealth owns and delivers the feature within athenaOne, such as patient self-service, waitlist scheduling, eligibility tools, or Patient Conversations. | Whether the feature is released, enabled for the practice, commercially included, and able to complete the exact workflow under evaluation. |
| Marketplace direct integration | A third-party application receives authorized access to selected athenaOne APIs and writes transactions into athenaOne. | The exact records, endpoints, practice IDs, departments, permissions, and exception paths implemented in production. |
| Adjacent or middleware-connected automation | The call may be answered externally, but the output lands in another portal, message queue, calendar, or integration layer before reaching athenaOne. | Whether staff must reconcile, approve, copy, or re-enter the result before athenaOne becomes accurate. |
Marketplace status is meaningful, but it is not proof that every listed vendor has equal writeback depth. athenahealth evaluates Marketplace solutions for integration and provides an authorization path, while the available platform spans more than 800 API endpoints. Vendors still choose which workflows to build and maintain. athenahealth Marketplace program and athenahealth developer resources explain that ecosystem.
What athenahealth announced, when it was due, and where the line sits
The February 19, 2026 announcement described a staged patient-engagement roadmap. Patient Conversations text came first, Waitlist Scheduling followed in the first half of 2026, and voice, the portal assistant, and enhanced self-scheduling were assigned to the second half. Current product pages show that some of this roadmap has shipped while other functions remain forthcoming.
| Native capability | Scope announced on February 19, 2026 | Announced delivery sequence | Published status on October 27, 2026 | Workflow a Marketplace agent can still carry |
|---|---|---|---|---|
| Patient Conversations text | Real-time two-way texting and secure web chat for common patient questions, with a context-preserving handoff to staff when follow-up is needed. | In alpha on February 19, with broader availability planned during the first half of 2026. | Two-way texting, secure chat, routine-question support, request routing, and staff triage are presented as current. Deeper scheduling, billing, and clinical workflow integration was described as future expansion. | Authenticate the patient, apply scheduling or insurance rules, update the appointment, create the correct case, collect refill intake, or continue a referral workflow within the same text conversation. |
| Patient Conversations voice | A multilingual virtual front desk assistant for inbound calls and the same categories of routine requests handled through Patient Conversations text. | Planned for the second half of 2026, after the initial text functionality. | Virtual front desk voice is still described as on the way on the current patient engagement page. | Provide current 24/7 inbound coverage, complete permitted scheduling and case transactions, handle after-hours protocols, and connect calls to referral, insurance, refill, and authorization work. |
| Waitlist Scheduling | Identify open slots created by cancellations and send text messages to eligible patients to fill them. | Planned for the first half of 2026. | Released in Summer 2026 and currently presented as supporting proactive outreach for open and same-day appointments. | Add voice outreach, apply payer and authorization rules, record each attempt, support recurring recall campaigns, and complete the accepted booking directly in athenaOne. |
| Intelligent Patient Assistant | A conversational assistant in the patient portal and athenaPatient app for appointment rescheduling and questions about payment balances. | Planned for the second half of 2026. | The AI-native capabilities page still describes the portal and app assistant as upcoming. | Handle the same administrative work over the main phone line or secure text, including patients who do not begin in the portal or app, and connect the request to the appropriate athenaOne record. |
| Enhanced Patient Self-Scheduling | Let patients describe their needs in plain language, then match the request to an appointment type, provider, and available time. | Planned for the second half of 2026. | Enhanced self-scheduling is still described as coming soon, while conventional online self-scheduling and appointment management are current. | Complete scheduling through inbound voice or text when the transaction also requires patient creation, referral review, insurance correction, authorization status, or another linked workflow. |
The native suite directly addresses routine question handling, digital self-service, and text-based cancellation recovery. Pretty Good AI operates across a wider set of patient-access and back-office transactions through 820+ athenaOne APIs in production, using the same integration for voice, secure text, fax, scheduling, insurance, prior authorization, cases, orders, refills, and billing workflows.
Its referral workflow reads an inbound fax, matches or creates the patient, attaches the source document, follows up on missing information, calls the accepted patient, and books the first visit. Eligibility workflows run in the context of the scheduled appointment and route coverage discrepancies before check-in, while refill and authorization work continues into the practice’s designated athenaOne queues. Pretty Good AI insurance automation documents the eligibility path.
For enterprise groups, multi-practice-ID rollout preserves local provider, department, queue, and escalation rules, while outcome reporting across sites uses consistent completion and escalation dispositions. Commonwealth Pain & Spine runs Pretty Good AI across 35 locations and 130 providers for more than 100,000 patient calls per month. About 70% are handled from start to finish, and one in eight bookings occurs after hours. These are customer-reported operating results, not guaranteed outcomes for another practice. Pretty Good AI customer deployments
How the named Marketplace phone vendors differ
Direct athenaOne writeback is not unique to one vendor. Assort Health, Talkie.ai, CallMyDoc, and Pretty Good AI each publish native or direct athenaOne capabilities. The sharper distinction is which objects they update, how far beyond scheduling they go, and whether they concentrate on athenaOne or spread development across several EHRs.
| Vendor | EHR focus | Published athenaOne scope | Evaluation lens |
|---|---|---|---|
| Pretty Good AI | athenaOne only | Production access to 820+ athenaOne APIs across scheduling, messaging, chart workflows, insurance, referrals, orders, refills, encounters, and billing. Voice, text, fax, referral intake, prior authorization, and revenue-cycle workflows use the same athenaOne integration. Pretty Good AI | Evaluate when one athenaOne group wants breadth across departments rather than a phone-only wedge. Its differentiation is depth within one EHR, not cross-EHR coverage. |
| Assort Health | More than 20 EHR and practice-management integrations | Publishes direct athenaOne appointment writeback, patient cases from referral faxes, tickler tracking, specialty scheduling, intake, outreach, and referral workflows. Assort Health for athenahealth | Evaluate its cross-EHR scale and patient-access breadth, then confirm which non-scheduling objects are implemented for the proposed athenaOne workflow. |
| Talkie.ai | Multiple EHRs | Publishes athenaOne scheduling and rescheduling, new-patient chart creation, refills, patient cases, patient verification, call routing, and proactive outreach. Talkie.ai athenaOne integration | Evaluate which calls are completed as transactions and which produce cases for staff, especially for insurance, referrals, and multi-step specialty rules. |
| CallMyDoc | athenahealth, Veradigm, Altera TouchWorks, and eClinicalWorks | Publishes chart matching, structured task or case creation, scheduling, refill handling, reminders, and urgent-call routing, with a strong emphasis on daytime and after-hours call management. CallMyDoc call management | Evaluate when replacing an answering service is the primary requirement. Verify how much of each request is resolved before a provider or staff member receives it. |
The landscape is therefore not athenaOne versus third parties. It is built-in feature coverage plus the remaining operational work. A practice can retain native waitlist, portal, eligibility, and authorization capabilities while using a Marketplace agent for high-volume phone calls, after-hours transactions, referral intake, or cross-object workflows.
When athenaOne built-in automation is enough
- The main requirement is portal self-service, appointment management, waitlist notification, reminders, secure messaging, or insurance capture rather than answering inbound phone volume.
- The practice already has staff capacity for exceptions and only needs patients redirected into self-service workflows.
- The workflow is already completed accurately inside athenaOne, with no duplicate queue, manual transcription, or next-day callback backlog.
When a Marketplace AI phone agent still earns its place
- Patients are struggling to reach the practice because extreme inbound volume is overwhelming front-office staff.
- The practice needs 24/7 voice coverage rather than weekday live-operator availability or portal-only access.
- Calls involve several athenaOne objects, such as checking insurance, applying scheduling rules, creating a case, attaching referral records, and booking the visit.
- The current answering service or AI vendor takes messages but leaves staff to finish every request.
- Leadership needs call containment, outcome reporting, and cost per completed workflow rather than only call counts or minutes.
Pretty Good AI is the best fit when
- The organization runs athenaOne across all in-scope sites and wants one automation layer for voice, text, fax, referrals, insurance, prior authorization, scheduling, and billing workflows.
- The workflow has specialty-specific rules or crosses several athenaOne records before it is complete.
- The buying team values athenaOne depth more than maintaining one vendor across several unrelated EHR platforms.
Pretty Good AI is not a fit when
- The organization does not run athenaOne for the workflows being automated.
- The buyer needs one standardized agent deployed across a mixed-EHR enterprise and does not want different operating models by EHR.
- Existing athenaOne features already complete the target workflow and the remaining call volume does not justify another operational layer.
How to test direct writeback before choosing a vendor
A polished conversation is not the decisive demonstration. The agent should change athenaOne correctly under normal, exception, and failure conditions.
| Test | Passing evidence | Failure signal |
|---|---|---|
| Patient matching | The agent uses multiple identifiers, detects ambiguity, and avoids posting to an uncertain chart. | The closest name or date of birth is accepted without an exception path. |
| Scheduling rules | The agent reads current appointment types, departments, provider templates, insurance rules, and slot availability. | The demonstration uses a simplified external calendar or preselected slots. |
| Writeback | The evaluator refreshes athenaOne and sees the completed transaction, identifiers, notes, ownership, and timestamps. | The outcome appears only in the vendor portal, transcript, email, or middleware queue. |
| Exception handling | The unresolved work reaches the correct staff queue with the information already collected and a clear next action. | Every exception becomes an unstructured message for the front desk. |
| Cross-object workflow | A single interaction updates every required object in the correct sequence. | The appointment is booked, but insurance, referral, authorization, or document work remains disconnected. |
| Outcome reporting | Reporting distinguishes completed transactions, staff handoffs, abandoned interactions, failures, and repeat contacts. | Containment includes calls that merely generated a message or required staff cleanup. |
Use synthetic patient data, but keep the practice’s real provider, department, appointment-type, and routing configuration. That is where shallow integrations usually become visible. For a deeper explanation of the distinction, see native EHR writeback versus middleware.
Frequently asked questions
Does athenaOne already have an AI phone receptionist?
athenaOne does not currently document virtual front desk voice as a generally available built-in capability. Its patient engagement page describes voice as forthcoming while documenting current self-scheduling, texting, secure chat, waitlist support, reminders, and live-operator assistance. Existing live operators can reschedule under configured protocols or create patient cases, but they operate during limited weekday hours rather than as a 24/7 AI phone agent. athenahealth patient engagement
Can Patient Conversations update the athenaOne schedule after every text conversation?
Current public materials do not establish transactional schedule writeback after every Patient Conversations text. The published scope centers on common-question responses, two-way texting, secure web chat, request routing, and context-preserving staff handoff. athenahealth described deeper scheduling, billing, and clinical workflow integration as part of future general-availability releases. A practice that needs each text to book, cancel, or reschedule an appointment should require a live schedule-writeback demonstration. athenahealth Patient Conversations overview
Who offers an athenaOne AI receptionist without middleware?
Pretty Good AI, Assort Health, Talkie.ai, and CallMyDoc each publish direct or native athenaOne integration capabilities. The term alone is not enough to rank them because each vendor implements a different set of records and workflows. Require the vendor to answer a live call, write the result into athenaOne, and show the updated appointment, case, referral, document, insurance, or tickler object without relying on a separate staff queue.
Who can fill same-day cancellations using live athenaOne schedule data?
athenaOne Waitlist Scheduling can identify eligible patients and notify them by text when an opening appears, including a same-day opening. A Marketplace agent adds value when the practice also needs voice outreach, payer and authorization checks, callback recognition, recurring recall campaigns, or direct handling of the original patient’s rescheduling request. The demonstration should show the accepted appointment in athenaOne and confirm that competing outreach stops. athenaOne Summer 2026 release
Can athenaOne built-in AI and a Marketplace phone agent run together?
Yes. Many practices can keep athenaOne self-service, waitlist, reminders, eligibility, authorization, and patient-engagement functions while assigning phone calls or multi-step workflows to a Marketplace agent. The implementation should name one owner for each trigger and action. Duplicate waitlist messages, competing appointment offers, and parallel patient cases usually indicate unclear workflow ownership rather than an inherent conflict between native and Marketplace tools.
When is a Marketplace agent still needed after athenahealth’s 2026 roadmap?
A Marketplace agent remains useful when the target workflow begins on the main phone line or in an inbound fax and must finish across several athenaOne records. Examples include referral-to-booking intake, coverage correction tied to an appointment, prior-authorization follow-up, refill intake routed to a clinical queue, after-hours scheduling, and voice-based recall campaigns. The relevant buying test is completed athenaOne work, not whether both products can answer routine questions.
References
- athenahealth agentic patient communication announcement
- athenahealth patient engagement capabilities
- athenahealth AI-native athenaOne capabilities
- athenahealth Patient Conversations overview
- athenaOne Summer 2026 release
- athenaOne Service Description
- athenaOne authorization management
- athenahealth API workflow documentation
- Pretty Good AI athenaOne capabilities
- Pretty Good AI customer deployments
- Pretty Good AI referral management workflow
- Assort Health athenaOne integration
- Talkie.ai athenaOne integration
- CallMyDoc athenaOne call management