athenaOne Built-In AI vs Pretty Good AI

The question is what still needs doing

An athenaOne practice does not need another product simply because that product has AI. It needs a defined piece of work completed correctly, under the practice’s rules, with a clear owner when a person must step in.

Pretty Good AI builds on athenaOne. Keep the EHR, its patient portal and the workflows that already work for your team. Bring us the process that still involves missed handoffs, repeat data entry or a queue nobody has time to work. We map it with your staff and agree on what should change before launch.

This guide distinguishes athenahealth’s published capabilities from implementation questions you should verify in your own environment. It is not an audit of your subscription or a head-to-head performance study.

What athenahealth documents today

Self-service and communication. The patient-engagement product page describes online scheduling, self-check-in, online payments and outreach messaging. Source: patient-engagement product page. The February 19, 2026 announcement separately describes Patient Conversations, combining two-way texting and secure web chat, with a virtual front desk voice assistant scheduled for the second half of 2026. Source: February announcement.

Released waitlist support. The August 12, 2026 Summer Release describes Waitlist Scheduling notifying eligible patients about newly available appointments. It also describes patient-registration improvements. Do not characterize waitlist support as merely a February announcement. Source: Summer 2026 Release.

Practice enablement matters. The athenaPatient page says self-scheduling and self-check-in must be enabled before patients can use them in the app. A capability appearing in public documentation does not identify your practice’s settings. Source: athenaPatient requirements.

Announcements are not an entitlement list. The February 19, 2026 announcement described several releases with different timing, including Patient Conversations, waitlist scheduling and portal assistants. Use that announcement as historical context, not proof that every announced feature is active in every account. Source: February announcement.

Before comparing proposals, ask your athenahealth contact to confirm the feature name, enabled configuration, supported workflow, release status and commercial terms for your practice. This guide does not label all built-in features free, bundled or generally available.

Where Pretty Good AI adds work around athenaOne

Our focus is the process your practice runs, not a second system of record. Production access to 820+ athenaOne APIs supports workflows built around the records and rules your staff already use. API access alone is not a finished workflow: the configured steps, review points and completion criteria still need to be agreed.

Patient Engagement. Voice, secure two-way text, web scheduling and self-check-in can share the practice’s rules. Evaluate a new-patient booking, an established-patient match and a visit that needs staff review. The web scheduling workflow explains what gets recorded and where a person steps in.

Task Automation. Map the request, the athenaOne case or task involved, the work to be performed and the handoff. A request that needs clinical judgment must reach the care team with context. Clinical decisions stay with your care team.

Referral Management. Fax, provider forms and patient self-referrals enter an intake and review workflow. Evaluate matching, missing-information follow-up, acceptance and scheduling as separate steps. The referral management workflow explains the review queue and patient outreach.

Revenue Cycle. Agree which insurance, authorization and balance-follow-up steps your billing team wants automated. Specify the athenaOne record updated and the exception owner. Keep checking eligibility, preparing authorization information and recording a payer response distinct from guaranteeing approval or reimbursement.

For each area, the comparison is the same: which agreed steps finish, what remains for staff, and who keeps the workflow working when your rules change?

Compare one real transaction, not two feature lists

Choose a workflow that consumes staff time today. Use a synthetic example in a demonstration, not patient information in a public form.

For scheduling, work through patient matching, provider and visit-type rules, the appointment writeback and any required intake. For referrals, follow the document through matching, review, outreach and the booked visit. Include a missing-information case rather than showing only the easiest path.

Inspect the result in athenaOne. An offered slot is not a booked appointment. A booked appointment is not an attended visit. A message sent is not a completed request. Count the milestone the practice actually wants improved.

If your current configuration already completes those agreed steps, there may be no additional workflow to commission there. Identify the next bottleneck instead. Pretty Good AI’s role is to build the workflow that still does not fit, not duplicate automation merely to add another subscription.

Decide ownership before activating overlapping tools

Two tools touching the same appointment are an implementation decision, not automatically a benefit or a problem. Use this checklist with your implementation team:

• Trigger and action: name the system responsible for each reminder, waitlist offer, referral outreach and booking action.
• Record and handoff: define where the outcome is written, who sees failures and what stops further outreach after the work finishes.
• Change ownership: identify who updates the rules when providers, locations, hours or scheduling policies change.

Then validate those choices in the agreed test environment. This checklist does not claim that all third-party products coordinate automatically. Your existing portal and other enabled athenaOne functions remain part of the practice’s operating model.

Scope, evidence and ongoing work belong in the decision

Compare the incremental workflow you are buying, the setup work your team must contribute, the records and permissions involved, and who maintains it. Review the commercial scope in the relevant agreements rather than assuming that two similarly named features include identical work.

Pretty Good AI starts with an agreed workflow and success measure. We agree on the first workflow, how success will be measured, and the pricing for continued use before launch. There are no setup fees. Your first 30 days live are free. The clock starts when your first agreed workflow goes live in your practice, whether that is voice, web scheduling, referrals or another workflow. When the free 30 days end, service continues automatically, month to month, at the pricing in your order form. New workflows are priced when activated.

The customer evidence and pricing explanation provide different parts of that evaluation. A named deployment establishes use; a measured improvement needs a defined cohort, time window and outcome. Do not use voice-containment results as a measured referral-conversion result.

Bring the work that still gets stuck to a working session. We will map the process, its athenaOne record changes and the human review points before agreeing the first workflow.