Topic starter
11/07/2026 1:54 pm
TL;DR: Merchant AI efforts stall in pilot mode because top-down mandates drive demos without durable process change, according to Riskified. Customer workflows still need identity checks, fraud context, and fallback handling before automation can safely execute.
Editorial analysis by NHI Mgmt Group, based on content published by Riskified: “Clever prompts, shallow impact: Why AI adoption is falling short in retail”.
By the numbers:
- The article says the cost of a human agent’s time is $5-20.
Key questions
Q: Why does identity matter when conversational AI handles customer requests?
A: Because the model is only one part of the decision.
Q: What breaks when AI is treated as a prompt machine instead of a workflow system?
A: Teams get impressive demos but little operational change.
Q: How should organisations decide which customer workflows are safe to automate with AI?
A: Start by separating routine, low-stakes requests from actions that change money, account state, or shipping details.
Practitioner guidance
- Define high-stakes workflow boundaries Separate low-risk customer intents from actions such as refunds, shipping changes, and account recovery, then require stronger controls for the latter.
- Add identity checks to agent decisions Use request context, account history, and fraud signals before letting a conversational agent complete a customer action.
- Measure automation by process completion Track whether AI actually resolves the end-to-end workflow, not just whether it can draft a response or pass a demo.
Bottom line: AI tourism produces visible experimentation without durable process change, which is why many merchant AI efforts stall before production value appears.
Glossary terms: AI Tourism, Workflow AI, Identity-Aware Decisioning, High-Stakes Customer Action
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 1 hour ago by NHI Mgmt Group
11/07/2026 2:05 pm
AI tourism is a governance symptom, not an adoption strategy. The pattern described here shows that organisations can generate visible activity without changing how work is actually done. Demos and pilots create motion, but they do not establish durable authority, decision rights, or exception handling. For practitioners, that means the real question is whether AI is being allowed to affect production outcomes or merely decorate an existing process.
A few things that frame the scale:
- Organisations that describe themselves as confident in their AI deployment actually experience a 72% security incident rate, compared to 33% for those who remain cautious, according to the 2026 Infrastructure Identity Survey.
- Only 13% of organisations feel extremely prepared for the reality of agentic AI despite the majority racing toward autonomous adoption, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What should teams do when a customer-facing AI action could affect money or account control?
A: Require a human fallback or a stricter approval path before the action is completed. For refunds, address changes, and similar high-impact requests, the system should verify request legitimacy, apply policy checks, and stop short of autonomous execution when confidence is insufficient.
👉 Read our full editorial: AI tourism is slowing merchant adoption, but workflow AI still matters