W.05 — DESIGN STUDY · AI · CUSTOMER SUPPORT
AI customer support copilots can lift agent productivity by 31% per day in shipped deployments. Most teams never see that lift. The bottleneck is not model quality. It is whether agents trust what the AI suggests enough to act on it. This study explores the design of that trust layer for the three internal roles that build and run these systems.
01 — THE CORE TENSION
The AI customer service market is projected to reach $47.82 billion by 2030, with 95% of customer interactions expected to be AI-powered by 2025. In shipped deployments, the productivity numbers are real. Intercom reported that agents at Lightspeed close 31% more customer conversations daily with their Copilot. Nielsen Norman Group found that support agents using AI tools handle 13.8% more inquiries per hour. ServiceNow reported a 52% reduction in time on complex cases. The capability is no longer the question.
Trust is. Edelman's 2024 Trust Barometer showed that only 25% of US adults trust AI to provide accurate information, and global trust in AI companies dropped from 61% to 53% in a single year. Inside support teams, the picture is similar. 64% of customers say they would prefer companies did not use AI for service. 53% would consider switching to a competitor if they learned a company uses AI for service. 47% of enterprise AI users admitted making at least one major decision based on hallucinated content in 2024.
For the agents on the front line, the dynamics are sharper still. Salesforce found that 56% of customer service agents report burnout, 77% say their workload has increased over the past year, and 69% of decision-makers say agent attrition is a major operational challenge. The product question is not whether AI can help. It is whether agents trust it enough to act on it, and whether the design of that trust holds up at scale.
02 — THE CHALLENGES
The most dangerous AI output is not a wrong answer. It is a confidently wrong answer. PlantNet shows '92% match: Japanese Maple.' That one number transforms blind trust into informed judgment. Most copilots in customer support today either show no confidence signal, or show one so opaque the agent learns to ignore it. The design challenge is calibrating what users see to what the system actually knows.
An AI suggestion without a source is a guess. The agent has to verify it anyway, which costs more time than writing the response themselves. Intercom's Copilot ships with inline source citations because that is what the workflow needs, not because it looks impressive. The design challenge is making the source as legible as the answer, without making the interface noisy.
What happens when the AI is wrong is often more important than what happens when it is right. Agents stop trusting copilots after a few high-confidence wrong answers, and that trust does not come back easily. The design challenge is treating low-confidence states, ambiguous queries, and edge cases as first-class screens, not as fallbacks.
03 — RESEARCH FOUNDATION
This study began with three weeks of desk research. I read public industry reports on AI in customer support: Salesforce State of Service, Zendesk CX Trends, the McKinsey 2025 AI Adoption Survey, Servion's market forecasts, the NBER paper on generative AI productivity in customer support, Nielsen Norman Group's research, and the Edelman Trust Barometer on AI. I studied the design of every shipped agent assist product I could access: Intercom Fin and Copilot, Zendesk Agent Copilot, Microsoft Service Agent in Microsoft 365 Copilot, NiCE Copilot for Agents, Assembled Agent Copilot, Yuma AI, Typewise, Talkative AI Copilot, Parloa, and Minerva CQ. I read failure case studies. The patterns are clear once you look at enough of them.
04 — THE FRAMEWORK
An answer without provenance is a guess the agent has to verify anyway. Source citations belong inline with the suggestion, not behind a tooltip. Intercom's Copilot ships this pattern for a reason.
'You'll love this' and 'You might like this' carry different confidence loads with zero additional UI. The model knows what it knows. The copy has to match. UX writing is a confidence signal, and it is the cheapest one to get right.
An accept/reject pattern forces a binary on an analog problem. Most suggestions are 80% right and need a small edit. The default action should be edit-and-send, not accept-as-is. The interaction model is the trust model.
Low-confidence states, ambiguous queries, refused responses, and escalations are not fallbacks. They are the screens that determine whether the system gets trusted on the high-confidence ones. Design them with the same care as the success path.
05 — SCOPE
Real AI customer support platforms have surfaces that take years to design well. This study scoped to the trust layer specifically: how the copilot communicates what it knows, surfaces what it does not, and handles its own failure. Anything outside that loop was deliberately excluded so the work could go deep rather than wide.
06 — THE ROLES
Most AI copilot products ship one surface and let role-based filtering do the rest. This study split the product into three role-specific dashboards built on a shared trust layer. The Agent uses the AI in real time. The Supervisor watches what the AI is doing across the team. The CX Admin trains it. Each one asks a different question first thing in the morning, and each one needs a different trust signal to answer it.
Primary question: Can I send this AI suggestion as-is, or do I need to edit it?
Primary action: Read suggestion, check the cited source, edit if needed, send.
METRIC — TICKETS CLOSED, TIME PER TICKET, CSAT ON THEIR CONVERSATIONSPrimary question: Is the team accepting AI suggestions safely, or are mistakes being shipped?
Primary action: Review flagged conversations, audit AI-assisted responses, calibrate escalation thresholds.
METRIC — AI SUGGESTION ACCEPTANCE RATE, EDIT RATE, ESCALATION RATE, QA SCOREPrimary question: Is the knowledge base feeding the AI accurate and current?
Primary action: Manage knowledge sources, review hallucination flags, tune escalation rules, retrain on rejected suggestions.
METRIC — KNOWLEDGE COVERAGE GAPS, HALLUCINATION FLAG COUNT, REJECTION PATTERNS, SOURCE DRIFT07 — KEY DECISIONS
Show the model's raw confidence score as a percentage on every suggestion. This is the path PlantNet and several developer tools take.
Three states: High Confidence, Moderate Confidence, Needs Verification. Each maps to a defined backend threshold. The percentage exists in the data, but the surface shows the state.
Raw decimals create cognitive load and false precision. An agent under time pressure does not need to interpret 73%. They need to know whether to send or to check. The three-state pattern is the right resolution for the agent's actual decision. Engineering still computes the percentage. The UI translates.
Show the answer prominently, hide the source behind a hover or click. Cleaner visually.
Source appears immediately below the suggestion, named and clickable. Snippet of the relevant text on hover. Always visible by default.
Provenance is the product. Hiding it behind an interaction defeats the purpose. Intercom's Copilot ships this exact pattern because the workflow needs it. The agent does not verify if they have to work to verify. Visible sources turn verification from a chore into a glance.
An Accept button and a Reject button as the default actions on every suggestion. Some products treat AI as a yes-or-no proposition.
The default primary action is Send with Edit. The suggestion drops into the response field as draft text. Accept-as-is and Reject are available, but not primary.
Most AI suggestions are 80% right and need a tweak. Forcing the agent to choose accept or reject is the wrong cognitive frame. Edit-first matches the actual workflow, lowers the cost of using the copilot, and produces better data on rejection (because rejection now actually means rejection, not just 'I wanted to change it').
Trust the agent to escalate when they sense the AI is wrong. Standard pattern. Lowest implementation cost.
Define hard auto-escalation triggers: repeated low-confidence states on the same case, refused responses, sentiment shift in the customer message, tool-call failures, or any keyword in a defined high-risk list. These trigger escalation without requiring agent action.
Agent judgment is a tired analyst's judgment by 3 PM. The system needs deterministic guardrails for high-risk cases. Yuma AI and NimbleBrain both document auto-escalation as core to keeping AI-assisted support trustworthy at scale. This is the design pattern that protects the team from the AI's own confidence bias.
Disclose AI involvement on every response. Or never. Both are common.
Disclose AI involvement only when confidence is moderate or the response was assembled from multiple sources. High-confidence answers grounded in a single canonical source do not require disclosure. Refused or escalated responses make the human-only path explicit.
Customers say they prefer no AI in service. But what they actually want is correct answers from someone who cares. Blanket disclosure on every response trains customers to distrust the channel. No disclosure at all is dishonest. Disclosing exactly when the system is uncertain treats the customer as an adult. This is the pattern that keeps the team's CSAT while preserving honesty.
08 — THE TRUST GRADIENT
The hardest design problem in this study was not deciding whether to show confidence. It was deciding how. A single confidence number puts the work on the agent. A binary trust-or-don't signal hides too much. The right resolution is a gradient: a defined relationship between the model's internal confidence, the visible UI state, the language used in the response, and the action available to the agent.
This is the artifact that lets engineering, design, and CX operations agree on what the product should feel like at each end of the spectrum. It is the artifact that should be reviewed by a Legal team before deployment. It is the artifact that turns "trust design" from a phrase into a specification.
Backend signal: Model confidence above defined threshold, single canonical source, no flagged ambiguity
UI treatment: Green confidence badge. Source visible. Suggestion shown as ready-to-send draft.
Language style: Direct, factual. 'Your order shipped on Tuesday and is expected Thursday.'
Available actions: Send. Edit and send. Skip.
Customer disclosure: Not required.
Backend signal: Model confidence in middle band, or multiple sources synthesized, or ambiguous customer intent
UI treatment: Amber confidence badge. Two sources visible. Suggestion shown with a 'Verify before sending' note.
Language style: Hedged. 'Based on your order history, it looks like your shipment is scheduled for Thursday. Please confirm.'
Available actions: Edit and send. Escalate. Skip.
Customer disclosure: Yes. 'Generated with AI assistance, reviewed by [Agent name].'
Backend signal: Model confidence below threshold, refused response, no source found, or auto-escalation triggered
UI treatment: Red confidence indicator. No suggestion shown. Reason for low confidence shown in plain language.
Language style: No AI-drafted response. Agent writes from scratch.
Available actions: Write manually. Escalate. Mark for retraining.
Customer disclosure: Human-only response, no AI involvement.
09 — THE DESIGN SYSTEM
A product where every screen depends on a trust signal needs token architecture that makes those signals consistent. The design system for this study uses a three-layer token model: primitive, semantic, component. Primitives never appear in components. Semantic tokens carry the confidence states. Component tokens scope to the specific UI patterns that depend on them: the suggestion card, the source citation block, the confidence badge, the escalation trigger banner.
Raw values, never used directly in components.
color-green-500: #16A34A
color-amber-500: #F59E0B
color-red-500: #DC2626
space-3: 12px
font-size-sm: 13px
Intent-based aliases for AI states. Components reference these.
color-confidence-high
color-confidence-moderate
color-confidence-low
color-source-citation
color-escalation-banner
Scoped to specific AI patterns.
color-suggestion-card-border-high
color-suggestion-card-border-moderate
color-confidence-badge-text
space-source-citation-inline
10 — WHAT COMES NEXT
If you are hiring for a senior product designer role in AI-integrated products and want to discuss this work or anything in my portfolio, reach me at hey@shahriarsultan.com.