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

In this issue:

→ Translation doesn’t prove the customer understood
→ Consent needs more than a checkbox
→ Privacy concern rarely becomes usable control
→ CallRail gives missed calls some memory
→ Action agents still need an owner

🔍 DEEP DIVE

Consent Can’t Be Another Checkbox

BandhuCare is getting ready for a pilot with head and neck cancer patients in India. The app answers routine questions by text or voice in eight Indian languages. It also turns conversational symptom updates into standard patient-reported measures and summarizes them for clinicians.

Here’s the part I’d watch. One AI layer pulls from a clinician-curated knowledge base. A second checks whether the response is actually grounded there. The consent agent explains the information in plain language, then checks whether the patient understood it before asking them to proceed.

That’s a bigger deal than it sounds, and it travels well beyond healthcare. We tend to treat translation as if understanding comes along for free. It doesn’t. A sentence can be readable and still leave the decision muddy. A fluent answer can hide uncertainty, miss a cultural cue, or push someone forward who isn’t sure what they just agreed to. In a high-stakes journey, the system needs to know when to explain again, stop, or bring in someone who can help.

Bottom Line: “The AI answered” is a weak success measure. The customer needs to understand enough to make a safe, informed next move.

🧭 OPERATOR PLAYBOOK

Test the Meaning, Not Just the Words

Take one AI-assisted explanation, disclosure, or consent flow and check four things:

1. The decision the customer thinks they’re making.

2. The language, literacy, disability, or context barriers that could change meaning.

3. The signal that the customer is confused or unsure.

4. The person or channel that can explain it differently.

Then ask a customer to describe the choice, the consequence, and the next step in their own words.

Ask your team: What do we currently count as consent or completion without checking comprehension?

📊 MARKET REALITY CHECK

Concern Isn’t the Same as Control

Customers are worried about AI privacy, but many can’t tell what the product is actually doing with their conversations. In a weighted survey of 1,999 U.S. adult AI-assistant users, more than 80% were concerned about how their conversation data was used. Roughly 60% didn’t know whether their assistant trained on those conversations. Only 18% had paid for stronger privacy protection.

Customers don’t treat every privacy issue the same way. In the study’s choice experiment, users valued keeping human reviewers out of their conversations at $11.20 a month. That’s nearly four times what they placed on preventing model training. It doesn’t prove what every customer will pay. It shows that human access, model training, memory, and sponsored influence are separate concerns.

Why it matters: Tell customers who can see their data, what the system remembers, and how to change it. Put those controls in front of them before they share something sensitive. Don’t bury them in a settings maze.

Data Source: arXiv

🧰 TOOL WORTH KNOWING

CallRail Voice Assist

What it does: CallRail's Voice Assist answers calls for small businesses, handles common questions, captures what the customer needs, and can now continue the conversation by text. It follows up after missed calls or hang-ups and keeps the call-and-text history together.

CX use case: Think about a plumber, repair shop, or local service business. The phone rings while everyone is already helping somebody. Voice Assist can capture the new customer’s need so the follow-up doesn’t begin with, “Tell me again why you called.”

Worth watching because: This is a very ordinary customer problem with real money attached. CallRail says 28% of business calls go unanswered on average. Voice Assist customers report 44% more answered calls, and leads are seven times more likely to engage than through voicemail. Those are vendor-reported engagement measures, not proof of resolution. Still, they point at a costly gap in the small-business journey.

Bottom line: Picking up is useful. The experience gets better only if the context survives, expectations stay honest, and urgent or unusual needs reach a person quickly.

📡 90-SECOND CX RADAR

Large action models push CX from answers into execution

A Genesys executive makes the case that the next shift is from language models that interpret intent to action models that coordinate work across systems. Utility Warehouse reportedly more than doubled containment in complex billing and service-restoration journeys using this approach.

Why it matters: Once an agent can authenticate, update, rebook, compensate, or restore service, “Did it give a good answer?” is no longer enough. Someone has to own the approved outcome, the exception path, and the evidence that the customer was actually helped.

✅ YOUR MOVE

Pick one AI interaction where the customer agrees, authorizes, accepts, or moves forward.

Ask three people who weren’t involved in designing it to complete the flow. Then ask them what they agreed to, what the AI can do with their information, and what happens next.

