What does Rivia Health do?

Rivia Health is patient payment software for specialty practices. It covers mobile-first payments that need no app or login, automated behavior-tailored outreach over text and email, a real-time billing workspace for staff, a 24/7 AI chat agent for billing questions, an AI voice agent that captures payment after hours, and integrated payment processing. It had 204 practice connections on the athenahealth Marketplace as of 5 September 2026.

Is Rivia Health a competitor to Pretty Good AI?

Partly. On patient balance outreach and the after-hours billing call the two products do the same job, and Rivia has a deeper payments feature set there. Across the rest of the front office they are not comparable, because Rivia does not schedule visits, work referrals or answer the general practice line. Most practices meet this as an overlap question rather than a bake-off.

We already run Rivia. Does Pretty Good AI replace it?

Not automatically, and often it should not. If Rivia is capturing balances well and the payment processing is already integrated, the sane arrangement is to leave the balance workflow where it is and let the platform own the phone line, the schedule and the referral work. What you must not do is let both systems run outbound patient contact without agreeing which one owns which conversation.

What is the double-messaging problem?

Two automated systems contacting the same patient in the same week, one about a balance and one about an appointment, with neither aware of the other. Patients read it as one disorganized practice. The fix is not technical, it is deciding up front which system owns outbound contact for which workflow and configuring both to respect that line.

Which one handles the after-hours billing call better?

Rivia built a bilingual voice agent specifically to capture payment after hours, so on that single call it is purpose-built. The difference shows up when the caller wants something else, because most people who ring a practice after hours are not calling to pay. If the same call needs to become a reschedule or a refill request, a payments-scoped agent has to hand off and a front-office platform does not.

Pretty Good AI vs Rivia Health

← All comparisons

Rivia Health chases the patient balance. Pretty Good AI runs the whole athenaOne front office, billing calls included. Where they overlap, where they collide, and when to run both.

Last reviewed September 7, 2026 7 min read

The short answer

Rivia Health is a patient payment platform for specialty practices. It runs digital payments, automated balance outreach over text and email, a billing workspace for staff, an AI chat agent for billing questions, and a bilingual AI voice agent that captures payment after hours on the practice existing phone line. It had 204 practice connections and 91 reviews at a 4.87 average on the athenahealth Marketplace as of 5 September 2026. Pretty Good AI is an athenaOne-native front-office platform where the balance conversation is one workflow beside scheduling, referrals and the phone line itself. The two products genuinely overlap on outbound patient contact, so the real question for a practice already running Rivia is not which to buy but who owns the patient conversation, because both dialing the same patient in the same week is the failure mode.

When Rivia Health is the better fit: Patient collections is the problem you are actually solving, your phone line and scheduling are already handled by something you are happy with, and you want a team whose entire product is the patient balance. Rivia publishes an ROI calculator and a free A/R assessment, is concentrated in orthopedics and womens health, and integrates payment processing directly, which is a narrower and often faster purchase than a platform. If your write-offs are the number on the board this quarter, buy the specialist.

Pretty Good AI vs Rivia Health, side by side

Feature-by-feature comparison of Pretty Good AI and Rivia Health
Dimension	Pretty Good AI	Rivia Health
Core job	The front office end to end: inbound and outbound voice, scheduling and capacity, referrals and orders, forms and intake, and revenue workflows including balance follow-up.	The patient balance end to end: digital payments, outreach, billing support and payment processing, with staff tooling and analytics around it.
Voice architecture	Built voice-first and extended into text and asynchronous channels. The voice agent calls athenaOne tools mid-conversation rather than handing off to a workflow after the call.	A bilingual AI voice agent scoped to capturing payment after hours on the existing phone line, layered onto a payments and workflow platform.
EHR scope	athenaOne only. 500+ athenaOne APIs connected out of roughly 800 endpoints athenahealth exposes.	Listed on the athenahealth Marketplace and publishes an implementation path that connects to the EHR without burdening IT. Not positioned as athenaOne-exclusive.
athenahealth Marketplace record	40 practice connections, 17 reviews, all five-star, listed September 2025.	204 practice connections, 91 reviews at a 4.87 average. A substantially larger and longer athenaOne track record than ours on payments.
Where a patient balance call goes next	The same agent can take the payment, answer why the balance exists, and book the follow-up visit in one call, because scheduling and billing sit behind one integration.	Handles the payment and the billing question. Booking the next visit belongs to whatever runs the schedule.
Specialty focus	20 specialties on the marketplace listing, including FQHC, family practice, neurology, pain management and ambulatory surgery.	Publishes dedicated solutions for orthopedics, womens health, and ambulatory and other specialties.
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. Publishes an ROI calculator and a free A/R assessment instead.
Running both	Workable if outbound ownership is split deliberately by workflow, so one system owns the balance conversation and the other owns everything else.	Workable on the same terms. The risk is not technical, it is two systems contacting the same patient in the same week about different things.
The balance conversation today	Balances surface before the visit is booked so the money conversation happens first, inbound billing calls are answered and routed, payment is taken by secure link during the call, and the family navigator shows one household balance across linked charts.	Digital payments, automated balance outreach by text and email, a staff billing workspace, an AI chat agent for billing questions, and a bilingual voice agent that captures payment after hours.

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 is not a payments company. It runs the front office of an athenaOne practice, and the balance conversation is one of the things the front office does, alongside answering the phone, filling the schedule, chasing referrals and handling forms.

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 cleanly and neither will break the other.

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.

