Pretty Good AI vs Confido Health

Breadth versus depth, stated plainly

Confido Health’s pitch is that one AI voice layer should work everywhere, published as 40+ EHRs, 20+ languages, and more than a thousand clinic sites. That is a genuine strategy and it serves organizations a single-EHR vendor cannot serve at all.

Ours is that the interesting work in a practice does not happen on the call. It happens after it, inside the record system.

Both are defensible. They are not the same product and they should not be evaluated as though they are.

What each vendor is optimizing

An athenaOne-only platform can build deeper in that one system. With production access to 820+ athenaOne APIs, the product can pick up a referral that arrived without imaging, chase what is missing, and put the result back into the order queue rather than describing the problem to a human who then does it. We build workflows around athenaOne’s records and the practice’s rules, connecting the steps needed to move the work forward and making exceptions visible to the team.

The marketplace record as of 5 September 2026

• Confido Health: listed 10 June 2026, 5 practice connections, no reviews published, 6 specialties, requires athenaCollector and athenaClinicals.
• Pretty Good AI: 45 practice connections, 22 ratings, all five-star as of October 2026. athenahealth Marketplace partner since 2025.

Confido’s listing is three months old. Read the gap as time on the board, not as a quality judgment. What it does mean is that an athenaOne buyer evaluating today has a much thinner athenaOne-specific evidence base to inspect on their side.

Scope to confirm for your practice

athenaOne depth. We hold production access to 820+ athenaOne APIs, read and write, with no middleware in between. Ask any vendor on your shortlist which athenaOne workflows it has already built, which it would build for you, and how long the second list takes. That question separates a connector from an operator faster than a feature grid does.

Language coverage. 20+ published languages is broader than this category typically ships. If a meaningful share of your inbound calls arrive in a language your front desk cannot handle, weight that heavily and test both vendors with real callers rather than a demo script.

Scale across small sites. Their published footprint is many clinic sites rather than a few large groups. If you are a network of small practices, that operating experience is relevant.

Where the athenaOne-only bet wins

Work completion. Answering the call is now table stakes across the whole category. The differences show up in what happens next: the referral that needs chasing, the eligibility check that failed and will become a denial in six weeks, the balance nobody has worked, the slot that opened at 4pm and stayed empty.

Evidence a buyer can verify. Practice connections and reviews on athenahealth’s own board, not vendor-supplied references.

Pricing you can read before the call. Platform fee per location, per-provider modules, voice priced per call, month to month, no setup or implementation fee, first 30 days live.

How to decide in one meeting

Put both vendors on the same question and time the answers:

1. Name the athenaOne records you write to. Not just the workflows, the records.
2. Take a live call from us in the language our patients actually use.
3. Show us where a failed automation surfaces and who owns it.
4. Send the current SOC 2 report and the standard BAA.
5. Put the price at our call volume in writing, month to month.

If you run several EHRs, question one is less important than question two. If you are athenaOne end to end, question one is the whole evaluation.