Don’t rescue the test with extra explanation. Whatever gets lost between the screen and their answer is what you need to fix.

If the customer can’t explain the choice, the journey isn’t finished.

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:

• A shiny fridge fooled Starbucks’ inventory AI

• Frontline workarounds became product evidence

• Governance rollbacks expose the production gap

• Cekura turns failures into regression tests

• IHG keeps old search beside AI

🔍 DEEP DIVE

The Fridge Was Part of the Product

Starbucks rolled an AI inventory tool across all 11,300 company-operated North American cafés. It was supposed to turn an hour-long count into a 10-to-12-minute scan. Nine months later, the company pulled it.

The failures were painfully ordinary. A shiny refrigerator doubled the milk count by reflecting cartons. Weak Wi-Fi erased progress. The system mislabeled syrups and sometimes counted the trash can as food. Meanwhile, manual counts were treated as no count, so the fallback stopped being useful precisely when the AI wasn’t.

That reaches the customer faster than it sounds. Bad inventory data becomes an unavailable drink, a wrong menu promise, a longer wait, or a barista doing cleanup during the morning rush. The problem wasn’t simply model accuracy. The café itself, including reflections, connectivity, storage layouts, and human judgment, was part of the product.

Bottom Line: If the field can break the AI, the field belongs in the test plan. Scale only makes an untested assumption more expensive.

Source: Fast Company

🧭 OPERATOR PLAYBOOK

Put the Mess in the Test Plan

Audit one customer-impacting AI workflow for four things:

1. The physical, digital, and data conditions the pilot avoided.

2. The frontline override when the model is plainly wrong.

3. The customer promise affected by a bad output.

4. The signal that pauses rollout before failure spreads.

Then test whether the fallback still works when the primary system doesn’t.

Ask your team: Which “user error” keeps appearing because the product was tested in cleaner conditions than the job?

📊 MARKET REALITY CHECK

Production Finds What the Pilot Missed

Sinch surveyed 2,527 enterprise decision-makers across 10 countries and six industries. Among organizations that had put an AI communications agent into production, 74% said they had been forced to roll one back or shut it down because of a governance failure.

The rate rose to 81% among organizations that described their guardrails as fully mature. That doesn’t necessarily mean mature teams are worse at AI. Sinch’s interpretation is that better monitoring helps them see failures that less mature teams miss. The reported triggers included customer-data exposure, hallucination or brand risk, and a lack of auditability.

Why it matters: Production is not proof that the system works. It is where teams need enough visibility to catch a bad customer interaction, stop the damage, explain what happened, and roll back without turning recovery into another project.

🧰 TOOL WORTH KNOWING

Cekura

What it does: Cekura tests and monitors voice and chat AI agents. Teams can simulate conversations across different personas, run repeatable evaluations before release, and track live-call signals such as latency, interruptions, sentiment, and failures after launch.

CX use case: Build scenarios around real customer journeys such as cancellation, rescheduling, authentication, escalation, noisy callers, or off-script requests. Replay known trouble spots after prompt or model changes so a fix becomes a regression test.

Worth watching because: Today’s issue is about conditions a demo ignores. Cekura gives teams a way to turn those conditions into release gates and alerts instead of waiting for customers to rediscover them.

Bottom line: A test tool can show you what failed. It cannot decide what customers should experience. CX still needs to define the journeys, thresholds, escalation rules, and recovery path.

📡 90-SECOND CX RADAR

IHG keeps traditional search beside its new AI option

IHG launched conversational search in beta on its U.S. website and app, using verified property data, guest reviews, real-time availability, pricing, points, and points-plus-cash options. Traditional search remains available during the beta.

Why it matters: Customer choice is part of rollout design. Keeping both paths visible gives IHG a cleaner comparison of findability, booking completion, correction, and where AI recommendations still need help.

✅ YOUR MOVE

Pick one AI workflow that has moved beyond the demo. Then walk it under the conditions the launch deck politely ignored.

Slow connection. Messy data. An unusual customer request. A frontline employee who disagrees with the output. A customer who wants the old path back.

Write down what breaks, who notices first, and whether that person can stop or correct the system without starting a committee.

Then add those conditions to the release gate. The goal is simple: keep customers from becoming the test environment.

If reality can break the AI, reality belongs in the test.

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:

• HSBC hires for code and customer judgment

• Travel tech still makes travelers do the stitching

