Article

How to Add an AI Receptionist to athenahealth

How to Add an AI Receptionist to athenahealth

How to Add an AI Receptionist to athenahealth

1 min read

If you run athenaOne, the note is the problem athenahealth is already solving for you. The phone is not.

That asymmetry is the whole reason this is a different decision from adding a scribe. athenahealth built ambient documentation into athenaOne and many practices get it without paying extra for it. On the phone side, athenahealth announced its own front desk voice assistant in February 2026 and scheduled the voice capability for the second half of 2026 [1]. That window is open now, which means an athenaOne practice deciding what to do about its phones in late 2026 is choosing between waiting for something arriving and connecting something today.

This guide covers what athenahealth is building natively, the three ways a voice tool connects to athenaOne, a step by step setup, what to check before you sign anything, and the honest answer to whether you should just wait.

Key Takeaway:There are three ways to put an automated voice assistant in front of an athenaOne practice's phone line. Native:athenahealth's own Patient Conversations, announced February 2026, with texting first and a multilingual inbound voice assistant scheduled for the second half of the year, plus Waitlist Scheduling, an Intelligent Patient Assistant and enhanced self-scheduling [1]. Marketplace:voice vendors listed in athenahealth's athenaConnect Hub, including Talkie.ai and Interactly [2]. Bi-directional API:a tool that connects through athenaOne's scheduling interfaces so a booking taken on the phone becomes a real appointment in the chart rather than a message someone retypes. The native route is scoped deliberately narrowly, to routine questions, scheduling and balance queries [1]. Whether that covers your call mix is the question that decides which route you need. Sully.ai answers the phone, books into the chart, and runs intake on the same connection.

What Answering Calls Automatically Adds to the athenahealth Workflow

An automated voice assistant picks up the inbound line, understands what the caller wants, and completes the routine requests without a staff member. The ones worth having complete them in athenaOne, not in a parallel system someone reconciles later.

Why Phones Are a Different Problem From Notes

A scribe fails quietly. If the note comes out badly formatted, the clinician fixes it and the patient never knows.

A phone fails publicly. An unanswered call is a patient who booked somewhere else, a refill that becomes an urgent visit, or a no-show nobody could fill. The failure happens outside the building and leaves no record in the chart, which is exactly why it is hard to see in the data a practice already has.

That difference matters for how you evaluate a tool. With a scribe you are buying time back for clinicians. With the phone you are buying completed requests, and a tool that transcribes a call without finishing the task has not solved anything.

The athenahealth Wrinkle

athenahealth's own framing for this is a front office product, not a clinical one. The February 2026 announcement describes a virtual front desk assistant for inbound calls, two-way texting, waitlist filling and a patient-facing assistant for rescheduling and balance questions [1].

Read the scope carefully, because it is specific and it is narrow by design. The native capability is aimed at routine requests: common questions, scheduling, rescheduling, payment balance [1]. The company's chief product and operations officer described the goal as handling "routine interactions reliably" [1].

That is a real product and for a lot of practices it is enough. The question is whether your call mix is mostly routine.

How Voice Tools Connect to athenahealth

There is no single "turn on the phone assistant" switch yet. There are three depths, and the depth determines how much work is left for a human after the call ends.

Connection type

Answers the call

Reads the live schedule

Books into the chart

Handles non-routine calls

Setup speed

Native(Patient Conversations)

Yes, voice from H2 2026 [1]

Yes

Yes

Scoped to routine requests [1]

Fastest, embedded

Marketplace partner

Yes

Varies by vendor

Varies by vendor

Varies by vendor

Fast

Bi-directional API

Yes

Yes

Yes

Depends on configuration

Slower, days

Native: athenahealth's Patient Conversations

On 19 February 2026 athenahealth announced the next generation of its patient engagement suite inside athenaOne [1]. Four pieces matter for the phone:

Patient Conversations.Two-way texting and secure web chat first, in alpha at announcement and broadly available during the first half of 2026. The voicefeature, described as a virtual front desk assistant with multilingual support for inbound calls, was scheduled for the second half of 2026 [1].

