Case Study · 01

TrackMate

A customer complaint tracking system designed and delivered for stc, from mobile self-service to an agent-facing web dashboard.

Associated With

stc (Saudi Telecom Company)

Type

Cooperative Training Project

Timeline

Jul – Nov 2024

My Focus

Requirements Analysis · Feature Planning · Workflow Design

TrackMate logo
01

Project Overview

TrackMate is a customer complaint tracking system built during my cooperative training with stc. It gives customers a way to submit, follow, and get resolution on service issues: network problems, billing questions, service interruptions, through the stc mobile app, while giving customer care agents a dedicated web dashboard to manage, track, and report on every ticket.

The product spans two experiences that had to work as one system: a lightweight, self-service ticket flow for customers, and a fuller operational view for the agents and teams resolving those tickets behind the scenes.

02

The Challenge

Customer complaints needed a clear, trackable lifecycle, from the moment a customer raises an issue to the moment it's resolved and closed. That meant defining what a "ticket" actually was across very different issue types (network, billing, service interruption, recharge), what statuses it could move through, and what information each side of the system, customer and agent, actually needed to see at each stage.

On the operations side, customer care teams needed visibility into ticket volume, response times, and overdue cases, without being buried in raw data.

Entry Point

TrackMate lives inside the stc app itself, alongside services like Number Management and Payment Management, so raising a complaint starts from a place customers already know.

03

The Approach

I approached TrackMate the way I approach most business problems: understand the process before designing the product. That meant analyzing business and operational data to see how complaints actually moved through the organization today, then working from that reality to define requirements, plan features, and design the ticket workflow, rather than designing in the abstract.

Throughout, I worked with cross-functional teams: operations, delivery, and IT, to make sure what got specified was actually buildable, and that what got built matched what customers and agents needed.

04

My Role

I owned requirements analysis, feature planning, and workflow design across TrackMate's product lifecycle, translating business needs into a practical digital product rather than a set of disconnected features.

Day to day, that included analyzing business and operational data to surface insights for decision-making and product improvement, developing KPI dashboards to monitor performance and ticket progress, supporting project planning and PMO reporting through data tracking, and translating business and product requirements into clear, actionable input for the development and delivery teams.

05

Process

01
Problem

Customer complaints lacked a structured, trackable path from submission to resolution.

02
Analysis

Analyzed operational data and existing processes to understand how complaints moved through the business.

03
Requirements & Planning

Defined requirements and planned features across the customer and agent-facing experiences.

04
Workflow Design

Designed the ticket lifecycle: statuses, tracking steps, and feedback points, for both sides of the product.

05
Outcome

Delivered a working mobile and web experience, tracked through KPI dashboards for the care team.

06

The Solution

TrackMate resolves into two connected experiences. On mobile, customers open a ticket, follow its status through a visual tracker, and close the loop with a short feedback step once it's resolved. On the web, customer care agents work from a full ticket queue with filters, statuses, and response-time metrics, and can open any ticket to see its full detail, tracking history, and a solution summary.

TrackMate mobile splash screen with Start and Cancel actions
TrackMate mobile ticket list, showing Open, Previous, and Cancelled tabs
TrackMate mobile ticket tracking view for a Network Issues complaint
TrackMate feedback modal asking customers to rate their satisfaction
TrackMate ticket detail asking whether the solution was helpful
TrackMate thank you screen confirming feedback was submitted

The customer journey: entry, ticket list by status, a visual tracker for each open case, and a lightweight feedback step once it's resolved.

07

Key Contributions

Requirements Analysis

Owned requirements analysis across the product lifecycle, from customer-facing flows to agent tooling.

Feature Planning

Planned features across the ticket lifecycle, balancing customer simplicity with agent-side detail.

Workflow Design

Designed the ticket tracking workflow: statuses, transitions, and the feedback step that closes each case.

KPI Dashboards

Developed KPI dashboards tracking performance, response time, and ticket progress for the care team.

Cross-Functional Collaboration

Worked with operations, IT, and delivery teams to keep requirements grounded and buildable.

PMO Reporting

Supported project planning and PMO reporting through ongoing data analysis and performance tracking.

08

The Agent Dashboard

The web experience is where customer care agents live day to day: logging in, scanning the ticket queue, and drilling into any case for its full tracking history and solution summary.

TrackMate web login screen
TrackMate web ticket queue with filters and response-time metrics
TrackMate web ticket detail page with overview, tracking history, and solution summary
TrackMate web dashboard showing ticket insights and daily tasks

Login, ticket queue, a single ticket's full detail, and the dashboard view: overview, tracking timeline, and solution summary.

09

Outcome

TrackMate was delivered as a working end-to-end solution: a mobile ticket-tracking flow for customers and a web-based operational dashboard for stc's customer care team, as part of my cooperative training engagement with stc.

Specific measured impact (e.g. resolution time, ticket volume, or customer satisfaction figures) is not included here, as no verified metrics were provided. Add real figures here if available.
Back to Work