One place, every update
One place, every update
Designing Service Central, a unified experience for order tracking and customer support at Verizon.
Designing Service Central, a unified experience for order tracking and customer support at Verizon.
Company
Verizon
Role
Co-designer for MVP, Lead designer post-launch
Responsibilities
System design, Information architecture, Stakeholder alignment
Verizon customers had no single place to track their orders, service activations, and support requests. I co-designed Service Central, a new app/web experience built on a newly consolidated backend, to unify tracking within one system. I designed the tracking detail pages and the shared status system that tied the experience together, mentored a new teammate, and used research to settle disagreements. We delivered the MVP in two months, launching to every Verizon customer.
Verizon customers had no single place to track their orders, service activations, and support requests. I co-designed Service Central, a new app/web experience built on a newly consolidated backend, to unify tracking within one system. I designed the tracking detail pages and the shared status system that tied the experience together, mentored a new teammate, and used research to settle disagreements. We delivered the MVP in two months, launching to every Verizon customer.
Service Central landing page



1 / 3



Problem
Problem
Tracking was siloed across Verizon. While My Orders offered a consolidated tracking experience, it was only for the fulfillment of physical items, like deliveries and in-store pickups. Phone activations, trade-ins, and service transfers each lived in its own separate experience. There was no clear path for customers to open, track, or manage a support request, so issues often stayed unresolved and customers called in for updates, driving unnecessary operational cost.
Tracking was siloed across Verizon. While My Orders offered a consolidated tracking experience, it was only for the fulfillment of physical items, like deliveries and in-store pickups. Phone activations, trade-ins, and service transfers each lived in its own separate experience. There was no clear path for customers to open, track, or manage a support request, so issues often stayed unresolved and customers called in for updates, driving unnecessary operational cost.
Order tracking was consolidated in My Orders, while everything else was tracked separately
Order tracking was consolidated in My Orders, while everything else was tracked separately



At the same time, engineering had developed a new backend that unified tracking milestones into a single system, treating orders, service events, and support as one connected customer journey. That created an opportunity, and a leadership directive, to build a front-end experience that could bring these disconnected journeys together for customers.
At the same time, engineering had developed a new backend that unified tracking milestones into a single system, treating orders, service events, and support as one connected customer journey. That created an opportunity, and a leadership directive, to build a front-end experience that could bring these disconnected journeys together for customers.
Role & team
Role & team
I worked alongside one other designer, who was new to the company. We split the work by area: he owned the landing page, where customers get an at-a-glance view of their journeys and support requests. I owned the tracking detail experience, the pages customers reach when they view a specific journey or request, along with the shared status system behind both.
I also helped him ramp up on Verizon’s design system, reviewing his work for consistency, and took the lead on how we presented to leadership. That meant framing trade-offs, preparing documentation to anticipate questions, and choosing the right format for each review, from a simple customer narrative to low-fidelity concepts or high-fidelity screens.
I worked alongside one other designer, who was new to the company. We split the work by area: he owned the landing page, where customers get an at-a-glance view of their journeys and support requests. I owned the tracking detail experience, the pages customers reach when they view a specific journey or request, along with the shared status system behind both.
I also helped him ramp up on Verizon’s design system, reviewing his work for consistency, and took the lead on how we presented to leadership. That meant framing trade-offs, preparing documentation to anticipate questions, and choosing the right format for each review, from a simple customer narrative to low-fidelity concepts or high-fidelity screens.
Constraints
Constraints
Service Central was designed on top of the unified backend, which already defined the milestone structure and journey types we had to work within. Any change to that structure meant additional development effort, and because the same milestones also powered the customer service agent experience, they weren’t originally built with customer clarity in mind.
Service Central was designed on top of the unified backend, which already defined the milestone structure and journey types we had to work within. Any change to that structure meant additional development effort, and because the same milestones also powered the customer service agent experience, they weren’t originally built with customer clarity in mind.
Backend powers both the customer and agent experiences
Backend powers both the customer and agent experiences

