Helix
Self-service help centers for retail and member brands, on Oracle Service Cloud.
- Client
- Helix Business Solutions · Oracle Service Cloud
- Year
- 2017–2018
- Role
- Application and CX Engineer — UX design and front-end
- Platform
- Mobile-first web · Oracle Service Cloud
- Disciplines
- Enterprise SaaS, Support UX, Front-end
Overview
Helix implements Oracle Service Cloud for brands with high support volume. I designed the UX of the customer-facing portals and built their front-end components in HTML, CSS, JavaScript and PHP. A help center is used at the worst moment in a customer relationship — an order that didn't arrive, a renewal that failed — so the job is to get people to an answer, or to a person, fast.
Task completion
~25%
faster after simplifying complex support workflows
The pattern
Many brands, one anatomy.
Every portal answers the same three questions in the same order: where do I search, what do most people come here for, and how do I reach a person. The brand changes; the structure doesn't.
That consistency is what made reusable UI patterns possible across client implementations — and why a new portal didn't start from a blank page.
01 · Search
The question comes first.
A single search field sits at the top, phrased the way a customer would ask — “How can we help you?”, “What can we help you with?” — before any menu.
02 · Top tasks
Two shapes for the same list.
Below search come the most common requests. When they're actions — cancel an order, request a price adjustment — they work as an icon grid. When they're topics, a scannable list of categories reads faster.
03 · Escalation
Always a way to a person.
When self-service runs out, the next step is never hidden: a plain Contact us, a feedback prompt on the page itself, a persistent live-chat tab.