UX writing challenge: Day 14
Something went wrong
Scenario: a user is shopping using a price comparison app that boasts “real-time” pricing on items. As they are checking the price of an item, something goes wrong. The problem is unknown.
Challenge: write a message that informs the user that they cannot access the app right now. You cannot specify “why” the app doesn’t work, you also want them to continue using the app.
Headline: 30 characters max
Body: 120 characters max
Button(s): 15 characters max
We have all come across this situation, whether on an app or website, where something goes wrong and we don’t know what exactly went wrong. The only thing that helps us out is the UX writing, which guides us as to what might be the fault and what can be done from our end.
Today, I’ll fill in the shoes of a UX writer and write a suitable copy for such scenarios.
Points to keep in mind
- What went wrong is unclear, but as a UX writer, it’s our duty to inform people that everything is going to be alright.
- We need to convey this in a manner that guides the user and notifies them they are still in charge while guiding them on what can be done.
- The approach needed will be friendly.
One can check this link to get a better idea on how to write an error message when the error is unidentified.
What I came up with
Idea 1
Heading- Something Went Wrong
It’s a classic! can be seen almost everywhere in the error messages. If the error is not identifiable, this works like a charm. Any user can easily process it.
Body- An error occurred while comparing, we’re fixing it! Till then, you can browse the app.
The body is clean and neat, guides the users to browse the app making sure they stay. (What I found was missing is that it seems a bit too straightforward without the fun and friendly element I wished for.)
CTA- Go Back
Idea 2
Heading- Something Went Wrong
Body- We’re experiencing a temporary issue fetching prices. Keep browsing, we’ll be back soon!🛍️
The body use a playful and a friendly tone to helps the user get an idea of what might have gone wrong, while ensuring the user stays on the app.
CTA- Keep Browsing
Feel free to comment with your views on my challenge; criticism is appreciated as it will help me hone my skills 🙌🏻.
Checkout my other challenges —
