ServiceNow · Agent workspace · highlight
SLA session tabs
Agents juggle many chats at once. I designed how a single small tab tells them which customer is waiting, and how urgently, without a ticking clock.
role
Product designer, agent experience
team
PM, engineering, platform design system
timeline
2024
status
Shipped in Yokohama
Active
the chat the agent is in
Quiet
no one waiting
New message
customer replied
Approaching
nearing the response threshold
Urgent
threshold almost reached
How a tab escalates while a customer waits. Names are fictional.
the problem
Agents handle several chats at the same time. When they switch away and a customer replies, that conversation sits in a tab that looks like every other tab, and it's easy to miss until the customer has waited too long.
what I designed
urgency that builds, instead of a clock
- new message
When a customer replies in a chat the agent isn't viewing, the tab changes state and an unread count appears. Both reset when the agent returns.
- escalation
As the response threshold nears, the tab moves through warning and urgent states. No numeric timer is shown, so agents get a calm signal instead of a wall of countdowns.
- only what matters
Only inactive chats change state. The chat the agent is in stays neutral, and replying resets the tab.
- admin control
Admins set response thresholds within the existing chat configuration, to match their own service levels.
the constraint
I didn't design the tab component from scratch. I extended an existing platform component that every workspace shares, so a change that looks small touched the app shell itself. That meant aligning with the platform and design-system teams on what the component could express: color, badges, icons and tooltips.
We also defined how success would be measured: admin enablement, how often tabs reached the urgent state, how quickly agents returned, and customer satisfaction.
also shipped
resizable chat panel
Alongside the tabs, I designed a resizable chat panel, so agents can give the conversation more or less room next to the record they're working in. Like the tabs, it changed the shared workspace layout rather than a single component, so it needed the same careful alignment with the platform teams.
back to the start