---
title: When Your Drive-Thru AI Can't Understand an Accent
description: McDonald's killed its AI drive-thru in 2024 because it could not understand an accent. Two years on, the industry is still working out why.
canonical: https://lukeocodes.dev/when-your-voice-agent-cant-understand-an-accent
type: article
locale: en_GB
published: 2026-06-12T00:00:00.000Z
modified: 2026-11-02T00:00:00.000Z
authors:
  - Luke Oliff
section: Voice AI
tags:
  - Voice AI
  - Developer Experience
  - Opinion
feed: https://lukeocodes.dev/rss.xml
search: https://lukeocodes.dev/search.json?q={query}
schema:
  - "@context": https://schema.org
    "@graph":
      - "@type": Organization
        "@id": https://ably.com/#organization
        name: Ably
        url: https://ably.com
      - "@type": WebSite
        "@id": https://lukeocodes.dev/#website
        url: https://lukeocodes.dev
        name: Luke Oliff
        alternateName: lukeocodes
        inLanguage: en
        publisher:
          "@id": https://lukeocodes.dev/authors/luke#person
        description: Personal blog and writing by Luke Oliff — developer relations, voice AI, developer experience.
        potentialAction:
          - "@type": SearchAction
            target:
              "@type": EntryPoint
              urlTemplate: https://lukeocodes.dev/blog/search?q={search_term_string}
            query-input: required name=search_term_string
      - "@type": Person
        "@id": https://lukeocodes.dev/authors/luke#person
        name: Luke Oliff
        url: https://lukeocodes.dev/authors/luke
        description: Staff engineer and Staff Tech Lead for Developer Experience at Ably. Writing about developer relations, AI, and the voice industry, from the UK.
        mainEntityOfPage: https://lukeocodes.dev/authors/luke
        givenName: Luke
        familyName: Oliff
        image: https://lukeocodes.dev/authors/luke.jpg
        jobTitle: Staff Tech Lead, Developer Experience
        worksFor:
          "@id": https://ably.com/#organization
        sameAs:
          - https://www.linkedin.com/in/lukeocodes
          - https://github.com/lukeocodes
          - https://bsky.app/profile/lukeocodes.dev
          - https://x.com/lukeocodes
          - https://hashnode.com/@lukeocodes
          - https://dev.to/lukeocodes
        knowsAbout:
          - Developer Relations
          - Developer Experience
          - Voice AI
          - Text-to-Speech
          - Answer Engine Optimisation
          - Search Engine Optimisation
          - Open Source
          - Developer Tooling
          - API Design
          - Speech-to-Text
          - Voice Agents
          - Community Building
        knowsLanguage:
          - English
        nationality: British
        alumniOf:
          - "@type": Organization
            name: The Open University
  - "@context": https://schema.org
    "@graph":
      - "@type": Organization
        "@id": https://ably.com/#organization
        name: Ably
        url: https://ably.com
      - "@type": Person
        "@id": https://lukeocodes.dev/authors/luke#person
        name: Luke Oliff
        url: https://lukeocodes.dev/authors/luke
        description: Staff engineer and Staff Tech Lead for Developer Experience at Ably. Writing about developer relations, AI, and the voice industry, from the UK.
        mainEntityOfPage: https://lukeocodes.dev/authors/luke
        givenName: Luke
        familyName: Oliff
        image: https://lukeocodes.dev/authors/luke.jpg
        jobTitle: Staff Tech Lead, Developer Experience
        worksFor:
          "@id": https://ably.com/#organization
        sameAs:
          - https://www.linkedin.com/in/lukeocodes
          - https://github.com/lukeocodes
          - https://bsky.app/profile/lukeocodes.dev
          - https://x.com/lukeocodes
          - https://hashnode.com/@lukeocodes
          - https://dev.to/lukeocodes
        knowsAbout:
          - Developer Relations
          - Developer Experience
          - Voice AI
          - Text-to-Speech
          - Answer Engine Optimisation
          - Search Engine Optimisation
          - Open Source
          - Developer Tooling
          - API Design
          - Speech-to-Text
          - Voice Agents
          - Community Building
        knowsLanguage:
          - English
        nationality: British
        alumniOf:
          - "@type": Organization
            name: The Open University
      - "@type": BlogPosting
        "@id": https://lukeocodes.dev/when-your-voice-agent-cant-understand-an-accent#article
        headline: When Your Drive-Thru AI Can't Understand an Accent
        alternativeHeadline: When Your Drive-Thru AI Can't Understand an Accent
        description: McDonald's killed its AI drive-thru in 2024 because it could not understand an accent. Two years on, the industry is still working out why.
        datePublished: 2026-06-12T00:00:00.000Z
        dateModified: 2026-11-02T00:00:00.000Z
        url: https://lukeocodes.dev/when-your-voice-agent-cant-understand-an-accent
        mainEntityOfPage: https://lukeocodes.dev/when-your-voice-agent-cant-understand-an-accent
        inLanguage: en
        author:
          - "@id": https://lukeocodes.dev/authors/luke#person
        isPartOf:
          "@id": https://lukeocodes.dev/#website
        keywords: Voice AI, Developer Experience, Opinion
        articleSection: Voice AI
        about:
          - "@type": Thing
            name: Voice AI
          - "@type": Thing
            name: Developer Experience
        abstract: "Friday fun: a fast food chain spent three years and millions of dollars on AI voice ordering at over 100 drive-thrus. The system could not tell the difference between a quarter pounder and a what-now? because a customer with a regional accent said it differently than the training data expected."
        speakable:
          "@type": SpeakableSpecification
          cssSelector:
            - .post-tldr
            - h1
        image: https://lukeocodes.dev/og.png?h=When+Your+Drive-Thru+AI+Can%27t+Understand+an+Accent&d=McDonald%27s+killed+its+AI+drive-thru+in+2024+because+it+could+not+understand+an+accent.+Two+years+on%2C+the+industry+is+still+working+out+why.&e=Writing
        wordCount: 700
        timeRequired: PT4M
        publisher:
          "@id": https://ably.com/#organization
      - "@type": BreadcrumbList
        itemListElement:
          - "@type": ListItem
            position: 1
            name: Home
            item: https://lukeocodes.dev
          - "@type": ListItem
            position: 2
            name: Writing
            item: https://lukeocodes.dev/blog
          - "@type": ListItem
            position: 3
            name: When Your Drive-Thru AI Can't Understand an Accent
            item: https://lukeocodes.dev/when-your-voice-agent-cant-understand-an-accent
