Brussels Missed a Deadline. Your Voice Agent Has Six Months.

Tuesday morning, two weeks after the deadline, and the Commission’s Article 6 page is still where it was at the end of January: a placeholder. The statutory date for the European Commission to publish its high-risk-classification guidance under the AI Act was 2 February 2026 — a Monday. The document did not appear, and as of this morning it still has not. Brussels missed it.

I waited two weeks before leading The Pass with this because I wanted to see whether the guidance would drop quietly in the second week of February. It didn’t. The Kennedys legal note this week framed it cleanly: the European Commission missed the 2 February 2026 deadline to publish guidelines on the practical implementation of Article 6, and there is no published date for when they land.

If you sell or deploy a hospitality AI product that touches an EU customer, this matters. Here is why, and what to be doing about it before the August date.

What was supposed to happen on 2 February

The Act gives the Commission homework alongside the obligations it puts on industry. Article 6 guidance was one of those assignments. The implementation timeline at artificialintelligenceact.eu records 2 February as the “deadline for [the] Commission to provide guidelines specifying the practical implementation of Article 6, including post-market monitoring plan.” That guidance is what tells a vendor — and by reference the operator deploying it — how to read whether a given AI system is high-risk in the first place.

Article 6 is the gate. Pass through it on the high-risk side and the heavy obligations attach: risk-management, data-governance documentation, logging, technical documentation, human oversight, robustness standards, post-market monitoring, and a conformity-assessment paperwork burden that sits on the provider but flows through to the deployer via contracts. On the not-high-risk side, you are mostly in Article 50 transparency territory and the load is lighter.

The guidance was supposed to give industry a workable yes/no test. It did not arrive.

Why this matters for hospitality voice and loyalty AI

The operator hearing this for the first time is probably wondering whether any of it touches the restaurant stack. Two categories where it bites hardest this year:

Voice agents on the phone. PolyAI, Slang AI, the wave of “we answer your reservations line” vendors that closed European deals through 2024 and 2025 — those fall squarely inside Article 50’s transparency obligation. The rule, as Freshfields summarises it on their AI Act tracker, is that providers of AI systems intended to interact directly with natural persons must design and deploy them so the person is informed they are talking to AI. The obligation lives in the Regulation and switches on with the rest of the Act on 2 August.

In practice: if your inbound reservations line is answered by AI voice and the system does not, at the start of the call, tell the caller they are speaking to AI, that is the gap to close before August. Some vendors handle this in their default prompt. Some don’t. Check.

CRM and loyalty AI that profiles guests. Most will not be high-risk under any reasonable reading — they are not deciding access to essential services, employment, or credit. But Article 6 guidance is the document that would have made that easy to say in writing on a vendor security questionnaire. Without it, EU customers are asking the question, EU operators are getting it asked of them, and nobody has the Commission’s text to point at.

The Omnibus is not yet a delay

The deal-desk read on this — Isaac’s piece on the August deadline made it well last month — is that everyone in Brussels has been quietly hoping the Digital Omnibus package, proposed by the Commission on 17 November 2025, will defer the high-risk obligations. The proposal does include language that would push the application of certain high-risk-system rules. It does not erase them. And it has not passed.

Until it does, the date that binds is 2 August 2026. That is twenty-four weeks from this morning. The missed Article 6 guidance does not move it. It just means industry has to do its own homework on the classification question with less help from the Commission than it was promised.

What to be doing before August

Three things, ordered by urgency:

• Audit your voice-agent disclosures today. If you run an AI-answered reservations or guest-services line in any EU country, listen to a call yourself this week. The first ten seconds should make it audible the caller is talking to AI. If they don’t, get your vendor on the phone and the prompt changed. This is a setting, not a roadmap item.
• Get the Article 6 classification on paper from every AI vendor in your stack. Even without Commission guidance, vendors should commit, in writing, to whether they self-classify as high-risk. If they refuse, that is a signal. Marco’s foundational piece on what the Act actually covers is the operator-language primer to send to procurement first.
• Do not pause the compliance budget on the Omnibus. The corporate-development conversation Isaac heard three times in January — “Brussels will move it” — is still the conventional wisdom. The deal-desk read remains: do not bet on it.

Brussels missing its own deadline is not, on its own, a story. Brussels missing it while the deadline that binds industry stays exactly where it is — that is the story. Twenty-four weeks.

— Hana edits The Pass. Tips: hana@tabletransfers.com.