What 100 operators, 115,000 tickets, and a new benchmark taught us at Commerce on Autopilot.
You can automate most of your support volume without hurting CSAT. That was the thesis of our NYC panel, and both the data and the operators in the room backed it up.
On July 14 we co-hosted Commerce on Autopilot with Shopify at their SoHo space, as part of our AI+CX Club. Around 100 CX and ops leaders filled the room over wine and cheese, out of roughly 400 who registered, and Shopify's official numbers are still landing. The crowd skewed toward smaller merchants this time, but the engagement was the real signal. The topic clearly landed, and a handful of conversations are worth following up on.
The panel ranged wider than support, into Shopify's bigger AI push and how bots are starting to read your store, and we'll get to that. But the heart of the night was customer experience, and one question ran underneath all of it: how far can you automate before quality slips? The answer, it turns out, is a lot further than most teams assume.
The headline numbers
Three findings from The State of CX Automation in Ecommerce 2026 framed the night:
- Top merchants sustain up to 87% automation, and that ceiling is universal. It isn't about how big you are or which helpdesk you run.
- Automating more didn't cost brands their CSAT. The ones automating the most kept customers just as happy.
- Across 100+ merchants, the report modeled about 86,000 agent-hours saved. The gap between good and great is setup and consistency, not smarter AI.
The trade-off everyone fears doesn't exist
Start with the myth the whole room came in carrying: automate aggressively and customers get frustrated. The data said the opposite, and Guillaume Luccisano, our CEO, put it bluntly.
The one that genuinely surprised me was that automating more didn't cost anyone their CSAT. Everyone assumes there's a trade-off, automate aggressively and customers get frustrated. The data showed the opposite: the brands automating the most were keeping customers just as happy as the ones barely automating. The trade-off everyone's afraid of basically doesn't exist.
Guillaume Luccisano, CEO, Yuma
Why does it hold? Because speed matters to customers more than a human does. A fast, correct answer beats a slow one from a person, almost every time. The second surprise in the data was how much quiet work this represents.
We're talking 86,000 agent-hours of work that just quietly disappears. When you see it in aggregate, you realize how much of a support team's day is spent on tickets that never needed a human in the first place.
Guillaume Luccisano
What 115,000 tickets a quarter actually feels like
Then Naomi Oriol, Head of CX at Freebird, grounded it in reality. Her team handled more than 115,000 tickets last quarter, automated the bulk of it, and held CSAT at 4.42. That's roughly 1,200 to 1,400 tickets a day, and it doesn't arrive evenly, a product drop or a shipping delay and it doubles overnight.
The before picture will be familiar to anyone in the room: the whole team living in the queue, triaging from the moment they logged on, a backlog that never quite hit zero. It felt like firefighting more than customer experience. What changed after automation wasn't the volume, it was that most of it stopped reaching a person.
The team question came up fast, and Naomi was clear: they didn't cut headcount, they repointed it. First response times went from hours to minutes, and her agents stopped copy-pasting tracking links and started handling the genuinely hard cases, the high-emotion and high-value conversations, plus maintaining the knowledge base and reviewing what the AI was doing. Her best people became CX operators instead of ticket-clearers.
The most useful moment was the honest one. Freebird got greedy early and switched automation on for a category before the knowledge behind it was deep enough.
The AI was confident and wrong on some edge cases, which is worse than being slow. The lesson was blunt: the AI is only as good as the knowledge and the guardrails you give it. Automating fast is easy. Automating well is a knowledge problem, not an AI problem.
Naomi Oriol, Head of CX, Freebird
So how do you hold a 4.42 through that kind of volume? Naomi's answer was mostly unglamorous. Treat the knowledge base as a living product, not a one-time setup. Review AI outputs every week, not just when something goes wrong. Keep humans firmly in the loop on the edge cases and anything high-stakes. And watch CSAT per workflow, not just the top-line number, so a dip shows up in one ticket type before it drags the whole score down.



















