Your daily signal on AI and CX — minus the hype.

In this issue:

→ The customer is real. The payment may not be.
→ A warning has to do more than protect the bank
→ AI search isn’t replacing Google. Customers use both.
→ Adobe follows the journey before the click
→ Europe buys time. Security teams still have work.

🔍 DEEP DIVE

The Customer Passed. The Payment Still Looks Wrong.

The credentials checked out. The device looked familiar. The customer approved the transfer.

So the payment goes through?

Maybe. The person holding the phone could still be following a scammer’s instructions.

Behavioral biometrics looks at what happens after login: the pauses, swipe patterns, touch pressure, device angle, and other small changes that suggest this session doesn’t feel normal. It is trying to answer a harder question than “Is this the right person?”

Is this person acting freely?

Lloyds Banking Group is testing where payment warnings appear, how they are worded, even their color and prominence. That sounds like a design choice. It isn’t. A warning that arrives too late or reads like legal boilerplate is basically compliance furniture.

But this gets messy fast. A pause might mean coercion. It might also mean distraction, disability, a new device, or a customer who simply needs a minute. Q2 Holdings says an anomaly should lead to human review, not make the decision by itself.

The bank needs more than a risk score. It needs a sensible way to slow the journey down without turning every unusual customer into a suspect.

Bottom Line: Stopping the scam matters. So does helping the legitimate customer finish.

Source: FinTech Futures

🧭 OPERATOR PLAYBOOK

Run the Awkward-Customer Test

Take a payment your system would flag. Now put four perfectly legitimate customers through it:

1. Someone using a new phone.

2. Someone distracted by a child or another conversation.

3. Someone receiving legitimate help.

4. Someone interacting differently because of an accessibility need.

Watch what happens. Does the warning explain the concern? Can the customer prove the payment is legitimate without starting over? And if they get stuck, does anyone actually own the recovery?

Ask your team: What evidence turns a warning into a decline?

Signal: The fraud model spots the risk. The customer experience is what happens next.

📊 MARKET REALITY CHECK

AI Was Supposed to Eat Search. Customers Didn’t Get the Memo.

EMARKETER found that 82% of weekly AI users still use Google Search every day, compared with 71% of all U.S. internet users.

That doesn’t mean AI causes heavier search use. It does kill the neat little story that one channel is replacing the other.

Customers are bouncing between them. Ask AI for an answer. Check Google for options. Visit the brand to see if any of it is true. Sometimes they do it in the opposite order.

Why it matters: Your product facts, policies, pricing, availability, and recovery instructions need to agree wherever the customer looks. If AI says one thing, search says another, and your site says a third, the customer gets the cleanup job.

🧰 TOOL WORTH KNOWING

See What AI Said Before the Customer Arrives

What it does: Adobe LLM Optimizer shows where a brand appears in AI answers, what gets cited, how the brand is described, and whether that visibility sends anyone to the site.

CX use case: A customer finds your product through an AI answer, checks a few alternatives, then lands on your site. Your team can see what the assistant said, which source it used, and whether the visit led anywhere useful.

Worth watching because: A lot of AI-search tools stop at “your brand was mentioned.” Nice chart. Limited help. Adobe is trying to connect that mention to the customer’s next move while flagging wrong answers and missing content along the way.

Bottom line: If AI shapes the expectation, CX needs to see what happened before the click.

📡 90-SECOND CX RADAR

Europe just moved the AI deadlines

The EU AI Omnibus entered into force July 27. High-risk AI rules now start December 2, 2027, with more time for AI built into physical products. It also drops a standardized post-market monitoring plan.

Why it matters: If your AI plan depended on one date sitting in a slide deck, change the slide. Don’t dismantle the testing, ownership, or recovery work customers still need.

AI security builders organize around the whole stack

NVIDIA and industry partners launched the Open Secure AI Alliance to share security tools for AI and agents. The work covers identity, permissions, guardrails, logs, evaluations, and the model itself.

Why it matters: The model can behave perfectly and the agent can still have too much authority. Security has to follow the whole customer task, including what the agent can access, change, and approve.

✅ YOUR MOVE

Find one AI-driven journey where a risk score can stop a real customer.

Sit down with Fraud, Service, and Accessibility. Run the awkward cases, not the clean demo. Then ask three questions: What will the customer see? Who can step in? How do they finish without starting over?

If the only choices are “allow” and “decline,” you’re not done.

A strange signal deserves a closer look, not an automatic guilty verdict.

Until tomorrow,

I’m obsessed with Wispr Flow Pro! Get a Free Month on me.

What they’re missing is someone who notices when customer behavior starts contradicting the assumptions the strategy is built on, can say what that costs, and can help the company do something about it.

That should be the Chief Experience Officer’s job.

The real question was never whether the role exists. It’s whether the person in it can actually change a decision.

Plenty can’t.

Some companies get along fine without a CXO. Others hand out the title and then keep the person miles away from anything that matters.

And I’ve met CXOs who can describe customer pain in exhaustive detail but go quiet the moment you ask what the company should stop doing, or which risk it should just live with. That’s not a knock on the role. It’s the bar the good ones clear.

The Customer Gets the Whole Company

Companies are built to split work apart.

Customers get the thing after it’s been glued back together. Inside, a problem lives across three budgets and four owners.

Outside, it shows up as one experience, under one logo.

Somebody has to see what all those separate decisions turn into by the time they reach a customer. That’s the CXO. Not the person who cares the most, but the one who can show the company the customer and commercial consequences of its choices at the same time. It’s a job about the whole business. That’s why it belongs near the top of it.

Reading the Road Isn’t Enough

I keep coming back to rally racing. I don’t know much about rally racing, but I do know that the driver handles the car and the co-driver reads pace notes for the road ahead: where the next corner tightens, what’s over the crest. And the co-driver isn’t there to say “slow down.” The point is the opposite: knowing what’s coming lets the driver push harder.

That’s the partnership a CEO should want.

But the metaphor only takes you so far. A CXO who spends the whole race calling out hazards from the passenger seat hasn’t done the job. They also have to help change the conditions creating the hazards in the first place. Spot a recurring problem but fail to get the organization to move on it, and all you’ve bought is a better view of the wreck.

This is where CX leaders get made, or found out.

Bringing the “voice of the customer” into the room has value. But showing people evidence of pain is not the same as giving them advice. The ones who earn the seat tend to do three things the others don’t.

• They talk in tradeoffs, not complaints. Sometimes the right call is to accept a worse experience. Not every complaint deserves a company-wide response, and some friction isn’t worth the money to remove. A credible CXO knows where being excellent actually wins you something, where good-enough is fine, and where you’re spending real money polishing something no customer will ever notice.

• They’re in the decision before the budget is. The advice has to land while the choice is still soft, before priorities are locked, and everyone’s just looking for validation.

• They follow the cost, not just the benefit.

When the Metric Stops Counting

That third one is the part almost everyone misses.

A decision’s benefit gets measured right where the decision was made. The cost often shows up somewhere else, months later, long after someone already declared victory. The metric wasn’t lying. It just counted the win where it happened and never went looking for the bill.

Take Starbucks. In April 2024, the company said a mid-teens percentage of mobile orders were being abandoned before purchase. People gave up over long waits and out-of-stock items.

The slide was already happening: North American comparable sales down 3 percent, transactions down 7. Those abandoned orders weren’t an early-warning light blinking off to the side of the numbers. They were the numbers. Customers were walking up to the digital front door and turning around.

Management said it had a handle on it.

By Q4, U.S. comparable-store sales were down 6 percent on a 10 percent drop in transactions, and EPS fell 25 percent. CX wasn’t the whole story. Starbucks also pointed to competition and a soft China. But the company’s own account connected the experience to the behavior: incoming CEO Brian Niccol said customers had decided Starbucks was a hassle and were coming in less.

You can file an abandoned order as a conversion problem. Or you can read it as a sign the operation can’t deliver the convenience it keeps promising.

Which one it is decides who owns it, and that call belongs to the CXO, assuming anyone let them in the room.

Dow Built the Capability. American Gave It a Title.

Dow just built the wider view.

Starting in 2017, its commercial and CX people worked out a shared way to listen to customers and actually feed it into decisions, and eventually wrote the Customer Experience Index into executive pay.

That index climbed 30 percent between 2018 and 2023, complaints and resolution times dropped double digits, and digital leads went up tenfold. Crediting one program for all of that would be too tidy. But the capability was real, and it didn’t need the exact title.

A Chief Commercial Officer and a Global Director of Customer Experience ran it.

American Airlines is the other version: same capability, but with a title and one name on the hook.

In early 2025, American created its first real Chief Customer Officer role and gave it to Heather Garboden, a senior VP, with a CX organization built to sit across both commercial and operations. “A true convergence,” as she put it to Newsweek.

It showed up in the results. In American’s own Q2 earnings release, “elevate the customer experience” is the first of the four commercial pillars the CEO puts in front of investors.

NPS was up five points year over year, on-time NPS rose for the 15th time in 17 months, and revenue hit a record. And Garboden did the thing that actually buys a CX leader a permanent chair: she built a number her CFO can use, pegging a single NPS point at somewhere in the tens of millions of dollars, a figure she’s quick to call directional, not gospel.

That’s what the rally metaphor was missing.

Not a co-driver who reads the road, but one who changes what the car is and can tell you what it’s worth in the only language the board really trusts.

The Board Should Know Who Can Change the Decision

Customer evidence has to show up while the choices are still being made, not after the budget’s set. And honestly, the relationship should be a little uncomfortable.

An advisor who never once changes the CEO’s mind is well-liked, sure, but I’m not convinced they’re advising anyone. Evidence that’s only welcome when it agrees with the plan isn’t worth much.

So here’s the question a board should just ask outright:

Who in this company can tell when customers are contradicting the strategy and can they change a real decision about it?

There should be a name. More and more, it’s the CX leader’s. Hand someone that job without the authority to act on it, and all you’ve done is make them the person who has to explain a problem they were never allowed to fix.

Call it CXO, Chief Customer Officer, whatever you like. What matters is that the capability exists, that one person owns it, and that the CEO reaches for it before the decision instead of after.

Do that, and the CX leader stops being a nice-to-have, or a conscience you keep at a polite distance. They become the person who keeps the strategy honest against the customer.

Which is more or less the whole reason the boardroom exists.

www.marklevy.co
Follow me on Linkedin

Leave a comment

Thanks for being here. I’ll see you next Tuesday at 8:15 am ET.

👉 If you enjoyed this newsletter and value this work, please consider forwarding it to your friends and colleagues or sharing it on social media. New to DCX? Sign Up.

Share Decoding Customer Experience

Your daily signal on AI and CX — minus the hype.

In this issue:

→ One prompt can keep working across days
→ Project questions are turning into fuller carts
→ Good chats can still build a bad relationship
→ Experian gives shopping agents an identity check
→ Messy order requests become drafts for approval

🔍 DEEP DIVE

The Assistant Is Still Working After You Leave

Meta’s new AI model is built to do more than answer. It can connect to email and calendars, keep recurring tasks, prepare daily briefings, watch Marketplace for a requested item, and maintain plans that stretch across days.

That changes the customer journey. A prompt no longer has to end with the session. It can become an assignment that keeps gathering context, making recommendations, and preparing the next action.

For customers, that continuity is useful. For brands, it creates a harder question: what exactly did the customer authorize? Preferences change. Prices move. Inventory disappears. A request that made sense Monday may be wrong by Friday.

The operating unit is no longer the conversation. It is the living assignment: what the customer asked, what context the assistant used, what it may change, when it must check back, and how the customer can stop or correct the work.

Meta has not published adoption or outcome data for these new capabilities. The signal is the product direction. Customer-side AI is gaining memory, connections, and time.

Bottom Line: When an assistant keeps the thread, brands need to keep the authority record.

🧭 OPERATOR PLAYBOOK

Audit the Standing Order

Take one journey where an assistant remembers or acts after the customer leaves:

1. Assignment: Can the customer see the current goal in plain language?

2. Authority: Which actions may happen automatically, and which require approval?

3. Memory: Can the customer inspect and correct the preferences being used?