• DBS measures resolution beside satisfaction

• Ada turns bot rules into managed releases

• Hospital logistics and licensed answers hit Radar

🔍 DEEP DIVE

Two Hundred Hires, One Operating Choice

HSBC is putting more than 200 new roles into one Singapore bet: over 100 AI specialists and another 100 wealth relationship managers.

That hiring mix is interesting.

The AI center will recruit people across natural language processing, data science, governance, and human-centered design. Its first work includes personalized wealth conversations, agentic treasury, and AI-enabled payments. At the same time, HSBC is adding relationship managers for customers whose decisions carry complexity, risk, and real money.

That is an operating choice. Speed and analysis can move to the machine. Context, challenge, judgment, and accountability still need a person customers can trust. The hard part is designing the handoff so the adviser receives the reasoning, customer history, and unresolved question instead of starting the conversation from scratch.

The hiring plan does not prove the experience will work. It does show what HSBC believes the service model requires.

Bottom Line: AI capacity without relationship capacity can make service faster and thinner. Build both, then measure whether customers get better decisions and cleaner handoffs.

🧭 OPERATOR PLAYBOOK

Audit the Pair, Not the Bot

Pick one customer journey where AI and a person are meant to work together.

Audit the operating model for four things:

1. Work shift: Which task genuinely moves to AI?

2. Judgment line: Which decision still belongs to a person?

3. Context handoff: What must arrive with the customer?

4. Shared measure: Which customer and business outcomes move together?

Then run a hard case through both sides of the model. A policy exception. A nervous customer. Conflicting data. A decision worth challenging.

Ask your team: Did we redesign the human role, or just leave a person waiting behind the automation?

📊 MARKET REALITY CHECK

Measure the Chat After the Answer

DBS says customer satisfaction for its Joy assistant rose 17% in Singapore during the first half of 2026, while calls or emails to customer service fell 7%. Its retail digibot resolved nine in ten queries digitally without a follow-up call.

That combination is the useful part.

Most chatbot reports stop at containment. DBS is at least putting customer satisfaction beside channel reduction and resolution. That gives operators a better question than, “How many contacts did the bot keep away from an agent?”

DBS still leaves some important blanks. It doesn’t publish the satisfaction scale, query mix, or how long it waited before counting a follow-up call. These are company-reported numbers, not an independent audit.

Why it matters: Deflection tells you work stayed out of the contact center. It doesn’t tell you whether the customer got what they came for. When satisfaction rises and repeat demand falls, the customer and the operating model may both be better off.

🧰 TOOL WORTH KNOWING

Ada

What it does: Ada is an AI customer-service platform built to resolve conversations across messaging, voice, and email. Its new Custom Instructions API gives teams a programmatic way to manage the system rules that shape how the AI agent responds and acts.

CX use case: Put tone, policy, promotion, and customer-specific rules through review, testing, staged activation, and rollback instead of changing them ad hoc in a live bot.

Worth watching because: Ada connects the customer-facing conversation to enterprise workflows across channels. The control layer matters because one instruction change can affect thousands of interactions.

Bottom line: If a rule can change what the customer hears or what the agent does, treat it like a production release.

📡 90-SECOND CX RADAR

The Patient Journey Has a Backstage

Deliverz.ai is coordinating robots and human transporters across hospital doors, elevators, clinical systems, and delivery routes. Its latest release says chemotherapy delivery between Sheba Medical Center’s pharmacy and oncology units fell by more than half.

Why it matters: Patients feel internal logistics as waiting. The next CX metric may live in the hallway between departments, with a named owner for the exception when the physical workflow stalls.

✅ YOUR MOVE

AI is getting more capable. The service model around it now has to get more deliberate.

Customers will judge the combined experience: the machine’s speed, the person’s judgment, and the handoff between them.

This week, inspect one blended journey. Name what AI owns, where human judgment begins, which context crosses the handoff, and which customer measure can stop the rollout.

If those answers live in different departments, put the owners in one room before adding another capability.

The customer does not care which part was automated. They care whether the whole service worked.

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:

→ 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.

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,

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.

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.

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.

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.

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.

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

In this issue:

→ Customers may arrive after AI chooses
→ Web content becomes a trust boundary
→ Prompt injection hits the buying journey
→ AI concierge moves into complex support
→ Banks get a resilience warning

