Ellipsis Health Buys Kouper to Let Sage Book EHR Visits

Ellipsis Health acquired Kouper Health so its Sage voice agent can book appointments directly in the host EHR. Customers of either brand should settle who controls scheduling writes, how data moves between the products and their exit terms.

By Rajesh Beri·November 7, 2026·9 min read
Share:
A hospital care-management desk with a telephone headset resting beside a monitor showing a blank appointment calendar grid, a printed discharge folder lying open next to the keyboard.

Illustration generated using AI

If you run Ellipsis Health's Sage or any Kouper agent, the November 5 deal means an AI voice agent is now designed to write appointments into your EHR without a coordinator in the loop. Before you let it, decide who approves those writes, which scheduling rules the agent may touch, and what your contract says now that one of your vendors has a new owner. Terms were not disclosed, and both brands keep running separately for now, so the paperwork is yours to get right.

Ellipsis Health announced on November 5, 2026 that it had acquired Kouper Health. The stated purpose is to give Sage, Ellipsis's voice AI care manager, Kouper's native EHR integrations and longitudinal patient maps so it can follow a patient across care transitions. According to HIT Consultant's report on the deal, when Sage identifies risk or an access need, the combined platform could match the patient with an in-network provider and book the appointment directly in the host EHR, with Epic, Oracle Health and athenahealth named as examples. No price was disclosed.

What Ellipsis Bought, and What Sage Did Before

Ellipsis bought the piece Sage was missing: a two-way connection into the hospital's record system. Sage already talked to patients. Kouper already sat on top of the EHR.

Sage calls patients for care-management enrollment, PHQ-9 and GAD-7 assessments, medication adherence checks and post-discharge follow-up, per HIT Consultant. It runs on what Ellipsis calls a patented vocal biomarker engine trained on more than 3 million clinically labeled patient interactions, which analyzes speech acoustics and language to flag distress. Ellipsis launched Sage alongside a $45 million Series A in June 2025, led by Salesforce, Khosla Ventures and CVS Health Ventures, and said then that Sage integrates with Salesforce Health Cloud.

Kouper came out of stealth in May 2025 with $10 million from General Catalyst, 25Madison and CVS Health Ventures, pitching AI infrastructure to automate scheduling and capture data as patients move between the emergency department, inpatient care, urgent care and home. It claimed deployments in as little as four weeks. Its current site sells three agents: PRIMUS for patient access (scheduling, intake, insurance verification, missed-call recovery), ARCHIE for inpatient and post-acute navigation, and CURA for care management. Unite.ai lists its named customers as LifePoint, Henry Ford Health's Mosaic Clinically Integrated Network and Ascension Saint Thomas, which was piloting at its Nashville Midtown site.

CVS Health Ventures invested in both companies before the deal, Unite.ai notes. So the deal is partly a consolidation inside one investor's portfolio.


Why an Agent That Writes to the EHR Is a Different Risk

An agent that reads your EHR can give a patient wrong information. An agent that writes to it can put a wrong appointment on a clinician's schedule, and that error lands in the system of record.

Today, a care-management call that ends with "you need a follow-up" hands off to a human scheduler. The deal is built to remove that handoff. A coordinator who books a visit applies local rules nobody wrote down: which cardiologist takes new Medicaid patients, which slots are held for post-discharge, which visit types need a referral on file. An agent books from whatever rules your EHR build exposes.

That build is not uniform across the three vendors. A September 2026 technical guide to FHIR scheduling from an integration firm describes three different paths. Epic books through the older STU3 Appointment.$book operation, and its $find slot search "requires pre-coordination with the healthcare organization," so your team has to build the scheduling rules first. Oracle Health supports a standard R4 create on Appointment. athenahealth's R4 interface is read and search only, so booking goes through the proprietary athenaOne API. Treat that guide as one integrator's reading, not vendor documentation, but the point holds: "books in Epic, Oracle Health or athenahealth" means three integration projects, and on Epic your own analysts decide what the agent can see.

Epic is also building toward the same job natively. It has shown a conversational AI tool that texts patients about due follow-up visits, offers slots by text and confirms through MyChart, and said in mid-2025 that some early-adopter providers had begun using it. If you are an Epic shop, you will be asked why you need a third party writing to your schedule when the EHR vendor offers its own agent. Ellipsis's answer is the clinical layer: risk screening and behavioral health assessment before the booking. That is a reasonable answer, and you should make the vendor show it in your data.

What the Outcome Claims Do and Don't Prove

Every outcome number in this deal is a vendor's own claim, and two of them don't match.

Unite.ai reports Ellipsis claiming six times faster care-management enrollment, a 60% reduction in administrative tasks, task-completion rates up to 66% higher than human agents and "up to sevenfold ROI." Ellipsis's own homepage lists 60% fewer administrative tasks, 6x faster enrollment and a 4x return on investment. Kouper's 2025 launch claimed a more than 50% rise in patient engagement and a more than 60% improvement in securing post-discharge and ED follow-up appointments from its first health-system partners. Kouper's current site shows its outcome metrics as "0%" placeholders.

None of these come with a baseline, a sample size or a control group, so price the combined product on results from your own pilot. The sandbox gap we covered in August applies directly: fewer than half of hospitals have a place to test vendor AI on their own data before it touches patients, and a scheduling agent is exactly the kind of tool that behaves differently against your build than against a demo instance.

