/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Google declines to provide the names of hair salon and restaurant used in controversial Google Duplex demo, or say whether the calls were edited

Over the years, I have experienced some great demos. Chris Davies / SlashGear : Google is suspiciously quiet about its incredible Duplex AI demo Shawn Knight / TechSpot : Did Google fake its Google Duplex AI demo? Alan Boyle / GeekWire : Worried about fake news? Get ready for the rise of fake humans that sound just like us MacDailyNews : What Google isn't telling us about its ‘Duplex’ AI demo Joe Maring / Android Central : That Google Duplex demo at I/O may not be as impressive as we think Daring Fireball : Axios Looks Into Google's Duplex Demo Tweets: Scripting Com / @davewiner : Google didn't prepare for the obvious questions because the tech press never asks any. The kinds of questions they get are like “How great are you?” Stuff like that. Keep going. There are lots of unreported stories. Big ones. http://www.vanityfair.com/... Steve Troughton-Smith / @stroughtonsmith : What a load of crap. Who the heck cares how much of this was staged? iPhone was introduced with screenshots-posing-as-apps, that didn't mean anything. They don't need to fake the tech, because this can be done with today's technology, and Google's best at it. Actors? So what? http://twitter.com/... @om : “Google may well have created a lifelike voice assistant...Or it was partially staged. Or something else entirely. We just don't know, because Google won't answer the questions.” @danprimack doing what journalists are supposed to do. Verify and dig deeper! http://www.axios.com/... Scripting Com / @davewiner : Finally journalism starts asks obvious questions of tech. Tech journalism has never asked basic questions like “how did you do this?"Apple once used my software to demo their tech, which wasn't ready.Reporters refused to ask about this. http://twitter.com/... Luther Lowe / @lutherlowe : A few more Qs to consider, @danprimack: - How is AI trained? (h/t @peard33) - Any data besides holiday hours collected (Accepts Amex, etc)? - What triggers the data collection? - Is this being used at scale now? Their last statement raised more Q than A http://www.techmeme.com/... http://twitter.com/...

Axios Dan Primack

Context & Ripple Effects

A week after Google's I/O stage demo of Duplex — an assistant built to sound human on the phone — triggered widespread pushback over how uncanny it was, Axios pressed the company on basic provenance: which hair salon and restaurant took those calls, and were the recordings edited? Google declined to answer either question, leaving the most-hyped demo of the show unverified.

The silence matters because the follow-up reporting did not let it stand: days later, a source told Bloomberg that some of the demo calls had been edited, ostensibly to protect the businesses involved. The episode sits between the initial backlash and Google's June move to confine Duplex to a small group of trusted testers and businesses that explicitly opted in to receiving calls.

First-order effects

  • Google's refusal to name the two businesses or confirm the tapes' integrity keeps the authenticity question open, turning press scrutiny from the demo's impressiveness toward whether it was staged.

Second-order effects

  • The credibility hit pushes Google to restructure Duplex's deployment around consent — the trusted-tester program restricts calls to businesses that have opted in, making disclosure a product requirement rather than a demo choice.

Third-order effects

  • If the pattern holds, high-stakes AI demos get audited after the fact by reporters, forcing companies to ship narrower, disclosed versions of what they showed on stage — as Google eventually did with a quiet, limited haircut-booking rollout of Duplex rather than the broad phone assistant from the keynote.

The trend: Voice AI is moving from theatrical keynotes to consent-based deployments, with post-demo scrutiny acting as the gate between what companies claim and what they are allowed to run.