Today, let’s talk about cars and credit card payments. Shall we?
Scenario: The user is trying to rent a car using an application but the credit card on file has expired.
Challenge: Write them an error message so that they can correct the problem.
Headline: 30 characters
Body: 45 characters
As stated in my day 5 challenge, error messages can be very troubling for users. Therefore, my goal for this challenge is to be a solution provider to my user. To help them quickly solve a problem in the clearest and most concise manner to enable them to get on with their activity.
This was my first copy consideration and I wanted to end it here. But, I chose to try other copies and test them before reaching a final decision.
The “sorry” in the headline will calm the audience and empathize with them. The body also provided the necessary resources on how to maneuver the situation. The copies for the buttons were also clear enough for any user.
While the headline seem ok, the body and buttons aren’t. Here is why: as a user who is in the process of renting a card, there’s a level of urgency to it. So, why direct such a user to a customer care team when you can as well just give them a guidance on what to do next and how.
Many users believe that support team take long hours in responding to messages. Therefore, giving ‘support team’ as a help option would further agitate the user and we don’t want that.
The heading is quite direct and it screams at the audience with no empathy or an attempt to calm the user. Also, it didn’t explain to the user why the credit card was declined. As a UX writer, I should give full information to my audience. Take them on the journey with me with detailed information. As humans, we are inquisitive. So why did the credit card get declined?