---

[Luke Oliff.](/)

- [Blog](/blog)
- [CV](/cv)
- [Uses](/uses)
- [User manual](/user-manual)
- [Living with ADHD](/living-and-working-with-adhd)
- [RSS](/rss.xml)

[Luke Oliff · Writing](/blog)

# When Your Drive-Thru AI Can't Understand an Accent

Jun 2026 · Updated Nov 2026 · [Voice AI](/blog/category/voice-ai) · 4 min read · [Luke Oliff](/authors/luke)

Friday fun: a fast food chain spent three years and millions of dollars on AI voice ordering at over 100 drive-thrus. The system could not tell the difference between a quarter pounder and a what-now? because a customer with a regional accent said it differently than the training data expected.

McDonald's ended its partnership with IBM in 2024 after viral clips showed the AI adding items nobody ordered, ignoring mid-order corrections, and just generally losing the plot whenever a customer didn't sound like the studio recordings it was trained on. By June 2026, the chain was piloting a Google-built system called ArchIQ at five locations, trying again.

I worked at Deepgram for years, and the restaurant accent problem was a recurring conversation in our Slack. Not because any of us were building drive-thru systems specifically. Because the core problem applies to every voice AI deployed in the real world: if your ASR model was trained on clean audio from a narrow demographic, it will fail on anyone who sounds different.

Deepgram published research on this exact topic on June 9, 2026. The article showed how accent variability in automatic speech recognition undermines multi-region voice ordering. It cited the McDonald's pilot as a case study: an ASR layer that works fine in the lab breaks in production because the training data did not cover how people in different regions actually speak.

This is not a hard problem to understand. It is a hard problem to solve because gathering diverse accent data is expensive, and most companies optimize for the demo, not the long tail of real users. The demo works in a quiet room with a clear speaker. The drive-thru at lunch rush with road noise, a teenager in the back seat, and a customer who says "warter" instead of "water" is a completely different system.

The Taco Bell AI had its own viral moment: a customer reportedly ordered 18,000 cups of water to force a handoff to a human. Wendy's FreshAI handled it better, but it too needed human backup about 21% of the time per industry benchmarks from that period. The gap between 79% autonomous and 95% with human support tells you everything about where the ceiling actually sits in mid-2026.

I think about this when I hear people talk about voice AI replacing cashiers. The tech is good, and it gets better every quarter. But accents are not a bug to be squashed in a sprint. They are a fundamental data problem. If your training set has 50 voices from California and zero from Glasgow, your system does not work in Glasgow. That is not a model fix. That is a data fix, which means time, money, and a recording strategy that covers the actual population.

McDonald's second attempt might work better. Google has more data than IBM did, and ArchIQ is processing about a million transactions with 90 percent autonomy by the franchisee reports. But the accent problem does not go away with more compute. It goes away with more representative data. And that is the kind of boring, expensive, undramatic work that does not make headlines but makes voice AI actually work for everyone.

### FAQ

**Why did McDonald's end its IBM AI drive-thru pilot in 2024?**
The pilot ran for three years across more than 100 locations. McDonald's ended it after accuracy issues became public. The core technical problem was accent and dialect interpretation: the ASR model could not reliably understand how customers from different regions spoke, leading to incorrect orders and viral social media clips of failures.

**How accurate was AI drive-thru ordering in 2026?**
Independent benchmarks from mid-2026 showed AI systems handled about 79 percent of orders without human intervention on average. When human staff supported the AI, accuracy rose to roughly 95 percent. The gap highlights how accent variability, background noise, and mid-order corrections were still the main failure modes.

**What is Deepgram's connection to restaurant voice AI?**
Deepgram published research on June 9, 2026 showing how accent variability in ASR layers undermines multi-region voice ordering. The research used McDonald's pilot termination as a case study and introduced techniques like Keyterm Prompting and per-region testing to keep accuracy stable across different accents.

[← Newer: My Voice Was Cloned Before Lunch on Day One](/my-voice-cloned-day-one-speechify)

[All posts](/blog) →

## Search this site

`GET https://lukeocodes.dev/search.json?q=<words>` returns matching posts as JSON, each with its page URL and its markdown URL. Add `&limit=<1-50>` for more than 10. How it works: [/blog/search](https://lukeocodes.dev/blog/search.md).

```sh
curl "https://lukeocodes.dev/search.json?q=developer+relations"
```

---

© 2026 Luke Oliff. Posts live at the root of this site.

- [GitHub](https://github.com/lukeocodes)
- [LinkedIn](https://www.linkedin.com/in/lukeocodes)
- [X](https://x.com/lukeocodes)
- [Bluesky](https://bsky.app/profile/lukeocodes.dev)
- [Email](mailto:luke@lukeoliff.com)
- [RSS](/rss.xml)

## Cookies

This site sets one analytics cookie, from Google Analytics, and only in a browser that accepts the cookie banner. A client that does not run scripts sets no cookies, so there is nothing to accept or decline here.

[Cookie policy](/cookies)
