On August 2, 2026 the central provisions of EU Regulation 2024/1689 — known as the EU AI Act — come into force. For restaurants that use, or plan to use, AI in customer-facing interactions, this date triggers binding obligations. Ignoring them risks fines and a reputational hit that weighs heavier than any monetary penalty.

This post answers the questions we hear most often from restaurant operators: what applies? To whom? What needs to happen, concretely?

What Article 50 requires

Article 50 governs transparency obligations for certain AI systems. The points relevant to restaurants:

1. AI interaction must be disclosed. When a guest interacts with an AI system — for example an AI phone agent or a website chatbot — they must be informed clearly and unambiguously that they are not speaking with a human.
2. The information must be early and understandable. It cannot be hidden in the fine print and cannot be revealed only at the end of the interaction.
3. An "escalate to a human" option must exist if users request it.
4. AI-generated audio, image or video content must be marked as such (relevant for marketing).

These obligations apply both to the provider of the AI system (typically the company behind Tablario) and to the deployer — in our case the restaurant itself.

What changes in practice for a restaurant

If you use an AI phone agent, here is what changes:

• Opening line on calls. Instead of "Restaurant Krone, good day" the AI says: "Restaurant Krone, good day — you are speaking with our AI assistant. If you would prefer to speak with a team member, just say so at any time."
• An escalation path must exist. On request — typically "agent please" or "I want to speak with a human" — the AI must hand off to a person or commit to a callback.
• Documentation. You should record the deployment date, the AI components used and the wording of your disclosure. In a dispute, that is the simplest defense.

For websites and booking forms the same logic applies: if you use a chatbot that is not obviously a bot, you need a visible label.

What does not apply

To prevent these rules from becoming a bureaucratic burden, several clarifications matter:

• Pure booking software without AI — calendars, table planners, automatic confirmation emails — does not fall under Article 50. There is no "AI interaction".
• Automated reminder SMS are not affected, as long as no generative AI is involved.
• Internal tooling without end-customer interaction (e.g. AI assistance for scheduling) does not fall under transparency duties towards guests — though it may fall under other parts of the regulation.

Article 50 is not about AI in general but about AI in guest interactions.

Fines for non-compliance

The regulation provides for tiered fines. Violations of the Article 50 transparency obligations can be sanctioned with up to €15 million or 3 percent of worldwide annual turnover, whichever is higher.

In practice this will not affect every restaurant equally. Authorities are likely to investigate first where complaints come in — i.e. with providers whose disclosure practice is perceived as misleading. Still: a documented, clean disclosure process is the best insurance.

How Tablario meets the requirements

We built Tablario with the AI Act in mind from the start. Concretely:

• Standardized disclosure on calls. Every call answered by the AI phone starts with a clear notice. Restaurants can adjust the wording but must retain the substantive content — AI identification and escalation option.
• Voice-command escalation. The AI recognizes phrases like "human please", "real person", "agent" and hands off immediately. If no one is available, a callback is scheduled and written into the Tablario dashboard.
• Documentation in call logs. Every call is logged with timestamp, disclosure confirmation and conversation transcript. In case of an inquiry from authorities, everything is at hand.
• EU hosting. Voice processing and data storage run on EU servers. GDPR and AI Act go hand in hand — we treat both as core architecture, not as a bolt-on.

What to do this week

Even without a Tablario context, three steps every restaurant can take now:

1. Inventory. Which AI systems do we already use or plan to use? Phone? Chatbot? Reservation bot? Marketing generator?
2. Disclosure wording. Does each of these systems already have a notice that it is an AI? If not: contact the vendor or update yourself.
3. Escalation path. Can a guest switch to a human at any time? If not: define the workflow.

Frequently asked questions

Do the obligations apply to interactions started before August 2, 2026? The regulation kicks in on August 2, 2026. Calls and interactions from that date on must meet the new obligations. Earlier interactions follow the rules in force at the time.

Do we need a written disclosure on the website? For AI phone, the spoken disclosure at the start of the call is enough. On websites with chatbot functionality we recommend a visible label on the chat widget ("This chat is answered by an AI").

What if guests miss the disclosure? You must give the notice — you do not need to ensure that every guest acoustically processes it. Documentation that the announcement was made is sufficient.

We are a small family restaurant. Does this really apply to us? Yes. The regulation has no size exemption for Article 50. The good news: implementation is trivial as long as you use a vendor that integrates the disclosure by default.

Will more rules follow? Further AI Act provisions enter force in stages through 2027. For restaurants, Article 50 is the central lever — the rest (e.g. on high-risk systems) is typically not relevant in hospitality.

Sources: EU AI Act, Regulation 2024/1689 (in particular Art. 50, in force August 2, 2026), available on eur-lex.europa.eu. Tablario product documentation for the technical implementation of disclosure obligations.