Voice in product UI: button labels, error messages, empty states, confirmations. Where the brand's "calm under pressure" actually has to land.
The full Voice & Tone document is the foundation. These are the operational rules for product copy specifically.
"Save changes" not "Saving!" — the latter strips the agency. Clarity is the priority. Warmth comes from word choice, not exclamation marks.
"We couldn't reach the server" not "Server returned 503". Speak as one person to another. Surface the technical detail only when it helps the user act.
Every error and empty state ends with a next step. If there's nothing they can do, say that — explicitly. Don't leave a dead end.
Errors are when the brand has to work hardest. Don't panic, don't apologize excessively, don't joke. Hold steady. Acknowledge, explain, offer a path.
UI copy is shorter, more directive, and rarely italic. Reserve the editorial voice (Lora, italic, longer rhythms) for marketing surfaces.
| Context | Marketing voice | UI voice |
|---|---|---|
| CTA | Let's work on it together. | Schedule a call |
| Section heading | Real, direct, grounded. | Account settings |
| Helper text | A space to think clearly about what's next. | We'll only use this for project updates. |
| Button | Take the next step | Continue |
When in doubt, write less. These are ceilings, not targets.
Verb + object. "Save draft", "Send invite", "Delete account". No "Click here", no "Submit form".
One short, declarative sentence. Tells them why the field exists or what format you expect.
What broke + what to do. Skip the apology unless you really cost them something.
Why it's empty + what they get + a single primary action. Avoid two CTAs of equal weight.
Title is the result. Body is the consequence or detail. Action verb if there's a next step.
Title states the question or action. Body explains the consequence. Buttons close the loop.
Use these verbatim where the situation matches. They've been calibrated to the brand voice — don't rewrite them ad hoc.
| Avoid | Prefer | Why |
|---|---|---|
| Submit | Save · Send · Continue | "Submit" is bureaucratic. Use the actual verb for the action. |
| Click here | Schedule a call · Read the brief | The link target is the label. Never make "click here" the link. |
| Please wait | Saving… · Generating your brief… | Tell them what's happening, not what to do. |
| Oops! | [direct description] | Cute language at error moments breaks trust. Stay steady. |
| Sorry, but… | [acknowledge + path forward] | Save apologies for moments when you actually cost them something. |
| Are you sure? | Delete this engagement? | State the action plainly. The user knows whether they're sure. |
| Awesome! | Done · Saved · Sent | The brand doesn't gush. Confirmation is the reward. |
| User | you · your team · the person | Speak to the person, not the database row. |
The same voice. Different volumes. The brand's confidence holds across all of these — what changes is the warmth and pace.
| Moment | Tone | Example |
|---|---|---|
| Welcome / onboarding | Warm, paced, encouraging | Welcome. Let's set up your team — this takes about three minutes. |
| Routine confirmation | Brief, plain | Saved. |
| Friction (validation, fix-this) | Direct, helpful | Add an "@" to make this an email address. |
| Trouble (system error) | Calm, candid | We lost connection. Your work is held locally — try again when you're back online. |
| Risk (irreversible action) | Plain, slowed-down | Delete this engagement? This removes all files and can't be undone. |
| Celebration (goal hit) | Quietly proud | That's the last brief signed off — you're ready to launch. |