4. Interrupt: Can the customer pause, revoke, or recover the work without starting over?

Then change one important preference midstream. If the assistant cannot surface the conflict and ask again, it is carrying old intent into a new decision.

Ask your team: Where does remembered intent expire?

📊 MARKET REALITY CHECK

A Good Chat Can Still Build a Bad Relationship

Stanford researchers count more than 140 state bills addressing AI in mental health contexts. Their larger warning applies to any company putting an AI assistant into an ongoing customer relationship: we know far more about how these systems perform in one session than what happens after repeated use.

Most CX dashboards measure one interaction at a time: resolution, containment, accuracy, or satisfaction. An assistant can score well on every chat while an incorrect memory shapes later recommendations, customer trust grows beyond the system’s competence, or human escalation arrives too late. A model update can also change the experience midway through the relationship.

Why it matters: If the AI remembers customers across visits, CX teams must measure the relationship across visits. Track whether remembered context stays accurate, customers can correct or revoke it, trust matches performance, and escalation works when the stakes rise.

🧰 TOOL WORTH KNOWING

Experian Gives the Shopping Agent an ID Check

What it does: Experian Agent Trust connects a verified person, device, and AI agent. It checks identity, payment, intent, consent, risk, and behavior before returning a transaction decision.

CX use case: A shopping agent finds a product and tries to buy it. The merchant can distinguish an authorized customer agent from unknown automated traffic, verify the request, and step up authentication only when the risk calls for it.

Worth watching because: Agentic commerce breaks the familiar assumption that the person, browser, and buyer are the same actor. Fastly’s new participation brings those trust decisions closer to the edge, where APIs, authentication, payments, and security controls meet.

Bottom line: The smoother agentic checkout becomes, the more precisely brands must verify who authorized what.

📡 90-SECOND CX RADAR

Proton turns messy requests into order drafts

Proton.ai’s new system converts customer emails, spreadsheets, PDFs, screenshots, and spoken requests into draft quotes or orders. It checks products, availability, and substitutions, then leaves the final send to a sales rep.

Why it matters: The useful automation is not just reading an inbound request. It is preserving customer intent while making the approval step faster and clearer.

✅ YOUR MOVE

Find one AI-driven journey where the customer’s intent persists after the session.

Write down what the assistant may remember, change, or buy. Then show the customer that same record. If your team cannot make the assignment visible, it is not ready to keep working in the background.

Memory without a correction path is just stale intent with permission.

Until tomorrow,

Four very different service changes point to the same test: did the customer’s job actually get easier?

A new app, policy, platform, or piece of store technology can look impressive from inside the business.

Customers use a simpler test. Can I get through this without repeating myself, making an extra trip, decoding a rule, or wondering whether the system is working against me?

That question connects airline integration, mobile account transfers, cash rounding, and smart shopping carts. The industries are different. The customer judgment is remarkably consistent.

Good experience design removes work and makes the remaining rules easier to see.

This Week’s Must-Read Links

Alaska and Hawaiian Put the Journey on One System

Alaska Air Group moved Alaska Airlines and Hawaiian Airlines onto one passenger service system, bringing booking, check-in, loyalty, airport operations, and employee support onto a shared foundation. Guest satisfaction rose 7 percentage points quarter over quarter, while Hawaiian’s rose 10 points.

What’s happening: Customers now use one app and a more consistent airport experience across both airlines. The operational shift also gives employees one system for handling the journey instead of asking travelers to absorb the seams between two carriers.

Why it matters: Airline mergers are easy to describe as corporate transactions. Customers experience them through boarding passes, bag tags, loyalty recognition, schedule changes, and the employee’s ability to find the right answer. The system underneath those moments is part of the service.

The bottom line: Alaska connected an internal integration milestone to visible customer and employee outcomes. That is a better standard than celebrating a platform launch by itself. The useful question is whether the new operating layer reduces inconsistency when the journey is moving normally and when it breaks.

TIM Brasil Removes a Store Visit From Switching Phones

TIM Brasil is introducing cross-platform eSIM transfers so customers can move service between smartphone brands or upgrade devices without visiting a store, replacing a physical SIM, or working through a complicated migration.

What’s happening: The capability is designed to move an eSIM profile securely across devices and operating systems in a few taps. For millions of Brazilian customers, a device change can become a self-directed digital task instead of a support or retail journey.

Why it matters: Customers rarely care which company owns the entitlement gateway. They care that buying a new phone doesn’t create another errand. This is a useful example of technology improving CX by deleting a step, not by adding another channel or interface.

Between the lines: Removing the visit also removes a human safety net. TIM will still need clear recovery paths for failed transfers, locked devices, identity checks, and customers who aren’t comfortable doing it alone. A shorter happy path only counts as progress if exceptions don’t become harder.

The Penny Is Becoming a Checkout Trust Problem

As the United States stops producing pennies, cash-handling businesses are dealing with shortages, a patchwork of state rules, and customer confusion over why a total can’t be settled exactly. Proposed federal rules would round cash totals to the nearest five cents while leaving electronic payments unchanged.

What’s happening: Retailers, restaurants, banks, and convenience stores want one national standard. Without it, frontline employees may have to explain different rounding practices while customers decide whether a few cents were handled fairly.

Why it matters: Small amounts can create outsized distrust when the rule is unclear. A customer at the register isn’t thinking about coin-production economics or legislative timing. They’re watching who benefits from the rounding, whether the practice is consistent, and whether cash customers are treated differently.

Reality check: This is an operating-policy change disguised as a minor payment detail. Signage, receipts, employee scripts, point-of-sale logic, refunds, and complaint handling all need to tell the same story. If they don’t, the cashier inherits a policy problem they didn’t create.

Smart Shopping Carts Change More Than Checkout

Researchers analyzed 12,418 smart-cart shopping sessions at a major German supermarket. Smart-cart use was associated with higher spending, larger baskets, and longer store visits, but the behavior changed depending on how customers used the technology.

What’s happening: Shoppers who uploaded lists were associated with higher basket values, smaller baskets, and shorter trips. Heavy users spent longer in the store and bought more items. One piece of technology was supporting several different shopping jobs.

Why it matters: Averages can hide the experience. “Smart-cart users spend more” sounds commercially attractive, but it doesn’t explain whether the cart helped someone finish faster, compare more carefully, discover products, or simply remain in the aisle longer. Each behavior calls for a different design and measurement choice.

The bottom line: Physical experience technology should be judged by the customer’s intended job as well as the retailer’s sales result. Segmenting usage patterns can show when the tool reduces effort and when it creates more interaction than the shopper wanted.

DCX Stat of the Week

Social Creates the Demand. Trust Gets the Transaction.

48% of consumers discover new products on social media, but only 6% prefer to complete the purchase there.

Takeaway: Discovery and conversion are now different jobs. ESW’s survey of 23,251 consumers across 18 markets shows that attention can move quickly while payment trust remains concentrated in familiar buying environments.

Source: ESW Signals 2026

DCX Case Study of the Week

Qualia Cut Onboarding Time While Expanding Capacity

CX Challenge: Qualia’s high-touch, one-to-one onboarding model was creating capacity bottlenecks. Some customers waited up to two weeks for a kickoff call, and the team needed to double capacity within three months.

Action Taken: Qualia used OnRamp to break onboarding into customer-facing tasks, let customers begin immediately, and give specialists visibility into progress. Live calls shifted from basic walkthroughs to coaching and problem solving.

Result: OnRamp’s customer story reports a 53% reduction in time to go live, onboarding completion rising from 92% to 99%, and three times the onboarding scale without added headcount.

Lesson for CX Pros: Self-service works better when it removes waiting and helps employees see where human attention is still needed.

Quote: “Customers shouldn’t be met with friction immediately after they start learning the product.” Brian Thome, Chief Customer Officer, Qualia

Have a case study to share? Reply and let me know!

One Last Thing

Customers don’t grade the sophistication of the system.

They notice the store visit they no longer need, the airline handoff that finally makes sense, the payment rule that feels fair, and the technology that helps them finish what they came to do.

That is where operational change becomes customer experience.

Have a great week ahead!

Your daily signal on AI and CX — minus the hype.

In this issue:

→ Uber cuts 10% of customer-service roles
→ Buying questions span all 168 weekly hours
→ Quiet-hour demand still produces orders
→ Autoplay turns product activity into proactive guidance
→ Shoppers choose AI over brand sites

🔍 DEEP DIVE

A Smaller Team Is Still a Customer Promise

Uber has cut 10% of jobs in its community operations customer-service organization. The company tied the reorganization to simplifying operations, strengthening in-person collaboration, and making better use of AI.

The internal logic deserves attention. Uber’s memo said the organization had become too complex and fragmented, and that frontier technology couldn’t scale on top of fragmented processes. That’s a real operating problem. AI laid over a broken service system usually makes the break travel faster.

But a smaller team doesn’t prove the work disappeared. The work may come back as repeat contacts, slower exceptions, weaker recovery, more customer effort, or more supervision for the people who remain. Uber didn’t disclose the size of the unit, expected savings, automation performance, or customer outcomes.

A headcount reduction is a capacity decision. It becomes an AI result only when the company can show what demand was removed, what customers now resolve more easily, and which recovery capacity remains protected.

Bottom Line: If AI removes service roles, measure the work that vanished and the effort that didn’t move to the customer.

🧭 OPERATOR PLAYBOOK

Audit the Capacity Claim

Take one AI-enabled service journey and compare the 30 days before and after the staffing change:

1. Demand removed: Which contacts, tasks, and follow-ups genuinely stopped?

2. Customer effort: Did repeat contact, channel switching, complaints, or abandonment rise?

3. Exception coverage: Can people still recover urgent, high-risk, and emotionally charged cases?

4. Verification tax: How much employee time now goes to checking, correcting, and explaining AI output?

Add a stop condition before the cut. If customer effort or unresolved exceptions rise beyond it, restore capacity or narrow the automation.

Ask your team: Which work disappeared, and which customer or employee picked up the rest?

Signal: Lower headcount is visible. Displaced effort hides in the journey.

📊 MARKET REALITY CHECK

Buying Questions Arrive 24/7

Gorgias found assistant-influenced orders occur during every hour of the week. The busiest hour generated only about 3.5 times as many orders as the quietest.

The pattern uses web orders placed during the last 90 days across merchants running Gorgias Shopping Assistant. The commercial signal is hard to miss: assisted buying journeys keep producing orders while human coverage gets thin.

Why it matters: Pre-purchase demand doesn’t follow contact-center staffing. A question left unanswered overnight can become somebody else’s sale.

🧰 TOOL WORTH KNOWING

Autoplay Helps Before the Ticket Exists

What it does: Autoplay feeds live product activity into an existing support AI agent. It turns clicks, progress, stalled steps, and completed workflows into structured context the agent can use.

CX use case: A customer stalls halfway through setup but never opens chat. Autoplay can recognize the gap, compare it with the intended journey, and trigger a relevant message, quick reply, modal, or in-app tour. Session states help the agent decide when to speak and when to stay quiet.

Worth watching because: Most support systems wait for customers to identify the problem and ask the right question. Autoplay treats behavior as the signal, moving help into the moment before confusion becomes a ticket or abandonment.

Bottom line: Proactive help earns its place only if it reduces stuck time without turning the product into a stream of interruptions.

📡 90-SECOND CX RADAR

Shoppers are choosing the AI front door

Bloomreach’s survey of 4,000 US and UK consumers found that 41.4% would choose to shop through an AI tool if forced to pick, compared with 38% who would go directly to a brand site. It also found that 80.4% said their AI shopping experience met or exceeded expectations.

Why it matters: Product data, comparison logic, policies, and brand explanations now shape the journey before many shoppers reach the company’s own experience.

✅ YOUR MOVE

Pick one service workflow where AI is part of the staffing case. Write down the capacity the model says you gained.

Then subtract repeat contacts, employee verification, exception handling, and customer recovery. If nobody owns those numbers, the savings are still a hypothesis.

Don’t count the role until you can account for the work.

Until Monday,

I’m obsessed with Wispr Flow Pro! Get a Free Month on me.

Your daily signal on AI and CX — minus the hype.

