Augment

UX Copy That Reduces Support Tickets

Many support tickets are really interface problems in disguise. Better words on the screen can remove a surprising number of them.

Close-up of a typeface specimen showing capital letters in bold weights
Photo by Markus Spiske on Unsplash, with an Augment halftone treatment
Executive Summary

Key Takeaways

  • Read your support tickets as UX feedback. Repeated questions point to unclear screens.
  • Use the user's words, not internal terms.
  • Error messages should say what happened, why, and how to fix it.
  • Put help where the question arises, not in a separate help center.

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

BeforeAfter
Error 500We could not save your changes. Please try again in a minute.
Invalid inputEnter a date in the format 25/12/2026.
Permission deniedOnly admins can change billing. Ask an admin on your team.
Request failedWe 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.

Frequently Asked Questions

Clear labels, helpful errors, and in-context hints answer questions before users have to ask.

Sources and further reading

  1. 10 Usability Heuristics for User Interface DesignNielsen Norman Group · Published · Updated · Accessed
  2. Shopify PolarisShopify · Undated page · Accessed
  3. GOV.UK Design SystemUK Government Digital Service · Undated page · Accessed

Credits

  • Written by Augment Editorial Team, Product design and engineering, Augment Lab.
  • Cover photo Photo by Markus Spiske on Unsplash, with an Augment halftone treatment, used under the Unsplash License.
  • Research Statistics and standards are cited from the sources above. Always check the original page for the latest version.

Augment Product Design

Ready to make your product clearer?

From first concept to go-live, we turn complex product ideas into clear, useful experiences.

UX Copy That Reduces Support Tickets | Augment. Lab