Hub
Customer Experience Agents
Every conversation should connect to a real resolution.
CX agents fail when they recommend instead of resolve. Here: identity checks, escalation design, evaluation harnesses and rollouts your support team can own — without leaking customer context across channels.
Evidence before autonomy. Each article below is written for operators and builders who need eval angles, decision framing and practices they can run — not another generic tip list.
Related on the main site: CX agents & service automation
Posts on this topic
- Google ships A2UI 1.0, a stable open protocol for agent-built UI · AI Products & Copilots · Customer Experience Agents
A2UI 1.0 lets agents describe interface screens that host apps render with their own registered components, and adds two-way function calls and accessibility support.
- Claude Haiku 5.5: a fast model for subagents and high-volume work · Models, Tooling & Developer Practice · Customer Experience Agents
Claude Haiku 5.5: 1M context, 128K output, $0.10/$0.50 per million tokens up to 100K-token prompts. Where it fits in routing, caching and subagent work.
- Compile-then-execute: how the Baya web agent blocks prompt injection · AI Reliability & Operations · Enterprise AI Governance
Baya compiles web tasks into programs before seeing any page: 77.8% task success on WebArena Verified and 0% attack success on WASP, per the authors.