The support desk is a clinical quality metric: response time in a franchise network

01

What actually happens while a clinic waits

Nothing dramatic, and that is the problem.

A coordinator has a patient in front of her with a medication history that does not match the protocol she was trained on. She asks the group. Nobody answers immediately, because it is 11am and everyone is in session. She has a room booked, a patient who took the day off work, and a surgeon who will be free in twenty minutes.

So she does the sensible thing: she looks at what the clinic did last time something similar came up, and repeats it. A capable person has made a good decision, and it is completely invisible to you. By the time the answer arrives at three, it has become a review rather than a decision.

Multiply that by a network and a year. The written standard describes what should happen. The lived standard is an accumulation of reasonable local guesses made while waiting, and the two drift apart quietly, at a rate set almost entirely by how long the wait is.

02

Measure it where support really happens

I would compare the ticket queue with the authorised channels staff actually use. A dashboard limited to tickets may miss an unresolved question in a chat group. The review should close that gap without making private conversation a source of casual surveillance.

So read the messages. Take a month of the busiest group, and go through it by hand. For each message, ask whether it was a question, whether an answer arrived, and how long that took. Then note whether the answer came with a name attached or evaporated into agreement.

Acknowledgement needs an owner for the next decision. Several sympathetic replies can still leave a clinic without an answer it can act on. I would track whether the issue reached the right authority and whether the action returned to the person who raised it.

The exercise takes a couple of afternoons. It will tell you more than the ticketing report has told you all year, because the ticketing report can only count the questions somebody thought were formal enough to raise formally.

03

Three clocks, not one

A single response target is the usual mistake. It is set at something like twenty four hours, which is far too slow for the question that has stopped a procedure and needlessly tight for the one about next quarter's stationery.

Split it by consequence.

The first clock is for anything that stops clinical work now. A protocol conflict, a consent question, an adverse event. Target in minutes, and name the person who carries the phone. If you cannot name that person for every hour your clinics are open, you do not have this clock, you have a hope.

A slower clock covers anything that changes what a clinic does this week. Scheduling, a supply substitution, a query about eligibility. Target in hours, inside the working day.

Everything else gets the last clock, and a day is fine. Most of your volume lives here, which is exactly why a blended average tells you nothing useful. The average is dominated by the questions that did not matter.

A number that mixes urgent and routine will always look acceptable and always hide the failure you care about.

04

When the urgent clock runs slow

For a slow urgent-response route, I would first check staffing coverage and decision authority. A queue may lack capacity, or the available person may be unable to make or obtain the required decision. Those problems need different actions.

Either the question should not have needed asking, because the standard does not cover a situation that comes up monthly, and the fix is to write that section rather than answer it faster forever. Or the person who can answer is one of two people in the whole network, and they are also doing something else. Knowledge has concentrated in too few hands, which is not a support problem, and it will hurt you the week they are on leave.

Both are worth finding. Neither shows up if you measure response time as a service level and stop there.

05

Where this leaves you

How many questions your clinics have is beyond your control. A growing network generates more of them, and a network doing new procedures generates harder ones. Chasing question volume down is the wrong ambition anyway; a clinic that has stopped asking has usually stopped checking.

Your share is narrower and more useful: a name against the first clock for every open hour, and a month of real messages read recently rather than a report about them. Then an owner on every answer, and the habit of writing a question you have answered five times into the standard, so the sixth clinic does not have to wait for you at all.