Messages
Messages consist of up to two sentences to communicate the system's current state and provide feedback on user actions. This pattern is commonly found in components like Inputs or Alerts.
General
Keep it as short as possible while still being descriptive enough. Also, remember there’s a 240-character limit per message.
| Do ✅ | Don't ❌ |
|---|---|
|
|
Don't use technical language.
| Do ✅ | Don't ❌ |
|---|---|
| Couldn't send invoice due to a technical issue | Error 298dx9283 prevented the invoice from being sent |
Reuse messages (or their structure) whenever possible.
| Do ✅ | Don't ❌ |
|---|---|
|
|
Don't use personal pronouns.
| Do ✅ | Don't ❌ |
|---|---|
|
|
Use an objective and neutral tone.
| Do ✅ | Don't ❌ |
|---|---|
|
|
Use common contractions.
| Do ✅ | Don't ❌ |
|---|---|
| Couldn't save provider due to a technical issue | Could not save provider due to a technical issue |
Use punctuation only when a larger message is extremely necessary.
| Do ✅ | Don't ❌ |
|---|---|
|
|
Use sentence case, but capitalize proper nouns.
| Do ✅ | Don't ❌ |
|---|---|
|
|
Specific
For the error texts in a form field, start with an imperative verb.
| Do ✅ | Don't ❌ |
|---|---|
|
|
In modals that confirm actions, personal pronouns, and question marks can be used.
| Do ✅ | Don't ❌ |
|---|---|
| This action can’t be undone. Are you sure you want to delete this product? | Do you want to delete this product? This can't be undone. |
For consistency, place the adverb “successfully” at the end of the phrase.
| Do ✅ | Don't ❌ |
|---|---|
|
|