Transforming customer support from disconnected, context-blind interactions into seamless, contextual engagement sessions. By designing a context-first platform that combines progressive escalation, real-time annotations, and intelligent routing, we reduced support costs while dramatically improving customer satisfaction and associate efficiency.
Customer support was fragmented across disconnected channels. Organizations struggled with high technician dispatch costs and inefficient troubleshooting. Customers, in turn, faced frustrating context switches between their application and a phone call, forcing them to repeat issues and feel "unheard" by support associates who lacked real-time visibility into their experience.
The core problem: Context Loss—every handoff, every channel switch, every misalignment between what the customer was experiencing and what the associate could see created friction and extended resolution time.
Engagement Scenarios – Rule-based configurations that automatically adapt the support interface based on where the customer is on the site. A technical troubleshooting page triggers video/screen share options, while a general FAQ page offers lightweight SMS support.
Progressive Escalation Path – Engagements start lightweight (audio/SMS) and upgrade to video or screen sharing only when complexity requires it, respecting user privacy while maintaining technical efficiency.
Context Attribute Sidebar – Associates see only data relevant to the triggered routing rule (customer name, cart value, page location), eliminating cognitive overload and keeping the UI actionable.
Live Annotations – The ability to freeze frames and draw directly on customer screens transforms support from verbal directions ("Click the red button... no, the other one") into precise visual guidance.
Our approach followed a rigorous user-centered design (UCD) cycle, starting with the insight that customer support's core friction is "repetition fatigue"—users having to repeat their issue multiple times across channels and associates.
We identified that support associates were operating "flying blind," lacking visibility into the customer's journey. This insight drove us away from a "phone call" mental model toward an "engagement session" model where context flows seamlessly through every interaction.
Phase 1: The Reactive Widget
A simple "Click-to-Call" button with no intelligence. Treated every user the same, creating friction for complex issues.
Phase 2: The Contextual Scenario
Introduced the Engagement Scenario engine. The interface now adapts dynamically—showing "Video Call" on technical pages but only "SMS" on general FAQ pages.
Phase 3: The Collaborative Canvas
Added Live Annotations, transforming support from "seeing" to "interacting." Both parties could now draw on screens in real-time, providing instant visual clarity.
During user testing, we observed associates struggling with verbal directions ("Click the red button... no, the other one"). This drove up Average Handle Time (AHT) significantly.
The annotation tool was designed as a "visual pointer," allowing associates to freeze frames and draw directly on customer screens. This single feature reduced misalignment and dramatically improved clarity.
The Frustrated Resolver (End-Customer)
Tech-savvy but time-poor. Their psychological state is "high-friction." They don't want a relationship—they want a path of least resistance to solve their problem (failed checkout, technical bug). When forced to repeat their issue, cortisol levels spike.
The Multitasking Associate (Support Agent)
Operating in a high-stress, efficiency-driven environment. Must rapidly switch mental contexts between customers and varied technical issues without losing conversational thread. Information overload is their enemy.
Pain Point: "Start-Over" Syndrome
The biggest frustration was transfer-induced repetition. Users had to explain their issue again to a new associate. Solution: Context Attributes ensured associates knew the user's name, cart value, and exact page location before saying "Hello."
Moment of Delight: The "Magic Pointer"
When associates used the Annotation Tool to circle a button on a customer's screen, users consistently reported: "I felt like the agent was standing right next to me." This became our highest-impact feature.
Average Handle Time (AHT): Context Attributes eliminated the need for manual identity verification and location confirmation, saving 60–90 seconds per call on average.
First Contact Resolution (FCR): Live Annotations and Screen Sharing enabled immediate visual troubleshooting, reducing follow-up tickets by 15–20%.
Channel Fluidity: By designing seamless upgrades from SMS to audio to video within a single session, we kept customers engaged without forcing app switches.
Retail Client Pilot: A major retail organization integrated the SMS-to-Screenshare workflow. Customers initiating conversations via text could be instantly upgraded to screen-share sessions. Result: 90%+ CSAT for those interactions—a significant uplift over standard support channels.
Customer Quote:
"The transition from a basic chat to a visual co-browse session felt like magic. I didn't have to explain the problem; the agent simply saw it and drew the solution on my screen." — Retail Pilot Participant
| Metric | Pre-Launch | Post-Launch |
| Context Awareness | Manual (Ask/Confirm) | Automatic (Context Attributes) |
| Channel Switching | Disconnected (Hang up/Call back) | Fluid (In-session Upgrades) |
| Visual Clarity | Verbal Descriptions Only | Real-time Annotations |
| User Drop-off | High (During "Wait for Agent") | Lower (Contextual Greetings) |
Download the full case study PDF for detailed design process, wireframes, and research findings.
I'm always happy to discuss design process, platform design, or how I approach enterprise experience optimization.
Enter the password to download the full PDF with wireframes and research findings.