In a private medical practice in Bergamo, specialising in cardiology, the secretary Stefania spends about an hour a day on the phone answering three recurring questions. "When is my next appointment?". "Do I need to fast before the echocardiogram?". "Where can I park?". These three questions, in minor variations, represent about forty per cent of incoming phone traffic. The rest are requests that actually require her judgement: rescheduling appointments with complex constraints, triage on symptoms that may require urgent attention, interactions with insurers and hospital referrals.
The practice owner, who has just stumbled on the problem while looking at the phone bill, puts it this way: "what does the front desk really cost? Not her salary, the time she does not dedicate to real work. Five hours a week, two hundred hours a year, on things anyone could answer given the right information".
Those who search for medical practice management software usually start from vertical products: Doctor Office, Telcom Medical, WinMedico, Shark Medical, GMI. All handle diaries, clinical records, online bookings, reminders. None, on its own, solves the problem of the five hours a week dedicated to repeatable questions. And it does not solve it because this problem is not in the diary or the clinical record; it is in a different layer.
The diary and the clinical record as base
The administrative-clinical part of the private medical practice is typically well covered. A good medical management system handles online bookings, sends SMS or email reminders, keeps digital clinical records with histories, digitally signs documents when needed, integrates with diagnostic equipment. It is a robust backbone, matured in the last ten years and widespread in different forms in almost all Italian and Ticino practices.
This base is not the problem. The medical management system does its job. The problem, as in the Bergamo practice, lies in non-clinical daily communication: the hundreds of small interactions between patient and practice that do not enter the clinical record, do not enter the diary in a structured way, and that today all rest on the shoulders of the front desk.
These interactions have common characteristics. They have a predictable nature, meaning they constantly recur. They do not require medical judgement, meaning anyone with the right information about the practice could reply. They concentrate at specific times (opening, closing, 12-14). And they are, from the patient's point of view, completely normal: the patient does not understand why he should wait thirty minutes on hold to know whether he can park in the courtyard.
The channel that changes the calculation
The obvious question is: why not reply via email or via a site form? Technically you can. In practice, in Italy and Italian-speaking Switzerland, in the over-forty-five audience which represents the majority of a private medical practice, these channels do not work. The patient prefers the phone because the phone is immediate and requires learning nothing.
There is a channel the over-forty-five patient already uses, daily, without friction: WhatsApp. The practice's number, if it becomes a WhatsApp contact, is saved in the patient's personal contacts at first use. From there on, writing is natural. It does not require opening a new app, does not require remembering a URL, does not require filling in a form.
On the practice side, WhatsApp has an operational advantage that the phone does not have: it is asynchronous. The front desk does not have to reply immediately; it can reply when it has a moment, within a reasonable time. This simple latency difference opens a space for an automatic system handling the repetitive questions without the front desk even seeing them.
The system that knows the practice
An automatic reply system on WhatsApp makes sense only if it knows the practice. A generic bot ("our company will reply as soon as possible", "for bookings visit the site") solves nothing; on the contrary, it makes the experience worse because it interposes a wall between patient and front desk.
Knowing the practice means knowing:
The patient's appointments: if Rossi writes "when is my visit?", the system knows that Rossi has a visit on Tuesday the 18th at 14 and tells him directly, without going through the front desk.
The preparations by type of exam: if Bianchi asks "do I have to fast for tomorrow's echocardiogram?", the system knows that the echocardiogram does not require fasting, but requires clothing leaving the chest exposed, and communicates it with the precision of someone who works in the practice.
The logistical information: parking, disabled access, floor of the building, opening hours for samples, behaviour in case of rain. This is information a site should contain, but which the patient prefers to ask for.
The recurring procedures: how to change an appointment, how to request a copy of a report, how to contact the doctor with questions about a report already received. These procedures are in the front desk's head but often not written consultable elsewhere.
When a system has this context, it is capable of replying to sixty to seventy per cent of incoming questions on WhatsApp without involving the front desk. The remaining thirty to forty per cent (complex requests, symptoms to evaluate, particular administrative issues) are correctly passed to the front desk with the conversation context already prepared.
The knowledge base that needs to be built
The technological part of this system is the least critical. There are tools that, given a practice knowledge base, can reply on WhatsApp convincingly. The problem is the knowledge base: where it comes from, who puts it together, who updates it.
In most medical practices, this base does not exist in structured form. The information lives in four places. In the management system's diary (structured data on appointments). In the clinical records (structured but clinical data). On the website (static information, often dated). In the head of the front desk and the doctors (everything else).
To build the system, you need to extract the "everything else" from the head of the front desk and the doctors, structure it so it can be consulted automatically, and update it as things change. This work is not a week of software configuration. It is work of structuring the practice's knowledge, which takes time but produces an asset useful beyond the WhatsApp system.
The same corpus, once structured, becomes useful for training new front desk staff, for ensuring coherence between multiple doctors in the same practice, for preparing informational materials for patients, for keeping the website up to date.
The economic return
Back to the cardiology practice in Bergamo. The front desk spends five hours a week on repeatable questions. The cost, in pure salary, is about one thousand seven hundred euros a year (considering an hour of work at about seven euros gross to the company). But the real cost is not the salary of those hours; it is the opportunity cost.
The front desk, in the five hours recovered, can do things it does not do today or does badly. Follow patients in complex treatment to verify they are respecting the recommendations. Contact patients who have not confirmed check-ups. Handle insurance relationships more accurately. In the Bergamo case, it emerged that about twenty patients a year skipped check-up visits because the front desk did not have time to call them back a second time. Those twenty patients, multiplied by the average value of a check-up visit and by the probability of subsequent care, produce a figure significantly higher than the cost of the front desk on the five hours.
This calculation, in rough form, is what a clear-eyed owner does when evaluating whether to invest in a WhatsApp system. He does not look at how much he saves in salary. He looks at what he can begin to do with the recovered time that today he does not.
A recurring variant of this dynamic concerns patients in chronic therapy. In a cardiology or endocrinology practice, the patient is seen three to four times a year. Between one visit and the next, the main risk is not forgetting the reminder, because the commitment is structured, but not adhering to the therapy or not contacting the practice when a symptom manifests. A system keeping a light educational presence during the periods far from the visit (a reminder on the best moment to take the drug, a question three weeks after the start of a new treatment, an informative check after a seasonal event that may interfere with the pathology) changes the adherence rate measurably. The practice does not become intrusive; it becomes present in the right moments, which are the ones the patient remembers.
Two options on the table
A medical practice owner who recognises the described pattern usually has two options on the table. Add another module to the existing medical management system (some suppliers have versions with integrated messaging features). Or build a new layer resting on the management system but living above it, specialised in daily communication.
Both routes make sense in different contexts. Choosing well requires a diagnosis: how relevant is the flow of repeatable questions in your practice, on which channel do your patients prefer to write, how structured is the operational knowledge today, how willing are you to invest in preliminary structuring work.
This diagnosis is done in forty-five minutes of conversation, looking together at the real numbers of your practice (phone traffic, diary, etc.). At the end there remains a document describing the situation as it is, with a direction proposal. It is useful regardless of what you decide to do afterwards.
If you recognise something of your practice in the story of the Bergamo front desk, that is the kind of conversation worth having before any tool choice.