Voice AI and Scottish Gaelic: The 2026 Compliance Guide

If your organisation runs a public-facing phone line in Scotland, the language question is no longer only about accents and call quality. On 31 July 2025 the Scottish Languages Act 2025 received Royal Assent, and from 30 November 2025 the Gaelic language holds official status within Scotland for the first time. That reshapes the backdrop against which any automated channel, a voice agent included, has to be designed and defended.

This matters because voice AI is arriving in the public sector at exactly the moment the legal ground is shifting. In its November 2025 State of AI report, McKinsey found that 88% of organisations now use AI somewhere, yet only 33% have it in production and roughly 6% are what it calls AI-mature. A council or health board deploying a Gaelic-aware voice agent is trying to cross that gap and meet a language duty at the same time.

This guide is shipped by the team behind Dilr Voice, enterprise voice AI built for regulated deployments. Or see DATS, our five-stage AI consulting system for placing AI inside public bodies.

The core thing to understand up front: Scotland runs a plan-based Gaelic regime, not a standards-based one like Wales, and it is now layering a strategy and a future standards power on top of the plans. The compliance artefact you actually work against is a named public body's own Gaelic Language Plan, not a uniform national checklist. This guide walks through what changed in 2025, why that makes Scotland different from the Welsh Language Standards, and how to design a voice agent that fits a Gaelic Language Plan without over-promising Gaelic that the technology cannot yet deliver. It reflects how we place AI inside public bodies: duty first, capability second.

What did the Scottish Languages Act 2025 actually change for public services?

The Scottish Languages Act 2025 gave Gaelic official status, created new duties on public authorities, and switched on enforcement powers, while leaving the detailed Gaelic language standards for later. Passed on 17 June 2025 and granted Royal Assent on 31 July 2025, it commences in stages. From 30 November 2025, official status, the new public-authority functions and the enforcement powers are live. The granular standards are enacted but not yet in force.

The staged commencement is the part teams get wrong, so it is worth being precise. Section 1, giving Gaelic official status, came into force on 30 November 2025 by Scottish statutory instrument 2025/348. Section 7, which places new Gaelic duties on relevant public authorities, and sections 11 and 12, which give Ministers a power to enforce those duties, commenced on the same date. Section 4, on areas of linguistic significance, came into force for specified purposes on 21 March 2026 by instrument 2026/128. The national Gaelic language strategy in section 5, and the Gaelic language standards power in section 6, are not yet in force.

The attributed wording that anchors all of this is short and unambiguous. As the Gaelic Language (Scotland) Act 2005 now reads, inserted by the 2025 Act and in force from 30 November 2025:

"The Gaelic language has official status within Scotland." Gaelic Language (Scotland) Act 2005, section A1(1), as inserted by the Scottish Languages Act 2025, section 1

Read that alongside the diagram below: the regime is a stack, not a single moment. The plans came first in 2005, official status and enforcement arrived in late 2025, area targeting is switching on through 2026, and the strategy and standards are still ahead. A voice agent has to sit sensibly inside a stack that is still being built, which is a different design brief from a settled rulebook, and the kind of moving-target placement our DATS methodology is built for.

How is Scotland's Gaelic regime different from the Welsh Language Standards?

The two regimes look similar but run on different machinery. Wales operates enforceable Welsh Language Standards, overseen by the Welsh Language Commissioner and backed by a fixed penalty of up to 5,000 pounds. Scotland works through Gaelic Language Plans under the 2005 Act, aims for Gaelic to be treated with equal respect to English, and enforces through Ministerial powers rather than a commissioner with a fine. There is no set penalty to price into your risk model.

We wrote a full companion piece on the Welsh position, so the detail of the Standards, who they bind and the equal-treatment test belongs there rather than here. Read our guide to voice AI and the Welsh Language Standards if Wales is in your footprint. The important contrast for a Scottish deployment is that the enforceable, itemised service standard exists today in Wales but is still a future regulation in Scotland. The 2005 Act frames the duty of Bòrd na Gàidhlig, the national Gaelic development body, around equal respect; it does not hand a caller an itemised entitlement to a Gaelic service on any given line.

