An interactive voice response system (IVR) in a medical practice is a call-routing tool that has to protect patients first and save time second. A well-designed healthcare IVR offers few options, recognizes urgent situations early, hands over to a trained person without friction, and relies on data hosting that meets French requirements. A poorly designed one adds a barrier between a worried patient and the care that patient needs.
This guide is written for general practitioners, specialists, paramedical professionals and health center teams in France. It covers the structure of the menu, the rules for triage, the moment of handover to a human, the compliance framework, and the way to test a flow before it goes live.
Key takeaways
- A healthcare IVR should act as a filter that preserves the human relationship, never as a wall. Three or four menu options, with a person reachable at every stage, is a sound starting point.
- Triage logic belongs to the medical team. Medical regulation is a medical act that engages the physician’s responsibility, so the IVR may sort and route but must never decide on care.
- Since 16 May 2026, HDS 2.0 certification is mandatory for actors hosting health data on behalf of third parties, which includes call data handled through telephone and IVR services.
- The flow must be tested with real call scenarios, including the awkward ones, before patients use it.
Table of Contents
- What an IVR is meant to do in a medical practice
- Menu structure: fewer choices, clearer words
- A sample call flow for a group practice
- Triage and emergencies: where the IVR stops
- Handover to a human: the moment that defines the experience
- Compliance: what French practices must check
- Voice menus, speech recognition and AI
- Testing before launch
- Our perspective
- How ClicFone supports practices
- FAQ
- Sources
What an IVR is meant to do in a medical practice
In a call center for retail or telecommunications, an IVR is judged by how many calls it resolves without an agent. In a medical practice, the measure is different. The useful question is whether each caller reached the right outcome, quickly and safely: an appointment booked, a prescription request recorded, a urgent symptom escalated, or a message passed on with enough detail to act on.
The Haute Autorité de Santé (HAS) stresses in its work on emergency call handling that automation should never dehumanize access to care, and that the person taking the call should have the useful information at a glance to orient the patient properly. That principle, written for SAMU call centers, transfers well to private practices: the IVR is there to prepare the human response, not to replace it.
Three functions are realistic for an IVR in a practice:
- Greeting and information: opening hours, address, access, closing periods, and a short instruction for emergencies.
- Routing: sending the caller to the right person or queue, such as the secretariat, the nurse line, or the on-call service.
- Capture: recording the caller’s identity, the reason for the call and a callback number when no one is available.
Anything beyond these functions, such as clinical questions or interpretation of symptoms, needs a qualified person.
Menu structure: fewer choices, clearer words
Most callers to a practice are not comfortable with long menus. Many are elderly, anxious, or calling from a mobile in a waiting room. The menu has to be understood the first time it is heard.
Limit the first level
Three or four options on the first level is a practical ceiling. Each option should describe the caller’s need, not the practice’s internal organization. “To make or change an appointment” is understood immediately; “for the administrative department” is not.
Put the emergency instruction first, and keep it short
A brief statement at the very start, telling callers with a life-threatening situation to hang up and call 15 or 112, costs a few seconds and removes a serious risk. It should be spoken before any menu, and it should not be hidden in a long welcome message. The message must be reviewed by the physicians of the practice, because the wording engages their responsibility.
Allow a way out at every level
A caller who presses nothing, or who presses the wrong key, must still reach a person or a message box that is monitored. Dead ends are the most common design fault: a menu that loops, a mailbox that is never emptied, a transfer to a line that rings without answer.
Write the script for the ear
- Use short sentences, one idea each.
- Name the option first, then the key to press.
- Avoid medical jargon and internal abbreviations.
- Record with a calm, clear voice, and update the message whenever hours or staffing change.
A message that announces a closure that ended three weeks ago erodes trust faster than any technical failure.
A sample call flow for a group practice
The table below shows a simple first-level structure. It is an illustration of the logic, to be adapted by each practice with its physicians.
| Caller’s need | Option | Destination | Fallback if no answer |
|---|---|---|---|
| Life-threatening situation | Spoken before the menu | 15 or 112 | Not applicable |
| Book, move or cancel an appointment | Option 1 | Secretariat or online calendar link | Callback request recorded |
| Medical question, new symptom, urgent need | Option 2 | Trained person applying the triage protocol | Escalation to the on-call physician |
| Results, prescriptions, administrative documents | Option 3 | Secretariat queue | Message with identity and reason |
| Anything else | Stay on the line | A person | Message with callback |
The fallback column matters as much as the destination. Every route needs a defined answer to the question: what happens if nobody picks up?
Triage and emergencies: where the IVR stops
The most delicate part of the design is the boundary between sorting calls and assessing them. According to HAS material on medical regulation, triage by IVR must rank requests by criticality, with a secure switch to a regulating physician or a trained medical regulation assistant (ARM). The regulation act itself is a medical act.
In practical terms, this means:
- The IVR can ask where the call should go. It can offer an option for “urgent medical need”.
- It should not try to interpret symptoms. Keyword detection on a free-form description may miss a serious situation or flag a harmless one, and the consequence of a miss is a loss of chance for the patient.
- Urgent routes must lead to a human quickly. A queue music loop is not an acceptable response for a caller who has selected the urgent option.
The HAS recommendation on handling calls for unscheduled care in the framework of medical regulation offers a useful reference for the structure of questions and the levels of response, even though it is addressed to regulation centers rather than private offices.
For practices that outsource their phone reception, the escalation chain should be written down: who is called, in which order, after how many unanswered rings, and who decides. ClicFone has published a detailed view of this in its article on four elements for emergency phone escalation, and another on the safety of medical phone triage.
Handover to a human: the moment that defines the experience
The quality of an IVR is judged at the instant the caller reaches a person. Two design choices make the difference.
Pass the context along
The caller should not have to repeat what was already said. Computer-telephony integration (CTI) allows the system to display the caller’s record, or at least the number, the chosen option and any captured details, before the call is answered. The secretary can then greet the caller by name and move directly to the request. This is what turns the IVR from an obstacle into what is sometimes called an intelligent filter: it organizes the flow while keeping the interaction personal.
Connect to the agenda
When the request is an appointment, the person answering needs live access to the calendar. In France, that means working with the scheduling platforms practitioners already use, such as Doctolib, Maiia, LibreRDV or CalenDoc. A call flow that ends with the secretary re-typing information in a second tool produces errors and double bookings. ClicFone covers this point from the angle of scheduling in its guide to AI agenda management for French medical offices and, for independent therapists and nurses, in its piece on AI-assisted agenda management for liberal paramedical practices.
Compliance: what French practices must check
A patient’s voice, name and reason for calling are health-related personal data. Choosing an IVR therefore involves legal obligations as much as ergonomics.
HDS certification
The French health data hosting framework requires certification for providers who host health data on behalf of others. The Agence du Numérique en Santé states that version 2.0 of the HDS certification became mandatory on 16 May 2026, once the 18-month transition period ended, and that it aligns with ISO 27001:2022. Before signing with an IVR or answering-service provider, a practice should ask which components of the service host health data, who the host is, and whether that host holds a valid certificate. The certification standard itself is published under article R1111-10 of the Public Health Code and describes the requirements providers must meet.
The ANS also published a reminder for the final stretch of the transition, “six months to be ready”, which shows how recent this requirement is. Practices that selected a vendor before 2026 should confirm that the vendor’s status has been updated.
Data sovereignty
The choice of a host is also a question of governing law. In the wake of the Schrems II ruling, French authorities encourage health providers to favor infrastructure whose governance and applicable law guarantee protection equivalent to the GDPR, and HDS 2.0 integrates these requirements more strictly. For an IVR, that means asking where voice recordings and transcripts are stored and processed, including by any AI or speech recognition subcontractor.
GDPR, recordings and consent
If calls are recorded or transcribed, callers must be informed, the purpose must be defined, and retention must be limited. The relationship with the provider is framed by a data processing agreement under article 28 of the GDPR. The CNIL publishes advice for professionals deploying voice assistants, which is relevant when an IVR uses speech recognition. ClicFone has detailed the practical steps in three articles: GDPR steps for medical calls, secure call recording and making verbal consent auditable.
A short checklist for the practice:
- Is the provider HDS-certified for the hosting activity involved?
- Is there an article 28 data processing agreement?
- Where are recordings and transcripts stored, and for how long?
- How is the caller informed about recording?
- Who at the practice can access the recordings, and is access logged?
Voice menus, speech recognition and AI
Touch-tone menus are predictable. Speech recognition lets callers say what they need, which can be easier for people who struggle with keypads, but it adds two risks: misunderstanding of accents, names and medical terms, and a larger volume of sensitive data to protect.
A cautious approach is to use AI for low-risk tasks, such as recognizing that the caller wants an appointment and offering available slots, and to keep clinical content under human control. Any conversation in which the caller mentions symptoms should switch to a trained person. Validation matters here: ClicFone describes a structured period of testing in its article on validating AI call triage for EU clinics.
Testing before launch
A call flow should be tested like any other care process. A simple protocol:
- Write scenarios. Include a routine appointment, a cancellation, a caller who is confused, a caller with an urgent symptom, a caller who does not speak fluent French, and a call outside opening hours.
- Test with colleagues who did not build the flow. They will press keys the designer never expected.
- Measure the right things. Abandoned calls, time to reach a person, share of urgent calls reaching a human within the target delay, and callbacks completed.
- Review after the first weeks. Listen to a sample of calls, with the legal basis for doing so documented, and adjust the wording.
- Re-test whenever something changes. New opening hours, a new colleague or a new calendar tool all alter the flow.
Peak periods deserve their own test. During winter epidemics, a menu that works on a normal Tuesday can saturate, so queue messages and callback options should be planned for it.
Our perspective
After more than 15 years of handling medical calls, we have seen that practices rarely suffer from a lack of technology. They suffer from calls that reach nobody, or reach someone who has no context. Our view is that the telephone remains the first point of contact for a large share of patients, and that it deserves the same care as the consultation room.
For that reason, we combine trained human tele-secretaries with AI support rather than choosing one or the other. The human operator handles what is delicate: a patient who is anxious, a request that does not fit the menu, a situation that may be urgent. The AI helps keep the service available at any hour and synchronized with the agenda. Medical decisions remain with the physician, and we design every flow so that this boundary is visible to the operator.
Our advice to any practice reviewing its IVR is to start from the worst call it received last month, not from the average one, and to design the flow so that call would have ended well.
— Rudolph Thierry
How ClicFone supports practices
ClicFone provides outsourced medical and paramedical telephone answering for general practitioners, specialists, paramedical professionals and health center teams. Operators trained for healthcare answer calls, book appointments directly in Doctolib, LibreRDV, Maiia or CalenDoc, and apply the practice’s own escalation rules. Practices that want to see how this fits their organization can start with the remote telephone secretariat page or review the medical phone triage service, or contact ClicFone directly.
FAQ
What does IVR mean in a medical context?
IVR stands for interactive voice response: an automated system that answers a call, plays a message and routes the caller according to a key press or a spoken request. In a practice, it handles greeting, routing and message capture. It does not assess symptoms, which remains the role of a trained person under medical responsibility.
How many menu options should a medical IVR have?
Three or four on the first level is a sound working limit, since callers must remember the options after hearing them once. The urgent instruction comes before the menu, and a path to a person should exist at every level. The right number ultimately depends on testing with real callers.
Does an IVR in France need HDS certification?
If the service hosts health data on behalf of the practice, such as recordings or transcripts containing health information, the host must hold HDS certification, and version 2.0 has been mandatory since 16 May 2026 according to the Agence du Numérique en Santé. The practice should ask the provider for proof of certification and sign an article 28 agreement. Practices with doubts can consult their data protection officer or the CNIL.
Can an IVR handle medical emergencies?
No. It can announce the emergency numbers, offer an urgent option and route that call to a person quickly, but assessing the situation is a medical act. HAS guidance on regulation requires a secure handover to a physician or a trained regulation assistant.
Sources
- HDS certification, Agence du Numérique en Santé
- Certification HDS: six months to be ready, ANS
- HDS certification standard, version 2
- Haute Autorité de Santé
- HAS, SAMU quality and safety guide summary
- HAS, handling calls for unscheduled care
- CNIL, voice assistants: advice for users and professionals
Recommended
- Encrypted Call Recording in Healthcare: The French Rules
- 3 Ways to Make Verbal Consent Auditable in French Healthcare
- Telephone Patient Orientation for Maisons de Santé
