Contact us, reframed
Contact us, reframed
Redesigning Verizon’s contact us page so customers reach the right help in fewer steps.
Redesigning Verizon’s contact us page so customers reach the right help in fewer steps.
Company
Verizon
Role
Lead designer
Responsibilities
Problem framing, Information architecture, Channel strategy
Verizon’s contact us experience required customers to answer a series of questions before showing any way to get help. After an agency-led engagement, I redesigned the experience, delivering a single page with phone numbers, dynamic wait times, and the top contact options up front. Leadership was worried that removing friction would spike call volume and recommended a throttled launch to a small customer group first. We saw no spike in volume and rolled out the redesign to everyone.
Verizon’s contact us experience required customers to answer a series of questions before showing any way to get help. After an agency-led engagement, I redesigned the experience, delivering a single page with phone numbers, dynamic wait times, and the top contact options up front. Leadership was worried that removing friction would spike call volume and recommended a throttled launch to a small customer group first. We saw no spike in volume and rolled out the redesign to everyone.
Redesigned experience
Redesigned experience
As shipped, fall 2025
As shipped, fall 2025
Scroll horizontally to see details

Problem
Problem
Verizon’s contact us page presented ways to get help only after a customer made up to four selections: a service (for home internet, a second choice between Fios, 5G Home Internet, and LTE Home Internet), an issue category, and often a sub-issue. The options they reached then varied by service: billing and payments led to different contact options on Mobile, Fios, 5G Home, and LTE Home.
Verizon’s contact us page presented ways to get help only after a customer made up to four selections: a service (for home internet, a second choice between Fios, 5G Home Internet, and LTE Home Internet), an issue category, and often a sub-issue. The options they reached then varied by service: billing and payments led to different contact options on Mobile, Fios, 5G Home, and LTE Home.
Previous experience - 5G Home Internet billing path
Previous experience - 5G Home Internet billing path
Simplified from archived captures (April 22, 2025)
Simplified from archived captures (April 22, 2025)
Scroll horizontally to see details

Previous experience - Contact options for billing across services
Previous experience - Contact options for billing across services
Contact options
Mobile
Fios
5G Home
LTE Home
Chat with us
Call us
We'll call you
Create a support request
Personalized suggestion
(self-serve)
Connect with us
(Facebook Messenger)
Contact us was part of a 2025 Verizon initiative to enhance digital shopping, support, and service experiences. An external agency defined the problem and the acceptance criteria, and its heuristic analysis and research audit pointed to the number of clicks it took to get help as a source of customer frustration. Leadership wanted a redesigned contact us page that offered dynamic recommendations and direct contact options.
Contact us was part of a 2025 Verizon initiative to enhance digital shopping, support, and service experiences. An external agency defined the problem and the acceptance criteria, and its heuristic analysis and research audit pointed to the number of clicks it took to get help as a source of customer frustration. Leadership wanted a redesigned contact us page that offered dynamic recommendations and direct contact options.
Role & team
Role & team
The agency defined the initial discovery and requirements, and I took it from there as the sole designer.
The agency defined the initial discovery and requirements, and I took it from there as the sole designer.
Constraints
Constraints
The acceptance criteria were intentionally open-ended, leaving room to define what the redesign should entail. The systems behind the page, however, were out of scope — I couldn’t consolidate phone numbers, change the IVR that greets and redirects callers, or unify hours for departments reached through the same number.
Verizon’s contact ecosystem was messy. There were many ways to get help, and some were outdated, like chatting through Facebook Messenger after Verizon had launched its own chat assistant. Channels didn’t support every service: scheduled calls, for example, were available only for Mobile and Fios.
The acceptance criteria were intentionally open-ended, leaving room to define what the redesign should entail. The systems behind the page, however, were out of scope — I couldn’t consolidate phone numbers, change the IVR that greets and redirects callers, or unify hours for departments reached through the same number.
Verizon’s contact ecosystem was messy. There were many ways to get help, and some were outdated, like chatting through Facebook Messenger after Verizon had launched its own chat assistant. Channels didn’t support every service: scheduled calls, for example, were available only for Mobile and Fios.
Process
Process
These constraints shaped a few key decisions.
These constraints shaped a few key decisions.
Reframing the problem
Reframing the problem
Before designing anything, I did a deep dive into Verizon’s contact ecosystem. Calling and chatting were the most used channels, while options like Facebook Messenger saw very little use. One phone number could also lead to different departments, like account and billing versus troubleshooting, each with its own hours.
These findings reframed the problem. Removing the multi-step flow wasn’t enough: the options customers reached also needed to be consistent and easier to parse. I recommended addressing both and got agreement to remove Facebook Messenger and present the remaining options together on one page, organizing phone numbers by service.
Before designing anything, I did a deep dive into Verizon’s contact ecosystem. Calling and chatting were the most used channels, while options like Facebook Messenger saw very little use. One phone number could also lead to different departments, like account and billing versus troubleshooting, each with its own hours.
These findings reframed the problem. Removing the multi-step flow wasn’t enough: the options customers reached also needed to be consistent and easier to parse. I recommended addressing both and got agreement to remove Facebook Messenger and present the remaining options together on one page, organizing phone numbers by service.
Are we removing too much friction?
Are we removing too much friction?
Leadership liked the straightforward one-page design but was concerned that removing this much friction could spike call volume and drive up costs. They recommended throttling the new experience to a small customer group to watch for a spike, and I agreed.
Leadership liked the straightforward one-page design but was concerned that removing this much friction could spike call volume and drive up costs. They recommended throttling the new experience to a small customer group to watch for a spike, and I agreed.

