← All work
AI Product Design · Hospitality · 2023–2024

Reimagining the Agent Experience

A confidential engagement with a global hospitality brand. I led UX design for a ground-up reimagining of the hotel agent desktop, turning a fragmented toolset into one intelligent workspace built around how agents actually work.

Role
UX Designer
Timeline
Nov 2023 – Feb 2024
Focus
Agent Tools, Booking UX, AI
Team
4 Designers

Structural representation — actual screens in the full case study.

The Problem

Agents were drowning in disconnected systems.

Hotel call center agents were managing complex guest interactions while juggling 4–5 separate tools — booking platforms, loyalty systems, CRM, case management, and performance dashboards — all open at once, none of them talking to each other.

The result was high cognitive load, slow resolution times, and agents who knew the guest's name but couldn't surface their last three stays, open complaints, or loyalty status without tabbing through three different apps.

4–5 systems open simultaneously during a single call
Manual data entry and re-entry mid-conversation
No unified view of the customer across touchpoints
Workarounds built on sticky notes and browser bookmarks
Some agents managing up to 10 conversations at once
The system landscape
Booking
Loyalty
CRM
Cases
Performance
Agent — context overload

Five siloed systems. One agent expected to hold the context together.

Research

In the field. Not in a workshop.

We conducted contextual inquiry with call center agents — standing beside them during live calls, watching real interactions in real time. The workarounds agents had invented told us more than any survey could have.

Contextual Inquiry

"The workarounds agents used told us more than any interview could."

Observing agents mid-call surfaced friction that would never appear in a structured session. We saw where systems broke down, what shortcuts agents invented, and where genuine failures occurred under pressure.

Method
Contextual inquiry
Context
Live call center environment
Approach
Observation during live calls
Duration
Multiple days on the floor
1
Where friction happens
Mid-call, when agents need context fast and systems require multiple steps to surface it
2
How agents move between systems
Alt-tab, copy-paste, memory. No handoffs, no continuity. Pure manual context switching
3
What workarounds they rely on
Sticky notes, browser bookmarks, personal cheat sheets — systems built by agents, for agents
Key Insights

Three themes across every session.

Different agents, different contexts, the same problems. These three themes surfaced repeatedly and shaped every design decision that followed.

01

Cumbersome Processes

Agents rely on manual workarounds to complete tasks that should be automatic. Every extra step is time taken away from the guest.

02

Fragmented Data

Customer information is scattered across systems with no consistent link between them. A full picture requires visiting multiple tools.

03

No Real-Time Support

When a situation escalates or an exception arises, agents are on their own. No guidance. No context. Just memory and instinct.

Framing the Opportunity

This was not a UI problem. It was a systems problem.

We reframed away from "how do we improve each tool?" and toward "how might we design an experience that makes the right information available at the right moment?"

How might we reduce cognitive load during live calls?
How might we unify customer information across touchpoints?
How might AI support agents in real time without adding complexity?
Approach

Research to system, not research to screen.

The brief called for a better interface. But the research made clear that better UI on top of fragmented data wasn't the answer. We had to rethink the information model before we could design anything meaningful.

01
Research & Discovery

Contextual inquiry in a live call center. Mapped the full agent journey from call pickup to resolution. Identified the five highest-friction moments and the workarounds agents had built around them.

02
Insight & Framing

Synthesized observations into design principles. Reframed the problem from "tool improvement" to "unified experience." Defined the information model agents actually needed.

03
Concept & Prioritization

Explored 12 concepts across the agent experience. Used a Desirability, Feasibility, Viability framework to narrow to three. Each concept had to earn its place across all three dimensions.

04
Design & Validation

Translated the three concepts into high-fidelity designs. Multiple rounds of prototype testing with live agents. Iterated on information density, AI placement, and interaction model before handoff.

Key Design Decisions

The calls that shaped the product.

Every project has moments where a decision constrains everything that follows. These are the ones that mattered on this one.

Surface AI suggestions contextually, not in a dedicated panel.

Why

Early concepts gave AI its own persistent sidebar. Testing showed agents ignored it — one more thing to check meant one more thing to miss. Embedding suggestions at the moment of relevance meant they were actually seen and acted on.

The tradeoff

Harder to build. Required close collaboration with the AI team on trigger logic. But the difference in agent response during testing was clear enough to push for it.

Prioritize depth over breadth in the Customer 360 view.

Why

The instinct was to show everything. Research said otherwise. Agents needed three things fast: loyalty status, open cases, and last stay. Committing to those clearly beat cramming in 20 fields.

The tradeoff

Stakeholders wanted more data visible. We made the case that a view agents actually use is better than a complete view they skim. Prototype tests backed us up.

One workspace, not a better way to switch between existing tools.

Why

There was pressure to build a more elegant tab switcher. We rejected that framing. The problem wasn't navigation — it was that context didn't transfer. A unified model meant rethinking what agents needed in one place.

The tradeoff

Higher design and engineering complexity. But solving the symptom without solving the cause would have shipped a feature, not a solution.

Outcomes

What the work moved.

↓40%

Time navigating between systems, measured across prototype testing

↑18%

Upsell conversion rate from contextual AI suggestions

360°

Unified customer view — one workspace instead of five tools

↑NPS

Agent satisfaction improved across every round of testing

Reflection
Agents didn't want more information — they wanted the right information at the right moment. AI had to earn its place on screen.

The biggest lesson was restraint. In AI design the instinct is always to show more — more suggestions, more data, more visibility. But in a high-pressure service environment, more is noise. The real work was figuring out what not to surface, and when to surface nothing at all.

Full Case Study

Go deeper with the full study.

The full case study includes the actual screens, research synthesis, and detailed iteration history. Password-protected for client confidentiality.

What's inside
  • Full research synthesis and raw findings
  • The actual interface — all three solution concepts
  • Prioritization artifacts and DFV scoring
  • AI placement rationale and iteration history
  • Prototype testing rounds and what changed
  • Stakeholder feedback and how it shaped decisions
Enter Password to View Full Case StudyDon't have the password? Request access