The Problem Hospitals Kept Raising After Connex

Connex was built to solve one problem: getting doctors and pharma field teams into a room, or onto a call, without the scheduling back-and-forth that ate up half of every rep's week. It has been live in pilot hospitals for several months now, and it does that job well.

What we did not expect was how many of those same hospital administrators would come back to us with a different question, unrelated to scheduling meetings at all.

The pattern

Across a dozen or so hospital conversations, the same complaint kept surfacing. A patient gets discharged after a procedure. They are told to come back in ten days, take a medication on schedule, or watch for specific symptoms. Then nothing happens until the follow-up appointment, if they show up at all.

One hospital administrator told us their orthopedic department was losing track of nearly a third of post-surgical patients between discharge and the two-week check-in. Not because the patients did not care, but because nobody was reminding them, in a language and format they would actually read.

We heard versions of this from five different hospitals in six weeks. None of them asked us to build a patient portal or an app. They asked, almost verbatim, whether Connex could just nudge their patients too.

Why we listened

We are wary of scope creep. FieldVoice took years to get right for pharma reps, and Connex is still earning its place with hospitals and pharma teams. Adding a half-built third thing because it sounded plausible would have been the wrong instinct.

But this was not a hypothetical ask. It was the same operational gap, described independently, by hospitals who were already trusting us with their doctor engagement workflow. That is a different kind of signal than a feature request pulled from a roadmap brainstorm.

So we started asking a narrower question: not whether we should build a patient engagement platform, but what the smallest thing is that closes this specific gap for hospitals already on Connex. That question is what eventually became PatientVoice, and we will walk through how we answered it in the posts that follow.