Microcopy patterns for errors and alerts
According to the NN Group's guidelines, a good error and alert message should be:
- Explicit: The error message should be concise but informative, explaining clearly what has happened (or will happen if it’s an alert) and providing the solution to fix this problem. As far as possible, the instructions shouldn't ask users to go to another page, remember some new information, or make an extra effort.
- Polite: When an error occurs, the system should never act like it's the users' fault. Take the blame, apologize for the inconvenience, and direct users to the next step.
- Written in human language: Avoid technical jargon, code snippets, or abbreviations that say nothing to your users and scare them bluntly. Investigate different types of errors and talk to developers so you can explain even the hardest problem in a simple way.[1]
Pro Tip: You can use humor in error messages to make users smile and feel less frustrated. Just ensure it matches your brand’s personality and won’t make users feel uneasy.