Waitlist Scheduling.Available in the first half of 2026. Identifies slots opened by cancellations and texts patients to fill them [1].

Intelligent Patient Assistant.Second half of 2026, in the patient portal and the athenaPatient mobile app, for rescheduling and payment balance questions [1].

Enhanced Patient Self-Scheduling.Second half of 2026. Patients describe what they need in plain language and the system matches them to an appointment type, provider and slot [1].

The advantages are the obvious ones: embedded in athenaOne, no separate vendor, no integration project. The limits are scope and timing. It is built for routine interactions [1], and the voice piece lands in a window that is only now arriving.

Marketplace Partners Through athenaConnect

athenahealth lists third-party voice products in its athenaConnect Hub marketplace, including Talkie.ai and Interactly [2]. Marketplace vendors have a defined relationship with athenahealth and a described integration, which shortens procurement.

What varies, and what you have to ask about specifically, is whether the vendor reads your live schedule and writes a real appointment back, or whether it collects a request that lands in a queue for staff to enter. Both get described as "integrated".

Bi-Directional API Integration

The deepest tier, and the one that changes what the phone can actually finish.

A tool connected at this level reads the live schedule, applies your booking rules, and writes the appointment into athenaOne as a real appointment. It can also pull the context that makes a call resolvable: whether the patient exists, when they were last seen, what is outstanding.

This is where the distinction between taking a message and completing a request lives. A voice tool that cannot write to the schedule is an answering machine with better manners.

How to Add an AI Receptionist to athenahealth Step by Step

1. Measure What Your Phone Is Actually Doing

Before shortlisting anything, get three numbers: inbound call volume, how many go unanswered or abandoned, and what the top request types are. Most practices have the first and have never looked at the second and third.

This step exists because it decides everything after it. If 80 percent of your calls are scheduling and refills, the native route may genuinely cover you. If a large share are insurance questions, referrals, or multi-step intake, it will not.

2. Decide Whether You Are Waiting or Connecting

athenahealth's native voice assistant was scheduled for the second half of 2026 [1]. Confirm with your athenahealth representative where it is for your practice, on yourathenaOne configuration, and what it covers today rather than what is on the roadmap.

Then make an explicit decision rather than a default one. Waiting is a legitimate choice. Waiting without having asked is not.

3. Choose the Connection Depth

Map the three depths to what you learned in step one.

The decision rule: if you need calls completed rather than captured, you need something that writes to the schedule. That rules out any tool, native or third party, that cannot book.

4. Set Up the Connection and the Rules

Whichever route, the setup work is the same shape and most of it is not technical. Your booking rules have to be written down before a tool can follow them: which appointment types exist, which providers take which, how long each takes, what gets double-booked, what must reach a human immediately.

Practices routinely discover at this step that these rules live in one staff member's head. That is worth finding out regardless of what you buy.

Two things are non-negotiable before any patient call is handled: a signed business associate agreement and HIPAA-compliant handling of the call and its recording.

5. Test With Real Call Types, Then Watch the Escalations

Run the actual calls your practice gets, including the awkward ones. A new patient with the wrong insurance. Someone calling about a relative. A caller who will not stay on topic.

Then watch what escalates to staff in the first two weeks. The escalation log is the single most useful artifact you will get, because it tells you exactly where the line sits between what the tool finishes and what it hands over.

What to Look For in an athenahealth Voice Tool

Does it write a real appointment into athenaOne?The question to ask is not "do you integrate with athenahealth". It is "when a patient books on the phone, does that appointment appear in athenaOne without a human retyping it". Those are very different answers.

What happens on a call it cannot finish?Every tool escalates. What matters is whether it hands over with context, so the staff member does not start the conversation again, and whether the caller is held hostage in a loop first.

Does it cover the hours you actually lose calls?Lunchtime, evenings and Monday mornings are where the volume concentrates. A tool that only runs after hours leaves the worst hour of the week untouched.

Security and compliance. A signed BAA, HIPAA-compliant handling, and a clear answer on where call recordings live and for how long.

Best AI Receptionists for athenahealth