We also had a tight two-month timeline, and needed to align multiple stakeholders, including several VPs across product and design leadership, on key experience decisions. Navigating that meant moving quickly without leaving feedback unaddressed.
We also had a tight two-month timeline, and needed to align multiple stakeholders, including several VPs across product and design leadership, on key experience decisions. Navigating that meant moving quickly without leaving feedback unaddressed.
Process
Process
These constraints played out in a few key decisions.
These constraints played out in a few key decisions.
Aligning on what each page was for
Aligning on what each page was for
Early on, my partner and I disagreed with product about how much detail belonged in the landing page components for journeys and requests. Product wanted to surface detailed information, but that made the component visually dense and hard to scan, especially with several stacked on one page.
To align on a direction, we built a sitemap that defined each page’s purpose — the landing provided at-a-glance status, while the details offered a deeper dive — and presented two component design options: one detailed and one minimal. After the sitemap reframed the conversation around the page’s goal, our partners preferred the minimal option.
Early on, my partner and I disagreed with product about how much detail belonged in the landing page components for journeys and requests. Product wanted to surface detailed information, but that made the component visually dense and hard to scan, especially with several stacked on one page.
To align on a direction, we built a sitemap that defined each page’s purpose — the landing provided at-a-glance status, while the details offered a deeper dive — and presented two component design options: one detailed and one minimal. After the sitemap reframed the conversation around the page’s goal, our partners preferred the minimal option.
Rejected
Detailed component

Shipped
Minimal component

Badge vs. progress wheel
Badge vs. progress wheel
A similar disagreement came up around how to represent journey and request status. Design wanted a text-based badge system (In progress, Take action, Completed) that could be reused across the experience. Product wanted a progress wheel, which had more visual impact but was less actionable.
A similar disagreement came up around how to represent journey and request status. Design wanted a text-based badge system (In progress, Take action, Completed) that could be reused across the experience. Product wanted a progress wheel, which had more visual impact but was less actionable.
Progress wheel
Progress wheel

Badge
Badge

To reach an agreement, we partnered with our in-house research team to test both options with customers, who found the progress wheel less clear, especially when they needed to take action to progress a journey or request. Using these findings, we landed on a solution that met both goals — text-based status paired with color coding — maintaining clarity while adding visual impact.
To reach an agreement, we partnered with our in-house research team to test both options with customers, who found the progress wheel less clear, especially when they needed to take action to progress a journey or request. Using these findings, we landed on a solution that met both goals — text-based status paired with color coding — maintaining clarity while adding visual impact.
Shipped
Shipped
Badge with color coding
Badge with color coding

Alternative states
Alternative states
Rethinking milestone labels
Rethinking milestone labels
The milestones were built to serve both customers and support agents, and that dual purpose created challenges. Transactions had more milestones than customers needed, and several labels used technical language. Product wanted one shared vocabulary for both audiences, but design believed the existing milestones were not clear enough to customers to serve that goal.
We tested the existing milestones and found they didn’t match how customers thought about their own journeys or requests, which helped justify additional engineering work to tailor the milestones specifically for the customer-facing experience.
The milestones were built to serve both customers and support agents, and that dual purpose created challenges. Transactions had more milestones than customers needed, and several labels used technical language. Product wanted one shared vocabulary for both audiences, but design believed the existing milestones were not clear enough to customers to serve that goal.
We tested the existing milestones and found they didn’t match how customers thought about their own journeys or requests, which helped justify additional engineering work to tailor the milestones specifically for the customer-facing experience.
Handling feedback at scale
Handling feedback at scale
In our initial design reviews, we received a wide range of feedback that pulled us in different directions, and presenting too many options caused leadership to anchor on minor details rather than high-level direction. We adapted our approach by grouping related feedback into themes, curating a focused set of options per theme, and presenting them in a decision matrix that traced each option back to the original feedback. That gave us a more structured way to drive alignment without losing anyone’s input.
In our initial design reviews, we received a wide range of feedback that pulled us in different directions, and presenting too many options caused leadership to anchor on minor details rather than high-level direction. We adapted our approach by grouping related feedback into themes, curating a focused set of options per theme, and presenting them in a decision matrix that traced each option back to the original feedback. That gave us a more structured way to drive alignment without losing anyone’s input.
Rejected
Detailed component


