34 articles on conversation design from the ICX blog.
In conversational AI, a content writer works on more than finished copy. The role can include source content, model instructions, test cases, and failure analysis. Scripted, generative, and hybrid systems need different writing inputs, but each needs clear standards for what an answer should say and when it should hand off.
Effective enterprise customer service chatbots are designed, not just deployed. The best practices: build from real intents, design the conversation before the prompts, set guardrails, plan fallback and human escalation, and measure resolution instead of containment. The model matters far less than the design underneath it.
Intent architecture is the structured map of everything a conversational AI is meant to handle. It groups what customers actually say into intents, links each intent to an action and a handoff, and adds fallback paths for the unexpected. Good intent architecture is what makes a bot resolve issues instead of guessing.
Anthropic's Skills feature lets teams package an AI capability as a small folder of instructions that loads only when relevant. It ends the mega-prompt era, makes capability portable across Claude surfaces, and turns AI governance into a file-review problem. For CX leaders, Skills are the first real reusable building block of enterprise AI.
On every turn, an AI assistant should pick one of seven moves: answer, ask, verify, repair, stop, escalate, or hand off. The move it picks shapes the whole experience. This guide gives a plain trigger for each one, so a bot acts well when it is unsure, limited, or asked to do something risky.
Loop engineering is the practice of designing AI agents that act, observe the result, decide what to do next, and repeat until a real goal is met. It is the skill replacing one-shot prompting. This guide explains the agent loop in plain words, shows real examples, and maps the new jobs it is creating.
A chatbot can run on rules, on a large language model, or on a hybrid of both. The right choice depends on the real system, not the demo. This guide shows how to decide per intent using six tests: determinism, compliance, latency, channel, memory, and backend access. Most strong systems are hybrid.
On June 11, 2026, Anthropic named Tata Consultancy Services its first Global Premier Partner and committed Claude to 50,000 TCS associates. The deal is not a vendor announcement. It is a quiet admission that enterprise AI scaling needs more than a frontier model. CX leaders should read it as a new playbook.
Sample-based quality review was built for a few human agents handling a few hundred calls a day. It cannot keep up with a fleet of AI agents handling thousands. Modern AI agent evaluation is continuous, rubric-driven, and tied directly into deployment gates. CX leaders who build it now will catch failures before customers do. Those who keep sampling will find their failures on social media.
AI evaluation is the discipline of testing whether AI systems actually behave the way you intended. Most enterprises still treat it as an engineering afterthought. In 2026 that mismatch is the leading reason agent rollouts stall and governance reviews fail. Here is what real eval looks like and why CX leaders own a bigger share of it than they think.
AI literacy is now the workforce risk most enterprises are not tracking. The EU AI Act made it a compliance requirement in February 2025. Generic training programs do not deliver it. Real literacy is role-specific, hands-on, and continuous. CX, governance, and HR leaders need to build it now or rebuild after the audit.
In June 2025, two leading AI teams gave opposite advice on multi-agent systems. Anthropic showed many agents beating one by 90 percent on research tasks, at about fifteen times the token cost. Cognition warned that splitting work across agents breaks context and creates fragile systems. For enterprise CX leaders, the real question is not how to coordinate agents but whether to, and what to build first.
On May 6, 2026, Anthropic gave Claude Managed Agents three new abilities. Dreaming lets agents learn from past sessions. Outcomes grades every output against a rubric. Multiagent Orchestration runs up to 20 specialist agents in parallel. Together they target drift, quality at scale, and complex work, and they raise fresh governance questions for CX leaders.
Context engineering is the discipline of designing what information an AI system receives, how it is structured, and when it enters the model's working memory. Gartner named it the breakout AI capability of 2026 and predicts context improvements will enhance agentic AI accuracy by 30%. For CX leaders, context architecture determines whether AI investments deliver customer trust or operational failure.
Anthropic launched a $1.5B enterprise AI services firm with Blackstone, Hellman & Friedman, and Goldman Sachs in May 2026 to embed engineers inside companies and redesign workflows around Claude. For CX leaders, the move carries a specific message. The AI bottleneck has moved from model capability to deployment expertise. The new firm covers technical integration. It does not cover conversation design, content engineering, or experience measurement: the layers that determine whether an AI deployment improves customer experience or degrades it.
Two-thirds of CIOs and CTOs are accountable for AI systems they don't fully control, per a June 2026 IBM study of 2,000 executives. Seventy percent say business teams deploy AI faster than IT can track. Organizations embedding control deploy 16 times more agents with 25 percent fewer incidents than those relying on manual governance. The AI Control Gap is structural and solvable, but only by treating governance as a deployment prerequisite, not a follow-on project.
Buying AI tools is not the same as being ready for AI agents. Most organizations stall somewhere between pilot and scale, not because the technology failed, but because governance, data, and measurement weren't in place before deployment. Only 21 percent of enterprises have mature agentic AI governance while 42 percent are already running it in production. That gap is where CX programs break down.
A conversational flow can be clear, well structured, and technically correct and still fail to move customers to act. Behavior design adds a second layer to conversation design: motivation, ability, prompt timing, and friction. The Fogg model (Behavior = Motivation, Ability, Prompt) and ethical friction reduction explain why and how to fix it.
Testing a conversational AI means validating logic before automating it, then measuring real behavior after launch. Use Wizard of Oz testing pre-build, an alpha-beta-scale sequence, a four-layer Bot Scorecard, and transcript review. Dashboards show where to look. Transcripts tell you what to redesign. Maturity begins after launch.
Project Glasswing is a new Anthropic-led effort, with partners like Amazon, Google, Microsoft, and JPMorganChase, to secure critical software using Claude Mythos Preview, a model that finds software flaws better than almost any human. Most coverage will focus on the hacking. This opinion piece reads it through a conversation designer's eyes: the names, the framing, and what it means for any business whose AI talks to customers.
Voiceflow is a strong design and prototyping platform for conversational AI. It excels at multi-channel chatbot design, visual flow building, and team collaboration. It hits a ceiling at enterprise scale on three fronts: production deployment infrastructure, governance and audit controls, and integration with enterprise identity systems. Best for mid-market teams and design-led organizations.
AI teams at enterprise companies are quietly adding linguists, conversation designers, and AI content strategists to their rosters. Engineering teams alone cannot build conversational AI that works. Language expertise is now table stakes for enterprise AI. The skills gap is widening because most computer science programs do not teach pragmatics, discourse design, or conversational repair.
A mid-market insurance carrier had a chatbot containing 42 percent of contacts but stuck at 61 percent customer satisfaction (CSAT). ICX audited the conversation logs, rebuilt the system prompt, redesigned the intent map, and replaced the escalation flow. Ninety days later, CSAT moved to 84 percent and same-day re-contacts fell 41 percent. The platform never changed.
Most failing chatbots have capable models, reputable platforms, and working integrations. Customers still complain. The reason is a language problem, not an AI problem. The bot misses pragmatics (what people mean versus what they say), discourse rules (how turns connect), and conversational repair (how to fix breakdowns). The fix is conversation design, not a new model.
AI agents are displacing chatbots in enterprise customer experience faster than most teams forecasted. The difference is not the chat window. It is what happens underneath. Chatbots classify and route. Agents plan, decide, and close. The transition exposes three failure patterns most teams hit: treating an agent like a smarter chatbot, skipping the orchestration layer, and underestimating the measurement gap.
Five conversational patterns cause users to rage-quit chatbots: the dead-end response (no path forward), false confidence (sounds sure but wrong), context blindness (forgets what was said two turns ago), hostile politeness (over-formal refusals), and circular escalation (asks for the same info repeatedly). Each pattern shows up in support data and is fixable in conversation design, not in the model.
Around 60 percent of chatbot projects quietly get shelved within their first year. The cost is not just the wasted build budget. The real ongoing cost shows up in repeat contacts (customers calling back the same day), CSAT damage that lingers for quarters, and the rebuild burden when leadership wants to try AI again. 'Good enough' AI is the most expensive AI.
Every AI chatbot will get something wrong. The real question is what happens next. Three failure types need explicit design: misunderstanding (the AI parsed the input wrong), low confidence (the AI is not sure of the answer), and out-of-scope (the AI cannot help with this kind of request at all). Each failure type has a different recovery pattern. Trust depends on getting these right.
When a leader asks why you need conversation design when ChatGPT can already handle conversations, here is the answer. ChatGPT can hold a conversation. It cannot reliably represent your brand, follow your policies, escalate at the right moment, or handle the customer questions you actually get. Conversation design fills that gap. The 'works' bar and the 'works well' bar are far apart in production.
Gamma is an AI-powered presentation tool that lets consultants generate decks, one-pagers, and reports from a prompt or outline. The tool changes the economics of consulting deliverables: hours of layout and formatting work compress into minutes. Gamma works best for strategy documents, workshop materials, and pitch decks where structure matters more than custom design. It struggles with highly visual or chart-heavy work.
Intelligent CX combines conversational AI, prompt engineering, and CX strategy to design customer experiences that resolve issues, build trust, and scale across channels. It is not a new technology category. It is a discipline that treats language, escalation, and measurement as design problems instead of vendor configuration tasks.
Choosing an AI customer support platform in 2026 means evaluating seven criteria, not feature lists: conversation design support, prompt customization depth, integration with your existing stack, analytics and observability, escalation design, multi-language support, and pricing model. The wrong platform will work in the demo and fail in production. The right one matches your use case, not the vendor's pitch.
Most enterprise chatbot projects fail within 12 months for five repeatable reasons: building for containment instead of resolution, skipping conversation design, ignoring the unhappy path, designing escalation as a wall instead of a door, and treating launch as the finish line. The fix is design discipline, not a better platform.
A chatbot is a rule-based system that matches keywords to scripted responses. Conversational AI uses natural language processing, large language models, and machine learning to understand intent, maintain context across multi-turn dialogs, and generate dynamic responses. Most enterprise chatbot projects fail because teams confuse the two and choose the wrong technology for the use case.