← work

ServiceNow · Virtual Agent and chat

Rich controls

Deciding where conversation stops helping. I designed a family of interactive controls that let customers finish complex requests inside a chat, instead of leaving it or answering twenty questions one at a time.

role

Product designer, only designer on omnichannel chat

team

PM, engineering, UX research, chat platform team

timeline

2023

status

2 shipped · 2 explored

Chat window with an inline iPhone order form, next to the end-of-chat feedback rating
01

the problem

Complex self-service tasks broke the chat: customers were sent to a browser pop-up, or asked every question one by one.

02

what I did

Designed four rich controls that bring structured tasks into the conversation, across the customer and agent experience.

03

the result

Star Rating shipped as a ServiceNow Store release, and Service Catalog shipped with omnichannel and was later extended to larger forms.

context

two ways chat was failing

Customers came to the chat assistant to get things done: request a laptop, report an issue, find an answer. When a task needed more than a few inputs, the experience fell apart in one of two ways.

option a · leave the chat
  • Selecting a request opened a browser pop-up
  • Focus left the conversation
  • Broke on third-party portals and mobile
  • The assistant couldn't see what the customer did
option b · stay and answer everything
  • Forms could have 15–20 fields
  • The bot asked them one at a time
  • Fixing an earlier answer was hard
  • No sense of how many questions were left

Before: choosing a request opened a pop-up over the page, and the chat was left behind. Illustration.

the question

How might we let customers finish a complex request without leaving the conversation, and without turning it into an interrogation?

my role

I was the only designer on omnichannel chat at the time, working with a PM, engineering, UX research and the chat platform team. I owned the problem framing, competitive analysis, flows, interaction design, prototypes and engineering handoff. For research, I built the flows we tested and observed the sessions, while our researcher planned and ran them.

four controls

one pattern, four kinds of task

shipped

Star Rating

Lets customers rate their experience right in the chat. My first feature as a full-time designer, released on the ServiceNow Store.

shipped

Service Catalog

Turns a catalog request form into an inline control, so customers fill it in without leaving the chat.

explored

Guided Decision

Walks customers through a branching decision inline. Designed to engineering handoff.

explored

Knowledge Article

Renders an interactive article, with images and video, inside the conversation.

key decisions

and what each one traded off

decision 01

Use conversation for easy inputs, and a structured control for the rest

considered

Everything as conversation

Feels natural for three questions. Feels like an interrogation for twenty.

chosen

A hand-off to an inline control

Simple questions stay in the chat. When the task gets complex, the remaining fields appear together in one control inside the conversation.

why

Seeing related fields together lets customers check and fix their answers before submitting, and know how much is left. Keeping it inside the chat means the assistant stays aware of what happened, with no pop-up and no lost context.

trade-off

We deliberately limited the first version to forms under 20 questions, in a single section, with no custom scripts or field types. Larger, multi-page requests came later.

The same order as a long one-question-at-a-time chat, compared with a hand-off to an inline form
decision 02

Design within the platform, not around it

the constraint

Each control depended on components owned by other teams, and on how the chat assistant decided to render content: inline, in a pop-up, in a new tab, or as conversation. Mobile responsiveness wasn't polish. It was a dependency.

what happened

Star Rating and Service Catalog shipped on existing components. Guided Decision and Knowledge Article reached engineering handoff, then paused when the mobile-ready components they needed couldn't be delivered in time.

solution

the shipped experience

Service Catalog order form and Star Rating feedback control

01Service Catalog

The request form appears inside the conversation, sized for mobile, so customers review everything together and submit without leaving the chat.

02Star Rating

A lightweight rating at the end of a conversation, so customers can give feedback without leaving the chat.

research

The concepts were tested rather than assumed. We ran a pilot in October 2023, then concept sessions with a general audience in December, including people who usually help themselves on websites and people who prefer chatbots. Validation with ServiceNow customers was planned as the next phase.

impact

Star Rating shipped as a ServiceNow Store release, and Service Catalog shipped as part of omnichannel. The catalog approach was later extended on the roadmap to larger requests, like multi-page forms and complex product orders, using the same inline pattern.

I'm now revisiting rich messaging controls in the product's newer visual language, mapping which platform patterns can be reused and where customer-service cases still need more.

reflection

what worked

Scoping the first version

Limiting the catalog control to simpler forms got it shipped, and gave the larger cases a proven pattern to build on.

what I'd change

Map dependencies first

Two controls stalled on components other teams owned. I'd map and confirm those dependencies before investing in detailed design.