AI Is Starting to Manage the Room
Plus: The customer experience isn’t only the screen, the bot, or the call. Sometimes it’s the temperature, the wait, the store, and the operations no one notices until they fail.
Your daily signal on AI and CX — minus the hype.
DCX Stat of the day: Asana says 75% of knowledge workers use AI at work, but only 5% of companies report meaningful productivity gains. Asana
In this issue:
→ AI moves into physical experience
→ Comfort becomes a CX signal
→ Agent access becomes a CX risk
→ Productivity needs shared work context
→ Governance moves into the Radar
🔎 Deep dive
Physical experience is still customer experience
Axiom Cloud expanded its AI platform beyond refrigeration into autonomous HVAC optimization. That may sound like a facilities story.
It is not only a facilities story.
HVAC affects whether a grocery store feels comfortable, whether employees can work well, whether shoppers stay longer, and whether a physical location feels cared for or neglected. Customers may never say, “This brand has poor building automation.” They just feel rushed, irritated, tired, or ready to leave.
That is the useful part of this announcement. AI is not just moving into chat, search, claims, marketing, or contact centers. It is moving into the operating systems behind the environment customers walk into. Temperature, uptime, maintenance, energy use, staff comfort, and store reliability all shape the experience before anyone opens an app or asks for help.
The risk is familiar. If no one owns the customer impact, the AI becomes an efficiency tool, not a service improvement. A system can save energy and still make the store feel worse. It can resolve a maintenance issue and still miss the moment customers actually felt the problem. Physical operations need the same CX discipline as digital journeys: clear ownership, visible signals, and a recovery path when the experience slips.
Source: Axiom Cloud
📬 Copy-Paste Take
AI customer experience is not only conversational. If AI is allowed to adjust the environment, the operating question is simple: did it make the place feel better for the customer, or just cheaper to run?
OPERATOR PLAYBOOK
Find the AI decision the customer feels
Start with one journey where a customer could lose money, time, access, trust, or momentum if AI gets something wrong.
Audit every agent-assisted workflow for four things:
What customer outcome the agent can influence.
Which policy, model, data source, and permission it relies on.
Which signal shows drift, misuse, unfair treatment, or a bad handoff.
Who can pause, correct, explain, or reverse the action.
Then run a simple test: can your team reconstruct one customer outcome without pulling screenshots and exports from five different systems?
Ask your team: If a customer asked why this AI made that call, could we answer in plain English today?
Signal: AI governance is useful when it helps the business fix the journey while the customer still has a reason to trust you.
📈 Market Reality Check
AI use isn’t the same as AI value
Asana’s latest release includes a useful gap: 75% of knowledge workers use AI at work, but only 5% of companies report meaningful productivity gains.
That sounds familiar.
One person gets faster. A team still waits for context. A customer still gets bounced between systems. A manager still can’t see what happened. The task feels improved, but the experience still breaks in the same old place.
Asana points to several blockers: people can’t find the right agents, agents don’t have enough work context, humans and agents aren’t working together cleanly, and leaders worry about unchecked access and cost. That doesn’t prove Asana has the answer. It does prove the adoption conversation is too shallow.
The question isn’t, “Are our people using AI?” The better question is, “Is AI helping the whole journey work better for the customer?”
Individual speed + broken coordination = faster internal friction.
🧰 Tool Worth Knowing
Willow
What it does: Willow helps companies see and control how AI agents connect to internal systems. It shows which agents employees are using, which tools and data they can reach, what actions they take, and how that activity is audited.
CX use case: Useful when an agent can touch support tools, CRM records, billing data, knowledge bases, approvals, or operating systems that shape what the customer sees next.
Worth watching because: Willow says it has already been deployed inside Wix across more than 5,000 employees. It can connect agents such as Claude, ChatGPT, Gemini, Codex, Cursor, n8n, and custom agents to enterprise systems with runtime permissions and audit trails.
Bottom line: A customer-facing AI problem may start with an internal agent that had too much access, too little supervision, and no clear owner.
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
IBM and Google Cloud expand production AI delivery
IBM and Google Cloud announced a new practice focused on scaling AI, modernizing core systems, and building industry-specific agents for Gemini Enterprise. The useful part is the move from pilot talk to production work in regulated functions where customer service, operations, and compliance all have to hold together. That is where AI stops being a demo and starts becoming a promise.
Cognizant and ServiceNow push AI governance into daily operations
Cognizant and ServiceNow are connecting Cognizant Neuro AI Trust with ServiceNow AI Control Tower. The CX signal is not the governance branding. It is the move toward live visibility, controls, and accountability when AI operates inside regulated or customer-facing workflows.
🧭 Your Move
Today’s edition is about one simple shift: AI is moving into the operations customers feel before they ever talk to support.
The same pattern shows up in Axiom’s HVAC launch, Asana’s productivity gap, Willow’s access controls, and the push to run production AI inside real operating systems.
Pick one experience signal customers feel but rarely describe well: comfort, cleanliness, wait time, noise, availability, order readiness, or staff attention.
Then ask who owns that signal when AI touches the operation behind it.
Who sees the evidence? Who can correct the setting? Who knows whether the customer felt the improvement? Who fixes it when the efficiency gain makes the experience worse?
If the answer is unclear, the problem isn’t the automation. The problem is ownership.
AI improves CX only when someone owns the part of the experience the customer actually feels.
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.