Support context concept

Support Portal: Customer Context for the Next Action

An enterprise support concept that helps an agent identify the customer’s concern, understand the account context, inspect recent activity, and choose the next action with the right context in view.

AudienceInternal Enterprise

DomainEnterprise workflow

RoleProduct designer

PlatformResponsive web

Year2021

ScopeCase study and prototype

Reading time5 min

Product evidence

The screens below show the customer context workflow. There is no public interactive prototype.

Evidence only

30 Second Summary

DESIGN MOVE

Sequence issue suggestions, account overview, recent activity, and customer DNA around the active support decision.

EVIDENCE

Four product screens show issue suggestions, customer overview, timeline activity, and customer DNA.

LIMITATION

This concept does not establish efficiency, satisfaction, or outcomes with working support agents.

Overview

A unified customer context workspace for support agents.

Support Portal helps an agent identify the concern, inspect account context, review recent activity, and interpret customer DNA before choosing a next action. I designed the information hierarchy across the four product screens.

Problem

Customer context was separated at the decision point.

Agents had to assemble the concern, account details, timeline activity, and profile signals across disconnected views. The opportunity was to keep that context together during the support conversation.

Problem and context

Issue suggestions, customer history, and profile context support the agent’s next action.

The four screens show issue suggestions, customer overview, recent timeline activity, and customer DNA. Together they frame what an agent should understand before choosing the next action.

Identify the concern

Suggested issues reduce the effort required to translate an open customer request into a more specific support topic.

Understand the current customer state

The overview brings account and relationship context into one scannable surface before the agent acts.

Interpret history and profile together

Timeline activity and customer DNA add behavioral and relationship context without claiming a complete resolution workflow.

Product evidence

Four screens build a clearer customer picture before the next action.

Issue suggestions, the customer overview, activity and profile context each contribute to the agent’s next decision.

01 · Identify the concern

Use suggested issues to narrow the customer’s need.

The search suggestions state helps the agent move from an open request toward a more specific concern without inventing a priority score.

02 · Understand the overview

Keep essential customer context visible before acting.

The overview brings the account and customer relationship into one scannable surface for the active decision.

03 · Inspect recent activity

Use timeline context to understand what happened before.

The timeline provides a chronological view of recent customer activity that can inform the agent’s interpretation.

04 · Interpret customer DNA

Add profile context before choosing the next action.

The customer DNA view surfaces relationship and behavioral context that may change how the agent responds.

Context decision record

What should an agent understand before choosing the next action?

The concept gives agents context for their decisions. It does not prioritize or resolve cases automatically.

Question

How can the workspace reduce context switching while keeping the agent in control?

Signal

Issue suggestions, the customer overview, recent activity, and customer DNA each contribute a different part of the situation.

My decision

Sequence those views around the active customer so the agent can form a coherent picture before responding.

Why

Context is most useful when it is connected to the immediate decision rather than distributed across unrelated tools or tabs.

Product consequence

The workspace keeps the relevant context together so the agent can choose the next action without giving up judgment.

Boundary

Queue ordering, ownership, handoff, resolution, notifications and return-to-queue behavior are not demonstrated in this concept.

Reflection

Context before action

Support agents need customer context at the moment of action. Bringing recent activity and account details together makes the next decision easier to assess; it does not replace the agent’s judgment.

Next project