In this issue:

→ Service agents get a post-launch improvement loop
→ Bank reps receive guidance in under three seconds
→ Nearly one-third of service failures get no recovery
→ Banks can set response freedom by topic
→ CX platforms push agents deeper into operations

🔍 DEEP DIVE

The Demo Is Over. Now the Customer Changes.

OpenAI has launched Presence, a managed product for putting voice and chat agents into live customer and employee workflows. The interesting part isn’t another agent answering a billing question. It’s what happens after the agent meets real customers.

Presence combines policies, approved actions, simulations, evaluations, escalation rules, and a Codex-powered improvement process. Production conversations expose gaps. Codex proposes changes. Teams test those changes against the live version and approve a controlled rollout. That sounds suspiciously like software release management, because that’s what customer-facing AI now needs.

OpenAI says its own phone agent resolves 75% of inbound issues without human help and cut handoffs by 15 percentage points in ten days. Those are company-reported results, but they point to the right operating question. An agent’s launch score matters less than whether the team can spot a bad pattern, trace the cause, test a fix, and change behavior without creating a new customer problem.

Bottom Line: The service agent isn’t finished when it goes live. Someone needs to own how it learns without turning customers into unpaid testers.

🧭 OPERATOR PLAYBOOK

Run the Friday Failure Review

Audit every live AI service workflow for four things:

1. Failure pattern: Which intents, customers, policies, or actions create repeat contacts, escalations, or corrections?

2. Decision boundary: What can the agent answer, recommend, approve, or change without human review?

3. Change control: Who tests and approves new prompts, policies, tools, and workflow behavior?

4. Recovery path: Can the team roll back a bad change and repair the affected customer journey quickly?

Then test whether the latest fix improves the failed journey without breaking three adjacent ones.

Ask your team: What did our agent learn from customers last week, and who approved the change?

📊 MARKET REALITY CHECK

No Recovery Is a Second Failure

After their most recent poor customer service experience, 29% of consumers said the company took no action. The original failure is only half the problem. Inaction tells the customer that the company either didn’t notice the breakdown or chose not to own it.

The finding doesn’t isolate AI-caused failures or prove which recovery action works best. It does expose a management gap. Monitoring a bad answer, broken handoff, or repeat contact creates no customer value unless someone can trigger outreach, remediation, and a fix to the underlying journey.

Why it matters: An agent-improvement loop is incomplete if the model gets fixed but the affected customer hears nothing.

🧰 TOOL WORTH KNOWING

Glia Banker Adds a Risk Dial

What it does: Glia Banker now lets financial institutions choose among three response modes by topic. Strict Mode returns approved wording. Rephrase Mode adapts approved answers to the customer’s language without adding information. Compose Mode generates from institution-approved content.

CX use case: A bank can allow a more natural answer for branch hours while keeping loan, fraud, or wire-transfer explanations inside tighter boundaries.

Worth watching because: It turns AI governance into a journey-level design choice instead of one blanket setting for every conversation.

Bottom line: The right amount of conversational freedom depends on what the customer is trying to do and how much harm a variable answer can create.

📡 90-SECOND CX RADAR

CX agents move from the front door into operations

Observe.AI and AWS are pushing customer, frontline, and operations agents onto one production platform. The useful shift is continuous visibility into quality, compliance, intent trends, root causes, and automation performance, not another isolated bot at the channel edge.

Why it matters: CX teams will need one operating view across what the agent says, what it does, and what the customer has to do next.

Shoppers want help without surrendering the final click

Zip says 68% of 1,755 surveyed US shoppers used an AI tool in the past three months, but 79% want full control over the final purchase decision.

Why it matters: Customers may welcome faster research and comparison while still expecting a visible stop before money moves.

✅ YOUR MOVE

Pick one live AI journey this week. Skip the launch deck and review the last 25 failures.

Look for the pattern behind the bad answer, repeated explanation, unnecessary escalation, or unsafe action. Then name the owner who can change the agent and the operator who can repair the customer impact.

A live agent needs a release process, not a victory lap.

Until tomorrow,

I’m obsessed with Wispr Flow Pro! Get a Free Month on me.

Your daily signal on AI and CX — minus the hype.

DCX Stat of the day: Customer conversations with explicit emotional validation scored 11.84% higher on Level AI’s inferred satisfaction measure than conversations without it.

In this issue:

→ Personal finance gets a new, unlicensed front door
→ Advice needs evidence before customers act
→ Shoppers keep control at the checkout
→ Squirro puts confidence inside automated quotes
→ Public services and payments confront human oversight

🔍 DEEP DIVE

Your Money Question Has a New Advisor

People are asking general-purpose AI tools how to budget, manage debt, choose investments, and plan retirement. The OECD (Organisation for Economic Co-operation and Development) says more than one-third of people across its member countries used AI tools in 2025, and personal finance is becoming one of the places they turn for help.

That changes the financial journey before a bank, insurer, or advisor even knows a decision is being made. AI can simplify dense documents, translate unfamiliar terms, and answer questions someone may feel awkward asking a person. It can also hallucinate, blur information with personalized advice, hide commercial influence, and invite customers to share more financial data than they understand.

The awkward part for CX leaders is that the customer may arrive with a confident answer from a system the business doesn’t control. Frontline teams need a way to inspect the claim, explain the tradeoff, and correct bad guidance without treating the customer like the problem.

Bottom Line: AI can lower the effort of asking a money question while raising the cost of trusting the wrong answer.

🧭 OPERATOR PLAYBOOK

Audit the Moment Advice Becomes Action

Pick one journey where AI guidance can change a financial decision, purchase, quote, or application.

Audit it for four things:

1. Evidence: Can the customer see what facts and sources shaped the answer?

2. Influence: Are commissions, preferred products, and business rules visible?

3. Permission: Is there a clear approval step before the system acts?

4. Recovery: Can a person inspect, reverse, or correct the decision?

Then give the flow one plausible but wrong AI-generated assumption. Watch whether the journey catches it or quietly turns it into a transaction.

Ask your team: Where does useful guidance become a recommendation we must be able to defend?

📊 MARKET REALITY CHECK

Checkout Is the Trust Boundary

64% of Australians have used AI assistants to browse, compare, or discover products. The same share feel uncomfortable allowing AI to complete a purchase on their behalf. Only 5% are fully comfortable letting AI buy independently.

That is a remarkably clean boundary. Customers will accept help narrowing the choice. Control gets more valuable when the journey reaches payment. The findings are regional and don’t predict behavior everywhere, but they give retailers a practical warning: investment in agentic checkout is running ahead of customer permission.

Why it matters: The winning journey may not be the most autonomous one. It may be the one that makes limits, approval, authentication, and reversal easiest to understand.

Assistance builds momentum. Visible control earns the transaction.

Data Source: Adyen

🧰 TOOL WORTH KNOWING

Squirro Gives the Quote a Confidence Score

What it does: Squirro’s new catalog packages 13 enterprise agents on one shared foundation for data connections, security, governance, and audit. Its Instaquote Agent turns insurance submission documents into structured SAP quotes and assigns a confidence score at every step.

CX use case: Commercial customers can move from a document-heavy request to a quote in minutes, while uncertain cases route to a person with the source context intact.

Worth watching because: The confidence score creates a useful decision point. Teams can define when automation proceeds, when a human reviews, and what evidence has to travel with the quote.

Bottom line: A faster quote helps. A quote the business can explain, inspect, and correct is much more valuable.

📡 90-SECOND CX RADAR

Public services get an AI invitation, with conditions

BCG found that 64% of citizens across 44 countries use AI at least weekly, while satisfaction with government digital services has fallen 13 percentage points over a decade. Nearly two-thirds still want human oversight for AI-enabled services, especially when decisions are complex or consequential.

Why it matters: Faster public service will not earn trust if citizens cannot see the safeguard, request review, or reach the person accountable for the decision.

More access is not the same as applied work

Gallup says 47% of U.S. employees now work at organizations that have integrated AI, yet one in five still do not know whether their employer has done so. The largest reported productivity gains appear in specific uses such as coding and process automation, not the broadest everyday uses.

Why it matters: Tool availability is a weak operating metric. Name the workflow, the owner, the expected customer or employee outcome, and the boundary on what AI can do.

Payments finally ask who owns the agent’s mistake

The Emerging Payments Association Asia and HSBC have launched a working group on agent identity, authorization, fraud, liability, and disputes. Its premise is blunt: agents are already transacting, while responsibility still assumes a human made the decision.

Why it matters: Agentic payment cannot scale safely until customers know who approved the action and who makes them whole when software exceeds its mandate.

✅ YOUR MOVE

Customers are inviting AI into decisions that affect their money, purchases, and access to services.

They are also drawing a clear line between getting help and surrendering control.

Choose one AI-assisted decision in your customer journey. Trace the evidence, commercial influence, approval step, confidence threshold, and reversal path. If any one of those disappears when the system acts, the customer is carrying a risk the business created.

Let AI make the path easier. Keep the consequential decision explainable and reversible.

Until tomorrow,

I’m obsessed with Wispr Flow Pro! Get a Free Month on me.

Your daily signal on AI and CX — minus the hype.

In this issue:

→ Europe makes AI disclosure a journey requirement
→ First contact becomes a compliance moment
→ Customers want identity and wait-time clarity
→ OpenDialog enters complex insurance quote flows
→ Banks reveal the gap between access and implementation

🔍 DEEP DIVE

Put the Label Where the Decision Starts

Europe has turned a familiar CX question into an operating deadline: does the customer know when they’re dealing with AI?

The European Commission’s new guidance explains Article 50 transparency obligations that apply from August 2. Providers of covered interactive AI systems must design them so people are informed that they’re interacting with AI, unless that’s obvious. The disclosure has to arrive no later than the first interaction.

The disclosure is only the start. Customers will reasonably ask what the AI can do, what data it uses, whether a person is available, and how to challenge an answer. A tiny bot badge beside a dead-end conversation may satisfy a design ticket while leaving the customer with the same practical uncertainty.

For CX leaders, the front door now needs three things at once: a clear identity, an honest boundary, and a visible escape route. Legal can define the obligation. Product, service, and operations still have to make it usable.

Bottom Line: Disclosure works only when it helps the customer understand the interaction and what to do when automation reaches its limit.

🧭 OPERATOR PLAYBOOK

Run the First-Interaction Test

Choose one customer-facing AI interaction and review the first 30 seconds:

1. Is the AI identity clear before the customer relies on it?

2. Does the interface explain the system’s practical boundaries?

3. Can the customer reach human help without starting over?

4. Is the disclosure logged with the interaction and version?

Then ask five people who didn’t build the flow to explain what they think the system can do. Their answers will tell you whether the disclosure is working or merely present.

Ask your team: Does this notice change what the customer understands and can do next?

📊 MARKET REALITY CHECK

Customers Want the Name and the Clock

55% of consumers expected companies to disclose whether they were communicating with AI or a human. Even more, 64%, expected an estimated wait time.

Those expectations belong together. Before the conversation unfolds, customers are already trying to answer two questions: Who has me, and how long will this take? Hiding the resource or the wait creates uncertainty the rest of the journey has to overcome. The figures don’t prove that a label or countdown fixes service, but they show what customers want made visible before they commit their time.

Why it matters: Transparency starts before the answer. Service design should identify the responder, set a credible time expectation, and make the next option clear when either one changes.

Data Source: CCW Digital

🧰 TOOL WORTH KNOWING

OpenDialog Steps Into the Hard Part of the Quote

What it does: OpenDialog builds AI agents for regulated insurance journeys, including quotations, policy questions, policy changes, re-engagement, and claims.

CX use case: New partnerships with Firemelon and Aequotech bring contextual guidance into insurance comparison and quote flows. Medical Travel Compared plans to use it where medical declarations and pre-existing condition questions often create confusion or abandonment.

Worth watching because: This is a good test of whether conversational help can make a regulated product easier to understand without weakening disclosure, auditability, consent, accessibility, or the path to a human before a policy is bound.

Bottom line: The useful agent isn’t the one that talks around the form. It’s the one that helps the customer complete a difficult decision with fewer doubts and a cleaner record.

