AI phone receptionists for clinics, salons and restaurants: what to say and what to keep away from the bot
The part that is the same everywhere
An AI that answers the phone interacts directly with people, so Article 50(1) of the AI Act applies. Callers have to be told they are talking to an AI at the latest at the first interaction (Article 50(5)). On a phone call that means the greeting:
"Hello, you've reached Riverside Dental. I'm the practice's AI assistant and I can book, move or cancel appointments. To speak to someone at reception, say 'reception' at any time."
The voice agent guide covers wording, transfers, voicemail and outbound calls. The duty sits with the provider of the system, which is often the software vendor, but the business that switches it on is the one callers complain to, so check the greeting yourself.
What changes by sector is what the bot hears and what it is allowed to decide.
Clinics: health data and the triage line
Health data. A caller who says "I need an appointment, my tooth is swollen and I have a fever" has given health data. That is special category data under Article 9 of the GDPR, which needs one of the Article 9(2) conditions on top of a normal lawful basis, and a bot that processes it at scale is a likely case for a data protection impact assessment (Article 35). Check where call audio and transcripts are stored, for how long, and whether the vendor uses them to train its models.
Do not let the bot triage. Booking the next free slot is administration. Deciding who is urgent is a clinical call, and it moves the system into other law:
- The AI Act lists as high-risk AI systems used to evaluate and classify emergency calls and emergency healthcare patient triage systems (Annex III, point 5(d)). Under the Digital Omnibus, high-risk duties for Annex III systems apply from 2 December 2027.
- Software intended by its manufacturer for a medical purpose, such as diagnosis, prediction or prognosis, can be a medical device under the Medical Device Regulation (Regulation (EU) 2017/745, Article 2(1)).
A receptionist bot that books appointments is unlikely to be either. One that asks about symptoms and decides who gets seen today might be. Keep a hard rule: any mention of chest pain, breathing problems, heavy bleeding, suicidal thoughts or similar triggers an immediate transfer or an instruction to call the emergency number (112 in the EU), and the bot gives no medical advice.
Salons: bookings, deposits and no-shows
Payments. Don't let the bot collect full card numbers by voice. Card data in a call recording or transcript is hard to secure, and card schemes' security standards apply to anyone who stores it. Send a payment or deposit link by SMS or email instead, through your booking system's payment provider.
Deposits and cancellation fees. If the bot tells callers about a deposit or late-cancellation fee, the wording has to match your actual terms. A bot that improvises a policy creates a promise you may have to honour. Keep these answers fixed, not generated.
Recognising regulars. Matching a caller's number to their booking history is ordinary personal data processing and should be covered in your privacy notice. Identifying people by their voice is biometric processing, which brings the GDPR's special category rules and can bring AI Act duties too (Annex III, point 1 covers some biometric identification systems). Most salons have no reason to do it.
Restaurants: allergens and reservations
Allergens. EU food information rules require allergen information for non-prepacked food, such as restaurant meals, to be available to customers (Regulation (EU) No 1169/2011, Articles 9(1)(c) and 44). A generative bot that guesses whether a dish contains nuts is a real risk. Either have it read answers from a dish-by-dish allergen list that staff maintain, or have it say "I'll pass that to the team" and take a callback number. Never let it say a dish is "safe" for an allergy.
Reservations and changes. Confirm every booking by text or email so the guest has a record that does not depend on the call. Say clearly when a request (a large group, a special occasion) needs a person to confirm it.
One script, three variants
| Sector | After the AI greeting, add | Hand to a person when |
|---|---|---|
| Clinic | "I can't give medical advice. If this is an emergency, hang up and call 112." | Any symptom question, urgency, results, prescriptions |
| Salon | "I'll text you a link to pay the deposit." | Complaints, refunds, treatment suitability questions |
| Restaurant | "For allergy questions I'll read from our allergen list or pass you to the team." | Allergies not on the list, large groups, complaints |
Setup check
- [ ] Greeting says it is an AI and how to reach a person, before anything else.
- [ ] Call recording and transcripts covered in the privacy notice, with a retention period.
- [ ] Vendor's training-on-your-data setting checked.
- [ ] Clinic: emergency words trigger a transfer or an emergency instruction; no triage or medical advice.
- [ ] Salon and restaurant: no card numbers taken by voice.
- [ ] Policy answers (fees, allergens, opening hours) come from fixed text, not generation.
- [ ] Every booking confirmed in writing.
Sources
- Regulation (EU) 2024/1689 (AI Act) on EUR-Lex: Article 50(1) and (5), Annex III point 5(d).
- Annex III and Article 50 at artificialintelligenceact.eu.
- Regulation (EU) 2026/1744 (Digital Omnibus on AI) on EUR-Lex, for the high-risk dates.
- Regulation (EU) 2016/679 (GDPR) on EUR-Lex: Articles 9 and 35.
- Regulation (EU) 2017/745 (Medical Device Regulation) on EUR-Lex: Article 2(1).
- Regulation (EU) No 1169/2011 (food information to consumers) on EUR-Lex: Articles 9 and 44.