A multi-site orthopedic group we work with hit exactly this shape. The balance outreach vendor and the scheduling automation were both configured to be helpful and neither had any idea the other existed. The patients who complained were the ones with an outstanding balance and a rescheduled visit, which is a small group and the most valuable one to keep happy.

The resolution was not ripping anything out. It was a rule: the payments system owns every outbound contact about money, the front-office platform owns everything else, and neither one initiates in a week where the other has an open thread with that patient. Staff kept a manual override for the accounts under active payment-plan negotiation, because those calls need a person who can agree terms and nobody wanted an automation near that decision.

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.

In our own deployments most of the after-hours volume 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. Roughly 13% of appointments across our customers get booked outside office hours, which is the clearest signal that the after-hours line is mostly an access channel rather than a collections one.

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 is not close, and any comparison that skated past that would be dishonest.

What we can say about our own footprint is that the largest deployments run over 100,000 calls a month, with about 60% of those handled start to finish by the AI, across groups with hundreds of providers and 20 specialties on our marketplace listing. Those are aggregate figures across customers, not a single reference account.

Both numbers are true and they measure different things. Rivia’s number says more practices have bought their payments product. Ours says the calls we do handle are handled at volume and mostly without a person. 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 ageing out to write-off, and the phone and the schedule are fine, buy the payments specialist. 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 ageing, 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 is allowed to contact a patient in a given week. Most practices have not, and that decision is free.

Why practices pick us over Rivia 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 Rivia Health do?: Rivia Health is patient payment software for specialty practices. It covers mobile-first payments that need no app or login, automated behavior-tailored outreach over text and email, a real-time billing workspace for staff, a 24/7 AI chat agent for billing questions, an AI voice agent that captures payment after hours, and integrated payment processing. It had 204 practice connections on the athenahealth Marketplace as of 5 September 2026.
Is Rivia Health a competitor to Pretty Good AI?: Partly. On patient balance outreach and the after-hours billing call the two products do the same job, and Rivia has a deeper payments feature set there. Across the rest of the front office they are not comparable, because Rivia does not schedule visits, work referrals or answer the general practice line. Most practices meet this as an overlap question rather than a bake-off.
We already run Rivia. Does Pretty Good AI replace it?: Not automatically, and often it should not. If Rivia is capturing balances well and the payment processing is already integrated, the sane arrangement is to leave the balance workflow where it is and let the platform own the phone line, the schedule and the referral work. What you must not do is let both systems run outbound patient contact without agreeing which one owns which conversation.
What is the double-messaging problem?: Two automated systems contacting the same patient in the same week, one about a balance and one about an appointment, with neither aware of the other. Patients read it as one disorganized practice. The fix is not technical, it is deciding up front which system owns outbound contact for which workflow and configuring both to respect that line.
Which one handles the after-hours billing call better?: Rivia built a bilingual voice agent specifically to capture payment after hours, so on that single call it is purpose-built. The difference shows up when the caller wants something else, because most people who ring a practice after hours are not calling to pay. If the same call needs to become a reschedule or a refill request, a payments-scoped agent has to hand off and a front-office platform does not.

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.

Rivia Health company site (accessed 2026-09-07)
Rivia 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.

Book a demo How our pricing works