Case studies
A look at how healthcare organizations put Flexbone AI voice and browser agents to work across revenue cycle and patient-access operations. Each study describes what the team was running by hand, what we deployed into their existing tools, and what changed once the agents took over the repetitive work.
Customer stories
Real deployments, described plainly. We name the numbers we can stand behind and skip the ones we cannot.
What do these deployments have in common?
The specifics differ by organization, but the pattern is consistent. Flexbone puts voice and browser agents into the tools a team already uses, then hands the repetitive work to the agents so staff can spend their time on the tasks that need a person.
Most of the work sits in revenue cycle and patient access, where the same steps repeat all day. The common workflow types are:
- Eligibility verification. Running 270/271 eligibility transactions and reading coverage out of portals such as Availity, including Medicare and Medicaid plans.
- Prior authorization. Assembling requests with the right CPT and ICD-10 codes, submitting them, and tracking status in the payer portal.
- Denials follow-up. Working denied and pending claims through the same screens staff use today.
- Patient outreach and scheduling. Placing and answering calls for reminders and confirmations, and booking or rescheduling appointments.
Voice agents place and answer the phone calls. Browser agents operate inside the web tools and portals, under HIPAA-aligned controls. Nothing gets ripped out and replaced, which is why staff do not have to learn a new system to get the benefit.
How should you read the metrics in these studies?
Each study reports only the figures we can support for that specific engagement. When we write that Nav Central made 300+ employees AI-powered and eliminated 1,000+ hours per month of manual work, those are the measured outcomes of that deployment, not a projection for yours.
Results depend on the volume and mix of work a team runs, which systems they use, and how much of it is repetitive. That is why every engagement starts by mapping the actual workflows before anything goes live, and why we scope the numbers to the deployment they came from.
Questions about our case studies
A Flexbone case study describes a real deployment: what a healthcare organization was running by hand, what voice and browser agents we put into their existing tools, and what changed once the agents took over the repetitive work. We report the numbers we can stand behind and leave out the ones we cannot.
Deployments commonly cover revenue cycle and patient-access work: eligibility verification with 270/271 transactions, prior authorization with the right CPT and ICD-10 codes, denials follow-up, patient outreach calls, and scheduling. Browser agents operate inside portals such as Availity and payer sites for Medicare and Medicaid plans, under HIPAA-aligned controls.
Talk to our team. We start by mapping the workflows your staff runs by hand, then scope where voice and browser agents fit inside the tools you already use. Case studies come out of real deployments, not pilots on paper.
See what this looks like on your workflows
If your team runs eligibility checks, prior authorization, denials, patient outreach, or scheduling by hand, we can map where agents fit and what they would take off your staff's plate.