Tickets are feedback
Export a month of support tickets and tag them. You will usually find a short list of questions asked again and again: where do I find this, what does this label mean, why did this fail. Each is a signal that something on the screen is unclear.
Principles for clear copy
- Use plain words. "Remove" beats "Deprovision".
- Say what the button does: "Send invoice" instead of "Submit".
- Keep sentences short and put the important word first.
- Be consistent. Do not call the same thing "project" in one place and "workspace" in another.
- Write for a tired person who is in the middle of something else.
Rewrite error messages
| Before | After |
|---|---|
| Error 500 | We could not save your changes. Please try again in a minute. |
| Invalid input | Enter a date in the format 25/12/2026. |
| Permission denied | Only admins can change billing. Ask an admin on your team. |
| Request failed | We could not connect. Check your internet and try again. |
A good error message answers three questions: what happened, why, and what to do next.
Place help in context
Add short hints next to fields that cause confusion. Add a link to a relevant guide from the screen where the problem occurs. Users will not leave the task to search a help center, but they will read one line beside the thing they are stuck on.
Close the loop
After you change the copy, watch the ticket volume for that topic. Keep a short record of what you changed and what happened. It builds the case for investing in clarity.



