01 THE PROBLEM

To downgrade, customers must submit a ticket resulting in churn and extra work for support

To downgrade, customers must submit a ticket resulting in churn and extra work for support

02 THE RESULTS

400+

400+

support hours saved in the first 3 months (team estimate)

60%+

60%+

reduction in support tickets

<5

<5

minutes to downgrade their plan versus days

03 THE SOLUTION

I designed an automated downgrade flow that handles most downgrade requests automatically

I designed an automated downgrade flow that handles most downgrade requests automatically

Want more details?

View the full process behind the work.

background dot pattern

We saved the Support team hundreds of hours by automating the downgrade flow

background dot pattern

We saved the Support team hundreds of hours by automating the downgrade flow

Reduced Customer Support tickets by more than 60%

Overview

I designed a self-serve downgrade flow to replace a painfully manual one. It did three things:
1) Improved the user’s self-serve experience and prevented “bad actors.”
2) Reduced Customer Support tickets by more than 60%.
3) Aligned with the direction of the FTC’s click-to-cancel rule.

Project details

Company

Company

WP Engine

Leading WordPress hosting providing fast, secure, and scalable solutions.

Role

Role

Design + Research

End-to-end design of a brand new feature. Conducted discovery and research.

Team and Stakeholders

Team and Stakeholders

10+ People

1 Product Manager, 8 Engineers, Business ops, Customer Experience and Customer Support.

Timeline

Timeline

4 Months

November 2024 – February 2025

Tools

Tools

Various

Figma, Miro, Zoom, Dovetail and NotebookLM for data synthesis

Type

Type

Desktop

Brand new feature, feature enhancement and flow redesign.

The problem

To downgrade, customers must submit a ticket resulting in churn and extra work for support.

Current experience

The current downgrade flow created a massive bottleneck for users.

Customer pain points

Untimely plan changes

Untimely plan changes

Some users treat downgrades as a seasonal adjustment. The unpredictable adjustment resulted in a lack of resources or unexpected charges.

Extensive back-and-forth

Extensive back-and-forth

Lacking awareness of 2 week notice periods caused unnecessary back-and-forth. With many expecting a downgrade to be instant.

Unnecessary friction

Unnecessary friction

Our reliance on traditional ticketing systems forced users into a slow and opaque process. Damaging our brand’s credibility and customer-centric reputation.

Internal pain points

Meanwhile, Customer Support experienced technical and operational challenges

Ticket routing issues caused delays

Ticket routing issues caused delays

Misrouted tickets were incorrectly sent to a general billing queue. This led to significant delays in ticket resolution.

All downgrades are a manual process, regardless of MRR

All downgrades are a manual process, regardless of MRR

Some plans are so complex and there's no other way to verify a request other than through a manual review.

A large percent of downgrades tend to be entry level plans

A large percent of downgrades tend to be entry level plans

Interviews revealed that most requests were lower MRR plans that were often ineligible for a downgrade.

Solution

We launched a self-serve flow that automated most downgrades while restricting ineligible requests to prevent revenue loss and bad actors.

Downgrading is now much simpler for customers because we added logic behind the scenes.

This feature allowed customers to responsibly manage their accounts independently

It was a win-win for customers and freed up Customer Support to focus on higher-value tickets.

Smart checkout prevented ineligible downgrades

If the customer’s usage exceeded the selected plan’s limits, then the system automatically added the resources at checkout. Otherwise, the downgrade was blocked.

Customers see in real time what a downgrade will change

We implemented a transparent self-service experience, giving customers real-time control over their plans during seasonal shifts.

Results

400+

400+

support hours saved in the first 3 months (team estimate)

support hours saved in the first 3 months (team estimate)

60%+

60%+

reduction in support tickets

reduction in support tickets

<5

<5

minutes to downgrade their plan versus days

minutes to downgrade their plan versus days

View more case studies

View more case studies

FOOD OASIS

Mobile web app optimization achieved 400 new users daily

A nonprofit based in Los Angeles gained 400 new users daily after enhancing usability and efficiency.

WP ENGINE

Plans page overhaul brought in 7.7% increase in upgrades

This redesign simplified plan modification decisions, resulting in a 7.7% increase in upgrades.