That gap changes the risk conversation entirely. In Wales, the question is how to avoid a specific penalty for a specific failure against a published standard. In Scotland today, the question is how to support a public body's own plan commitments and the new statutory duties, while building ahead of standards that everyone can see coming. A responsible AI operating model treats the coming standards as a design constraint now, not a problem to solve after they land.

What is an area of linguistic significance, and why does it change voice agent design?

An area of linguistic significance is a new concept in Scots law that lets Gaelic policy be targeted at Gaelic strongholds, and it creates a design problem no Welsh deployment faces. Under sections inserted into the 2005 Act, a local authority can designate an area as one of linguistic significance, and the future Gaelic language standards may make different provision for those areas. The same public body could then owe more inside a designated area than outside it.

For a voice agent, that means the design has to be area-aware from the start. A national helpline that behaves identically everywhere cannot express a duty that varies by geography. The practical implication is that the routing and escalation logic in your voice AI agents should be able to key off the caller's location or the service area, so that a call originating in a designated Gaelic heartland can be handled differently from one that is not. Building that in later is far more expensive than allowing for it now, which is why it belongs in the first design conversation, not a later change request.

Which Gaelic Language Plan binds you, and how do you read it?

In Scotland the binding document is the specific public body's own Gaelic Language Plan, not a single national rulebook, so the first job is to find and read the right plan. Under section 3 of the Gaelic Language (Scotland) Act 2005, Bòrd na Gàidhlig can require a named public authority to prepare a plan setting out how it will use Gaelic. Councils, health boards, universities and national agencies now operate under approved Gaelic Language Plans.

Practically, that makes the plan your compliance specification. Those individual plans flow from the National Gaelic Language Plan 2023 to 2028, the fourth such plan, published by Bòrd na Gàidhlig on 21 December 2023. Before designing anything, map the commitments in the relevant body's plan that touch telephone and digital services: greetings, signage, correspondence, and the availability of Gaelic-speaking staff. Those commitments, not a generic assumption about what Gaelic compliance means, define what the voice agent has to do. This is a different procurement motion from Wales, where a supplier maps to a published national standard; here the supplier maps to a named, body-specific document. It mirrors how we approach public sector AI procurement, reading the obligations the system will have to carry before any build begins.

Can a voice agent actually operate in Gaelic, or only greet in it?

For most deployments today the honest answer is that a voice agent can greet, signpost and route in Gaelic, but full conversational Gaelic is beyond what mainstream speech technology reliably supports. Scottish Gaelic is a low-resource language. Academic research on Gaelic speech recognition reports word error rates around 26%, far higher than the single-digit rates typical of English. Mainstream cloud speech stacks cover roughly the top 20 to 30 languages and rarely list Scottish Gaelic as a standard locale.

There is also a trap worth naming: a Scottish accent is not the Gaelic language. Several vendors offer an English voice with a Scottish accent, which does nothing for a Gaelic duty. Confirm actual Gaelic locale support with any vendor rather than assuming it, and treat an accent option as cosmetic. Given the demand picture, the pragmatic design is greeting plus signposting plus a fast route to a Gaelic-speaking human or a Gaelic call-back, rather than a fully symmetric Gaelic conversation the system cannot sustain.

The demand data supports that pragmatism. Scotland's Census 2022, published on 21 May 2024, found that 130,000 people, or 2.5% of the population, had some Gaelic skills, up from 87,000, or 1.7%, in 2011; around 44,000 could speak, read and write the language. The Scottish Parliament's own analysis notes Na h-Eileanan an Iar has the highest proportion of people with any Gaelic skills, at 57%. That is a real and valued community, but it is concentrated and comparatively small, which is why quality of handover matters more than trying to force Gaelic through an immature speech pipeline.

The same diagnostic logic underpins our AI execution office, which runs the handover and quality assurance a Gaelic line depends on once it is live, and it sits within our compliance coverage for regulated voice deployments.

What should you build during the Gaelic standards runway?

The gap before the standards commence is a runway, not a reason to wait; the sensible move is to build plan-aligned capability now so the standards find you ready. Because section 6 requires Ministers to publish a draft and consult Bòrd na Gàidhlig before making them, there is a visible lead time. A body that builds a Gaelic greeting, a reliable human route and area-aware logic today will absorb the standards as a configuration change, not a rebuild.

