(Verizon)

Number Transfer Redesign: Reducing Customer Friction Across Channels

Redesigned the mobile number transfer experience to reduce a 33% fallout rate, resulting in 1.5M fewer failed transfers annually.

Role
Sr. Experience Designer
Duration
6 months
Year
2022
Tags
UX DesignService DesignOmnichannelResearch
(Overview)

When customers transferred their mobile numbers to Verizon, 33% experienced "fallout" — failures that require manual intervention by customer service representatives. This created significant operational costs and often a poor first service experience for new customers.

(Challenge)

In addition to the third of customers who experienced fallout, a small but significant number didn't have or know the account numbers and PINs required from their old carrier. With no visibility into transfer status and no way to self-correct, customers were forced to troubleshoot on their own — bouncing between retail stores, websites, and customer service.

Key Metrics

Metric
Value
Annual ports
9.4M
Monthly customer service calls
314K · 4% of all Verizon calls
Transfers initiated in retail stores
75%
Fallout rate requiring manual resolution
33%
(Research)

We conducted user interviews and collaborated with product managers to create a comprehensive service blueprint mapping the end-to-end porting journey across all touchpoints.

Customer journey map across Search+Learn, Shop+Buy, Wait for Transfer, and Transfer Complete stages, with channels, thoughts/feelings, pain points, and opportunities captured on sticky notes.
Research synthesis — a journey map of the porting experience across stages, capturing customer actions, thoughts, pain points, and opportunities.
Service blueprint mapping customer actions and port-process steps against front-stage channels (retail, web, SMS, IVR, chat, email) and backstage teams (LNP center, ACSS, POS).
Service blueprint documenting the full porting journey across every front-stage channel and backstage team — the foundation for the redesign.

What we learned

(Approach)

Rather than rebuild legacy systems, we designed a unified customer experience layer that worked across existing infrastructure — giving customers agency and visibility regardless of where they started.

Unified Messaging Framework

Audited and streamlined scores of status and error messages down to four core types with clear, actionable language. Added proactive "device waiting to ship" notifications to set expectations.

Number Transfer Messaging Matrix mapping transfer steps to proactive SMS and web status messages, including the fallout branch.
Port Status Messaging Matrix — consolidating dozens of messages into four core types across SMS and web, including the fallout branch.

Retail to Digital Handoff

Created an SMS-based bridge for the 75% of customers who started in stores:

Diagram: Store (POS) hands off to Digital Self Serve (SMS to Form) and Care Assisted (ACSS module).
Retail-to-digital handoff: when a customer chooses “port later,” a tokenized SMS link routes them to self-service — with the same intent captured in the care-assisted channel.
SMS thread leading to Verizon mobile-web screens: transfer checklist, get information, enter account info, review and submit.
SMS-to-web self-service flow allowing customers to complete a number transfer from their mobile device.

Self-Service Status and Updates

Built responsive interfaces allowing customers to:

SMS thread and three Verizon mobile-web status screens showing transfer info received, transfer started, and SIM install.
Transfer status surfaced with real-time tracking through the porting journey, triggered by proactive SMS.
Four My Verizon app screens showing the number-transfer status tracker with received, started, and approved steps.
The same status tracker surfaced inside the My Verizon app.
SMS thread and Verizon mobile-web screens with a missing-account-info banner, PIN/password entry, and an updated-details confirmation.
Self-service failure recovery: customers supply missing account info (PIN, password, zip) directly, with clear confirmation when it’s accepted.

Cross-Channel Integration

Coordinated with technical teams to sync data across retail systems, IVR platforms, and digital channels — ensuring consistent information regardless of touchpoint.

(Results)

2.5% reduction in fallouts in the year following launch (2022) — roughly 1.5M fewer failed transfers annually.

(Lessons Learned)

Working Within Constraints — this project taught me how to drive customer experience improvements within the reality of legacy systems. Rather than waiting for a perfect technical solution, I focused on the experience layer: unified messaging, proactive communication, and smart channel handoffs.

Cross-Functional Orchestration — success required aligning retail, digital, IVR, and technical teams around a shared vision. I used the service blueprint as a collaboration tool to build consensus and identify integration points across siloed systems.

Incremental Impact — by starting with the highest-volume channel (retail-to-digital) and the clearest pain point (messaging), we could deliver value quickly while building toward a more comprehensive omnichannel solution.