The steel-man for moving fast is real. Discharge follow-up is a known leak. Kouper's own launch pitch cited an estimated $53 billion a year in avoidable US readmission costs, and a call that ends with a booked visit instead of a voicemail is the outcome care managers want. What needs settling is the set of controls around the write.


The Compliance Line Runs Through the Middle of Sage's Workflow

Sage's workflow straddles a line some state laws draw between administrative and clinical messages, so one call can fall on both sides.

California's AB 3030, in force since January 1, 2025, requires providers that use generative AI for patient communications about clinical information to disclose it (for audio, at the start and end of the interaction) and to tell patients how to reach a human, per Arent Fox Schiff's summary. Administrative matters such as appointment scheduling are excluded. A message that a licensed clinician has read and reviewed is exempt.

A Sage call that runs a PHQ-9 and then books a behavioral health visit is clinical in its first half and administrative in its second. Your compliance team should decide which rule covers the whole call before the agent starts writing appointments. If you operate in several states, run the same analysis for each one.

Change of control raises its own paper. Kouper's team is joining Ellipsis, and Unite.ai reports that both companies will keep serving existing customers under their own brands while building a combined roadmap, with new health-system offerings expected in the months ahead. Your business associate agreement names one entity. Data flowing between the two products after integration is a new use your BAA may not cover. We walked through the same pattern on a radiology deal in Sopris's purchase of Blackford Analysis.

What to Do Before the Combined Product Ships

Health systems and plans on either product should settle three things now: who controls scheduling writes, how data moves between the two brands, and how they can leave.

This Week:

  1. Ask your Ellipsis or Kouper account team, in writing, which legal entity now holds your contract and BAA, and whether any patient data will flow between Sage and Kouper systems under the current agreement.
  2. Pull the list of EHR write permissions your Kouper integration holds today. On Epic, that means the scheduling build and the service account behind it. If no one can produce the list in a day, that is your first finding.
  3. Name one owner for agent-initiated appointments: the access center, care management or IT. Agent bookings with no owner tend to go unreviewed.

This Month:

  1. Run a reconciliation pilot. For two weeks, have the agent propose bookings that a scheduler approves, and count the ones the scheduler changes. That rate tells you whether to turn on direct writes.
  2. Get the vendor's outcome claims restated on your population: enrollment rate, completed follow-ups and no-shows for agent-booked visits against human-booked ones.
  3. Have compliance map each Sage call type against AB 3030 and any other state rule you operate under, and decide where the disclosure and human-contact script go.

Before Renewal:

  1. Add a clause requiring notice before any combined-product change that alters what the agent can write to your EHR.
  2. Fix data export and deletion terms for call recordings, transcripts and vocal biomarker outputs, with a timeline and format.
  3. If you are an Epic customer, price Epic's native scheduling agent against the combined Ellipsis product for the administrative half of the workflow, so you know what you are paying for the clinical half.

If you are weighing voice agents more broadly, our per-minute pricing teardown and the containment benchmark across eleven stacks show how far a demo number can drift from a production one.


The Bigger Picture

Healthcare AI is moving from reading the record to writing into it, and the buying decision moves with it.

Ambient scribes went through this first. They draft notes, and a clinician signs before anything enters the chart; our ambient scribe comparison found the time savings smaller than vendors claimed even with that human step in place. A scheduling agent that books directly removes the signature. In contact centers, the same consolidation is playing out with larger checks, as in Salesforce's planned purchase of Cresta. Ellipsis and Kouper are a smaller version of that bet aimed at care management.

The vendors' combined roadmap will decide what the product does next year. Your scheduling build and your contract decide what it can do inside your system. Get the write permissions list from IT this week.

Continue Reading

Share:

Frequently Asked Questions

Did Ellipsis Health acquire Kouper Health?

Yes. Ellipsis Health announced on November 5, 2026 that it had acquired Kouper Health. Terms were not disclosed. Kouper's team is joining Ellipsis, and both companies will keep serving existing customers under their own brands while they build a combined roadmap.

What does the Kouper acquisition add to Ellipsis's Sage?

Kouper brings native EHR integrations and longitudinal patient maps. The stated goal is for Sage, Ellipsis's voice AI care manager, to match patients with in-network providers and book appointments directly in the host EHR, such as Epic, Oracle Health or athenahealth, without a coordinator handoff.

Can an AI agent book appointments in Epic, Oracle Health and athenahealth the same way?

No. Per one integrator's September 2026 guide, Epic books through an STU3 operation that requires the health system to build scheduling rules first, Oracle Health supports a standard R4 appointment create, and athenahealth's R4 interface is read-only, so booking uses its proprietary athenaOne API.

Does California's AB 3030 apply to AI voice agents that schedule appointments?

AB 3030 requires a generative AI disclosure and human-contact instructions for patient communications about clinical information, but excludes administrative matters such as appointment scheduling. A call that runs a clinical assessment and then books a visit spans both, so compliance teams should decide how to treat the whole call.

What should Ellipsis or Kouper customers do after the acquisition?

Confirm in writing which entity holds your contract and BAA, list the EHR write permissions the integration holds, assign one owner for agent-booked appointments, pilot with human approval before direct writes, and add notice, data export and deletion terms before renewal.

Newsletter

More on Industry Solutions, every Sunday

The week's enterprise AI news, Industry Solutions included, in one Sunday email.

Weekly, free. Unsubscribe any time. Privacy

Latest Articles

View All →