📡 90-SECOND CX RADAR

Prompt volume is outrunning implemented workflows

More than 200,000 Bank of America employees use AI-enabled capabilities and generate more than 400,000 prompts a day. The bank has more than 300 approved AI use cases, but 34 are fully implemented.

Why it matters: Access scales faster than operating change. Track implemented customer and employee workflows, not the number of people who opened the tool.

✅ YOUR MOVE

Customers need to know when AI has entered the journey. They also want an honest signal about how long the next step will take.

Both questions are tests of operating clarity.

Pick one live AI interaction this week. Review the disclosure, the boundary, the human route, and the event log. Then test the wait-time promise: what starts the clock, what stops it, who updates the customer, and what happens when the estimate slips?

Tell the customer who’s talking. Then prove the business knows what happens next.

Until tomorrow,

I’m obsessed with Wispr Flow Pro! Get a Free Month on me.

A customer has called three or four times. They’ve explained the problem to different people, repeated information the company already has, and waited for callbacks that never came. The complaint may have been bouncing around for days or weeks.

Then an email reaches the CEO.

Everything changes.

They forward it to other leaders with a short note: “Can you look into this?”

Suddenly, everyone’s looking into it.

Others get added to the thread. Account records are pulled. Calls are reviewed. Someone contacts the customer directly. Teams that couldn’t seem to coordinate before now work across functions. A policy that was supposedly firm turns out to have some room in it after all.

By the end of the day, the customer may have an apology, a resolution, and the direct number of someone senior enough to make sure the problem stays solved.

It’s hard to miss the contrast.

The company that made an ordinary customer work for every answer becomes focused, fast, and surprisingly resourceful once an executive is watching.

You could look at that response and see the company at its best.

I see something else.

I see a version of the company that most customers can’t access.

The Executive Attention Upgrade

Most large companies have a hidden level of service.

It’s not listed on the website. Customers can’t buy it. There aren’t any published requirements for getting it.

You qualify when your complaint attracts someone with enough organizational power.

Call it the executive attention upgrade.

Once that happens, you’re no longer navigating the regular customer experience. You get an owner. Someone assembles your history. Internal handoffs happen without your involvement. Updates come to you. People start asking what it’ll take to solve the problem instead of explaining why the usual process won’t allow it.

I’ve seen how quickly this upgrade can take effect. An issue that sat in a queue yesterday becomes urgent today. People who knew nothing about it a few hours ago now want a status update. Obstacles that had seemed permanent start looking a lot more negotiable.

There are good reasons for some of this. Executive complaints can carry legal, regulatory, reputational, or commercial risk. Leaders need to know that serious issues will get serious attention.

But besides those, something else has happened.

The customer hasn’t simply moved to the front of the line. They’ve entered a different operating model.

Normal constraints loosen. Authority expands. Departments cooperate. Employees get permission to use judgment. The company begins carrying some of the effort it previously placed on the customer.

The resolution may be excellent. But it no longer represents the experience most customers get.

Executive attention has temporarily replaced the normal customer journey.

The Problem Didn’t Suddenly Become Easier

This is the part that has always stayed with me.

The customer’s problem doesn’t change when the escalation arrives. The billing error is still a billing error. The missed appointment is still a missed appointment. The refund is still denied.

What changes is how much the organization cares about resolving it.

Earlier, the customer might have been told nothing could be done. Now someone finds a way. The complaint that kept getting handed from team to team suddenly has one person seeing it through. And instead of the customer chasing updates, the company starts doing the calling.

The issue didn’t become easier. It became visible to someone with authority.

That should make a CEO uncomfortable.

It suggests that the organization may have had the ability to resolve the problem all along. What it lacked was enough internal consequence to act.

Sometimes it’s authority — the frontline employee can see the reasonable answer but isn’t allowed to give it. Other times it’s ownership, with each function handling its small piece while the customer’s actual problem falls through the cracks between them.

Often, the information is just scattered across systems, and nobody in the normal process has the access or time to pull it together. And in some companies, the truth is simpler: they’ve learned to respond to hierarchy faster than to customer harm.

Executive involvement brings visibility, authority, coordination, and consequence. Of course, the organization moves faster.

The more important question is why customers normally have to do without those things.

The Rescue Can Hide the Failure

The people who step in and rescue an escalated customer often deserve credit. I’ve worked with plenty of people who cared deeply, moved quickly, and pushed through internal barriers to make things right.

The problem isn’t the rescue. It’s what the company concludes from it.

A senior leader sees people rally around a customer and thinks the organization responded well. The customer sends a grateful email. The case gets closed. Everyone feels good that the company came through when it mattered.

But the case only started to matter after someone important noticed it.

That’s a different story.

The recovery proves there are capable people inside the company. It may also prove that those people need executive cover before they can do what the customer needed in the first place.

If fixing a fairly common problem requires a senior leader, a special team, or an exception to the normal process, the company hasn’t demonstrated that its customer experience works. It has demonstrated that it knows how to work around it.

Those workarounds can feel satisfying because they give everyone a clean ending. The customer gets help. The executive gets closure. The team gets thanked.

Meanwhile, other customers with the same problem are still stuck in the regular system.

They don’t know the CEO. They may not have a large social media following. They might not write the kind of complaint that gets forwarded to six senior leaders.

Most will keep calling, give up, quietly leave, or accept an outcome they shouldn’t have been asked to accept.

One executive complaint can mobilize a room.

Ten thousand ordinary complaints can disappear into an average.

Study What Changed

Escalations are necessary. Some cases are unusual, sensitive, or genuinely complicated. Senior leaders should get involved when the circumstances call for it.

But saving one customer shouldn’t be the end of the work.

Every executive complaint creates a useful comparison between two versions of the company: the one the customer originally encountered and the one that appeared once leadership got involved.

The most valuable information is in the distance between them.

What authority suddenly became available? Who finally owned the whole thing? Which teams that never talked started coordinating, what information got assembled, and which “firm” policy turned out to bend? And the one that always confounds me: why couldn’t any of that have happened when the customer first asked?

Then there’s the question that matters most: Could the next customer get the same outcome without executive involvement?

If the answer is no, the experience hasn’t been fixed. The company has solved one visible case while leaving the conditions that created it untouched.

The goal isn’t to eliminate escalation. It’s to learn from the version of the company that shows up during one.

If executive attention helps the organization solve a problem quickly, look closely at what made that possible. Move those conditions closer to the frontline. Give employees clearer authority. Create ownership across handoffs. Fix missing information. Revisit policies that repeatedly need senior exceptions.

Otherwise, the company keeps repeating the same cycle. The customer struggles. The complaint becomes visible. Senior people mobilize. The case gets resolved. Everyone moves on.

Until the next one lands.

The Experience Power Can’t Easily See

Executives rarely experience their own companies under normal conditions.

People recognize their names. Their questions get answered. Employees prepare before meeting with them. When a CEO asks what happened, the organization can suddenly produce the history, the context, and a recovery plan.

Most customers don’t carry that kind of weight.

That makes it hard for CEOs to see the company customers actually deal with. Their involvement changes the behavior they’re trying to understand.

Executive escalations make that distortion especially clear.

The CEO sees a responsive organization moving with purpose. The customer may have spent weeks dealing with a company that felt fragmented, rigid, and indifferent.

Both versions of the company are real.

But only one is available to everyone.

That’s the blind spot.

An escalated complaint doesn’t just show the CEO that the company can recover. It shows how much influence was required for the organization to behave as if the customer’s problem mattered.

And it leaves a difficult question:

Why should a customer need executive attention to receive an experience the company already knows how to provide?

www.marklevy.co
Follow me on Linkedin

Leave a comment

Thanks for being here. I’ll see you next Tuesday at 8:15 am ET.

👉 If you enjoyed this newsletter and value this work, please consider forwarding it to your friends and colleagues or sharing it on social media. New to DCX? Sign Up.

Share Decoding Customer Experience

Your daily signal on AI and CX — minus the hype.

In this issue:

→ One answer can hide the entire shortlist
→ Recommendation records become a CX control
→ Grocers bring shopping agents in-house
→ VitalCX owns the work behind patient access
→ Automation leaves humans the harder queue

🔍 DEEP DIVE

One Answer Can Hide the Entire Shortlist

France’s competition authority is warning that AI agents may become gateways between customers and markets. For CX leaders, the risk starts before the customer reaches the journey you designed.

A customer asks which product to buy, airline to use, hotel to book, or provider to trust. The agent returns one answer or a short list. Behind it sit decisions about data, ranking, inventory, commercial relationships, and which options never appeared.

A recommendation is compressed journey design. When its logic is invisible, customers can’t tell whether the answer is useful, sponsored, incomplete, or simply wrong. Brands may lose the visit, the behavioral data, and even the chance to explain why they belong on the list. The company that fulfills the choice may also inherit a promise it never made, then own the scheduling, handoffs, exceptions, and recovery that follow.

Bottom Line: When an agent controls the shortlist, recommendation design and downstream ownership become part of CX governance.

🧭 OPERATOR PLAYBOOK

Can You Defend the Shortlist?

Choose one journey where an AI agent could decide what the customer sees next. Capture ten real or simulated recommendations, then build a simple decision record for each one:

1. Customer request and context used.

2. Options considered, included, and excluded.

3. Ranking rules and commercial influence.

4. Named owner when the recommendation fails.

Track three measures: how often the reason is visible, how often customers can compare or change the choice, and how often recovery reaches an accountable owner.

Ask your team: Could we defend this shortlist to the customer who received it?

📊 MARKET REALITY CHECK

What Happens When the Store Owns the Assistant?

EveryAisle says it is live across 80+ independent grocers through AWG under the SmartMeals brand. Its pilot data says shoppers who planned meals with EveryAisle spent 22% more per trip than other loyalty members, while pilot stores saw a 72% surge in loyalty signups and 310% ROI over a 90-day deployment window.

If those vendor-reported pilot results hold at scale, the ownership model matters as much as the interface. These grocers are placing the assistant inside their branded experience, where recommendations can connect to live inventory, loyalty, coupons, household preferences, and first-party data. The basket, the promise, and the recovery path stay with the retailer.

Why it matters: An owned agent can turn customer intent into revenue without giving away the relationship that produced it.

🧰 TOOL WORTH KNOWING

VitalCX Takes Responsibility Past the Front Door

What it does: VitalCX is a healthcare experience platform that combines managed operations with GraceAI across scheduling, triage, referrals, outreach, medical records, billing, and patient support.

CX use case: A patient can receive the right recommendation and still get lost between referral, authorization, records, appointment availability, follow-up, and billing. VitalCX is built to coordinate that operational work across care teams and systems.

Worth watching because: VitalCX pairs automation with defined workflows, real-time oversight, quality and compliance monitoring, and named ownership. Its site says Westside Family Healthcare used the service to answer 99,000+ calls and schedule nearly 19,000 appointments year to date, while abandoned calls fell from 38% to 6.5%.

Bottom line: The value comes from keeping AI, people, workflow design, and an accountable owner focused on the same patient outcome.

📡 90-SECOND CX RADAR

Automation is leaving humans the harder queue

As AI handles more routine service, the human queue concentrates exceptions, complaints, sensitive issues, and judgment calls. Average handle time may rise even when the overall system is working better.

Why it matters: Staffing, coaching, QA, and productivity targets need to account for case complexity, or the people handling the hardest work will look less productive on paper.

✅ YOUR MOVE

AI agents are moving customer choice upstream from the journeys most companies measure.

The same accountability has to continue downstream. Once AI starts the journey, someone still has to own the scheduling, handoffs, exceptions, follow-up, and recovery.

Run the same customer request through three agents this week. Save the answers, then trace one recommendation all the way through fulfillment. Ask:

• Did the shortlist change, and can you explain why?

• Were paid or preferred relationships visible?

• Where does ownership move from recommendation to delivery?

• Who handles the first exception without restarting the customer?

The answer starts the journey. Accountability has to survive the rest of it.

Until tomorrow,

I’m obsessed with Wispr Flow Pro! Get a Free Month on me.

Customers are still willing to trade. They’ll trade speed for savings. They’ll trade simplicity for a better result. They’ll even work with a new kind of AI partner when the value is clear.

