Pretty Good AI vs Luma Health
Pretty Good AI vs Luma Health
Luma Health runs patient access across many EHRs. Pretty Good AI goes deep on one. What athenaOne practices should ask before choosing, and when keeping Luma is the right call.
The short answer
Luma Health is an operational AI platform for patient access, covering scheduling, referrals, waitlists, reminders and recalls, registration and prep, intake and forms, eligibility, payments, feedback management and a conversational agent, with no-code AI workflow building on top. It is multi-EHR and had 39 athenahealth Marketplace practice connections as of 5 September 2026. Pretty Good AI covers a narrower slice of the same territory but only on athenaOne, with 500+ of athenahealth roughly 800 endpoints connected and a voice-first architecture. For an athenaOne practice the choice is breadth of platform against depth of integration, and for a practice already running Luma happily the honest answer is often to keep it.
When Luma Health is the better fit: You run more than one EHR, or you expect to after an acquisition, and you need one patient access layer across all of them. Luma is built for exactly that and we are not. Also choose Luma if you are already live on it and it is working, if your priority is breadth of the patient access surface rather than depth of any one workflow, or if you want no-code workflow building your own team can own without waiting on a vendor. A platform your staff already know how to run has real value that a feature comparison will not show.
Pretty Good AI vs Luma Health, side by side
| Dimension | Pretty Good AI | Luma Health |
|---|---|---|
| EHR scope | athenaOne only, deliberately. 500+ athenaOne APIs connected out of roughly 800 endpoints athenahealth exposes. | Multi-EHR patient access platform. Integration depth is necessarily spread across the systems it supports. |
| Platform breadth | Voice and messaging, scheduling and capacity, referrals and orders, intake and forms, revenue workflows, reporting. | Broader published surface, including patient pipeline for acquisition, feedback and reputation management, broadcast, and fax transform, alongside the core access workflows. |
| Voice architecture | Built voice-first. The agent calls athenaOne tools mid-conversation, so a call can check real availability and book inside the call rather than queueing work for afterwards. | A conversational agent plus outbound conversational AI for no-show recovery, layered onto a platform that began with asynchronous patient messaging and workflow. |
| Workflow configuration | Configured with the practice during the first 30 days live against live calls and the practice own scheduling rules. | No-code AI workflow creation, so the practice team can build and change workflows directly. A genuine advantage for groups with operations staff who want to own this. |
| athenahealth Marketplace record | 40 practice connections, 17 reviews, all five-star, listed September 2025. | 39 practice connections and 1 review on the marketplace. A much larger company overall, but a comparable athenaOne-specific footprint. |
| Scheduling rule complexity | Reads appointment types, provider group and department rules and live slot availability directly from athenaOne, so the rules the practice already maintains are the rules the agent follows. | Scheduling across supported EHRs. Practices with unusual athenaOne rule structures should test their specific cases during evaluation. |
| Published pricing | Pricing model published: platform fee per location, per-provider fee for modules switched on, voice metered per call handled. Month-to-month, first 30 days live are free. | No public pricing. |
| Best fit | Single-EHR athenaOne practices where phone volume is the constraint. | Multi-EHR groups, or practices wanting the widest patient access surface from one vendor. |
| Where the coverage overlaps today | Referral intake, waitlists, reminders and recalls, registration and prep, intake and forms, eligibility, payments and feedback all run here, on athenaOne only, with the phone answered live in front of them and symptom screening on the Schmitt protocol. | The same territory across scheduling, referrals, waitlists, reminders and recalls, registration and prep, intake and forms, eligibility, payments and feedback management, multi-EHR, with no-code workflow building and a conversational agent. |
A page that is not trying to talk you out of Luma
Most comparison pages are written on the assumption the reader is unhappy. This one is not, because in practice the athenaOne groups who ask us about Luma Health are usually running it and are usually fine with it.
So the useful thing is not a list of reasons to leave. It is a clear statement of what the two products are actually optimized for, so a practice can tell whether it has the problem that justifies a change.
Luma Health is a patient access platform built to work across EHRs. Its published surface is wide: scheduling, referrals, waitlists, reminders and recalls, registration and prep, intake and forms, eligibility, payments, feedback management, broadcast, a conversational agent, and no-code workflow building on top of all of it.
Pretty Good AI is narrower and only works on athenaOne. That is a deliberate constraint, and it is the whole basis of the difference.
What building for one EHR buys
athenahealth exposes roughly 800 endpoints. We connect 500+ of them.
That number only means something when a workflow needs an endpoint most integrations never touch. Reading the live slot table rather than a cached copy. Writing to the order and tickler queue. Pulling the appointment type and provider group rules the practice has already spent years maintaining, instead of asking staff to rebuild those rules a second time inside a vendor tool.
A multi-EHR platform cannot go that deep everywhere, and it would be a strange use of engineering to try. The trade is real in both directions: breadth costs depth, and depth costs portability.
If you run athenaOne and expect to keep running it, depth is the side of that trade you can afford to take. If you run athenaOne and eCW because you acquired a practice last year, it is not, and Luma is built for the situation you are actually in.
The no-code question
Luma publishes no-code AI workflow creation. That is a genuine advantage and it is worth being explicit about, because it changes who has to be in the room when something needs to change.
A group with an operations lead who wants to build and adjust workflows without filing a vendor ticket will value that highly. Some of the best-run practices we see are exactly that shape.
Our model is different. Workflows get configured with the practice during the first 30 days live, against live calls and the practice’s own scheduling rules, and adjusted with us afterwards. For a practice without spare operations capacity that is the faster path. For a practice that wants to own the thing itself, it is a constraint they should weigh honestly.
Where the phone line changes the answer
The reason athenaOne practices call us while running a working access platform is almost always the same, and it is narrow.
Calls are not being answered. Volume spikes on Monday mornings and after holidays, hold times climb, and a measurable share of callers hang up before anyone picks up. The access platform is doing its job on reminders, forms and messaging, and none of that touches the queue on the phone.
That is a voice problem, and voice-first is an architectural position rather than a feature. An agent that can call athenaOne tools during the conversation can check real availability and book inside the call. An agent layered onto an asynchronous platform tends to capture the request and complete it afterwards, which works, and is a different experience for the caller who wanted to be done.
We see the outcome of that at the largest deployments: over 100,000 calls a month with roughly 60% handled start to finish by the AI, across groups with hundreds of providers. Those are aggregate figures across customers rather than one account.
A specialty group running a busy line will recognize whether this is their problem within about a week of looking at their own abandoned-call rate. If it is not their problem, this whole section is irrelevant to them and they should stop reading.
An honest picture of overlap
Both products schedule. Both message patients. Both handle intake and forms. Running both without a decision about ownership produces the same mess any two-system setup produces, which is patients hearing from the practice twice about different things in the same week.
The arrangement that works is boring: the access platform keeps the asynchronous workflows it is already configured for, the voice agent owns the phone line, and somebody writes down which system initiates outbound contact for which workflow. That decision takes an afternoon and prevents the complaint that otherwise arrives in month two.
The short version
Run more than one EHR, or want the widest access surface from a single vendor, or already have Luma working with staff who know it: keep Luma. That is the honest answer and it is the most common one.
Run athenaOne only, and have a phone line that is the actual constraint on how many patients you can see: that is the case worth a conversation, and it is a smaller claim than replacing your access platform.
Why practices pick us over Luma Health
Four parts, one platform, and each part uses the others. Most of the vendors on this site own one of these four well. The argument for us is that the same integration and the same patient memory carry all four, and that it is athenaOne only.
Patient engagement
We bring patients in and keep them close
We pick up the phone, day and night. Patients reach you by phone, text, chat or video. They book, reschedule, ask for a refill or get an answer. We call and text for you too — confirmations, recalls, and open slots to fill. Our AI remembers what a patient already told your practice, across every channel, so nobody repeats themselves.
Workflow automation
We do the staff work that piles up
A cancellation, a new referral, an overdue follow-up or a staff request starts a job. We do the steps, reach the patient if we need to, and hand the rest to your staff with everything they need. Your team sees the work in the Pretty Good AI Console or right inside athenaOne. Clinical decisions stay with your care team, always.
Referral management
We turn referrals into first visits
Referrals arrive by fax, portal and form. We track each one from intake to first visit, chase the missing information, reach the patient and book the visit. You see where every referral stands, and where the funnel leaks.
Revenue cycle
We keep revenue moving
Money leaks around every visit. We check insurance before the visit, track approvals so visits are not held up, call patients about balances, set up payment plans, and follow up on the claims your team hands us. Built to your billing team’s rules.
We only do athenaOne
One system means we go deep. We connect 500+ of the roughly 800 endpoints athenahealth exposes, and we read and write the real record — no middleware. Most vendors in this category connect ten or twelve. That depth is what lets a workflow finish instead of stopping at a handoff.
We build yours
If you can write down the rule, we can automate it. Your scheduling rules, your intake questions, your handoffs, your billing follow-up. And if another athenaOne marketplace app does a workflow you need, we can build it for you — same APIs, your rules, one vendor.
Live and measured
- 100,000+
- patient calls a month, at more than one customer
- About 60%
- of those calls handled start to finish by the AI at the largest deployments
- Hundreds
- of providers inside a single group
- 20
- specialties on our athenahealth Marketplace listing
The mix is deliberately wide: FQHCs, family practice and primary care, OB-GYN, behavioral health, orthopedics, pulmonology and sleep, gastroenterology, urology, urgent care and surgery centers among them. Different specialties break the front office in different places, and the rules that fix them are not the same rules.
Customer-reported results. Your numbers will vary by workflow, staffing, seasonality and call mix.
Month to month, no setup fees. We build your first workflow before you pay anything, then the first 30 days live are free from the day it goes live — not the day we start building.
We don’t sell AI. We build yours.
Frequently asked questions
- What does Luma Health do?
- Luma Health describes itself as operational AI for healthcare. Its published platform covers patient access and retention, referrals, scheduling, waitlists, registration and prep, intake and forms, eligibility and verification, payments, patient communication, reminders and recalls, feedback management, broadcast, analytics and a conversational agent, with no-code AI workflow creation. It works across multiple EHRs and had 39 athenahealth Marketplace connections as of 5 September 2026.
- Is Luma Health better than Pretty Good AI?
- On breadth of the patient access surface, Luma publishes more. On athenaOne integration depth and on voice, we go deeper because we only build for one EHR. Neither of those makes one product better in general. The question that decides it is whether your practice runs one EHR or several, and whether your binding constraint is the phone line or the wider access workflow.
- We already use Luma and like it. Should we switch?
- Probably not, and we would rather say so than pretend otherwise. Ripping out a working patient access platform is expensive in staff retraining and workflow rebuild, and the gain has to be large to justify it. The case for talking to us is narrower: your phone line is still the bottleneck, calls are going unanswered or to voicemail at volume, and you want that specific problem solved deeply on athenaOne. That is a different purchase from replacing your access platform.
- Can a practice run both?
- Yes, and for some groups it is the sensible arrangement, with Luma owning the asynchronous access workflows it is already configured for and a voice-first agent owning the phone line. The rule is the same as with any two-system setup: decide explicitly which system owns outbound patient contact for which workflow, or patients will hear from both.
- How do the athenahealth Marketplace numbers compare?
- They are close. As of 5 September 2026 Luma had 39 practice connections and 1 review; Pretty Good AI had 40 connections and 17 reviews, all five-star. Luma is a much larger company with a much larger overall customer base, so the marketplace figure reflects athenaOne-specific adoption rather than company size, and it is the figure an athenaOne practice should weigh.
- What should we test during an evaluation?
- Your hardest scheduling rules, not your average ones. Take the appointment types that require a specific provider, a specific room or a preceding visit, and make each vendor book them live in your own environment. Also test what happens when a caller asks for something the agent cannot do, because the handoff to a person is where most front-office automation actually fails.
Sources
Everything stated here about another vendor comes from that vendor's own public material or from the athenahealth Marketplace listing, on the date shown. Vendors change their products and their pricing; if something below is out of date, email contact@prettygoodai.com and we will correct it.
- Luma Health platform overview (accessed 2026-09-07)
- Luma Health — athenahealth Marketplace listing (accessed 2026-09-07)
- Pretty Good AI — athenahealth Marketplace listing (accessed 2026-09-07)
See it against your own athenaOne data
The honest way to compare is on your own call volume, your own schedule and your own payer mix. Book a working session and we will walk your numbers.