HALO Cloud — CCaaS Platform
Product design across the cloud contact-center platform — enterprise workflow interfaces, internal tools and the product experience itself.
Client
Ubona Technologies — internal product (confidential)
Role
UX/UI Designer — product UI, interface patterns and internal tools.
Platform
Web Product
Confidentiality: Internal product details and interfaces are confidential. Patterns shown are sanitised.
01Overview
HALO Cloud, the CCaaS platform behind Ubona's conversational and contact-center products: enterprise workflow interfaces, internal tools and the product experience itself.
02Context
A capable platform with engineering-first surfaces needed a coherent product experience — consistent patterns, clear workflows and usable internal tools.
03User Journey
The platform problem
04UX Decisions
01Patterns before features
Consistency came from a shared component and state library, applied incrementally.
02Internal tools are user-facing too
Operators use these tools all day — the same UX discipline applied to them.
03State coverage in the library
Loading, empty, error and permission states shipped with every component, not added later.
06Edge Cases
Good UX is what happens when things go wrong. Each case: the problem, the user-facing message and the recovery action.
Permission-denied surface
Edge caseA user opens a tool without permission.
“This tool requires admin access.”
Recovery: Explained placeholder with a request-access path.
Legacy data shape
Edge caseOld records lack fields new interfaces expect.
“This record has incomplete data.”
Recovery: Graceful degraded rendering with a note — never a crash.
07Final Experience
Platform surface
Platform surface
Consistent patterns across enterprise workflows and internal tools.
Schematic placeholder — add an approved screenshot via data/case-studies.ts