UX writing and microcopy: the words that make interfaces work
By Kiara DalmiaContent Writer, Advorize
The short answer
UX writing is the text inside a product — buttons, labels, errors, empty states and confirmations. Good microcopy tells people what will happen, what went wrong and what to do next, in their words. It is one of the cheapest ways to improve conversion and reduce support tickets.
Key takeaways
- Buttons say what happens: 'Send ₹120', not 'Submit'.
- Errors explain the fix, not the fault.
- Empty states are onboarding, not decoration.
- Use your customers' words, not your org chart's.
| Before | After | Why |
|---|---|---|
| Submit | Book my appointment | Says what happens |
| Invalid input | Enter a 10-digit mobile number | Says how to fix it |
| No data | No orders yet — import from your old system | Turns empty into a next step |
| Are you sure? | Delete 3 invoices? This can't be undone. | States the consequence |
Rules we write by
- Front-load the important word; people scan, they don't read.
- Be specific about money and time — fees, totals, delivery dates.
- Never blame the user in an error message.
- Keep terms consistent — 'order' everywhere, not 'order', 'purchase' and 'booking'.
UX writing is built into every UI/UX design project we deliver; you can read the microcopy in each concept in our portfolio.
Sources
Written by
Kiara Dalmia
Content Writer, Advorize
Kiara writes Advorize's guides on design, development and digital systems, turning the team's project work into practical, plain-language answers.