Priya had answered the enquiry line at a heart surgery information desk for eight months when her supervisor played back one of her calls. She had said “I will check and come back to you” four times in six minutes, and not once had she written down a number to call back on. Eight months of daily calls had made her fast. They had not made her better. That gap is the whole subject of this primer: deliberate practice for the people who answer questions at a heart surgery information service, with a small glossary entry after most sections to explain the terms.<\/p>\n
A note before we begin. Everything here is about the administrative side of an enquiry desk: how a call is taken, how a form is checked, how a handover is made. Nothing in this article is medical advice, and none of the drills involve judging anyone’s health. Questions about symptoms, procedures or treatment belong with qualified clinicians, and one of the first skills a good desk worker practises is passing them there promptly.<\/p>\n
It is natural to assume that the person who has handled two thousand calls is better than the person who has handled two hundred. Often they are simply more comfortable. Comfort feels like skill from the inside, but the two are different things. A habit repeated without anyone looking at it is just a habit, and habits can be good or bad; they harden either way.<\/p>\n
Priya’s habit was a verbal filler that bought her time while she searched for an answer. It sounded polite. It also left callers with nothing concrete, and it meant her colleagues had no record of what had been promised. The fix was not another month of calls. It was a ten-minute drill aimed at exactly that one weakness, with someone listening honestly afterwards.<\/p>\n
Mini-glossary: deliberate practice.<\/strong> Practice that targets one named weakness, is short enough to stay focused, gets honest feedback straight away, and ends with one small adjustment to try next time.<\/p>\n A drill is smaller than a training day and more specific than “get better at calls”. It has four parts, and skipping any of them turns it back into plain repetition.<\/p>\n Mini-glossary: scripted caller.<\/strong> A colleague who plays an enquirer using a short written scenario, so the drill is repeatable and the feedback can be compared with the last attempt.<\/p>\n The hardest part for a beginner is not the drill itself but choosing what to drill. Most people pick the thing they already like, because it feels good. A better method is to listen to three recent calls, or read three recent enquiry notes, and ask a boring question: where did the caller have to repeat themselves?<\/p>\n Repetition by the caller is a reliable sign. It points to a specific gap, such as a name spelled wrongly, a request that was not summarised, or a question that was passed along without being written down. Pick the one that appears most often, and write it as a single sentence in the form “I will do X on every call this week”. If the sentence needs the word “and”, it is two drills.<\/p>\n Some desks find it useful to share a short list of common slips so that people do not each have to discover them alone. Typical ones are listed below, and none of them has anything to do with clinical knowledge.<\/p>\n Mini-glossary: handover.<\/strong> The moment an enquiry moves from one person or team to another. A clean handover carries the caller’s details, the question in one sentence, and what has already been said.<\/p>\n Honest feedback is the part people most often get wrong, usually by being too kind or too broad. A few rules keep it useful.<\/p>\n First, describe behaviour, not character. “You paused before giving the return number” can be acted on; “you sounded nervous” cannot. Second, keep it to one observation per round. A list of six improvements teaches nothing because the learner cannot hold six changes in mind while speaking. Third, let the learner answer first. Asking “what did you notice?” often brings out the very point the listener was going to make, and people remember what they discover themselves far better than what they are told.<\/p>\n Mini-glossary: feedback loop.<\/strong> The short cycle of attempt, observation, adjustment and second attempt. The quicker the loop, the faster the improvement.<\/p>\n Back to Priya. Her supervisor, Meera, did not enrol her on a course. She asked for ten minutes after the last call of the day, five days running, and she picked one target for the week: every call ends with a return number and a day.<\/p>\n On Monday they ran the drill three times with Meera as a caller asking how to send documents ahead of an appointment. The first attempt ended with “I will get back to you”. Meera pointed out the missing number. The second attempt added it but forgot the day. The third had both. Eleven minutes, start to finish.<\/p>\n On Tuesday Priya caught herself mid-call, and finished the sentence properly. She told Meera afterwards that it felt clumsy. Meera said clumsy was the right word, and that it would stay clumsy for about three days and then stop being noticeable.<\/p>\n By Thursday she had stopped using the filler phrase without trying. On Friday they replaced the target with a new one, summarising the request back in one sentence, and the cycle started again. None of this required extra hours on the phones. It required a small amount of attention in the right place.<\/p>\n The same approach works for form checking. Take a blank enquiry form, fill it in with deliberate mistakes, and ask a colleague to find them in under two minutes. Then swap. The point is not to catch every error but to learn which kind of error your own eyes slide past, and then to drill that kind for a week.<\/p>\n Most of this can be done inside a single desk with nothing more than a colleague and a timer. Occasionally a team decides it wants a trained outsider to watch a drill and give a view it cannot give itself. If that is a technical team rather than a front desk, such as an IT group supporting the hospital’s booking systems, the listing at DevOpsTrainer<\/a>, which gathers DevOps trainers, instructors and coaches, gives them a place to start when they want a teacher for that kind of focused practice. For the front desk itself, the colleague in the next chair is usually enough.<\/p>\n Drills have a way of becoming rituals. After a month, people go through the motions, give vague feedback, and repeat the same scenario because it is easy. Three habits keep them alive.<\/p>\n Readers who want to see how clear communication supports patients outside the front desk may find it useful to look at our overview of telehealth follow-up after heart surgery<\/a>, which shows how much of good care depends on information passing cleanly between people. A related administrative topic is covered in the piece on planning specialised heart care through a remote consultation<\/a>. Treat both as background reading; questions about a person’s own health go to their doctor.<\/p>\n If you remember only a handful of lines from this primer, make them these. Hours of calls build habits, not necessarily skill. Pick one weakness from your own recent calls. Run a ten-minute drill with a scripted caller. Ask for one honest observation. Try one adjustment, then stop. Next week, choose the next weakness.<\/p>\n Priya still answers the enquiry line. She still says she will check on things. The difference is that every such sentence now ends with a number and a day, and her colleagues can see exactly what was promised. That small change took five short drills, not eight more months of hoping for improvement.<\/p>\n","protected":false},"excerpt":{"rendered":" A storytelling primer with a mini-glossary on how front-desk teams get better by drilling one call habit at a time, not by logging endless hours.<\/p>\n","protected":false},"author":13,"featured_media":3536,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1401],"tags":[],"class_list":["post-3535","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-healthcare-it"],"yoast_head":"\nThe anatomy of a good drill for an enquiry desk<\/h2>\n
\n
Choosing the weakness worth drilling<\/h2>\n
\n
Feedback that a beginner can actually use<\/h2>\n
A week of drills, written as a story<\/h2>\n
Where outside help fits in<\/h2>\n
Keeping the drills healthy over time<\/h2>\n
\n
A short recap for new starters<\/h2>\n