What they’re getting less patient with is the fog around the tradeoff.

Shipping fees that show up late. Returns that feel punitive. Loyalty programs that matter in theory but barely shape behavior. AI tools that promise help but leave people doing the same work with a better interface.

That’s the thread this week: value has to be visible before people feel the cost. Not just the price. The time, effort, uncertainty, and judgment customers and teams have to supply along the way.

Let’s dig in.

This Week’s Must-Read Links

Convenience fees are becoming loyalty tests

In a new ICSC Survey: Consumers Reassess the Cost of Convenience, shoppers are making it clear that delivery fees, return costs, and fulfillment choices now sit inside the loyalty decision.

What’s happening: ICSC surveyed 1,000 U.S. consumers and found that 70% of online shoppers have abandoned a cart because of shipping costs. Sixty-seven percent say return fees make them less likely to buy online, and 65% have stopped or would consider stopping shopping with a retailer because of delivery fees, slow shipping, or inconvenient returns.

Why it matters: This is not a checkout-detail problem. It is a trust and value-design problem. Customers can accept tradeoffs when they understand them early. What damages the relationship is surprise, opacity, or the feeling that the retailer has shifted the cost of convenience onto the customer after commitment.

The bottom line: Physical stores still matter because they solve practical online friction: no shipping fee, no delivery wait, easier returns, and a chance to see the product before buying.

The agentic company needs an operating manual

Agents, Inc. is a new book from Adam Brotman, Andy Sack, and Vera Brown (AI), but the more interesting CX signal is how it was made: the authors wrote and published it in 3 months with Vera as their AI agent partner.

What’s happening: Vera was not treated as a search box or a writing shortcut. She was part of the work system: helping shape the book, continue the conversation after publication, and produce personalized mini-books for readers based on their role, company, and current priorities. The experience around the book is itself a working example of agent partnership.

Why it matters: That is the useful leap for CX leaders. Agents are not only tools for deflection or content generation. They can become thinking partners for journey research, service blueprinting, customer-signal synthesis, frontline coaching, proposal generation, recovery design, and internal decision support. The question is not just what the agent can produce. It is what kind of working relationship the team builds with it.

Reality check: A book-writing process is not the same as a customer-facing service operation. But it gives CX teams a concrete model to study: humans setting direction, an agent carrying context, and the output improving because the collaboration is designed, not improvised.

Human judgment needs a design brief

In The Future Worth Building Is Human, Thinking Machines argues that AI work should be built around human creativity, judgment, and agency instead of treating people as awkward parts of the machine.

What’s happening: The piece is not a CX article in the narrow sense. It is a useful correction to automation thinking that quietly assumes the goal is to remove people from the work. For CX leaders, that assumption is dangerous. The most valuable moments in service, research, product, and recovery often depend on interpretation, empathy, taste, and accountability.

Why it matters: If teams design AI only for output, they can miss the human job that makes the experience trustworthy. The better question is which parts of the journey need better tools for human judgment, not just faster automation.

Reality check: Use this as a framing piece, not proof of a deployment. Its value is in the question it forces: where does the customer still need a human standard of care?

Better design language is not cosmetic

NameThatUI looks small at first: a visual dictionary for interface elements. But the CX lesson is bigger than the tool. A lot of digital experience work slows down because teams cannot name the thing they are trying to fix.

What’s happening: The site gives designers, builders, and AI coding agents shared labels for UI patterns: popovers, scrims, disclosure triangles, progress rings, truncation, drawers, sheets, segmented controls, and the tiny interaction details that often create user confusion.

Why it matters: Vocabulary sounds soft until a project is late because the product manager, designer, engineer, support lead, and AI assistant all mean different things by “the dropdown thing.” Clear naming reduces rework. It also helps teams describe customer friction with enough precision that someone can actually fix it.

The bottom line: Experience quality often depends on unglamorous shared language. If the team cannot name the control, state, or failure mode, the customer problem stays vague.

DCX Stat of the Week

Loyalty programs matter more than they move behavior

Upside’s 2026 loyalty research found that 86% of shoppers say loyalty rewards matter to them, but regular usage lags across categories: 59% for grocery, 49% for fuel and convenience, and 38% for restaurants.

Takeaway: Enrollment is not loyalty. If rewards do not show up clearly in the moments where customers choose, switch, or return, the program may be valued without changing behavior.

DCX Case Study of the Week

Foot Locker Turned Gen Z Shopper Research Into Roadmap Evidence

CX Challenge: Foot Locker needed a better way to understand Gen Z shopping behavior, style identity, and reluctance to trust AI shopping experiences.

Action Taken: The Experience Design team used Dscout for video auditions, a week-long diary study, and stakeholder-friendly storytelling. Researchers put findings into the planning tools product teams already used and shared customer clips early instead of waiting for a final report.

Result: A new feature inspired by the study was prioritized onto Foot Locker’s product roadmap.

Lesson for CX Pros: Customer evidence carries more weight when it is specific, visual, timely, and delivered in the language of the team making the decision.

Use this in a meeting: If customer research does not reach the roadmap, we have not finished the research job.

Further Reading: dScout Use Case

Have a case study to share? Reply and let me know!

One Last Thing

The easy CX mistake is to assume customers only count money.

They count the whole bill. So do teams.

The fee customers did not expect. The return they cannot complete cleanly. The loyalty program that matters until it fails to shape the next purchase. The vague design language that slows a fix. The AI agent that could become a real partner, or just another tool sitting on top of the same work.

That is useful work for CX leaders: make the value visible, make the tradeoff honest, and design the working system so customers and employees are not quietly paying for gaps the company could have fixed.

Have a great week ahead!

Your daily signal on AI and CX — minus the hype.

In this issue:

→ Support cases that arrive half-solved
→ Why trust lags AI time savings
→ Ticketing agents move into checkout
→ Health agents chase the front door
→ Chatbots turn recovery into sludge
→ A test for evidence-rich escalation

🔍 DEEP DIVE

Meet the Case File That Works Overnight

Pylon introduced a beta agentic support platform built around a simple shift: support teams direct agents to investigate, prepare, route, and update work instead of starting every customer issue from scratch.

That matters because the slow part of support is often not the reply. It’s the archaeology. Someone has to check the account, past tickets, product usage, CRM notes, Slack, issue trackers, logs, and sometimes the codebase before the customer gets a useful answer.

Pylon says early customers are using agents to gather that evidence before escalation, turn strong operators’ processes into reusable Skills, and make context available across Support, Success, Product, Sales, and Engineering. The customer consequence is practical: fewer “can you repeat that?” moments and fewer handoffs that arrive as a shrug with a ticket number.

Bottom Line: The support advantage moves from faster response to better prepared judgment. If AI cannot preserve evidence, it just helps the team say “we’re looking into it” more efficiently.

🧭 OPERATOR PLAYBOOK

Audit the First Fifteen Minutes

Pick one messy support path where customers often wait, repeat themselves, or get bounced between teams.

Audit every escalation for four things:

1. What evidence the first responder has to collect manually.

2. Which systems hold the missing context.

3. What must be true before another team can act.

4. What the customer has already explained, uploaded, or proved.

Then test whether AI can prepare the handoff without hiding uncertainty.

Ask your team: If this case moved to Product, Engineering, Risk, Billing, or Success right now, would the next owner know what happened and what to do next?

Signal: The handoff is healthy when the next person starts with judgment, not investigation.

📊 MARKET REALITY CHECK

The Operating Model Has to Catch Up

Agentic AI is moving faster than many operating models.

Genesys says 40% of CX organizations already use agentic AI, and 82% of CX leaders expect autonomous AI agents to orchestrate customer experiences within three years. That is a big shift for companies still fighting aging infrastructure, broken context transfer, and handoffs that make customers repeat themselves.

Why it matters: The technology is entering customer journeys before many companies have fixed the data, ownership, and handoffs underneath them. Automation will not hide those gaps. It will expose them faster.

Agentic AI + weak handoffs = faster exposure.

🧰 TOOL WORTH KNOWING

Satisfi Labs AI Ticketing Agent

What it does: Satisfi Labs launched an AI ticketing agent for tourism with Ventrata that handles discovery, recommendations, checkout, confirmation, and post-purchase support inside one chat conversation.

CX use case: Attractions, tours, and venues can use it where visitors face layered ticket options, availability questions, mobile browsing, and purchase hesitation.

Worth watching because: The agent connects the conversation to live commerce instead of stopping at advice. In the City Sightseeing New Orleans pilot, Satisfi says the agent logged more than 1,800 ticket interactions, averaged 2.5 tickets per transaction, and saw 90% of discovery and purchases happen on mobile.

Bottom line: This is the customer front door and the cash register moving into the same chat. Useful, if inventory, refunds, accessibility needs, payment failure, and human recovery are designed before the agent starts closing sales.

📡 90-SECOND CX RADAR

CVS Wants the Health-Care Front Door

CVS is working with Google on Health100, an AI assistant meant to help customers schedule care, refill prescriptions, understand coverage, and organize health information across its pharmacy, insurance, and provider footprint.

Why it matters: The next health-care app fight is really a trust fight: who gets to organize the patient’s data, decisions, reminders, and next best action?

The Chatbot Sludge Is Getting Personal

WIRED’s missing-ebike saga is a painfully useful reminder that AI service can turn recovery into endurance work when customers need a human path across merchant, shipper, bank, card issuer, and local agency handoffs.

Why it matters: AI does not have to be malicious to become sludge. It just has to block the customer from the owner who can actually fix the problem.

✅ YOUR MOVE

AI support is starting to move from answer generation into evidence preparation.

That is a better target. Customers do not care how clever the reply is if every handoff still starts at zero.

This week, pick one escalation and build a required case file. Define the context, evidence, customer history, system checks, decision owner, and recovery path that must travel with the issue.

Then ask the uncomfortable question: where are you asking the customer to be the integration layer?

The best support AI will not make the customer repeat less by sounding nicer. It will make the business remember more before the next handoff.

Until Monday,

I’m obsessed with Wispr Flow Pro! Get a Free Month on me.

Your daily signal on AI and CX — minus the hype.

In this issue:

→ Service avoidance becomes a loyalty signal
→ AI has to lower customer effort
→ Phone stress gets a business cost
→ Voice agents need local context
→ The front door needs ownership

🔍 DEEP DIVE

The Customer Already Dreads the Door

Genesys’ new consumer and CX leader research puts a useful number on something most customers already know in their bones: contacting service often feels worse than the original problem.

That is the real AI test.

If AI makes a customer repeat themselves, search for the right menu, argue with a bot, wait for an agent, then explain the whole thing again, the issue is not the model. It is the operating design around it. The customer is still being used as the integration layer between channels, policies, data, and departments.

The hidden risk is that AI lets companies respond faster while still making the customer carry the work. A faster bad path is still a bad path. It just reaches frustration sooner.

For CX leaders, the useful question is not “Can AI answer this?” It is “Can AI remove the next piece of customer labor?” That might mean recognizing intent, pulling context, checking eligibility, routing to a human, explaining the next step, or triggering recovery before the customer asks twice.

Bottom Line: Service AI earns trust when it reduces effort customers can feel, not when it hides the same old maze behind a friendlier voice.

🧭 OPERATOR PLAYBOOK

Audit the Work You Hand Back to Customers

Do not start with the bot transcript. Start with the customer’s job.

Audit every high-volume service path for four things:

1. What the customer has to repeat.

2. What the customer has to prove.

3. What the customer has to find.

4. What the customer has to chase.

Then test whether AI removes that work or simply makes the customer move through it in a new channel.

If the answer is “the customer still has to explain it to a human later,” your automation may be creating a nicer waiting room, not a better journey.

Ask your team: Which part of this service path exists only because our systems cannot talk to each other?

Signal: Customer effort is often just internal fragmentation made visible.

📊 MARKET REALITY CHECK

The Phone Call Is Already Expensive

Zoom’s Virtual Agent Receptionist launch makes the service-pressure point plain: 71% of consumers say calling a business is more stressful than the issue they are trying to resolve, and 50% say they would switch to a competitor after one bad experience.