Dynamic recommendations by intent
Dynamic recommendations by intent
To offer dynamic recommendations, I designed an intent widget highlighting the relevant phone number and contact options for a signed-in customer’s likely issue. The widget was a template that could extend across intents. Leadership wanted to focus on billing, so I tailored it into a bill intent widget for bill shock, when a customer’s bill was higher than expected, a common call driver.
To offer dynamic recommendations, I designed an intent widget highlighting the relevant phone number and contact options for a signed-in customer’s likely issue. The widget was a template that could extend across intents. Leadership wanted to focus on billing, so I tailored it into a bill intent widget for bill shock, when a customer’s bill was higher than expected, a common call driver.
Approved intent widget - Bill shock
Approved intent widget - Bill shock
Routes customers to an agent
Routes customers to an agent

The approved design routed customers to an agent. During development, cost concerns led to the widget being redefined toward self-serve, and I updated the design to a simple tile with text and a call to action.
The approved design routed customers to an agent. During development, cost concerns led to the widget being redefined toward self-serve, and I updated the design to a simple tile with text and a call to action.
Redefined intent widget - Bill shock
Redefined intent widget - Bill shock
Highlights self serve
Highlights self serve

Solution
Solution
The redesign replaced the sequence of questions with a single page. Phone numbers for Verizon’s core services sit up front with dynamic wait times (where data was available) that switch to “Currently closed” when a department is closed, and the top contact options (Chat with us, Create support request, Schedule a call) appear together instead of varying by service.
The redesign replaced the sequence of questions with a single page. Phone numbers for Verizon’s core services sit up front with dynamic wait times (where data was available) that switch to “Currently closed” when a department is closed, and the top contact options (Chat with us, Create support request, Schedule a call) appear together instead of varying by service.
Open - Estimated wait time
Open - Estimated wait time

Closed - “Currently closed”
Closed - “Currently closed”

Top contact options presented upfront
Top contact options presented upfront

Other needs, such as prepaid, business, accessibility, and mailing addresses, sit behind a More services button, so the default view stays focused on core products. The outdated Facebook Messenger entry point was removed.
Other needs, such as prepaid, business, accessibility, and mailing addresses, sit behind a More services button, so the default view stays focused on core products. The outdated Facebook Messenger entry point was removed.
More services - Expanded
More services - Expanded
Scroll horizontally to see details

With no service choice up front, the contact options weren’t tied to a service. For customers with both mobile and home services, I designed screens for chat and scheduled calls that asked which service they needed help with. These were approved for the fall 2025 launch. Support requests already handled this through a device selector, designed earlier as part of another project.
The self-serve intent widget shipped as a fast follow and was shown to signed-in customers likely to have a billing issue.
With no service choice up front, the contact options weren’t tied to a service. For customers with both mobile and home services, I designed screens for chat and scheduled calls that asked which service they needed help with. These were approved for the fall 2025 launch. Support requests already handled this through a device selector, designed earlier as part of another project.
The self-serve intent widget shipped as a fast follow and was shown to signed-in customers likely to have a billing issue.
Outcomes
Outcomes
The redesigned page shipped and, after the throttled launch showed no spike in call volume, was released to all visitors to Verizon’s website in fall 2025. I don’t have post-launch metrics beyond that, and the live experience has evolved since launch.
The redesigned page shipped and, after the throttled launch showed no spike in call volume, was released to all visitors to Verizon’s website in fall 2025. I don’t have post-launch metrics beyond that, and the live experience has evolved since launch.
Reflection
Reflection
In the support space, call volume is a key metric product partners are always measured against, and that pressure has pushed experiences to add friction on the way to human support. This project presented a chance to do the opposite.
I was nervous that removing so much friction would be seen as too risky. What made it feasible was the option to test in production: a throttled launch turned leadership’s concerns into something we could measure, reducing risk and enabling us to make an informed decision.
If I took this further, I’d look beyond the page, advocating for consistent contact options for all services, streamlined IVR routing, and unified hours of operation.
In the support space, call volume is a key metric product partners are always measured against, and that pressure has pushed experiences to add friction on the way to human support. This project presented a chance to do the opposite.
I was nervous that removing so much friction would be seen as too risky. What made it feasible was the option to test in production: a throttled launch turned leadership’s concerns into something we could measure, reducing risk and enabling us to make an informed decision.
If I took this further, I’d look beyond the page, advocating for consistent contact options for all services, streamlined IVR routing, and unified hours of operation.

