Undeliverable
Undeliverable
Designing clarity into delivery exceptions and refunds.
Designing clarity into delivery exceptions and refunds.
Company
Verizon
Role
Lead designer
Responsibilities
Experience strategy, Service blueprinting, System design
When a delivery failed or a package was returned to sender, Verizon’s My Orders tracker went silent — leaving customers anxious and driving expensive support calls. As lead designer, I mapped the post-purchase journey with a service blueprint, then designed new tracker states and a refund milestone to keep customers informed and in control when they encounter delivery issues.
When a delivery failed or a package was returned to sender, Verizon’s My Orders tracker went silent — leaving customers anxious and driving expensive support calls. As lead designer, I mapped the post-purchase journey with a service blueprint, then designed new tracker states and a refund milestone to keep customers informed and in control when they encounter delivery issues.


My Orders Landing page


1 / 2
Problem
Problem
My Orders is where Verizon customers track current and past orders. When a delivery attempt failed, or an order was returned to sender (RTS), however, the tracker offered no status updates, no explanation of what had gone wrong, and no guidance on what would happen next. This ambiguity created anxiety for customers, led to preventable RTS orders, and drove shipping-related calls into customer care.
My Orders is where Verizon customers track current and past orders. When a delivery attempt failed, or an order was returned to sender (RTS), however, the tracker offered no status updates, no explanation of what had gone wrong, and no guidance on what would happen next. This ambiguity created anxiety for customers, led to preventable RTS orders, and drove shipping-related calls into customer care.
Landing page offers no status update

Order tracker remains stuck at "Shipped"

Around the same time, Verizon had gained access to new, more detailed carrier tracking data, creating an opportunity to offer clarity and guidance for delivery issues.
Around the same time, Verizon had gained access to new, more detailed carrier tracking data, creating an opportunity to offer clarity and guidance for delivery issues.
Landing page does not communicate failed delivery


1 / 2
Role & team
Role & team
I was the lead designer on a cross-functional team of product owners, engineers, and content strategists. I used a service blueprint to map the post-purchase journey, connecting new carrier tracking data to customer-facing touchpoints and aligning partner teams around one vision.
I designed the digital tracking components and UI, while Verizon’s CRM and Product teams led the authoring and execution of the SMS and email notifications.
I was the lead designer on a cross-functional team of product owners, engineers, and content strategists. I used a service blueprint to map the post-purchase journey, connecting new carrier tracking data to customer-facing touchpoints and aligning partner teams around one vision.
I designed the digital tracking components and UI, while Verizon’s CRM and Product teams led the authoring and execution of the SMS and email notifications.
Scroll horizontally to see details

Constraints
Constraints
This experience was built on top of Verizon’s existing order tracker, which had no way to represent temporary delivery exceptions — only permanent outcomes like order cancellations. Any new state I introduced had to work within the tracker’s existing patterns and scale across every order type.
The tracker’s new states were also shaped by the carrier tracking API. The delivery events it provided (delivery attempted, out for delivery, RTS) determined which moments we could design for.
This experience was built on top of Verizon’s existing order tracker, which had no way to represent temporary delivery exceptions — only permanent outcomes like order cancellations. Any new state I introduced had to work within the tracker’s existing patterns and scale across every order type.
The tracker’s new states were also shaped by the carrier tracking API. The delivery events it provided (delivery attempted, out for delivery, RTS) determined which moments we could design for.
Process
Process
These constraints shaped three central design decisions.
These constraints shaped three central design decisions.
Temporary vs. permanent exception states
Temporary vs. permanent exception states
Verizon’s tracker used a static error icon for permanent states like cancellations, a pattern designed to be the tracker’s final milestone. Using it for a failed delivery risked implying the order was canceled instead of pending redelivery, and it left no room for the “Delivered” milestone that still needed to follow. A failed attempt is temporary and resolvable, while a cancellation is not, and the tracker needed to make that distinction clear.
I designed a new “resolvable exception” state that signaled a temporary issue, kept “Delivered” visible as the next step, and reverted automatically once the package went back out for delivery.
Verizon’s tracker used a static error icon for permanent states like cancellations, a pattern designed to be the tracker’s final milestone. Using it for a failed delivery risked implying the order was canceled instead of pending redelivery, and it left no room for the “Delivered” milestone that still needed to follow. A failed attempt is temporary and resolvable, while a cancellation is not, and the tracker needed to make that distinction clear.
I designed a new “resolvable exception” state that signaled a temporary issue, kept “Delivered” visible as the next step, and reverted automatically once the package went back out for delivery.
Rejected
Permanent exception - “Delivered” hidden

Shipped
Resolvable exception - “Delivered” visible

Classifying RTS orders
Classifying RTS orders
When an order became RTS, Verizon’s systems canceled it and started an associated return, raising the question of whether to list it under “Purchases” or “Returns” on the My Orders landing page. Customers hadn’t initiated a return; Verizon’s systems had, so “Returns” didn’t match how they thought about their order.
I listed RTS orders under “Purchases,” in line with the customer’s original intent, and added a “Returned to Verizon” status message.
When an order became RTS, Verizon’s systems canceled it and started an associated return, raising the question of whether to list it under “Purchases” or “Returns” on the My Orders landing page. Customers hadn’t initiated a return; Verizon’s systems had, so “Returns” didn’t match how they thought about their order.
I listed RTS orders under “Purchases,” in line with the customer’s original intent, and added a “Returned to Verizon” status message.
Rejected
System driven