That does not mean every caller wants an AI receptionist. It means the current front door is already costly.

The first call is often high-intent. Someone wants an appointment, an answer, a status update, a fix, or a person who can help. If AI can answer routine questions, schedule, route, and preserve context, it can lower effort. If it becomes another screen before the real help, it will make the phone feel even more insulting.

Why it matters: The customer-service front door is no longer just a cost center. It is a retention, revenue, and trust test that starts before the customer reaches an employee.

🧰 TOOL WORTH KNOWING

AethexAI

What it does: AethexAI builds localized voice-agent infrastructure for emerging markets, including speech models, deployment tools, workflow-aware routing, telephony, analytics, and agents that can handle support, sales, onboarding, and collections.

CX use case: It is built for service journeys where the customer’s language, accent, dialect, call quality, workflow, and local operating context decide whether automation helps or makes the caller work harder.

Worth watching because: AethexAI says its Kora 1 stack is trained on real conversational speech across emerging markets, supports native tool calling, sub-500ms turn-taking, dialect-aware agents, testing against real call scenarios, and workflows that read, write, trigger actions, and close loops inside existing systems.

Bottom line: Voice AI only reduces customer labor if it understands the customer in the market they are actually calling from. Otherwise, “call automation” becomes another translation job handed back to the caller.

📡 90-SECOND CX RADAR

The AI note-taker in the exam room gets a closer look

Ambient clinical AI listens during a patient visit and helps turn the conversation into clinical notes, summaries, and follow-up documentation. Regenstrief Institute and Suki are partnering to study whether that actually improves the visit, not just the paperwork.

Why it matters: If the tool helps the doctor spend less time typing and more time listening, patients may feel the benefit. If it creates errors, consent confusion, or awkward exam-room behavior, the customer experience problem moves straight into the medical record.

✅ YOUR MOVE

AI is not automatically making service easier.

Sometimes it just gives customers a new place to get stuck.

Pick one high-volume service journey and run a customer-labor audit. Look at what the customer has to repeat, prove, find, chase, translate, or escalate.

Then ask five questions:

1. What should the system already know?

2. What can AI retrieve without asking the customer again?

3. When should the path stop and hand off?

4. What context must transfer to the employee?

5. Who owns the fix when the same issue repeats?

The best service AI does not make the company sound smarter. It makes the customer work less.

Until tomorrow,

I’m obsessed with Wispr Flow Pro! Get a Free Month on me.

Your daily signal on AI and CX — minus the hype.

In this issue:

→ Surveys meet the messy real journey

→ Customer pain gets a new evidence trail

→ Travel advisors become AI operators

→ DoorDash builds memory into shopping

→ Meal planning moves closer to checkout

🔍 DEEP DIVE

The Complaint Is Already Talking

BBVA, one of the largest banks in the world, is using generative AI to analyze selected customer conversations across calls, chats, complaints, web, and app interactions, then combine that evidence with NPS comments and digital behavior.

That sounds like a measurement upgrade. It is really an ownership test.

Surveys tell you what a customer remembers after the fact. Calls and complaints show where the work actually broke. App behavior shows whether one customer’s friction is becoming a pattern. The useful move is not collecting more sentiment. It is connecting the evidence to the team that can fix the broken login, unclear form, blocked payment, confusing policy, or repeated service question.

The customer consequence is simple: if the bank can see friction faster, customers should not have to keep reporting the same problem in different channels. The business consequence is also simple: a live friction map is only valuable if it changes queues, product backlogs, policy wording, and recovery ownership.

Bottom Line: AI can make customer pain easier to see, but visibility without ownership just creates a more sophisticated dashboard of things nobody fixed.

🧭 OPERATOR PLAYBOOK

Give the Signal a Place to Land

Do not treat AI-based experience measurement as a better listening tool. Treat it as a routing system for customer pain.

Audit every high-volume journey for four things:

1. Which customer signals already exist before the survey.

2. Which signals show repeated effort, confusion, delay, or distrust.

3. Which team owns the root cause behind each signal.

4. Which fixes can be tested without waiting for another quarterly report.

Then test whether the same customer issue appears in more than one channel. If it shows up in calls, complaints, app behavior, and survey comments, it is probably not an attitude problem. It is a journey problem with witnesses.

Ask your team: What customer pain do we keep measuring because nobody has agreed to own it?

📊 MARKET REALITY CHECK

AI Is Joining the Back Office, Too

Travel advisors are already using AI for the invisible work behind a high-trust trip: research, itinerary building, supplier comparison, booking administration, client communications, trip audits, and approval-controlled actions.

PhocusWire reports that 59% of advisors are using generative AI, up from 41% a year earlier. Tern says AI use among 6,900 advisors nearly tripled in the last year. Fora says daily AI users generated 3.5 times more bookings and 3.5 times more repeat clients per advisor than non-users.

That does not prove AI caused the whole performance gap. It does show where the operating pressure is moving. Customers may still want the human advisor, but the advisor who can audit options, summarize constraints, check details, and communicate faster has a different service ceiling.

Why it matters: AI is changing the employee capacity layer behind complex service promises, far beyond the customer-facing chat window.

🧰 TOOL WORTH KNOWING

Ask DoorDash

What it does: Ask DoorDash is a shopping assistant architecture that combines an LLM with specialized agents, live backend services, customer memory, and tool access for catalog, cart, checkout, and order-history tasks.

CX use case: It helps shoppers move from vague intent to usable choices without making every request a new search session.

Worth watching because: InfoQ reports DoorDash saw roughly 24% higher grocery checkout conversion, 17% larger baskets, and 7% fewer conversational turns during a seven-day evaluation. That is the right kind of test: did the assistant reduce effort and move the customer closer to a successful task?

Bottom line: Personalization gets useful when memory, inventory, cart logic, and confirmation rules work together. Otherwise, it is just a charming search box with a better vocabulary.

More: InfoQ

📡 90-SECOND CX RADAR

Woolworths tests meal planning that can reach the basket

Woolworths’ My Woolies Chef is an app-native food AI assistant built around recipes, preferences, household needs, product information, local availability, and shopping functionality.

Why it matters: The grocery journey includes deciding, planning, substituting, checking availability, and getting the right items into the cart without making dinner feel like project management.

✅ YOUR MOVE

AI is making more customer evidence visible before the survey ever arrives.

That only helps if the business has a place for the evidence to go.

This week, pick one journey with heavy repeat contact. Pull three signal types from it: survey comments, service conversations, and digital behavior. Then ask where the same friction appears across all three.

Look for four things:

1. The repeated customer question.

2. The moment customers abandon or escalate.

3. The team that can change the root cause.

4. The smallest fix you can test in two weeks.

If AI helps you hear the customer sooner, the next question is not what the customer said. It is who changes the system because they said it.

Until tomorrow,

I’m obsessed with Wispr Flow Pro! Get a Free Month on me.

Your daily signal on AI and CX — minus the hype.

In this issue:

→ Human-in-the-loop isn’t a magic wand
→ Frustration changes the handoff
→ AI referrals raise the landing-page bar
→ Commerce tools move beyond the website
→ Recovery needs earlier ownership

🔍 DEEP DIVE

The Rescue Window Closes Fast

Tuck’s Lauren Xiaoyuan Lu looked at a Taobao experiment where agentic AI handled customer-service chats while human agents monitored the work and stepped in when the system flagged trouble.

The useful part is where the handoff broke. When escalation happened because the AI hit a technical limit, humans could still preserve service quality. But when escalation happened after the customer was already frustrated or skeptical, recovery got much harder. Ratings dropped. Follow-up contacts rose. Agents also appeared to put in less effort once the customer emotion had already gone sideways.

That is the customer-experience lesson. “Human in the loop” only works if the human enters while the relationship is still recoverable. If the customer has already spent ten minutes arguing with the bot, the human is not receiving a clean handoff. They are inheriting damage.

Bottom Line: Escalation is part of the product. Timing decides whether it feels like help or cleanup.

🧭 OPERATOR PLAYBOOK

Write the Stop Rule First

Audit every AI-assisted service flow for four things:

1. The first signal that the customer is confused.

2. The first signal that the customer is emotionally done.

3. The exact moment automation must stop.

4. The context a human needs to recover the relationship.

Then test whether your escalation logic catches frustration before the customer starts repeating themselves, changing channels, or asking for a manager.

Ask your team: Are we measuring how fast AI answers, or how early it gives up when the customer needs judgment, empathy, or authority?

📊 MARKET REALITY CHECK

Borrowed Intent Is Easy to Waste

Retail Dive’s Adobe Commerce-sponsored July 13 piece points to a commerce shift worth watching: AI-referred shoppers can arrive with unusually clear intent. The article cites Adobe-backed metrics that these shoppers convert 42% better than other traffic, have a 27% lower bounce rate, spend 38% longer on site, and view 10% more pages per visit.

Treat that as a signal, not gospel. The operating point still matters: AI may do more of the discovery work before the customer reaches you. That means the landing experience has to preserve the intent the assistant created. Slow pages, weak search, vague product data, messy policies, and dead-end support will waste the introduction.

Why it matters: AI is changing where customers discover you. It is also changing how much intent they bring when they arrive, and how quickly your own experience can squander it.

🧰 TOOL WORTH KNOWING

Revamp

What it does: Revamp uses AI agents to personalize customer engagement across email, SMS, and commerce journeys. It adapts messages to browsing behavior, purchase history, product affinity, timing, discount sensitivity, average order value patterns, brand voice, and product catalog changes.

CX use case: It helps D2C brands move from broad promotional blasts to customer-specific communication that reflects what the customer has actually done, bought, browsed, preferred, and ignored.

Worth watching because: Personalization is usually where customer experience gets weird. Too generic and it feels lazy. Too personal and it feels creepy. Revamp is interesting because it pairs 1:1 message generation with brand voice, product data, integrations, analytics, and guardrails.

Bottom line: If AI is going to talk to every customer differently, the operating question is bigger than “Can it personalize?” It is “Can it personalize without breaking trust, tone, timing, or the business rules?”

📡 90-SECOND CX RADAR

Banks Are Splitting on What AI Is For

Visa says 86% of European banking leaders believe AI will reshape retail banking by 2030, but fewer than one in three cite customer experience or fraud prevention as their primary AI driver. That is the split to watch. Some banks are using AI to cut cost. Others are wiring it into real-time decisions customers actually feel.

Why it matters: CX teams should watch whether AI funding is going toward efficiency slides or customer-impacting decision flows.

Chewy Is Turning Pet Care Into an AI Operations Test

Chewy is using AI across customer service, pharmacy operations, fulfillment, marketing, and veterinary-clinic workflows. The clinic examples are the useful bit: AI agents can prepare triage reports, scribe appointments into practice systems, write follow-up notes, and give veterinarians time back.

Why it matters: The CX story is not “AI in retail.” It is what happens when service, clinical context, pharmacy delivery, and post-visit follow-up start sharing the same operating layer.

Even San Francisco Can’t Make AI Adoption Automatic

San Francisco gave roughly 30,000 city employees access to Microsoft Copilot, and city workers sent or received more than 1 million Copilot messages between July 2025 and April 2026. Still, uptake stayed below 50% across most departments.

Why it matters: Access is not adoption. Public-service AI needs role fit, training, verification rules, and clear accountability before residents feel the benefit.

✅ YOUR MOVE

Today’s issue is about timing. AI can make service faster and discovery smarter, but speed does not rescue a customer who already feels trapped.

The pattern is the same in support and commerce: intent has to be preserved before it turns into frustration.

This week, pick one AI-assisted journey and inspect the first failure signal. Not the final escalation. The first small sign that the customer is confused, skeptical, angry, stuck, or about to switch channels.

Then make the owner name what happens next:

• Does automation keep talking?

• Does a human enter early?

• Does the employee receive the history?

• Does the customer have to start over?

• Does anyone own the recovery?

The moment to save the experience is before the customer has to prove it is broken.

Until tomorrow,

I’m obsessed with Wispr Flow Pro! Get a Free Month on me.

AI is about to make bad customer judgment look disciplined, repeatable, and hard to challenge. That’s what changes the CXO job before most org charts admit it.