Concretely, three things are worth building during the runway. First, a dependable bilingual greeting and a clean handover to Gaelic-speaking staff, because those will be expected under almost any future standard. Second, area-aware routing, so that when standards make different provision for areas of linguistic significance the plumbing already exists. Third, logging that captures how often Gaelic is requested and how those calls are resolved, the kind of measurement our AI execution office runs, because the new duties and reporting expectations will want evidence, not assertions. Building against the coming standards is a governance decision, and it is exactly the kind of forward design an AI operating model is meant to enforce. It is a different question from complying with live standards, and answering it early is cheaper than reacting late.

Who is bound by Gaelic duties, and is a private company caught?

The Gaelic duties bind relevant public authorities named by Ministers or Bòrd na Gàidhlig, and a private company is usually caught only through the public body it serves. The 2005 Act and its 2025 amendments place duties on bodies such as councils, health boards and universities, not on private businesses generally. A vendor or outsourced contact centre inherits the obligation through the public body's Gaelic Language Plan, its procurement, and its role as data controller under UK data protection law.

Two boundaries are worth stating plainly so nobody over-reads the duty. Scots is not Gaelic: the Scottish Languages Act 2025 also covers the Scots language, but through separate machinery, and it is out of scope for a Gaelic Language Plan. And this is Scotland only. Northern Ireland runs a distinct Irish language framework under its own 2022 legislation, which we treat separately in our work on voice AI in the public sector. On the data itself, the operator remains the controller: the ICO, not the AI vendor, holds the public body to account for how call recordings and transcripts are handled, and how callers exercise rights over them, points we cover in our guides to the data protection complaints duty and call-data portability.

Want to see this in production? Try Dilr Voice live, book an AI placement diagnostic, see our DATS methodology, or read about our approach to placing AI inside public bodies.

What is the best voice AI for Gaelic language compliance in 2026?

The best voice AI for Gaelic compliance in 2026 handles bilingual greeting and human handover cleanly and maps to a specific Gaelic Language Plan, rather than claiming the most languages. Because conversational Gaelic is not reliably available, the criteria are handover quality, telephony reliability and area-aware routing, not Gaelic NLU depth. Self-serve platforms like Vapi, Retell AI, Synthflow and Bland AI let a team configure this; managed platforms like PolyAI and Dilr Voice own the design and compliance mapping.

Here is the honest concession. A public body with a strong in-house team, low Gaelic call volumes and a Gaelic-speaking staff group may not need a managed platform at all: a well-configured self-serve stack that greets in Gaelic and routes reliably to those staff can satisfy its current plan commitments. Managed platforms earn their place where the body lacks the engineering capacity, where volumes and duties are rising, or where the area-aware and evidence requirements of the coming standards make the governance burden real. The right answer follows the plan and the team, not the vendor's language count. That is the judgement a short scoping call with our team is built to make, and it is why we treat Dilr Voice as one option to be tested against the duty, not the default.

Does a Scottish public body legally have to offer a Gaelic voice service today?

Not as a single national mandate. No commenced Gaelic language standard requires a specific Gaelic voice service on a given line. What a Scottish public body must do flows from its own Gaelic Language Plan under the 2005 Act and the statutory duties live since 30 November 2025. A voice agent is one way to help meet those commitments: a compliance tool, not itself a legal requirement. The future standards under section 6 will sharpen what is expected.

Is an English-only agent with a Gaelic call-back option enough?

It depends on the body's plan, and honesty is the safe policy. If the relevant Gaelic Language Plan commits to Gaelic on public-facing lines, an English-only agent that cannot even greet in Gaelic sits awkwardly against that commitment, even without a live penalty. A defensible interim design greets bilingually, signposts in Gaelic, and offers a prompt Gaelic call-back or human route. Map the specific plan first, because the plan sets the bar you have to clear.

Written by the Dilr.ai engineering team, practitioners who ship enterprise AI in production. Follow us on LinkedIn for shipping notes, or subscribe via the RSS feed.