Shipped
Customer intent focused

Separating refund confirmation from the RTS event
Separating refund confirmation from the RTS event
Verizon issues a refund at the moment an order is RTS, and engineering wanted to fold both events into one tracker milestone. But once a package is returned, a customer’s attention shifts from “Where is my package?” to “Where is my refund?” Combining the events risked burying the one they were looking for.
I designed a dedicated “Refund issued” milestone showing the amount, date, and payout method, so customers had the confirmation they needed to feel comfortable placing a new order. This meant revisiting the rule that the error icon marks the final milestone. I made the refund an exception because it was the one piece of information that let customers close out the order in their minds.
Verizon issues a refund at the moment an order is RTS, and engineering wanted to fold both events into one tracker milestone. But once a package is returned, a customer’s attention shifts from “Where is my package?” to “Where is my refund?” Combining the events risked burying the one they were looking for.
I designed a dedicated “Refund issued” milestone showing the amount, date, and payout method, so customers had the confirmation they needed to feel comfortable placing a new order. This meant revisiting the rule that the error icon marks the final milestone. I made the refund an exception because it was the one piece of information that let customers close out the order in their minds.
Rejected
Consolidate events - Obscures refund

Shipped
Separate events - Highlights refund

Rejected
System driven


1 / 2
Rejected
Consolidate events - Obscures refund


1 / 2
Rejected
Permanent exception - “Delivered” hidden


1 / 2
Solution
Solution
The final experience extended Verizon’s existing order tracker with new, purpose-built states. A dynamic estimated delivery date updated in real time throughout the journey, and an “Out for delivery” milestone gave customers a clear signal that their package was on its way.
The final experience extended Verizon’s existing order tracker with new, purpose-built states. A dynamic estimated delivery date updated in real time throughout the journey, and an “Out for delivery” milestone gave customers a clear signal that their package was on its way.
Estimated delivery date displayed under the “Delivered” milestone

Estimated date updates to “Scheduled to arrive today” when out for delivery

Delivery issues appeared as a “resolvable exception,” RTS orders stayed under “Purchases,” and refund status was communicated clearly through a dedicated refund milestone. The new delivery attempted and RTS states were paired with proactive notifications, and the existing “Out for delivery” notification gained a matching tracker state, so customers stayed up to date without checking the tracker. My service blueprint defined when each new notification should trigger, guiding Product and CRM as they handled the message execution.
Delivery issues appeared as a “resolvable exception,” RTS orders stayed under “Purchases,” and refund status was communicated clearly through a dedicated refund milestone. The new delivery attempted and RTS states were paired with proactive notifications, and the existing “Out for delivery” notification gained a matching tracker state, so customers stayed up to date without checking the tracker. My service blueprint defined when each new notification should trigger, guiding Product and CRM as they handled the message execution.
“Delivery attempted”

“Returned to Verizon” & “Refund issued”

Because these states had to work consistently across every order type, I authored updated pattern guidelines for the My Orders design system.
Because these states had to work consistently across every order type, I authored updated pattern guidelines for the My Orders design system.
"Delivery attempted"


1 / 2
Upcoming
The event is planned but hasn’t happened yet.
Upcoming
The event is planned but hasn’t happened yet.

Completed
The event has happened or is underway. If it’s the final milestone, it marks the order complete.
Completed
The event has happened or is underway. If it’s the final milestone, it marks the order complete.

Permanent exception
The order can’t be completed and has been canceled. Usually the final milestone unless followed by a refund confirmation.
Permanent exception
The order can’t be completed and has been canceled. Usually the final milestone unless followed by a refund confirmation.

Resolvable exception (new)
Something has stopped the current event from completing. The customer, Verizon, or a third party can resolve it, and the order continues.
Resolvable exception (new)
Something has stopped the current event from completing. The customer, Verizon, or a third party can resolve it, and the order continues.

Estimated delivery date displayed under “Delivered” miletones


1 / 2
Outcomes
Outcomes
This shipped as a core enhancement of Verizon’s post-purchase journey, adding flexibility and clarity to the existing order tracker. We don’t have hard usage or call-volume metrics, but the decisions were grounded in how customers think about their orders and aimed to address the anxiety and confusion behind shipping-related calls.
This shipped as a core enhancement of Verizon’s post-purchase journey, adding flexibility and clarity to the existing order tracker. We don’t have hard usage or call-volume metrics, but the decisions were grounded in how customers think about their orders and aimed to address the anxiety and confusion behind shipping-related calls.
Reflection
Reflection
This project reinforced how easily backend logic can dictate the customer experience. Designing for the customer’s intent instead of the system’s classification was the difference between a confusing experience and a clear one.
The service blueprint gave design, product, engineering, and CRM a shared reference for how backend logic, messaging, and UI needed to fit together, which made cross-functional alignment smoother.
If I took this further, I’d use carrier reason codes to explain why an attempt failed, and build self-serve actions into the tracker, like updating a delivery preference or pre-signing for a package, so customers can resolve delivery issues themselves.
This project reinforced how easily backend logic can dictate the customer experience. Designing for the customer’s intent instead of the system’s classification was the difference between a confusing experience and a clear one.
The service blueprint gave design, product, engineering, and CRM a shared reference for how backend logic, messaging, and UI needed to fit together, which made cross-functional alignment smoother.
If I took this further, I’d use carrier reason codes to explain why an attempt failed, and build self-serve actions into the tracker, like updating a delivery preference or pre-signing for a package, so customers can resolve delivery issues themselves.