Until now, the CXO’s job has mostly been about bringing customer reality into the room and making the case for change. That worked when most of the experience lived in places people could see: the bill, the call center, the broken handoff.

AI changes where the experience gets made. More of it now sits upstream, inside routing logic, eligibility rules, service automation, agent-assist tools, and choices a model makes before a customer reaches a person.

The future CXO won’t just explain what customers are experiencing. They’ll have to help the business decide what it’s willing to automate, what it’s willing to make harder, and where a human being still has the authority to use judgment.

That’s an operating role, not an advocacy role with a bigger title.

The deflection trap

A company deploys AI in service with a straightforward brief: reduce inbound volume. A few weeks later, call traffic is down, queues are shorter, and the early numbers look good. It’s easy to see why the launch gets called a win.

The trouble is that the early numbers may not tell you whether customers got what they needed. The model gets good at closing easy tickets and looping hard ones back into self-service. Handle time falls because the expensive conversations stop happening, not because the problems got solved. Customers make a second attempt, then a third. A quarter or two later, churn is up and nobody connects it to the containment metric people got rewarded for.

The problem isn’t the model. The company treated a deflected call and a solved problem as the same thing because the people setting the measure, building the system, and dealing with the customer were working from different definitions of success.

With AI, that becomes a question of who gets to make the decision and what they’re measured on. Once the logic is in the system, it can hit every channel at once.

From feedback to decision design

The conventional description of the CXO job is that they own customer outcomes. That’s too tidy. The work that creates those outcomes is spread across the roadmap, operating process, financial tradeoffs, legal risk, and technology. By the time it reaches the contact center, it’s somebody else’s customer problem to clean up.

Customers don’t experience that org chart. They experience what it protects: the policy exception, unclear handoff, system limitation, and leadership decision that never looked like a customer-experience decision when it was made.

AI makes the gap between accountability and authority harder to live with. A CXO can’t govern an automated experience with a monthly readout after the decision has been wired into a model. The role has to move earlier, into the choices that shape the system.

CX doesn’t need to own every AI initiative. But it needs a defined role in how customer-impacting automation gets built and governed. Before a high-impact system goes live, the business needs to agree on what it won’t do to a customer in pursuit of a metric. If the goal is contact reduction, what counts as a solved problem? After two unsuccessful attempts, the system should escalate to a person.

Then settle who can change the logic, who owns the exception path, and who can call the experience unacceptable even when the primary metric looks good. Those questions sit across Product, Technology, Operations, Risk, and Service. Vague ownership has always been expensive. AI makes it show up everywhere.

There’s one simple operating rule I’d make non-negotiable: never report deflection by itself. Put repeat contact beside it, along with the number of customers who need a human after self-service fails. Before launch, run a handful of real exception cases through the system, including customers who have already failed twice. If the tool sends them in circles, the owner has to change the logic or explicitly accept the harm. That decision shouldn’t disappear into a project plan.

That’s the shift from customer feedback to decision design. The CXO makes the customer impact visible before the business commits it to code.

The journey is still the org chart

Customer problems often survive because they’re useful to someone inside the building. A transfer may protect a boundary. A delay may manage risk. A confusing bill can be the price of product complexity. None of that requires bad intent. It comes from an organization that lets each function make its own local tradeoff and asks the customer to absorb the combined effect.

This is what journey maps got half right. They showed companies that customers don’t experience departments. But the map was never the point. The point was whether the company would reshape itself around what it revealed. Most didn’t. They funded the easy fixes, then returned to their original shape because budgets, incentives, and authority never moved.

AI doesn’t erase those seams. It executes them faster. It can’t settle competing incentives or fix unclear ownership. It just reproduces the organization’s existing logic at scale.

The future CXO has to keep the journey and the operating model in view at the same time: which internal choice created the friction, who benefits from leaving it in place, and who has the authority to change it?

The future CXO builds consequence into the system

The future CXO won’t win by becoming the company’s AI expert. They’ll win by being able to see the full consequence of a decision that everybody else sees only in pieces.

That means putting some unglamorous discipline into the work: review customer impact before high-risk automation goes live, give people a path to escalate when repeat effort starts climbing, and name an owner when the same complaint keeps coming back.

It also changes the posture of the role. CX has always relied on influence. In the AI era, that influence has to become operating discipline. The CXO may still not own the roadmap, budget, or model. But they need enough standing to force a decision when the business is using automation to avoid one.

Weak leadership is often hiding right there: a leadership team lets every function defend its own reasonable tradeoff and never forces a decision about the total experience. The customer pays for the reluctance to choose.

Most org charts still don’t give CX leaders the authority to govern systems. Product and Technology control or force consequences into tradeoffs. Finance and Legal approve. A bigger title won’t solve that.

The question I’d bring into the next AI meeting isn’t, “How can we automate this?” It’s: What are we willing to stop protecting so the customer stops paying for it?

www.marklevy.co
Follow me on Linkedin

Leave a comment

Thanks for being here. I’ll see you next Tuesday at 8:15 am ET.

👉 If you enjoyed this newsletter and value this work, please consider forwarding it to your friends and colleagues or sharing it on social media. New to DCX? Sign Up.

Share Decoding Customer Experience

Your daily signal on AI and CX — minus the hype.

In this issue:

→ The missing couch problem
→ Why customers leave owned channels
→ The exception path test
→ A workflow agent worth watching
→ Three fresh Radar signals

🔍 DEEP DIVE

Meet the Bot With a Delivery Window

A customer does not experience “logistics.” They experience the text that never comes, the delivery window they miss, the support rep who cannot see the truck, and the second day they have to rearrange their life for a couch.

That is why the Sundays and Cartage AI story is more useful than another chatbot demo. Sundays is using Cartage’s AI logistics coordinator, Wilson, to handle freight quoting, booking, shipment tracking, carrier coordination, customer questions, and delivery-exception handling. Wilson has its own email address and phone number, can answer shipment questions, and escalates when it cannot resolve the issue.

The CX lesson is simple: AI creates value when it sits where the customer pain actually starts. In this case, that is the messy middle between warehouse, carrier, delivery partner, service team, and customer.

Bottom Line: Post-purchase AI has to own visibility, not vibes. If the system cannot see the handoff, it cannot improve the experience.

🧭 OPERATOR PLAYBOOK

Audit the Moment Customers Go Blind

Pick one post-purchase journey where customers keep asking, “What is happening?”

Audit every exception flow for four things:

1. The first system that knows something went wrong.

2. The employee who can see the full customer context.

3. The customer message that sets a real next step.

4. The owner who fixes the issue when AI cannot.

Then test whether a customer can get a useful answer without repeating the story across channels.

Ask your team: Where do we make customers do detective work because our internal systems do not share the same truth?

📊 MARKET REALITY CHECK

Customers Are Bringing Their Own Bot

Gartner’s July customer-service survey found that customers are about 3x more likely to use third-party GenAI tools than company-provided chatbots for service issues. The same release says third-party GenAI use in service has nearly doubled in the past year, while company chatbot use has stayed statistically flat since 2022.

That does not prove brand chatbots are dead. It does prove customers are not waiting politely inside the channel map. If your owned service tools cannot complete tasks, customers will use outside AI to interpret policies, draft complaints, compare options, and decide whether your answer sounds credible.

Why it matters: Service leaders are investing heavily in AI, but customers are rewarding usefulness, not ownership. The brand channel has to solve the problem faster than the customer’s workaround.

🧰 TOOL WORTH KNOWING

Fini AI

What it does: Fini is a self-improving AI customer-support agent for voice, chat, and email. Its site says it can resolve 90% of support tickets at 99% accuracy, go live in 14 days, and become autonomous in 30.

CX use case: Useful for high-volume support teams that need one AI layer across channels, especially where tickets move between Zendesk, Intercom, Salesforce, Front, Freshdesk, Gorgias, LiveChat, Slack, Discord, and related systems.

Worth watching because: The promise is bigger than faster answers. It is whether the same support logic can follow the customer across voice, chat, and email without losing context or making each channel feel like a separate company.

Bottom line: If AI support is going to touch the post-purchase mess, channel memory matters as much as answer quality.

📡 90-SECOND CX RADAR

Deutsche Telekom is rewiring telecom work with AI

OpenAI says Deutsche Telekom is using AI across employee workflows, customer care, network operations, live translation, in-call assistance, and post-call summaries, with more than 50,000 monthly active users of ChatGPT and API tooling.

Why it matters: Telecom AI will show up in familiar voice channels first, so the real test is whether customers get fewer transfers, cleaner context, and clearer escalation.

UK regulators move to oversee cloud providers for financial resilience

Reuters reports that the UK plans to regulate cloud service providers such as Microsoft and Google to protect financial stability.

Why it matters: Customer-facing banking AI depends on cloud concentration, uptime, failover, and vendor controls. The customer does not care which infrastructure layer failed. They care whether they can reach the bank when money is at stake.

AI agents can now pay. Permission is the hard part.

Forbes’ fintech column points to the next agentic-commerce problem: payment agents need clear permissions, audit trails, dispute resolution, and liability rules before customers trust them with real money.

Why it matters: Once AI can pay, checkout becomes a consent, evidence, and recovery journey. “The agent did it” will not be good enough when the purchase is wrong.

✅ YOUR MOVE

AI service work is moving into the part of the journey where customers feel abandoned: after the promise, before the resolution.

That is where brand trust gets built or quietly shredded.

This week, pick one high-friction exception path and map the visibility gap. Who knows first? Who tells the customer? Who owns the fix? What can AI answer safely? What must still go to a human with context?

Treat this as a recovery-cost audit, not a chatbot roadmap discussion.

If the customer still has to chase the business for a basic status answer, the AI project is starting in the wrong room.

Do not automate the apology before you fix the handoff.

Until tomorrow,

I’m obsessed with Wispr Flow Pro! Get a Free Month on me.

Most companies still treat customer effort as a UX problem: a few too many clicks, a clumsy page, a long hold time.

But some of the worst effort lives elsewhere. It’s the work customers take on because the company won’t carry it: scanning their own groceries, chasing an airline claim, babysitting a handoff, or keeping track of a basic task that should’ve just happened.

That’s the thread running through this week’s links. Customers are finding backup for jobs companies quietly handed them, from a staffed checkout lane to software that chases a claim.

Automation can help. But it only earns its place when it takes work off the customer. When it merely moves work around, people notice.

This Week’s Must-Read Links

Walmart’s self-checkout retreat is really about customer loyalty

Self-checkout had a clean pitch: shorter lines, lower labor costs, more control for shoppers. Then customers got stuck weighing produce, waiting for an override, packing bags under a camera, and wondering why a quick grocery run suddenly came with a shift assignment.

What’s happening: Vance Morris argues that Walmart, Target, and Dollar General aren’t just dialing back self-checkout because of shrink. They’re responding to the experience cost of making customers do work the store used to do. That cost shows up in irritation, distrust, and the simple decision to shop somewhere else when the errand feels harder than it needs to.

Why it matters: This is where automation conversations get slippery. A company can remove a staffed lane and call it convenience. The customer judges the whole exchange: Did it save time? Did it make me feel competent? Was help there when the machine balked? Did the store make me do its work?

Reality check: Self-service is a trade, not a free upgrade. Customers will make it when the payoff is obvious. They won’t keep making it when the store pockets the benefit and leaves them with the hassle.

The first all-robot hotel is a hospitality stress test

A fully robot-staffed hotel is coming to the artificial island built for China’s Shenzhen-Zhongshan Link. The easy headline is novelty. The more useful one is that hospitality is about to find out which parts of a stay are really transactional and which parts depend on somebody noticing.

What’s happening: New Atlas reports that the hotel, planned for 2027, will put robots to work across reception, cleaning, and other guest-facing jobs. That’s a big enough experiment to be interesting even if it ends up feeling more like a demo than a destination.

Why it matters: A guest doesn’t need much human contact when everything goes right. The need shows up when the room isn’t ready, the directions are wrong, a child is sick, or a late arrival needs a decision that isn’t in the script. Hospitality has always depended on these unscripted moments, even when the operating model barely acknowledges them.

