Increasing Backups
Protected Exodus users from losing their money and reduced the number of support tickets.
Problem
During an all-hands call, Support gave a presentation that included many stories of customers losing access to their funds because they never wrote down their 12-word recovery phrase that allows them to access their wallet after they lose or change their device.
I could see it’s devastating for customers and also hurts the company, so I talked with my manager to see if I could spend some time on a personal project to tackle it.
Goals
Reduce support tickets about lost wallets
Improve backup rates (so people don’t lose their money)
Make the backup need feel urgent, not just explain it
Existing content
There actually was already a good amount of content throughout the app that was meant to educate the user and guide them toward backing up. However, it wasn’t effective enough.
In these cases, I was often asked to simply rephrase existing content so that it includes a new detail. However, I knew updating content such as this 6-screen story and maybe 1 or 2 other locations wouldn’t be effective enough. Plus, our UI is usually limited with not much room available for extra details.
Also, Exodus was only in English at the time, so rephrasing long copy might not be effective for non-fluent English users.
I knew needed something more obvious. Something concise and unignorable.
Aiming to target the right time and right place for the message, I looked at our existing backup flow to see if there was room to add new content or steps.
I also thought the way our words were presented reduced reading comprehension. This problem affected the multiple areas in the app, but it was most crucial in our backup flow.
Here’s an example of how I showed ways to make our modals easier to read. This was out of scope for this specific project, so I didn’t start this discussion until after this project was done. I knew we needed something faster than major design changes that can’t be implemented quickly. Plus, there’s usually a lot of pushback for changes like this.
Brainstorming solutions
I thought maybe a badge or an element of gamification could incentivize the user to back up.
I also thought of a small social media company that makes completing a profile feel like a quest. In order to get full access to all features, the user needs to do prerequisites such as adding a profile image or react to a post.
I didn’t want to block the user from any features, but I thought it’d be effective to make the user feel like there’s something incomplete when they haven’t backed up yet.
Various solutions inspired by all of this were shared with the lead UX designer. I showed her where I thought we could use icons and short messages in key areas of the UI that would effectively guide the user to the Backup feature.
Solution
We really threw the kitchen sink at this problem.
We added components in key areas to inform and remind customer without long copy.
I wanted to make it feel like something was incomplete, not just explain it technically.
Dismissible banner on the main portfolio screen. This would open a banner (shown later) that would educate the user and guide them toward the backup flow.
This card also took the user to the backup flow.
“!” icon to make the Security tile feel incomplete and urgent. The nudged the user to open Security.
Once they opened Security, they were then shown the “Incomplete” pill so that they might tap Backups to start the backup process.
These only appear if the user has a funded wallet. We didn’t want users to feel scared or pressured when there was no risk.
Modals periodically appeared to remind customer to back up their wallet.
We created four versions to make the message less repetitive.
If the user hadn’t backed up yet, we also reminded them after they receive money.
This avoids bugging them when they have no funds yet, which would block revenue-generating actions.
This is another example of telling users the right thing at the right time.
Results
Once these changes were release in February 2023, backup-related support tickets decreased by 57.1% in 2 months.
The second chart shows the total number of tickets (including all topics) did not go down. This data shows that the number of tickets specifically about backups drastically went down, independent of the overall number of support tickets.
The messaging became more accessible and intuitive, especially for non-native English speakers.
The feature was cost-efficient: reduced support burden, improved user outcomes, and required minimal engineering lift.