A common trust building problem
Your copy reads like a system talking
The short answer: write like a human. Here is how to recognise this problem in your funnel, why it happens, and how the best consumer apps design it away.
How to recognise it
- Error messages quoting codes at users
- Screens explaining features instead of outcomes
- Users rereading instructions and still asking support
Why does robotic copy erode trust?
Users read interface copy the way they read a person: tone tells them whether anyone here cares. “An error has occurred (code 5033)” tells them nobody does.
System language creates distance at exactly the moments trust is decided: errors, payments, permissions, anything confusing. The user leans in with a question and the product answers like a printer.
Every string is a chance to sound like someone on their side. Squandered one string at a time, the product acquires the personality of a form.
How do you write UX copy that builds trust? Like a human, about outcomes
Rewrite the copy at trust moments first: errors, empty states, confirmations, asks. The rule for each: a human explaining to a friend what happened and what to do next.
Errors get the full treatment: what happened, in plain words. Whether their stuff is safe. What to do now. “We couldn't save that. Your draft is safe. Try again in a minute” does more for trust than a year of marketing.
Run every string through the reading-aloud test: would a person say this sentence to another person? “This feature allows you to...” fails. “Now you can...” passes.
Keep the register honest: human is not jokey. At high-stakes moments, warmth means clarity and calm, not a pun over your payment form.
The building blocks that solve it
- JTBD Copywriting: Every string written from the user's side of the glass.
- Fail Safe: The words that matter most say what is safe.
Who does this well
Monzo: Banking messages in plain, calm English: the tone is the trust strategy.
Headspace: Even system moments keep the coach's voice: the product never breaks character into bureaucrat.
Questions founders ask
Can copy be too casual?
Yes: at moments of money, errors and anxiety, jokes read as not taking the user's problem seriously.
Human does not mean funny. It means clear, warm and on their side, at whatever seriousness the moment carries.
Which strings matter most?
In order: errors, anything near payment, permission asks, empty states, buttons.
Those are the moments users are deciding whether to trust you, which makes them the highest-leverage sentences in the product.