Blog · JUN 19, 2026 · 3 min read
What We Learned Bundling PatientVoice Into Existing Connex Accounts
Eleven hospitals in, bundling was the easy part. Getting language and ownership right per patient was the real lesson.
Six weeks after launch, PatientVoice is live in eleven hospitals, all of them existing Connex accounts. We expected the bundling itself to be the easy part, since there was no new contract to sign and no new system to install. We were partly right, and partly wrong, and the wrong part taught us more.
What went smoothly
Every hospital that turned PatientVoice on did so within the same week they asked for it. Because the toggle sits inside their existing Connex account, there was no procurement delay and no new IT security review. Three hospital administrators told us this was the fastest new capability they had added to any system in the past year.
What did not
The friction we did not anticipate was language configuration, not integration. Hospitals assumed the language setting was one choice per hospital. In practice, a single hospital in Hyderabad serves patients who read Telugu, Urdu, and English in roughly equal numbers, and the discharge language needed to be set per patient, not per hospital account. We shipped a fix within the first two weeks, but it should have been in the original design.
We also underestimated how many hospital staff wanted the missed-follow-up flag to route to a specific person rather than a general queue. In four of the eleven hospitals, one nurse or coordinator effectively owns follow-up calls, and they wanted flags addressed to them by name.
The numbers so far
- •Across the eleven hospitals, roughly one in five patients who would previously have gone silent after discharge is now flagged and called back before their follow-up date lapses
- •Message read rates on WhatsApp are running above 90 percent, well above what any hospital reported from SMS reminders previously
- •Average setup time per hospital is four working days, almost entirely spent on language mapping, not technical integration
None of this required us to add scope. It required us to get the narrow thing right, which turned out to mean treating language and ownership as per-patient and per-person details, not hospital-wide settings. That is a small correction, but it is the kind that only shows up once real hospitals are using the product, not before.