Between the lines: Judge this hotel by recovery. Delivering a towel is easy; getting a stranded guest back on track is where hospitality earns its keep.

A household run by AI agents shows where delegation starts

Jesse Genet has put AI agents to work on the kind of life admin most people keep in their own heads: parenting logistics, homeschooling, reminders, follow-ups, and all the loose ends that make a week feel like a pile of tabs left open.

What’s happening: The Cut profiles Genet’s growing team of agents and the way they handle pieces of family coordination. It’s an unusual setup, sure, but the need behind it isn’t unusual at all. People are tired of being the manual link between every service, appointment, purchase, and promise in their lives.

Why it matters: Many customer journeys still assume the customer will remember every deadline, compare every option, chase every exception, and bring all the context back when something breaks. That assumption gets expensive once a person has someone, or something, handling the admin for them.

The bottom line: A delegated customer journey has two audiences. The customer still wants confidence and control. The agent needs clean information, proof it can rely on, and a next step it can actually complete.

AirKaren is what happens when service recovery becomes customer work

AirKaren is funny until you sit with why it exists. Nobody wants to become an amateur airline lawyer after a disrupted flight. They do it because getting a fair answer can mean reading regulations, assembling evidence, filing a claim, and following up until somebody finally responds.

What’s happening: AirKaren says it will take on that job for travelers. A customer explains what went wrong, then the service cites the relevant rule, files the claim, and pursues the compensation or remedy the traveler is due.

Why it matters: This is customer effort in its least flattering form. The service failure has already happened, yet the customer still has to learn the company’s rulebook before the company will make things right. The recovery model is broken long before anyone complains about the interface.

Reality check: An outside advocate becomes attractive when a brand makes its own customers prove they deserve help. By that point, the airline may settle the claim, but it has given up the relationship.

DCX Stat of the Week

One-third of customers are ready to delegate the decision

32% of consumers would allow an AI agent to make purchase decisions within boundaries such as budget and preferences, with the customer approving the final purchase.

Takeaway: The agent may soon narrow the field before the customer sees the options. Being available at checkout will not matter if the brand never makes the shortlist.

Source: Accenture Consumer Pulse Research 2026

CX Signal of the Week

Will Guidara on the Restaurant Mistake Customers Feel

“Most restaurants get this wrong,” says Will Guidara in this EntreLeadership clip. His point: teams make decisions from their side of the counter, then mistake an operationally sensible process for a good guest experience.

It sounds obvious until a team is standing inside its own process. Short staffing, a backed-up kitchen, an old policy, and a clumsy handoff can all look reasonable from the inside. Across the dining room, the guest is simply waiting, guessing, or trying to work out whom to ask.

Why it matters: Restaurants make the lesson easy to see, but the problem travels. Customers don’t experience your org chart, your staffing model, or the exception that made sense in last Tuesday’s meeting. They experience the moment in front of them.

Lesson for CX Pros: Get out of the internal story and watch the actual moment. Better yet, make the owner of the journey walk it with you. The conversation changes fast when the rough edge isn’t a slide, but something happening in real time.

Have a CX signal to share? Reply and let me know!

One Last Thing

Customers are not waiting for companies to make every experience easier.

They are finding ways around the work.

They are rejecting self-service that feels like labor, testing what robots can take over, assigning admin to agents, and using outside tools to fight for recovery. That does not mean every company needs more automation.

It means every company needs a clearer view of the work it has pushed onto customers.

Start there.

Have a great week ahead!

Your daily signal on AI and CX — minus the hype.

In this issue:

→ Service AI gets decision rights
→ Vulnerable customers need daylight
→ AI budgets hit bad plumbing
→ Chatbot security becomes CX work
→ Your handoff needs receipts

🔍 DEEP DIVE

The Handoff Is the Experience Now

Commonwealth Bank and Microsoft are showing where service AI is actually headed: away from the cute chatbot in the corner and toward an operating layer that decides where the customer goes next.

The bank’s platform uses Copilot Studio, Microsoft Foundry, and Dynamics 365 to interpret intent, route work, and keep context attached when the conversation moves. Simple questions can stay in self-service. Fraud disputes follow guarded paths. Sensitive or vulnerable language can push the interaction to a human specialist, with summaries and suggested responses waiting for the employee.

That is the part worth stealing.

The CX win is not “the bot handled it.” That is a vanity metric with nicer shoes. The win is whether the system knows the difference between a status question, a policy question, a fraud dispute, a vulnerability signal, and a moment where the customer needs judgment.

A customer who needs help should not have to perform distress convincingly enough to escape the automation.

Bottom Line: Service AI earns trust when it makes the hard cases easier to see, faster to route, and harder to ignore.

🧭 OPERATOR PLAYBOOK

Write the Bot’s Stop Rule

AI service design needs a stop rule before it needs a victory lap.

Audit every AI-assisted service flow for four things:

1. Intent: What can AI answer without judgment?

2. Risk: What policy, fraud, vulnerability, or complaint signal changes the path?

3. Handoff: What does the employee see before saying hello?

4. Repair: Who fixes the customer impact when routing fails?

Then test the transfer like a customer having a bad afternoon, not like a demo team clicking the happy path.

Ask your team: What exact customer language, account condition, policy risk, or frustration signal forces the system to slow down and bring in a human?

Signal: If the stop rule lives in someone’s head, it does not exist for the customer.

📊 MARKET REALITY CHECK

The Checkbook Found AI. The Plumbing Did Not.

PYMNTS Intelligence reports that 85% of financial services and insurance firms plan to increase AI budgets over the next 12 months, based on a March survey of 60 senior technology executives at U.S. enterprises with at least $1 billion in annual revenue.

Good. The board is awake.

Less good: the same report says 30% of financial firms cite data quality and fragmentation as the top barrier to further AI deployment. Translation: the checkbook found AI before the plumbing was ready.

Why it matters: Regulated-service AI inherits the quality of the data, permissions, knowledge base, routing logic, and ownership underneath it. More budget helps only if it pays for the unglamorous work customers actually feel.

🧰 TOOL WORTH KNOWING

Varonis Atlas AI Security

What it does: Varonis Atlas is an AI security platform for governing AI tools, agents, pipelines, identities, and the sensitive data those systems can touch.

CX use case: For teams deploying AI service agents, the customer conversation is now part of the trust boundary. Chat logs, account details, insurance data, complaint histories, and authentication clues need visibility, guardrails, and audit trails.

Worth watching because: Axios reported this week that Google patched a Dialogflow CX flaw that could have exposed or hijacked customer-service chatbot conversations. Varonis says Atlas can inspect prompts and responses in real time, enforce policies, and show audit trails of AI interactions, including LLM calls, data access, and guardrails.

Bottom line: If AI is going to sit inside service journeys, CX and security need to review the same customer conversation before the customer has to.

📡 90-SECOND CX RADAR

Google patched a chatbot flaw that could have exposed customer conversations

Axios reported that Varonis found a critical vulnerability in Google’s Dialogflow CX platform, which is used for customer-service chatbots and voice assistants. Google said the issue was fully mitigated, with no known indication of customer compromise.

Why it matters: Customer support AI now carries the same trust burden as the rest of the service journey. The bot is a conversation, a data surface, a permission question, and a recovery risk wearing one friendly little chat bubble.

✅ YOUR MOVE

Service AI is getting real enough to be boring. That is usually when the risk starts.

Banks are building orchestration layers that decide where the customer goes next. That makes the handoff the new proof point.

This week, pick one AI-assisted service journey and inspect the transfer moment. Look for the first place a customer could be misrouted, misunderstood, exposed, or left without a clear human path.

Then ask for the receipts: the trigger, the transcript, the employee view, the override, the audit trail, and the owner of the fix.

Automation should make routine cases faster and hard cases impossible to miss.

Until next week,

I’m obsessed with Wispr Flow Pro! Get a Free Month on me.

Your daily signal on AI and CX — minus the hype.

In this issue

• Siemens replaces the old phone-tree guessing game with natural-language routing.

• Oreo appeared in only 10% of AI chatbot recommendations for cookies.

• Dscout shows how AI research tools can keep real customer input in the decision loop.

Deep Dive

The Phone Tree Is Becoming a Judgment Call

Siemens Global Business Services supports finance, procurement, HR, sales operations, order and delivery management, employee lifecycle queries, and technical support across more than 80 countries. That is exactly the kind of service surface where old IVR menus break down.

The customer problem is simple: callers often do not know which internal bucket owns their issue. So they guess, wait, repeat themselves, get transferred, and start over.

Siemens says its production AI routing agent replaces that menu tree with natural-language intent detection. A caller says what they need. The system identifies the intent, resolves common questions from a knowledge base when it can, routes to the right team when it should, and hands the conversation to a human with context when confidence drops.

That last part is the operator lesson. The goal is not to make the customer prove they deserve a person. The goal is to remove the guessing, keep the receipt, and make escalation feel like continuity instead of failure.

The dangerous version of this is a fluent wall between the customer and help. The useful version is a better traffic controller.

OPERATOR PLAYBOOK

Build the Escape Hatch First

Before you put an AI agent in front of a high-volume service entry point, pressure-test four things:

1. Intent map: What are the top reasons people actually contact you, in their own words?

2. Confidence threshold: At what point does the agent stop trying and hand off?

3. Context handoff: What exactly does the human receive before speaking to the customer?

4. Recovery clock: How quickly can you detect a bad routing pattern and fix it?

The best question for the service team is: What is the first sentence the customer hears after the AI gives up?

If that sentence sounds like, “Can you start from the beginning?”, the design is not ready.

Market Reality Check

Loyalty Has to Be Machine-Readable

Accenture Consumer Pulse Research 2026 report has a sharp example hiding inside the agentic-commerce conversation: Oreo, one of the world’s most recognized brands, appeared in only 10% of AI chatbot recommendations for cookies.

That is not a branding problem in the usual sense. It is a visibility problem in the agent layer.

Accenture says Mondelez is overhauling its $3.5 billion digital commerce strategy around that reality: unblocking crawlers, restructuring its digital presence, and making product content machine-readable across its portfolio.

The CX lesson is bigger than cookies. A customer can love a brand and still have their agent fail to find it, trust it, compare it, or choose it. In an agent-mediated journey, loyalty depends on proof the machine can parse and performance the customer can feel.

That brings today’s Siemens story into sharper focus. Whether the agent is routing a call or choosing a product, the operating question is the same: can the system understand the intent, read the evidence, make the right next move, and recover when the answer is not obvious?

Tool Worth Knowing

Dscout

What it does: Dscout is an AI-powered feedback and testing platform for product, research, and experience teams. Its AI Studio can draft studies from a question, Figma prototype, or URL; run AI-moderated interviews; surface patterns and takeaways; and ask source-backed questions of the data.

CX use case: When teams are redesigning a service flow, testing a new AI assistant, or deciding which customer problem deserves automation, Dscout gives them a faster way to hear from real people before the roadmap hardens.

Worth watching because: Today’s Siemens story is about getting the handoff right. Dscout is useful on the other side of that decision: testing whether customers understand the flow, where they get stuck, what language they actually use, and what the AI should never guess.

Caution: AI can make research faster, but it can also make teams overconfident. The value comes from better questions, real participant input, and clear evidence before the business changes the customer journey.

90-Second CX Radar

Retail AI chatbots still have a trust-and-use problem

EMARKETER reports that 38.2% of U.S. digital shoppers have not used a retail AI chatbot and are not interested in doing so. That is a useful counterweight to shopping-agent hype. Discovery, education, handoff, and a clearly better task path still matter.

WhatsApp pushes AI agents deeper into business messaging

The Meta Business Agent rollout in India gives businesses a familiar messaging surface for support, booking, lead qualification, and commerce. The customer journey question is whether brands make handoff and accountability as easy as the chat.

Your Move

Pick one high-volume service entry point this week. Phone, chat, email, portal, WhatsApp, whatever carries the most customer confusion.

Do not start by asking, “Can AI answer this?”

Ask: What does the customer need the system to understand before anyone answers?

That is where the real design starts.

I’m obsessed with Wispr Flow Pro! Get a Free Month on me.