Introducing a practice chat: is it worth it for your practice?
There is no honest urgent answer to "why now". There is, however, a calculation, and it can be drawn up in a week.
Texts about practice chats answer the timing question almost identically: change is under way, patient expectations have shifted, whoever fails to act now falls behind. That may be true, but it is not an argument — it is pressure, and it helps nobody decide.
The more useful question is not "why now" but "how much". A chat replaces phone calls. How many it replaces depends on what those calls are about, and that is measurable before buying anything.
The calculation
For one week, reception keeps a tally with two columns: calls that concerned medical advice, and all the others. The second group covers appointment changes, repeat prescriptions, asking after a result, and organisational queries.
| Share with no medical content | What it means |
|---|---|
| under 30% | A chat is barely worth it. The bottleneck is elsewhere, usually in documentation or incoming post. |
| 30 to 50% | A chat carries its weight if patients can use it without installing anything. Otherwise only part of it shifts. |
| over 50% | The channel usually pays for itself within a few months, on saved reception time alone. |
The reason for the threshold is simple: a call ties up two people at the same time, a message does not. The gain comes not from an answer being faster to write than to speak, but from it being written when there happens to be time.
A call requires both sides to have time in the same moment. That is the cost, not the length of the conversation.
What changes besides the time
Two effects appear in no calculation and are nonetheless mentioned regularly. The first is reachability outside surgery hours: queries that would otherwise arrive as a call next morning are already there in writing when the practice opens.
The second is traceability. What was agreed on the phone is written nowhere; what was written is there. For follow-up questions and in a dispute that is a noticeable difference, and it costs nothing extra.
When it is not worth it
Three cases in which introducing one is better avoided.
- When the share of organisational calls is low. The bottleneck is then in documentation or incoming post, and attention would be better spent there.
- When another changeover is already under way in the same quarter. Two simultaneous changes hold each other up, and afterwards both count as failures.
- When the channel requires patients to have an account and an app. Some of them will not use it, the phone remains for those, and reception then serves two routes instead of one.
If the calculation works out
Then the same applies as to any other changeover : start small, close the old route rather than banning it, and listen for two weeks. The comment "that used to be quicker" is not criticism but the only reliable information on whether the new route holds up in daily work.
And the legal side belongs before the selection, not after: data processing agreement, provider domicile, handling of connection data. Those three questions decide which services qualify at all, faster than any feature list.
