Skip to content
Compliance

EU AI Act voice AI classification: limited, high-risk, or out of scope?

  • DPOs / Privacy
  • Procurement / IT-Sec
  • VP / COO
By Lewis CrookPublished
Bottom line up front

Voice AI under the EU AI Act sits in one of three buckets: out of scope, limited-risk (transparency duty only), or high-risk (full Annex III regime). The bucket is decided per use case by what the AI is doing, not by which vendor sold it. Most servicing deployments are limited-risk; biometric authentication and eligibility decisioning are not.

The three classifications that matter

The EU AI Act creates four risk categories — prohibited, high-risk, limited-risk, and minimal-risk — but voice AI in enterprise contact centres realistically sits in only three of them. Prohibited practices (real-time biometric identification in public spaces, social scoring) do not apply to inbound customer service.

Limited-risk is the default for most servicing use cases. The obligation is narrow but specific under Article 50: the deployer must inform the natural person that they are interacting with an AI system, unless this is obvious from the context. 'Obvious from the context' is a higher bar than vendors often suggest — a voice that sounds human, in a channel a human would normally answer, requires disclosure.

High-risk is the regime that changes the economics of the deployment. The full conformity assessment, technical documentation, post-market monitoring, and EU database registration apply.

When voice AI becomes high-risk: Annex III triggers

Annex III lists eight high-risk use case families. Four of them are routinely triggered by voice AI deployments. Read each one literally — the language is the test, not the marketing.

Annex III triggers commonly hit by voice AI
Annex III areaVoice AI triggerPractical example
Biometric categorisation / identificationVoice biometrics used for authentication or to infer protected characteristicsVoiceprint-based caller verification; emotion or sentiment inference used in routing decisions
Access to essential servicesAI determines eligibility or priority for utilities, banking, insurance, or public servicesEnergy hardship-tariff eligibility decided in the call; bank account opening completed end-to-end
Creditworthiness / credit scoringAI scores or makes credit-related decisions on natural personsCredit limit increase approved or declined in the call; lending pre-qualification
Employment / worker managementAI used in recruitment, task allocation, or performance evaluation of workersOutbound voice AI screening candidates; AI evaluating contact-centre agent calls for performance

Roles: provider, deployer, distributor

The Act distinguishes three roles. The vendor that develops and places the voice AI platform on the market is the provider. The enterprise that uses it under its own authority is the deployer. The reseller or system integrator that supplies it without modification is the distributor.

Most obligations sit with the provider — conformity assessment, technical documentation, EU database registration. Deployer obligations are narrower but real: human oversight, monitoring use against the provider's instructions, logging, transparency to affected persons, and (for high-risk systems serving public functions or essential services) a fundamental rights impact assessment.

A deployer that substantially modifies a high-risk system — for example, by replacing the underlying LLM with one not covered by the original conformity assessment — becomes a provider in its own right for that modified system. This is the trap most often missed in build-on-platform deployments.

Limited-risk: the transparency duty in practice

For limited-risk deployments, the obligation under Article 50 is to inform the natural person that they are interacting with an AI system, at the start of the interaction, in a clear and distinguishable manner.

What this means in the call: a disclosure within the first turn ('You're speaking with an automated assistant') that is unambiguous and not buried in legal text. A voice that introduces itself by name without disclosing its nature does not meet the duty. A disclosure offered only on request does not meet the duty. The disclosure is owed to the caller, not to the deployer's legal team.

Documentation: what each tier requires

Limited-risk deployments need: a transparency disclosure record, a basic data-protection assessment that overlaps with the GDPR DPIA, and a description of the use case kept on file.

High-risk deployments need: the provider's technical documentation under Annex IV (supplied to the deployer), a risk management system, data and data governance documentation, human oversight design, accuracy and robustness evidence, logging that supports post-market monitoring, and — for deployers in scope of Article 27 — a fundamental rights impact assessment before first use.

  • Transparency disclosure record (limited-risk and above)
  • DPIA / FRIA alignment under UK/EU GDPR (all tiers)
  • Provider technical documentation under Annex IV (high-risk)
  • Human oversight design with documented authority to intervene (high-risk)
  • Logging and post-market monitoring plan (high-risk)
  • EU database registration where the deployer is in scope (high-risk public-function deployments)

Timelines and enforcement

The Act's obligations phase in. Prohibitions applied from February 2025; general-purpose AI obligations from August 2025; high-risk obligations under Annex III apply from August 2026, with the harmonised-standards regime for high-risk products applying from August 2027.

Enforcement is by national competent authorities, with fines up to 7% of global turnover for prohibited-practice breaches, 3% for most other obligations, and 1.5% for supplying incorrect information to authorities. The fine exposure is meaningful; the reputational exposure is larger.

Do this on Monday

List every voice AI use case currently in production or in the next two quarters of roadmap. Mark each against the four Annex III triggers in the table above. The marked rows are your high-risk programme — start their documentation now.

Key takeaways
  • Most servicing voice AI is limited-risk — the obligation is a clear AI disclosure at the start of the call.
  • Annex III triggers (biometrics, essential services, credit, employment) push the deployment into high-risk.
  • Classification is per use case, not per platform — and the deployer makes the call.
  • Substantially modifying a high-risk system makes the deployer a provider in its own right.
  • Annex III obligations apply from August 2026 — the preparation runway is measured in months, not years.

Frequently asked questions

Is a customer service voice AI automatically high-risk?
No. A voice AI that books appointments, answers status queries, or takes payments is limited-risk under the Act. It only becomes high-risk when the use case falls within an Annex III category — biometric identification, essential-services eligibility, creditworthiness, employment, and a small number of others.
Does the transparency duty mean the AI cannot sound natural?
No. The Act is silent on voice naturalness. It requires that the caller be informed that they are interacting with an AI, in a clear and distinguishable manner, at the start of the interaction. A natural-sounding voice that introduces itself as an automated assistant meets the duty.
Who is responsible — the platform vendor or our company?
Both, in different roles. The vendor is the provider and carries the conformity, documentation, and registration obligations for the platform. Your company is the deployer and carries the transparency, monitoring, human-oversight, and (where in scope) fundamental-rights-impact-assessment obligations for how you use it. Neither role can be contracted away.
When do the obligations actually bite?
Limited-risk transparency obligations apply now. High-risk obligations under Annex III apply from August 2026 for new deployments and from August 2027 for systems already in operation at that date. Preparation timelines are tight if a deployment touches an Annex III category.

Terms used in this guide

  • Voice AIVoice AI is software that answers the phone, understands what the caller wants, and takes action — not just a smarter IVR.
Last reviewed: 2026-06-15. This guide is updated when production patterns shift; see the corrections page to flag anything that no longer matches reality.
About the author
Lewis Crook
Practitioner writer on enterprise voice AI

Lewis Crook — 20 years in enterprise technology, from FTSE 100 voice deployments to over a million AI-handled minutes a month across Asia-Pacific. Buyer, builder, and now working with CX leaders on enterprise voice AI. Writes The Voice AI Brief. Connect on LinkedIn. More about Lewis.

Newsletter
Liked this? Get the next edition.

Plus the Voice AI Readiness Diagnostic in the welcome email.

Welcome email includes the Voice AI Readiness Diagnostic. No second list, no extra form.