Evolving Dell's AI support from a cramped chat box into a full-screen workspace where 12+ APIs, source-tagged answers, and the sales portal's tools all sit under one conversation. Ticket volume fell 55%, self-serve adoption hit 85%, and reps finally trusted what the AI said.
Dell employees were stuck inside a cramped chat window that surfaced shallow AI answers and hid the platform's real capabilities. Checking a single order meant opening four other tabs, then pinging a teammate anyway.
IntelliAssist 2.0, a full-screen AI workspace that unifies 12+ APIs, source-tagged answers, and the centralized sales portal into one place. Fewer tickets, more self-serve, and trust in what the AI says.
Lead UX Designerone of two designers · research, IA, interaction, visual
Dell Technologies2 PMs, 8 engineers, 2 designers
8 monthsdiscovery through pilot launch, 2024
Figma · Figma Make · Claude Design · Copilotdesign, prototyping, and AI-assisted build
If you only read three paragraphs, read these. Problem, change, and results in about a minute.
Dell employees worked inside a cramped chat box that surfaced shallow AI answers and hid the platform's real capabilities. Checking a single order meant opening four other tabs, then pinging a teammate. Adoption stalled and support tickets piled up.
I rebuilt IntelliAssist into a full-screen AI workspace that unifies 12+ APIs, source-tagged answers, and the sales portal's tools under one conversation. Reps see where each answer came from, trust what they read, and stay inside one surface.
From pilot telemetry and post-launch surveys: ticket volume dropped 55% across enterprise support, self-serve adoption hit 85% on the new workspace, task completion ran 78% faster vs. 52% on the legacy chat, and 85% of pilot users reported easier access to critical tools.
Reps needed answers about orders, configs, and customer history mid-conversation, but the AI lived in a cramped chat box. Assembling one response meant toggling four to six systems, so tickets piled up, adoption stalled, and reps quietly fell back to bookmarks and pinging teammates.
Three problems showed up at the same time. The chat surface was too small for real work. The AI underneath gave generic answers that no one trusted. And the tools that could have helped were spread across a portal nobody could navigate. The redesign had to fix all three.
A full-screen AI workspace: prompt suggestions, source-tagged answers, and the sales portal's tools sitting right under the conversation.
The business needed one stable platform to add AI and unify sales tools. Without it, adoption stalled and workflows stayed fragmented.
Across user interviews, a clear pattern emerged. Employees lacked confidence in the tool, found it slow to navigate, and rarely discovered features on their own. The result was low adoption, fragmented workflows, and delays in customer resolution.
The AI gave surface-level details without supporting context, related information, or follow-up questions. Users couldn't tell what to trust.
"The chatbot gives generic answers. I can't trust it." Sales Representative
The sparse landing screen failed to highlight the AI's full capabilities. Feature discovery was low, and employees defaulted to peer-dependent learning.
"I have to ping a teammate to get the right resource." Project Manager
Search was so slow that users had quietly stopped using it. Bookmarks were faster, even when stale. The tool was being routed around, not used.
"I just use bookmarks. Searching takes too long." Data Engineer
The shipped IntelliAssist 2.0 wraps a full-screen AI chat in a workspace that holds context. Underneath, five interface decisions made the new pattern work for employees who'd been burned by the old one.
Role-specific prompt chips at first load kill the blank-page hesitation and quietly surface what the AI can actually do.
Reusing the legacy card layout meant reps recognized the new workspace on day one, instead of relearning where everything lives.
A collapsible sidebar lets reps self-navigate to the old tools, a familiar fallback that made committing to the new surface feel safe.
Follow-up chips and a "search instead" option let reps reframe a query when the AI misses, instead of hitting a blank wall.
Visible sources and related links let reps check where an answer came from, which is what actually built trust in the AI.
The five decisions added up to one workspace. A full-screen AI surface that holds context, surfaces prompts, attaches sources, and keeps the legacy self-serve tools one click away. This is the shipped state, the same view a Dell sales rep sees on day one.
"This tool transformed how our teams operate. Finally, the right resources are at their fingertips, exactly when needed."Director, Operational Intelligence · IntelliAssist 2.0 launch retrospective
Due to tight launch timelines, we validated critical workflows with pilot users, iterating rapidly on feedback like confusing navigation and unclear AI responses. The numbers below come from pilot telemetry and post-launch surveys.
Centralizing AI chat, self-serve tiles, and sales tools cut redundant tasks like order tracking by 40%, letting employees focus on high-value work.
Integrated sales portal resources eliminated daily platform-switching for 72% of pilot users, freeing up time for higher-impact work.
Feature discovery rose by 55%. 85% of users reported "easier access to critical tools" once the new workspace was live.
The constraints on this project (tight deadlines, leadership-driven requirements, ambiguous AI capabilities) weren't problems to solve. They were the conditions of the work. Three things I learned about designing inside them.
Strict leadership requirements often mirrored hidden user needs, like faster workflows.
With tight deadlines, I prototyped only critical flows first like order tracking, then iterated post-launch.
Letting go of "perfect" features like custom animations freed time to solve bigger issues like AI response accuracy.
The legacy chatbot was a collapsible side panel. The obvious fix, and the one most stakeholders asked for, was to make the panel wider. I pushed back on that.
If reps can keep the panel closed and still do their job, they will. Full-screen forced a commitment: open IntelliAssist or don't. That commitment eliminated the half-in, half-out usage pattern where reps would open the panel, distrust the answer, and call a teammate anyway. Ticket volume dropped 55% not because the AI got smarter, but because there was no easy exit to the old behavior.
Three pilot reps requested a "compact mode" during testing. My concern was that compact mode would become the default and reproduce the low-commitment usage we were trying to break. I proposed a collapsible source drawer instead: visible proof that answers are traceable, available without exiting the surface. That addressed the underlying need (transparency) without reopening the escape hatch.
Two layers of impact that don't show up in the metrics. The work that shaped how I designed it, and the patterns the team kept using after I shipped.
Adoption didn't move when the AI got smarter. It moved when reps could see where each answer came from. Source-tagging, prompt suggestions, and recovery paths did more for behavior than any single model improvement. That changed how I scope every AI feature now.
IntelliAssist 2.0 was the first full-screen AI surface at Dell. The patterns we shipped became the reference for every team that followed, so the next AI projects didn't have to rediscover what worked.