🔍 DEEP DIVE

Your Customer May Send a Scout First

Customers are starting to send AI into the buying journey before they show up themselves.

That agent may research, compare, filter, and recommend before the customer ever reaches a brand’s site.

That changes the job of customer understanding.

Surveys, complaints, reviews, click paths, and sales calls still matter. But if an assistant is shaping the shortlist, the customer journey starts inside a system you don’t fully see. The assistant may read product pages, support docs, comparison sites, reviews, policies, pricing pages, FAQs, and whatever else looks authoritative enough to answer the customer’s question.

That creates a practical problem. Your content can’t be marketing fog. It has to be clean enough for a machine to parse, specific enough to prove, and current enough to trust.

If the agent gets the wrong answer, the customer still blames the experience.

Fair? Maybe not.

But that’s the job now.

Bottom Line: If AI becomes the customer’s scout, CX leaders need to treat public content, policy pages, proof points, and recovery paths as journey infrastructure.

🧭 OPERATOR PLAYBOOK

Audit the Journey the Agent Reads

Before trying to influence what AI recommends, audit the customer decision path your human buyer and their assistant both inherit.

Start with one high-intent journey: product comparison, renewal, return, booking, eligibility, support escalation, or payment.

Then check four things:

1. Source truth: Is there one current page for pricing, availability, terms, exclusions, and eligibility?

2. Proof: Are customer claims backed by specific evidence, or by soft positioning that sounds good until someone asks for details?

3. Policy clarity: Are return, cancellation, privacy, escalation, and complaint rules written like someone might need them under stress?

4. Recovery ownership: Is there a named human path when an AI-shaped expectation is wrong?

Then test whether an assistant can answer a real customer question without inventing the connective tissue you forgot to provide.

Ask your team: If a buyer asked an AI agent to compare us with two competitors, which page would make us sound trustworthy, and which page would make us sound slippery?

📊 MARKET REALITY CHECK

Hidden Instructions Are Now Journey Design

A malicious page can now talk to the agent without talking to the customer.

That’s the nasty customer-journey wrinkle in Zscaler’s research. Web content can carry instructions meant for agents, not people. Malicious sites used search poisoning and hidden page elements to influence AI agents that were trying to complete tasks.

Across 26 LLMs, 4 failed to respond correctly in a payment-scam test, and 2 misclassified a fraudulent DeBank impersonation page.

That doesn’t prove every shopping or service assistant is fragile. It does prove the trust boundary has moved onto the page.

Why it matters: If agents start browsing, comparing, recommending, booking, or paying for customers, CX teams inherit a security and content-quality problem. The journey now includes what the agent reads, what it ignores, what it trusts, and who fixes the outcome when a hidden instruction bends the decision.

🧰 TOOL WORTH KNOWING

Lorikeet

What it does: Lorikeet is an AI customer concierge for complex support, built to help companies resolve complicated cases across channels and around the clock.

CX use case: Useful for teams where support work isn’t a simple FAQ lane: insurance claims, healthtech coordination, fintech account questions, travel changes, telecom troubleshooting, or any service moment where the customer needs a real resolution across systems and policies.

Worth watching because: It’s a good test of the next support promise. If AI is going to shape customer expectations before the customer reaches you, the support layer has to do more than deflect tickets. It has to understand the case, use the right source of truth, take the right next step, and know when a human needs to own the outcome.

Bottom line: The useful question isn’t “Can AI answer?” It’s “Can AI resolve the messy part without making the customer pay for the mess?”

📡 90-SECOND CX RADAR

Bank of England flags AI as an operational-resilience risk

The Bank of England’s Financial Policy Committee warned that rapid frontier AI advances have increased cyber and operational-resilience risks, because bad actors may be able to create shocks and outages at lower cost and larger scale.

Why it matters: For banks and other high-trust services, AI risk shows up as access, outage communication, fraud response, remediation, and who owns the customer when the system fails.

✅ YOUR MOVE

The customer journey is starting earlier than your analytics may show.

It may start when a customer asks an AI assistant what to buy, who to trust, what policy applies, or whether your promise is credible.

Pick one journey this week and walk it as a customer’s AI assistant would.

Check five things:

1. What sources would the assistant read?

2. Which answer would it probably give?

3. Which claim would it struggle to prove?

4. Which policy would it misunderstand?

