Evaluate what happens when a caller changes an appointment ambiguously, when two patients have similar names or when a medical question enters the conversation. This guide concerns operational and technical planning. It does not provide clinical triage rules or replace the legal and professional review of a particular practice workflow.
Key takeaways
The main points for planning an AI phone assistant in a medical practice are:
- An assistant can confirm an appointment only after the destination system has successfully stored it.
- Collect only what the administrative task needs, because the GDPR treats health data as a special category.
- Callers need a comprehensible route to practice staff, and a transfer destination must be staffed at the time it is offered.
01 / 10
Which practice calls can an AI phone assistant handle administratively?
Start with activities for which the practice already has clear instructions: opening hours, directions, callback requests and particular appointment categories. A request for a prescription or referral can be recorded without confirming that it is medically appropriate or will be fulfilled.
The table shows five typical practice requests, their possible administrative handling and the boundary each one needs.
| Request | Possible administrative handling | Necessary boundary |
|---|---|---|
| Opening hours and directions | Give approved practice information | Include current exceptions |
| Appointment request | Capture a category or book an authorised slot | Do not invent a clinical classification |
| Cancellation | Update the system after appropriate checks | Caller ID alone is insufficient |
| Prescription request | Pass the request to the practice team | Do not promise a prescription |
| Medical question | Offer the approved human route | No diagnosis or treatment recommendation |
Doctolib's official description includes telephone appointment management and message intake. That documents a product capability; it does not establish compatibility with every practice-management system or suitability for every speciality. Doctolib product announcement
02 / 10
An AI receptionist for a dental practice: a bounded example
A dental practice can start with administrative requests that reception already handles under written instructions. For example, a fictional practice may allow the assistant to explain opening hours, collect a callback request or request a change to a known appointment. The practice must define which appointment types, if any, may be booked automatically.
The table lists five proposed test calls for a dental practice and the administrative outcome to assess for each.
| Proposed test call | Administrative outcome to assess |
|---|---|
| Existing patient requests a different appointment time | Verify identity using the practice-approved route; confirm availability and the resulting record before claiming a change |
| New patient asks whether the practice accepts enquiries | Give current approved information or collect a request without promising acceptance or treatment |
| Caller describes symptoms or asks whether it is safe to wait | Follow the practice-approved human or urgent-contact instructions; do not improvise clinical advice or urgency decisions |
| Caller asks about a procedure's price | Use approved published information within its stated scope; route individual treatment estimates to the practice |
| Caller acts for another patient | Apply the practice's authority checks rather than relying on shared names or caller ID |
These are proposed administrative tests, not clinical triage rules or a live dental-software demonstration. A practice lead should approve the conversation boundary, patient-information handling and local contact instructions before deployment. Do not transfer German product or professional guidance unchanged to an Austrian, Swiss, UK or Irish practice.
Keep the ordinary reception route usable when the assistant or practice software is unavailable. Measure whether staff receive enough authorised information to act, while avoiding unnecessary collection of symptoms or other health details. The AI-versus-human answering-service comparison helps decide which calls should stay with people from the outset.
03 / 10
Which rules does appointment booking need from the practice?
An empty calendar slot is not a complete appointment rule. These constraints may all matter for an appointment in a medical practice:
- duration
- clinician
- location
- equipment
- new-patient status
- preparation requirements
The practice team should document these constraints before an integration receives permission to write appointments.
Clinical judgement. Where selecting the appropriate appointment requires clinical judgement, the assistant should collect a callback request. Adding more scripted questions does not automatically make an automated assessment suitable. The practice must decide what information is necessary for administration and who handles the cases that need judgement.
Availability is not a booking. Availability and booking are also separate actions. An assistant can confirm an appointment only after the destination system has successfully stored it. When the scheduling application cannot be reached, the outcome remains a request. A polished summary must not make an unconfirmed preference look like a binding appointment.
Several locations. For providers with several locations, include the address in the spoken confirmation. Repeating “Thursday at ten” is insufficient if the patient normally attends a different branch. Confirm the date, local time, location and any approved practical preparation information in a way the caller can correct.
04 / 10
Worked example: changing another person's appointment
Synthetic scenario: Someone asks to move “my mother's appointment on Thursday”. The calling number matches a family contact. That does not establish which patient is involved or whether the caller is authorised to change the booking.
The assistant follows the practice's approved verification process and collects only the necessary information. If reliable matching is not possible, it creates a callback task. The original appointment remains unchanged. The task describes the requested change and the unresolved check, without speculating about relationships or authority.
Where a change is permitted, the assistant offers a suitable alternative, repeats the date and time, and performs the update. A confirmed system result allows a definite acknowledgement. If the response is lost or ambiguous, reception needs a reconciliation task so that the patient does not receive two inconsistent confirmations.
This distinction should appear in the staff interface. “Requested”, “awaiting verification” and “changed successfully” are operational states, not interchangeable wording for the same call. Staff need to know which action, if any, has already occurred.
05 / 10
How much health information should the assistant collect?
Collect only what is needed. The fact that someone contacts a particular practice, or the name of an appointment type, may reveal sensitive information. Collect what the administrative task needs. A detailed medical history is generally a poor default requirement for a routine callback request.
Special category. The GDPR treats health data as a special category with additional conditions for processing. In Austria and Germany, assess the applicable requirements alongside the general legal basis. Professional confidentiality and national rules can also be relevant. GDPR, particularly Articles 5, 6 and 9
Each data form separately. Assess audio, transcripts, summaries and destination-system records separately. Who can access each one? For how long is it needed? Can a service provider use it for its own purposes? A statement about the location of one server does not answer those questions. Swiss practices also need assessment under the applicable Swiss rules; a European supplier's marketing statement does not replace it.
Access. Access should follow operational responsibility. Someone who manages the assistant's opening-hours knowledge does not necessarily need to read patient messages. Avoid distributing sensitive summaries widely through ordinary notification emails when a restricted clinical working system is available.
Got a workflow like this?
Tell me about it. Honest take and a rough price, usually within a day.
06 / 10
How do callers reach practice staff, and what happens with urgent statements?
Route to staff. Callers need a comprehensible route to practice staff. That includes people facing language barriers, speech difficulties or simply preferring a human conversation. After repeated misunderstandings, the assistant should offer an alternative instead of asking the same question indefinitely.
Staffed destination. A transfer destination must be staffed at the time it is offered. Busy lines and unanswered calls need an explicit fallback. Promise a callback deadline only where the practice can organise and monitor it. Automatically filling a permanently overloaded inbox does not create a reliable service.
Medical urgency. Statements suggesting medical urgency require a professionally approved practice process. This article deliberately does not supply a symptom checklist or triage algorithm. Test that the agreed boundary is respected and that the assistant does not add reassuring clinical conclusions of its own.
07 / 10
How do you verify supplier compatibility with your practice system?
A product description does not establish compatibility with every practice-management system. Ask each supplier to demonstrate one complete workflow: the call, appropriate matching, a record in the application the practice actually uses, and reception processing that record. An emailed summary may be acceptable for a limited intake service. It is not automated appointment management.
If itellicoAI is considered, note its explicit distinction between appointment intake and direct calendar booking scoped to a customer integration. Doctolib offers an approach connected to its practice environment. Decide through existing systems and demonstrated task coverage, rather than assuming that similarly named features have identical behaviour. itellicoAI appointment and integration scope
Before contracting, obtain the integration method, permission requirements, division of responsibilities, outage procedure and deletion process. Price the actual scope. An advertised package for another practice size or a different software combination may not represent the implementation you need.
08 / 10
How do you test the assistant from reception's perspective?
Using synthetic patient data, the acceptance test for a practice phone assistant should include these cases:
- a cancellation
- similar names
- a third-party caller
- an unavailable appointment
- a medical question
- a destination-system outage
Then ask reception to process the resulting tasks without extra explanation. Missing details and unclear states become visible quickly.
Measure complete administrative outcomes, correctly escalated exceptions and the additional work staff must perform. A high answer rate is insufficient when reception has to ask for the same information again. Record the tested configuration and repeat the important cases after changes.
Practice leadership, qualified clinical staff, data-protection responsibility and technical support should each assess their part of the rollout. A bounded administrative workflow with an accessible human alternative gives the practice something concrete to approve, monitor and improve.
09 / 10
Take the worksheet
Worksheet
Download the editable CSV table
| Request | Administrative workflow proposal | Practice decision required |
|---|---|---|
| Appointment request | Capture type and contact | Which appointments may be booked directly |
| Prescription request | Send request to practice team | Clinical review and authorisation |
| Results enquiry | Arrange protected callback | Identity and disclosure checks |
| Acute health concern | Use approved instruction and alternative route | Professionally reviewed escalation |
| Uncertain identity | Withhold sensitive information | Verification procedure |
Columns to fill in, in the file: Your value / observation, Owner, Next action.
Download the editable CSV table (CSV). Add your own values, owners and open actions. This worksheet contains no measured client results.
10 / 10
Related decisions
These pages cover the service overview, the industry page for medical practices and the related decisions for a practice phone assistant:
- AI phone assistants: functions and boundaries
- AI automation for medical practices
- AI in medical practices: administrative workflows and clear boundaries
- Review data protection for an AI phone assistant
- Human handover and callbacks for AI phone assistants
For a workflow review, start with the task, systems involved and typical exceptions. Discuss it with modernagents.
