Why the Wrong Apology Can Hurt the Experience
DCX Links May 3, 2026
Welcome to the DCX weekly roundup of customer experience insights!
This week’s stories point to a blunt reality: customers don’t experience your strategy. They experience your operating model.
They feel the culture behind the script. They notice the gaps between teams. They remember whether loyalty was easy to use, whether service actually made things simpler, and whether your apology helped or just highlighted a problem they hadn’t noticed.
There’s also a clear signal for teams sprinting into AI. Smarter orchestration won’t cover broken journeys. It will expose them faster. The companies that pull ahead won’t be the ones with the flashiest tools. They’ll be the ones who know exactly where their experience works, where it breaks, and what their best customers are already trying to tell them.
Let’s dig in.
Join me on Thursday, May 7, for a lively discussion
A practical peer conversation for CX pros sharing what they’re trying, testing, and learning with AI to improve customer insight, journeys, operations, and support.
When: May 7 at 9:30 AM PDT
Length: 90 minutes
Location: Virtual
Cost: Free
Hosted by: Me
Reserve Your Spot
Space is limited, so everyone gets a voice
This week’s must-read links:
Culture Is the CX Operating System
Your Biggest Fans Are Telling You Where the Business Works
Agentic CX Will Expose Your Journey Gaps Faster
When “Sorry” Creates a Bigger CX Problem
DCX Stat of the Week: Customers are getting comfortable letting AI handle service problems for them
DCX Case Study of the Week: The Fresh Market Brings Loyalty Hospitality Into the App
I’m obsessed with Wispr Flow Pro! Get a Free Month Now!
Culture Is the CX Operating System
Shep Hyken’s point is simple: customers feel the culture long before they read the values. If employees work inside confusion, weak leadership, or performative customer-first language, that eventually leaks into the experience.
Inside job:
Customer experience starts with how leaders treat employees, set expectations, and model behavior.
The operating consequence:
Culture is not the poster on the wall. It is what people are allowed, rewarded, coached, and expected to do when the customer moment gets messy.
The leadership test:
If leaders want stronger loyalty, consistency, and NPS, they need to look at the internal experience first. Broken employee experience has a way of becoming a customer problem with a nicer dashboard.
The CX To-Do: Audit the employee friction behind your biggest customer complaints.
🔗 Go Deeper: Forbes
Your Biggest Fans Are Telling You Where the Business Works
Marcus Buckingham, author of the NY Times best-selling book, Design Love In, argues that companies should pay closer attention to their most devoted employees and customers. They are not sentimental outliers. They are evidence of what is already creating loyalty, performance, and advocacy.
The useful part:
Your fans show where the experience is working, not just where the brand is liked.
The CX angle:
Most companies over-study dissatisfaction and under-study devotion. Complaints tell you what to fix. Fans show you what to repeat, protect, and build around.
The leadership move:
Look for the conditions that create advocacy: the team behaviors, product moments, support experiences, and cultural habits that make people want to stay, buy, recommend, and defend the company.
The CX To-Do: Interview your biggest fans like they’re a roadmap, not a compliment.
🔗 Go Deeper: HBR.org
Agentic CX Will Expose Your Journey Gaps Faster
Jeannie Walters’ recent conversation with IBM leaders Betsy Rohtbart and Jay Trestain lands on a practical point: AI orchestration only works if the customer journey is already clear enough to be orchestrated.
The useful shift:
Rohtbart says teams should start with the task the customer is trying to complete, then design the experience so that task “pays off” consistently. That’s a cleaner standard than chasing personalization for its own sake.
The CX risk:
Customers feel the gaps between teams more than the moments teams proudly designed.
Secret shopping your own trial, onboarding, and service flows will show where the handoffs break. Annoying? Yes. Useful? Also yes.
The AI wrinkle:
Trestain frames agentic orchestration as AI agents working across enterprise workflows.
His warning is the keeper: governance is what turns pilots into value, because someone has to own decisions, KPIs, and what happens when the workflow fails.
The CX To-Do: Secret shop one journey before adding agents to it.
Go Deeper: Experience Action Pod
Also, congratulations to Jeannie on the release of her new bestseller, Experience is Everything!
When “Sorry” Creates a Bigger CX Problem
A good apology can rebuild trust. A badly timed one can teach customers they had a problem they did not even notice.
This HBR article makes a useful CX point: service recovery needs judgment, not reflex. Across five studies, including a food delivery field experiment, researchers found that apologizing for failures customers were unaware of reduced satisfaction, trust, recommendations, repeat purchases, and revenue.
The CX wrinkle:
Companies can now spot small service failures before customers do.
That makes proactive apology tempting.
The risk: the apology reframes a minor miss as a bigger failure.
The operating lesson:
If the customer complained, apologize.
If the customer clearly knows the failure happened, apologize.
If the issue is invisible, low harm, or uncertain, a neutral update may work better.
The CX To-Do: Build apology rules into recovery workflows. Don’t turn “sorry” into an automated panic button.
Go Deeper: Harvard Business Review
DCX Stat of the Week: Customers are getting comfortable letting AI handle service problems for them.
34% of people would prefer an AI assistant to contact customer service and fix issues without their intervention. EY also found that 16% of people globally have already used AI systems that act on their behalf in the past six months.
Takeaway: This is where CX gets interesting. Customers may not fully trust AI in the abstract, but they already use it when it saves time, reduces effort, or removes a hassle.
That changes the service standard. Your customer may not be the only one trying to resolve the issue. Their agent may show up, too.
Source: EY Global AI Sentiment Survey 2026
🔗 MORE STATS: Daily Stats on Substack Notes
DCX Case Study of the Week: The Fresh Market Brings Loyalty Hospitality Into the App
CX Challenge: Its 4-year-old loyalty program had value, but digital access was too hidden, and the name was hard for guests and associates to use clearly.
Action Taken: The grocer relaunched the program as TFM Rewards, built its first native app in-house with Cencosud’s digital factory, moved rewards to the app’s main navigation, added Club progress tracking, personalized offers, member events, and 5% off curbside orders of $60+.
Result: Post-relaunch performance isn’t reported yet, but the loyalty foundation is proven: the original program reached 1 million members in seven months. New benefits include 5% curbside savings and $5 birthday rewards.
Lesson for CX Pros: Don’t just add perks—make loyalty effortless to find, understand, and use across channels.
Quote: “We want to make it really easy for our guests to engage with us.” — Emily Turner, Chief Marketing Officer, The Fresh Market
Further Reading: Grocery Dive
Have a case study to share? Reply and let me know!
See you next week.
If this edition sparked ideas, share it with a colleague or team member. Let’s grow the DCX community together!
Join me on Thursday, May 7, for a lively discussion
A practical peer conversation for CX pros sharing what they’re trying, testing, and learning with AI to improve customer insight, journeys, operations, and support.
When: May 7 at 9:30 AM PDT
Length: 90 minutes
Location: Virtual
Cost: Free
Hosted by: Me
Reserve Your Spot
Space is limited, so everyone gets a voice
So the apology is basically the notification. You're ringing someone up to tell them they have a reason to be annoyed. Half the ops teams I've seen are about to automate their way into exactly this problem.