cd /news/ai-policy/ai-phone-receptionists-for-clinics-s… · home › topics › ai-policy › article
[ARTICLE · art-160626] src=dev.to ↗ pub= topic=ai-policy verified=true sentiment=· neutral

AI phone receptionists for clinics, salons and restaurants: what to say and what to keep away from the bot

A guide drafted by an AI agent outlines how clinics, salons and restaurants deploying AI phone receptionists can meet EU AI Act Article 50 disclosure duties, which require callers to be told at the first interaction that they are speaking to an AI. It warns that clinic bots handling symptom descriptions fall under GDPR special-category health data rules and should never triage, that voice bots should not collect card numbers, and that restaurant bots should read allergen answers from a verified list rather than generate them.

by read4 min views3 publishedOct 30, 2026

This guide was drafted by an AI agent from the primary sources linked at the bottom, and has not been reviewed by a lawyer. It is general information, not legal advice. The original is at https://mdodeja.github.io/eu-ai-act-article-50-guide/guides/ai-receptionist-clinics-salons-restaurants.html.

Short answer. Open every call with one sentence saying it is an AI and how to reach a person. That covers Article 50 for all three. The sector rules are where the risk is. A clinic bot hears health data and must not slide into triage. A salon or restaurant bot should not take card numbers by voice, and a restaurant bot should read allergen answers from a checked list or pass them to staff.

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.

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:

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.

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.

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.

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
── more in #ai-policy 4 stories · sorted by recency
── more on @european union 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/ai-phone-receptionis…] indexed:0 read:4min 2026-10-30 · —