UX Case Study — Telecom & Contact-Center Platform

Designing dtWorks,
a live-signal for
customer engagement.

An end-to-end design system and product surface for agents and customers — covering sales & appointment dashboards, a 7-step prepaid connection flow, a self-care storefront, and a 360° order & service console. Built from a blank canvas and shipped to production.

RoleLead Product Designer, 0→1 (UX + UI)
Deployed atImagine Telecom, Brunei · Government Contact Center
ScopeResearch → Wireframes → Hi-Fi UI → Handoff → Usability testing
SurfacesAgent console, Customer self-care web, Ops dashboards
dtworks / sales-dashboard.html
dtWorks sales dashboard showing live sales tracking, total sales, key metrics, ACV, CLV, sales-by-channel, and leads pipeline widgets
7
Step guided flow designed for new prepaid connections
2
Live deployments — enterprise contact center & telecom operator
3
Surfaces unified under one design system — agent, ops, customer
1→N
Dashboards, charts & reports built from a single wireframe kit
The Product

A customer engagement platform for enterprises that can't afford friction.

dtWorks is a customer engagement platform built by BahwanCyberTek — it gives contact-center agents and back-office teams one workspace to onboard customers, manage services, track sales performance, and resolve issues, while giving customers a self-care storefront to manage their own plans.

My Role

From the first whiteboard sketch to the deployed product.

  • Ran discovery and brainstorming sessions with product owners and telecom operations stakeholders to map how agents actually process a connection, a complaint, and a sale.
  • Designed the full wireframe kit for every module — dashboards, onboarding flows, self-care storefront, and 360° customer/order views.
  • Took wireframes to production-ready hi-fi UI, defining the visual language, component library, and data-visualization patterns reused across the platform.
  • Worked side-by-side with the development team through build, catching gaps between spec and implementation.
  • Ran usability testing rounds with agents and iterated on flows like the prepaid connection journey based on real task-completion friction.
Process

Four passes, one system.

Every module — from a dashboard widget to a seven-step onboarding flow — moved through the same discipline before it reached engineering.

01 — Discover

Map the real workflow

Sessions with call-center agents and telecom stakeholders to understand how a connection is sold, a plan is upgraded, and a complaint is closed today.

02 — Wireframe

Structure before style

Greyscale layouts for every screen — dashboards, forms, storefronts — validated for information hierarchy before a single color was chosen.

03 — Design

Build the visual system

A shared component library and data-viz language — cards, funnels, gauges, steppers — so every new dashboard looked native from day one.

04 — Test & Build

Sit with development

Close pairing with engineers through build, plus usability passes with agents to catch friction in multi-step flows before launch.

wireframe
Greyscale wireframe of the sales dashboard establishing layout for live sales tracking, key metrics, ACV/CLV charts, sales by channel and leads pipeline
Low-fidelity structure — hierarchy and grid locked first.
final ui
Final hi-fidelity sales dashboard with color, illustration and live data applied over the wireframe structure
Production UI — same grid, dtWorks visual language applied.
Signature Flow

A seven-step new-connection journey, built for an agent mid-call.

The prepaid connection flow is the platform's most-used journey — an agent captures customer ID, address, service plan, SIM and number, account and payment, all inside one guided stepper. Every screen carries a persistent progress rail so an agent can resume a journey interrupted mid-call.

STEP 01
Step 1: Customer details — upload ID document or enter details manually
Customer Details
STEP 02
Step 2: Customer address — locate on map or enter manually
Customer Address
STEP 03
Step 3: Service plan selection with filters for contract length and plan type
Service Selection
STEP 04
Step 4: Number access — SIM details and number allocation
Number Access
STEP 05
Step 5: Account address details with option to reuse customer address
Account Setup
STEP 06
Step 6: Payment — invoice summary with online payment link and QR code
Payment
STEP 07
Step 7: Preview and submit — full summary of customer, address, service and account details
Preview & Submit
Design decision

A dual-path pattern — scan a document or type it manually — runs through every capture step, so the flow never blocks an agent when a scanner isn't available. The stepper stays visible and clickable at every stage, letting an experienced agent jump back without losing entered data.

Ops & Agent Tools

Dashboards built to be scanned in seconds, not studied.

Customer-Facing

A self-care storefront that mirrors the agent's product catalog.

Customers browse and purchase the same plans agents sell — postpaid, prepaid, bundle, and addon — with quantity steppers, subscription-length toggles, and a persistent cart tray so switching between product tabs never loses progress.

Outcomes

What shipping this changed.

Live in production

Deployed to a real telecom operator (Imagine, Brunei) and a government contact center — designs weren't a concept, they carried live customer onboarding and payments.

One system, many surfaces

The same component and data-viz language now powers agent, ops, and customer self-care surfaces — new dashboards ship without re-solving layout or chart patterns from scratch.

Fewer dead ends mid-call

The onboarding stepper's dual scan-or-type pattern and persistent progress rail were direct responses to usability testing friction with live agents.

Reflections

What I'd carry into the next system.

01

Wireframe the data, not just the layout.

Because the sales dashboard's wireframe locked in real metric hierarchy — live tracking before vanity totals — the hi-fi pass was mostly a styling exercise, not a renegotiation of what mattered.

02

Long forms need an escape hatch.

A seven-step flow only works mid-call if every step can be skipped, revisited, or filled two different ways. That flexibility mattered more than trimming steps.

03

Shared components pay off across surfaces, not just screens.

Building one card, funnel, and stepper language early meant the appointment dashboard, order 360, and self-care storefront could all launch faster once the pattern existed.