5. Where does a human recover the relationship?

If an AI assistant is going to carry your promise into the room, make sure it isn’t carrying a blurry copy.

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:

→ Backlogs are pushing AI into service
→ Self-service needs an escape hatch
→ Delegation is becoming customer behavior
→ Call copilots move into sales
→ Finance agents get runtime guardrails

🔍 DEEP DIVE

The Phone Line Was the Symptom

Texas DPS didn’t have a chatbot problem. It had a demand problem.

The agency’s Driver License Division was handling roughly 640,000 calls a month, while the old system answered only about 10% of incoming calls. Instead of only adding people, Texas rebuilt the contact center around Amazon Connect, Salesforce, chat, text, AI-powered virtual agents, automated voice response, and a unified agent desktop.

The useful CX lesson is simple: automate the reason people are stuck, not the conversation about being stuck. Texas found that roughly 40% to 45% of callers just wanted license-status updates. That’s exactly the kind of high-volume, low-judgment demand AI can remove from the queue if the journey still gives complex cases a human path.

Bottom Line: The win is not a smarter front door. It is fewer customers trapped at the front door in the first place.

🧭 OPERATOR PLAYBOOK

Split Demand Before You Automate It

If customers are waiting, don’t start with the AI feature. Start with demand anatomy.

Audit every high-volume service flow for four things:

1. The top repeat questions that need retrieval, not judgment.

2. The moments where customer anxiety requires a human.

3. The systems agents open to answer one basic question.

4. The status updates customers should never need to call for.

Then test whether the automated path reduces live demand without hiding exceptions.

Ask your team: Which customer contacts would disappear if the status, next step, and recovery owner were visible before the customer asked?

📊 MARKET REALITY CHECK

Customers Are Delegating the Work They Resent

Accenture’s 2026 Consumer Pulse research surveyed 25,590 consumers across 16 countries and found that 74% would let an AI agent handle routine tasks such as negotiating deals, resolving complaints, renewing subscriptions, or reordering.

That doesn’t mean customers want to hand over the entire relationship. The same report says 32% are ready to let an agent make purchase decisions inside defined boundaries, while 9% are open to fully autonomous shopping. The pattern is more useful than the headline number: people delegate hassle first.

Why it matters: CX teams should expect AI adoption to start around repetitive status checks, complaint handling, renewals, returns, replenishment, and post-purchase work. Those are the places where customers already feel the brand is making them do unpaid labor.

🧰 TOOL WORTH KNOWING

HeyCaddie

What it does: HeyCaddie is an AI copilot that joins sales calls, listens live, pulls answers from a private knowledge base, and can feed the rep the right fact or say it aloud during the conversation.

CX use case: For sales and account teams, the customer experience problem is the stall: “let me get back to you,” wrong pricing, fuzzy integration claims, or a missed proof point that was sitting in a deck somewhere. HeyCaddie is built to reduce those mid-call gaps.

Worth watching because: It connects Google Calendar, Gmail, and Drive, joins Zoom, Google Meet, or Teams calls, grounds answers in the team’s own docs, flags knowledge gaps, and records what answer was given and what source it came from.

Bottom line: Live call copilots are moving AI from after-call notes into in-call performance, which means teams need source quality, escalation norms, and rules for when the copilot should stay quiet.

📡 90-SECOND CX RADAR

MAS backs runtime safeguards for finance agents

Singapore’s financial regulator and industry partners published the SAFR framework for AI agents in finance, focused on controls at the point of action. That matters because payments, treasury, advisory, compliance review, and client engagement all become customer-impacting when agents can act inside predefined mandates.

Why it matters: Journey teams will need action logs, stop rules, and mandate boundaries before agentic workflows reach money movement or advice.

✅ YOUR MOVE

This is the practical line for CX teams: don’t automate a channel until you understand the demand inside it.

Some demand is status. Some is reassurance. Some is exception handling. Some is customer confusion created by your own policies, forms, pricing, portals, or handoffs.

Pick one service queue this week and sort the top contact reasons into three buckets: automate, assist, and protect. Automate what shouldn’t require a human. Assist the employee where judgment still matters. Protect the moments where the customer needs a person, not a prettier deflection loop.

That’s how AI moves from demo to service design.

The goal is not fewer conversations. The goal is fewer unnecessary conversations.

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:

→ AI starts routing patients
→ Consent becomes a service moment
→ Scribes test patient trust
→ Heidi shows the workflow layer
→ Travel agents get transaction power

🔍 DEEP DIVE

When the App Becomes the Front Desk

The NHS plans to use AI inside its app to route patients toward the right service: a GP appointment, pharmacy, A&E, or another care path. First-year reach is expected to be about 200,000 patients, with availability for all users planned by April 2028.

On paper, that’s exactly the kind of thing healthcare needs. Fewer phone queues. Less appointment roulette. Better use of clinical capacity. Nobody’s sitting around wishing the 8 a.m. call scramble had more hold music.

Here’s the rub. The first decision in a care journey is often the scariest one. The patient isn’t asking for a slick routing layer. They’re asking, “Am I safe? Where do I go? What if this is wrong?”

So the test isn’t whether AI can move people through the front door faster. It’s whether the patient can understand the recommendation, challenge it, reach a human, and avoid getting penalized for being old, anxious, confused, offline, or just not fluent in app logic.

Bottom Line: AI can make healthcare access better, but only if the recovery path is as visible as the recommendation.

🧭 OPERATOR PLAYBOOK

Write the Wrong-Door Plan First

If AI’s going to direct customers, patients, travelers, shoppers, or account holders, don’t start with the happy path. That’s the demo. Start with the misroute. That’s the business.

Audit every AI-assisted access flow for four things:

1. What the customer’s told when AI recommends a path.

2. Who owns the override when the path feels wrong.

3. What happens to people who can’t or won’t use the digital channel.

4. How quickly the business corrects a bad recommendation.

Then test whether the customer can recover without starting over.

Ask your team: Where can AI send someone to the wrong place, and who owns the apology plus the fix?

Signal: The front door’s no longer a page, phone number, or intake form. It’s a decision someone has to own.

📊 MARKET REALITY CHECK

The Note Taker Is Part of the Visit

The Guardian Australia reports that use of AI scribes by Australian GPs nearly doubled from 22% in August 2024 to 40% in November 2025, according to an RACGP online poll. That’s not a lab experiment. That’s the third presence in the room.

And look, the pressure is real. Clinicians need time back. Notes need to get finished. Health systems are drowning in admin. If AI can give the clinician more eye contact and less keyboard time, patients may actually feel the benefit.

But consent isn’t fine print here. It’s part of the care experience. Patients need to know when a visit’s being recorded, where the data goes, whether saying no changes access, and who checks the note before it becomes part of their record.

Why it matters: Healthcare AI won’t be judged only by productivity. It’ll be judged by whether patients feel respected when the system listens, records, routes, and stores their most sensitive moments.

🧰 TOOL WORTH KNOWING

Heidi Health

What it does: Heidi Health is an AI clinical documentation platform that turns consultations into notes, codes, follow-up tasks, patient communications, and other care workflow outputs.

CX use case: The useful promise is simple: less face-in-screen time, faster follow-up, fewer dropped tasks, and cleaner documentation for the next person in the care chain.

Worth watching because: Tools like this sit right on the consent line. They can make the visit feel more human. They can also make the patient wonder who’s listening, what gets saved, and whether the clinician actually checked the output.

Bottom line: AI documentation becomes a customer experience tool when it gives time back to the visit without making the patient feel managed by a silent recorder.

📡 90-SECOND CX RADAR

AI agents can now move from travel search to booking

eDreams ODIGEO says it’s working with Visa to support AI-initiated transactions across its travel brands, using Visa’s Trusted Agent Protocol, Agentic Directory, and Payment Passkeys. That moves agentic travel from “help me compare options” to “book this within my rules.”

Why it matters: Once AI can transact, CX needs agent identity, permission limits, payment recovery, and a clean way to unwind the wrong booking.

✅ YOUR MOVE

AI’s starting to sit at the first decision point in high-trust journeys.

That can make access faster. It can also make the wrong turn harder to challenge.

This week, pick one AI-assisted flow and write the recovery map before you write the success metric.

Check:

1. What decision can AI make or influence?

2. What does the customer see when that decision happens?

3. Where can a human override it?

4. What happens when the customer says no?

5. Who owns the fix when the path is wrong?

If AI becomes the front door, don’t make the human door a scavenger hunt.

Until tomorrow,

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