Don’t Make Good Customers Prove They’re Innocent
Retailers want AI to catch bad returns faster. The harder job is making sure honest customers don’t get trapped in the fraud lane.
Your daily signal on AI and CX — minus the hype.
DCX Stat of the day: 9% of all retail returns are fraudulent, according to the 2025 Retail Returns Landscape from NRF and Happy Returns. National Retail Federation
In this issue:
🔍 The refund desk gets a risk score
🧭 Put the return flag on trial
📊 Bot traffic needs a name tag
🧰 MX brings banking AI in-house
📡 Klaviyo blurs marketing and service
🔍 DEEP DIVE
The Refund Desk Just Got a Risk Score
Retailers are using AI to flag return fraud, spot label swaps, identify product mismatches, score risky return behavior, and move inventory back into sale faster. That makes sense. Returns are expensive, fraud is getting sharper, and manual review does not scale gracefully. Anyone who has watched a warehouse team process holiday returns knows this is not a tiny back-office nuisance.
But the customer feels the control differently. A return is usually a recovery moment. The customer bought the wrong size, got the wrong product, changed their mind, or had a real issue. If AI treats that moment like a fraud investigation by default, the brand may protect margin while teaching legitimate customers that the company does not trust them.
That is where the money shows up. A bad return experience costs more than the refund. It can cost the next purchase, the loyalty account, the review, and the service contact that follows. The useful move: clearer evidence, faster escalation, and a human review path before refunds get delayed or denied. AI can flag the risk. It should not become the only witness.
Bottom Line: Returns are now a trust checkpoint where fraud prevention, loyalty, margin, and service recovery collide.
📬 Copy-Paste Take
Before using AI to slow, deny, or inspect a return, define the customer proof path: what evidence triggers a review, who can override the flag, how the customer is told what happened, and how fast a clean return gets unstuck. Fraud control without recovery design turns honest customers into suspects and sends tomorrow’s revenue to the competitor with the easier apology.
🧭 OPERATOR PLAYBOOK
Put the Return Flag on Trial
Audit every return, refund, chargeback, exchange, and exception flow for four things:
The exact signals AI is allowed to use before a customer is flagged.
The human review step before a refund is delayed or denied.
The customer-facing explanation when the system needs more proof.
The service recovery path when the system gets it wrong.
Put CX, fraud/risk, service ops, legal, product, and ecommerce in the same room for 30 minutes. Then test whether a loyal customer with an unusual but legitimate return can still get through without needing three calls and a blood sample. Metaphorically. Please do not add the blood sample.
Ask your team: Where can AI slow a customer down today without a named owner for the explanation, override, and apology?
Signal: Any automated fraud score that affects a refund should have an owner, an appeal path, and a clock.
📊 MARKET REALITY CHECK
Bot Traffic Needs a Name Tag
Cloudflare says automated agents and bots now drive more than half of all web requests. That matters far beyond publishers. As AI systems browse, cite, shop, summarize, and transact, businesses need to know whether traffic is search, training, agent use, fraud, monitoring, or a legitimate customer acting through software.
Cloudflare is moving toward separate classifications for search, training, and agent use, with new defaults scheduled for September 15, 2026 for certain customers and pages. Same operating problem, different doorway: if the business cannot tell what kind of machine is at the front door, it will block useful agents, feed bad actors, or make customers pay the price for messy controls.
Why it matters: CX teams will inherit the fallout when bot policy is handled as a security-only decision. Discovery, checkout, support, refunds, and content trust all depend on knowing who or what is acting for the customer before the experience gets slowed, blocked, or misread.
Unclear traffic = unclear accountability.
🧰 TOOL WORTH KNOWING
MX Conversational Financial Intelligence
What it does: MX announced an enterprise conversational financial assistant for banks, credit unions, and fintechs. It is designed to live inside the financial institution’s own secure digital channel, answer customer money questions from permissioned data, and keep the relationship with the institution instead of handing the moment to a third-party assistant.
CX use case: Digital banking support, financial wellness guidance, product recommendations, account insights, and next-step routing when a customer needs help understanding their money.
Worth watching because: The design separates conversational guidance from high-stakes actions like transferring funds or opening accounts. That is the right instinct. In financial CX, a helpful answer can become a bad experience the second it feels like the system acted beyond the customer’s intent.
Bottom line: Useful if your AI roadmap touches money, eligibility, account action, or customer advice. The assistant is only as trustworthy as the permission rules, audit trail, and handoff design around it.
The DCX AI Today - AI Tool Directory - If you lead a CX team and want a curated shortlist of tools worth evaluating, this is your starting point.
📡 90-SECOND CX RADAR
Klaviyo moves marketing and customer agents into public beta
Klaviyo is pushing Composer and Customer Agent into public beta, tying campaign, segment, service, preference, and intent data closer together. That can help teams fix abandoned-cart gaps and answer support questions faster. It can also create a new kind of fatigue if every service signal becomes a marketing trigger.
Why it matters: The customer does not experience marketing and support as separate departments. If AI starts coordinating both, someone has to govern cadence, consent, channel fit, and when silence is the better CX move.
✅ YOUR MOVE
AI is getting closer to the moments where customers ask the business to trust them: refunds, financial guidance, service conversations, and agent-mediated traffic.
That is where automation gets useful. It is also where sloppy ownership gets expensive.
Pick one customer-impacting AI flag this week. A fraud score, refund hold, support escalation, personalization trigger, or financial recommendation.
Put the owner of the journey, the owner of the risk, and the team that has to answer the customer in the same conversation.
Then ask four questions: What evidence does it use? Who can override it? What does the customer see? What happens when the flag is wrong?
If AI can slow the customer down, someone has to own the way back.
Until Monday,
👥 Share This Issue
Think of one person who’s wrestling with AI in CX right now
and forward this to them.
I’m obsessed with Wispr Flow Pro! Get a Free Month on me.
If someone forwarded this to you, they thought you needed to see it before your next AI planning meeting. Get your own copy.