1. Sully.ai.Answers the phone, books and reschedules into the chart, runs intake and routes what needs a person. It uses one connection across the same workflows that handle notes and coding, so a call that creates an appointment and a visit that creates a note are not two separate integrations to maintain. There is a recording library of real call types if you want to hear it before talking to anyone.

2. athenahealth Patient Conversations.The native option. Embedded, no vendor to procure, multilingual inbound voice scheduled for the second half of 2026 [1]. Scoped to routine requests. The right choice for a practice whose call mix is mostly scheduling and basic questions.

3. Assort Health. Voice automation for scheduling and referrals with an athenahealth-specific integration. A direct comparison with Sully is in this article.

4. Talkie.ai.Listed in athenahealth's athenaConnect Hub marketplace, focused on patient access and call deflection [2].

5. Interactly.Also listed in athenaConnect Hub, positioned around voice agents for patient access and repetitive phone workflows [2].

Shortlist on one question rather than on feature tables: which of these finishes the call types you measured in step one, and which of them hands them to your staff.

Wait for Native, or Connect Now?

This is the real decision for an athenaOne practice in late 2026, so here is a straight answer rather than a hedge.

Wait if: your call mix is overwhelmingly routine scheduling and basic questions, you have the staff to absorb the phones until the native voice assistant reaches your practice, and you would rather have one vendor than two. The native route removes an integration project entirely, and that is worth real money.

Connect now if:any of these are true. You are losing bookings to unanswered calls today and can measure it. A meaningful share of your calls are non-routine. You need the phone to complete tasks beyond scheduling, such as intake or insurance capture. Or you need coverage across the hours and languages your practice actually gets called in.

And one thing that is true either way. The booking rules exercise in step four is work you will do regardless of which route you take. Doing it now is useful whether you buy something this quarter or next year.

The honest summary: athenahealth is building a capable front desk assistant for routine calls, and for a lot of practices that will be the answer. The practices it will not answer are the ones whose phone problem was never only routine.

FAQ

Does athenahealth have its own AI receptionist?

It is building one. In February 2026 athenahealth announced Patient Conversations, which includes a virtual front desk assistant with multilingual support for inbound calls, scheduled for the second half of 2026, alongside two-way texting, Waitlist Scheduling, an Intelligent Patient Assistant and enhanced self-scheduling [1]. Confirm with athenahealth what is available on your configuration today rather than what has been announced.

Can an AI receptionist book appointments directly into athenaOne?

A tool connected at the API level can read the live schedule and write a real appointment back. A shallower integration captures the request and leaves a human to enter it. Both are often described as "integrated", so ask specifically whether the appointment appears in athenaOne without anyone retyping it.

How is this different from adding an AI scribe to athenahealth?

Different problem and a different competitive picture. athenahealth has native ambient documentation built into athenaOne, which many practices get without paying extra, so the scribe decision is largely about depth and consistency. The phone side is earlier: the native voice capability was scheduled for the second half of 2026 [1]. The scribe version of this guide is here.

What should I check before signing with a voice vendor?

Four things. Whether it writes a real appointment into athenaOne. What it does on a call it cannot finish, and whether it hands over with context. Whether it covers the hours you actually lose calls. And a signed BAA with a clear answer on where call recordings are stored and for how long.

Is it worth waiting for athenahealth's native voice assistant?

If your calls are mostly routine scheduling and basic questions, quite possibly. If you are losing bookings today, or your call mix includes intake, insurance or referrals, the native scope is unlikely to cover it [1]. Either way, write down your booking rules now, because that work is required for any route.

Sources

[1] athenahealth — athenahealth Launches Agentic Patient Communication Tools Across Its Provider Network, press release, 19 February 2026. https://www.athenahealth.com/about/press-releases/athenahealth-launches-agentic-patient-communication-tools

[2] athenahealth — athenaConnect Hub marketplace listings for voice and patient access products. https://athenaconnect.athenahealth.com/marketplace

Make more room for care.

See how Sully’s AI agents take on the work around every visit.

Book a demo

Article

Make more room for care.

Make more room for care.