---
title: "Errors"
canonical: "https://documentation.chaos.com/space/DOCSGUIDE/697663514/Errors"
format: markdown
---
This page provides details on writing microcopy for errors.


## **What are Error Messages?**

---

**Error messages** help users get where they want to go and, if necessary, indicate that there’s a problem getting there the way the users intended. Error messages are used to maintain trust and avoid assigning blame to the users, even if the error is their fault. There are three types of error messages: *incline error*, *detour error*, and *blocking error*.


## **Types of Error Messages**

---

**Inline errors** are the least intrusive. Inline errors advise the user to make a correction before they can move forward. Example: In a sign-up window, when you type a 5-digit number instead of a 10-digit number, an inline error pops up, stating “Enter a 10-digit number, then try again.”

**Detour errors **should have the main instruction in the most prominent spot. Example: In a web app, when the payment method is declined, the error message first provides instructions, then an explanation, and finally the single action to take to move forward. “Add a new way to pay. The payment did not go through. To buy this, add a different card. Cancel or Add.”

**Blocking errors** indicate that the way forward is blocked until the user takes an action that is outside of the scope of the experience. For example: Connect to the Internet. To buy a valid license, turn on Wi-Fi and connect to the internet. Turn on Wi-Fi button.”


## **Rules**

---

- If moving forward isn’t possible, make it clear.
- If an apology is appropriate in the context of the Chaos brand, apologize for the delay, loss, inconvenience, or disappointment to the user.
- Add useful links if needed.
- Don’t use the word ‘invalid’. It has been used in the United States to indicate a person with disabilities and has a negative connotation.
- Use ‘please’ and ‘sorry’ intentionally, without overdoing it.
- Focus on clarity and practicality, and don’t try to be clever or use jokes. Jokes are forbidden and only frustrate users further.
- Make it simple, use simple short sentences.
- Use a neutral and human voice.
- It is better to avoid using words like ‘error' or 'failure’. For example, avoid messages such as “Error! Please correct the field.” or “The action failed. Try again.”
- Avoid blaming the user. For example, instead of “Phone number is invalid”, use “Phone number should be 10 digits.”
- Avoid dramatic statements like ‘fatal error’ and overly complicated technical terms that otherwise can be explained using simple, plain language.


## **Common Patterns**

---

- Incline error general structure: [verb] the [noun] For example, Enter a 10-digit number.
- Detour error general structure: [verb] the [noun] for the title, [because of problem name] do X for the description, and [verb] for the button.
- Blocking error general structure: [Problem name] for the title, {because fo problem name] you can’t X [until Y happens].


## **Example**

---


---