1 / 2
Solution
Solution
The MVP focused on support requests and upgrade orders, which let us validate our milestone structure and the shared status system before expanding to other journey types. For both requests and upgrades, we consolidated, relabeled, and regrouped milestones based on customer research, and applied the text-and-color status system across every landing and detail page.
The MVP focused on support requests and upgrade orders, which let us validate our milestone structure and the shared status system before expanding to other journey types. For both requests and upgrades, we consolidated, relabeled, and regrouped milestones based on customer research, and applied the text-and-color status system across every landing and detail page.
Milestone restructuring - Upgrade journey
Milestone restructuring - Upgrade journey

The biggest design challenge was the support request details page, where a tracker and an asynchronous agent chat needed to coexist on a mobile viewport, and neither could be secondary: the tracker gave customers context, and the chat was how they moved their request forward. We explored a few directions, including stacking the tracker and chat in different orders and a chat-bubble icon that opened a modal, before landing on a bottom-sheet drawer fixed above the navigation footer that slides up to reveal the chat.
The biggest design challenge was the support request details page, where a tracker and an asynchronous agent chat needed to coexist on a mobile viewport, and neither could be secondary: the tracker gave customers context, and the chat was how they moved their request forward. We explored a few directions, including stacking the tracker and chat in different orders and a chat-bubble icon that opened a modal, before landing on a bottom-sheet drawer fixed above the navigation footer that slides up to reveal the chat.
Support request details page


1 / 2
Support request details

Chat bottom-sheet drawer

The drawer kept our asynchronous chat visually distinct from Verizon’s global live chat, which uses a floating chat-bubble icon — an important distinction since customers shouldn’t expect immediate replies. It also let customers move seamlessly between the chat and the rest of the page, referencing the tracker or their original submission details, without the disruption of a full-screen modal.
The drawer kept our asynchronous chat visually distinct from Verizon’s global live chat, which uses a floating chat-bubble icon — an important distinction since customers shouldn’t expect immediate replies. It also let customers move seamlessly between the chat and the rest of the page, referencing the tracker or their original submission details, without the disruption of a full-screen modal.
Outcomes
Outcomes
The MVP shipped on time, within our two-month timeline, to all Verizon customers across app and web. We don’t have hard usage metrics, but the impact shows up in other ways. Customer research settled our two most contested decisions, the status display and the milestone labels, and in both cases the simpler, more customer-centered direction prevailed. The milestone restructuring from the MVP became the standard approach that product and design used as Service Central expanded to additional journey types, and I stayed involved in that work after launch.
The MVP shipped on time, within our two-month timeline, to all Verizon customers across app and web. We don’t have hard usage metrics, but the impact shows up in other ways. Customer research settled our two most contested decisions, the status display and the milestone labels, and in both cases the simpler, more customer-centered direction prevailed. The milestone restructuring from the MVP became the standard approach that product and design used as Service Central expanded to additional journey types, and I stayed involved in that work after launch.
Reflection
Reflection
Looking back, I’d implement the feedback process we eventually landed on — grouping themes, curating a focused set of options, and using a decision matrix to gain alignment — into leadership reviews from day one. While our early reviews worked, they took longer than they needed to and made iteration harder to manage.
I’d also lean on AI tools to speed up our early layout exploration. AI-assisted design was far less mature at the time, but using it now would let me move through initial concepts faster, freeing up more time for the more nuanced design decisions like resolving the status display and milestone-label decisions where discussion and research mattered most.
Looking back, I’d implement the feedback process we eventually landed on — grouping themes, curating a focused set of options, and using a decision matrix to gain alignment — into leadership reviews from day one. While our early reviews worked, they took longer than they needed to and made iteration harder to manage.
I’d also lean on AI tools to speed up our early layout exploration. AI-assisted design was far less mature at the time, but using it now would let me move through initial concepts faster, freeing up more time for the more nuanced design decisions like resolving the status display and milestone-label decisions where discussion and research mattered most.

