Notable

Agents performing workflows end to end are the product, and Flow Builder sells the capability to author more of them. There is no non AI version of the offering.

Agents are described as handling workflows autonomously and as virtual team members performing end to end work, including prior authorization submission and denial management, which are consequential actions with financial and access implications. No escalation criteria, confidence thresholds, human review checkpoints, or exception handling policy were retrieved. This is the same pattern flagged for Waystar and Elation in this index: strong autonomy claim, thin oversight disclosure, in workflows where errors cost patients access or money.

Named health system deployments at Intermountain, Trinity Health, and MUSC, with published customer results that state both the metric and the site: 64 percent voice containment and roughly $360,000 in annual savings at one system, registration reduced to 30 seconds at another, and an insurance FAQ voice assistant at a stated $4 saving per call. Containment rate is the correct metric for voice deflection and it is rarely published. Held back from A because the figures are customer stories curated by the vendor rather than independently audited.

Among the most pragmatic integration positions in the index, and the honesty is the point: the company states it uses whichever method actually reaches the field, including APIs, RPA, and HL7, across Epic, Oracle Health, MEDITECH, athenahealth, and payer portals, reading and writing both structured and unstructured data. Acknowledging RPA rather than claiming pure API integration is a more truthful description of how healthcare data access actually works, and buyers should note RPA based paths are more brittle to vendor interface changes than certified APIs.

No public pricing. Contact the vendor. Enterprise agreements with health systems; no published rate card. Buyers evaluating this against a point solution should establish whether pricing is per agent, per workflow, or platform level, since the platform model is only economical if multiple workflows are deployed.

Broad but clearly enumerated by function rather than vaguely claimed: patient access, revenue cycle, and care operations, with named workflows under each. The company makes no clinical decision support claims, which is the correct scope for operational automation.