Pretty Good AI vs Rivia Health

Two products that meet on one phone call

Rivia Health is a patient payments company. It takes the balance a patient owes after insurance and works it: a payment link that opens without an app or a login, outreach over text and email tuned to how that patient has behaved before, a workspace where staff can see the whole revenue picture, and an AI agent that will answer a billing question or take a payment at eleven at night.

That is a real business problem and Rivia has a real athenaOne track record on it. 204 practice connections and 91 marketplace reviews at a 4.87 average is not a new listing finding its feet.

Pretty Good AI collects patient payments too. We take them on the Pretty Good AI web scheduler, and we send secure payment links through your practice’s existing payment portal wherever that is the rail your billing team wants, with balances, documented payment plans and follow-up running to your billing team’s rules. The difference is what surrounds it: the balance conversation sits inside the same front office that answers the phone, fills the schedule, chases referrals and handles forms, so a patient asking about a bill is talking to the system that also knows their next appointment.

So the overlap is narrow and specific. It is the outbound patient contact, and it is the after-hours call.

Where the collision actually happens

The failure mode is not a technical one. Both products integrate, and whether they interfere is a configuration question rather than an inevitability.

The failure mode is a patient who gets a text on Monday asking for $180, a call on Tuesday about an appointment they need to move, and a second text on Wednesday about the same $180, from what is supposed to be one practice.

Practices discover this in the second month, not the first, and usually from a patient complaint rather than a dashboard.

The following is an illustrative workflow, not a customer story. A multi-site orthopedic group runs a balance outreach vendor and a scheduling automation at once, both configured to be helpful and neither aware of the other. The patients who complain are the ones with an outstanding balance and a rescheduled visit, a small group and the most valuable one to keep happy.

The workable resolution is not ripping anything out. It is a written rule about which system owns which outbound workflow, agreed before both go live. Accounts under active payment-plan negotiation stay with a person who can agree terms, because that is not an automation’s decision to make.

The after-hours call is where the products differ

Rivia built a voice agent to capture payment after hours. On that specific call it is purpose-built and bilingual, and it is doing the job it was designed for.

The question is what fraction of after-hours calls are that call.

Most after-hours volume at a typical practice is not billing. It is people trying to move an appointment, asking whether they need to fast, chasing a refill, or asking whether they should come in. Your own phone logs will show the mix at your practice, which is the number this decision should be made on.

That is an architectural difference rather than a quality one. A voice agent scoped to payments will handle a payment call well and hand off everything else. A front-office agent handles the mix, and takes the payment as one of the things it can do, because the scheduling API and the billing context sit behind the same integration.

Neither is the right answer in the abstract. It depends on which calls your practice is actually getting at 9pm, and you already have that data in your phone logs.

Scale, honestly stated

On payments specifically, Rivia has more athenaOne practices than we do: 204 connections against our 40 as of September 2026, and any comparison that skated past that would be dishonest.

The numbers measure different things. Rivia’s says more practices have bought their payments product. Ours is a younger, athenaOne-only listing. A practice should weigh the one that matches the problem it has.

How to decide

Ask what is actually broken.

If the answer is that too much patient responsibility is aging out to write-off, and the phone and the schedule are fine, a payments specialist is the matching scope. That is a clean problem with a clean product attached to it, and Rivia publishes an A/R assessment that will tell you the size of the gap before you commit to anything.

If the answer is that nobody is answering the phone, the schedule has holes in it, referrals are sitting in a queue, and also the balances are aging, then you have a front-office capacity problem that happens to show up in the collections number. Buying a payments tool will improve the collections number and leave the cause in place.

And if you already run Rivia and it is working, the useful question is not whether to replace it. It is whether anyone has decided, explicitly and in writing, which system owns which outbound workflow. Most practices have not, and that decision is free.