What an Online Consultation Team Learned About Patient Expectations

Health Tech

Picture a small patient-support team at an online consultation service, the kind where people book a video visit with a doctor from their living room. This team is made up for the telling, though anybody who has stared at a spinning wheel before a video call will recognise their world. Their lead, Nandini, had a problem that did not show up in any dashboard: patients were happy with the care and unhappy with the experience around it. Her team’s journey toward fixing it is a story about online consultation expectations, and about how far a few honest lines of preparation can go. Nothing here is medical guidance; it is entirely about logistics and communication.

The complaint that kept arriving

Every Monday, Nandini’s team read the feedback messages. The words were different each week, but the shape was the same. “I thought the doctor would call exactly at the booked time.” “Nobody told me I needed my previous reports ready.” “I did not know the visit would be this short.” “I assumed the prescription would arrive immediately.” None of these were complaints about the doctors. They were all complaints about gaps between what the patient pictured and what happened.

Nandini found this oddly reassuring. If the issue were poor care, the fix would be hard. If the issue was unspoken expectations, the fix might fit on a single page.

Asking the team what patients are never told

She gathered the three people who spoke to patients daily and asked a simple question: “What do patients not know before their first visit that we all take for granted?” Within ten minutes the whiteboard was full. Patients did not know how early to log in, how long the doctor typically has, what paperwork to keep within reach, what happens if the connection drops, or who to contact if something goes wrong on the day. Nobody had ever listed these, because to the team they felt obvious.

This is a common pattern in service work. The people closest to the process stop seeing it. What feels obvious to staff is invisible to a newcomer.

Turning the whiteboard into a short note

The team grouped the answers into five headings and wrote two or three plain sentences under each one.

  • Before the visit: log in a few minutes early, check your internet and keep any earlier reports or medicine lists within reach.
  • The timing: the doctor may start a little before or after the slot, and the visit has a set length, which is stated up front.
  • If something fails: here is the number to ring if the video drops, and here is what the team will do to reconnect you.
  • What the visit does and does not cover: it is a conversation, and the doctor will explain in the call what follow-up, if any, is appropriate.
  • Afterwards: you will receive a summary by a stated time, and here is how to ask a follow-up question about it.

They kept the language warm and short. They deliberately avoided any statement about conditions or treatments, because that belongs to the doctors and not to a logistics note.

The first test: a confused relative

Before sending the note, Nandini read it to her uncle, who rarely uses video calls. He stopped her halfway. “What does ‘stable connection’ mean?” he asked. The team rewrote it as “a place where your phone or laptop shows strong signal”. Small changes like that matter, because a note written by experts can be unintentionally full of jargon. The best test is a person who has never used the service.

What happened after the note went out

The note was sent with every booking confirmation and shown again on the waiting screen. The change was gradual, not dramatic. Weekly messages about unexpected waiting dropped, and the feedback tone shifted from “I was not told” to “thanks for letting me know”. Doctors reported that patients arrived with reports at hand, which made the available minutes more useful. The support team had fewer panicked calls in the first five minutes of visits.

For readers who want to see how this service thinks about patient-facing explanations, the write-up on helping ear, nose and throat patients make sense of a remote appointment shows the same instinct for plain description. And if a reader is unsure whether a symptom calls for a visit at all, the site’s overview on spotting everyday breathing complaints and deciding when to get help is a sensible place to begin, though it is general information and never a substitute for speaking to a professional.

Handling the people who still arrived confused

The note did not reach everyone. Some patients skipped the confirmation message, and others read it hurriedly on a busy day. Nandini made peace with that and asked the team to treat confusion as normal rather than as a failure by the patient. When someone phoned in a flap, the first thing the agent did was restate the key points calmly: when the call will start, what to have ready, and what to do if the picture freezes. Repeating the note aloud took under a minute and settled most callers, which suggested that the content was right even when delivery missed.

The team also added a gentle reminder message a few hours before each visit, containing just three lines. A reminder is a second chance for an expectation to land, and it costs almost nothing to send.

The slip that taught them the most

A few weeks later, the team made a mistake. A software update changed the login steps, and the note became out of date overnight. Patients followed the old instructions and got stuck. Nandini’s response was to treat it as proof of how much people rely on the note. She added a line at the bottom stating the date it was last checked and set a fortnightly reminder to review it. An expectation that was accurate when written but stale when read is worse than none, so currency became part of the routine.

What the doctors noticed

The clinicians never saw the note itself, but they noticed its effect. Visits began with less apology and less scrambling. Patients opened the call already knowing roughly how long they had, so they came with their top question ready instead of circling it. One doctor remarked that the first minute of each call, once spent on sorting out basics, now went to the conversation itself. Nandini passed the comment around the team on a printed slip, because it showed in the plainest way that a logistics note can improve the human part of the service.

Lessons from the story

Several lessons stand out. First, the gap between expectation and experience is often wider than the gap between good and bad service. Second, the people who run a process are the least able to see what newcomers miss, so ask newcomers. Third, a short note beats a long policy; nobody reads the policy. Fourth, a note is a promise that needs maintaining. And fifth, a good note asks something of the reader, such as logging in early or having reports to hand, and says why.

Beyond the consultation room

The same approach works for any experience that people must attend at a certain time and place. When someone buys a ticket to an evening show or a community fair, they too picture how it will go. A directory such as BhopalOrbit, which gathers Bhopal’s events and venues and lets organisers sell tickets to the people who find them, shows how much easier it is for guests to arrive happy when the listing says plainly what to expect.

As for Nandini, she still reads the Monday messages. They are shorter now, and sometimes they are simple thanks. She keeps the whiteboard photo from that first meeting in her notes, with the list of things “everybody knows”. It reminds her that the most useful sentence a service can write is often the one that feels too obvious to say.