Brand voice in UI messages: keep your character when things go wrong
Keep your brand recognisable in errors, hints and confirmations without letting jokes or slogans obscure the status of the task.
Article language: English

In this article
“Oopsie, something fell apart!” can sound light-hearted when the thing that fell apart is a short animation. When someone has just typed a long project description, cannot tell whether their message was accepted and needs to leave the house in a moment, a brand with a sense of humour suddenly becomes a brand with rather peculiar timing.
Brand voice is a recognisable way of speaking. Tone is how that voice adapts to the situation. You can be warm and specific in a welcome message and after an error, while leaving out the joke when the reader needs a clear answer. Character does not disappear when you use an ordinary sentence such as “We couldn't send your message”. Sometimes that is precisely where it becomes most credible.
For a team designing a website, the problem is usually a lack of material to work with. The brand guidelines describe a personality that is bold, intelligent and approachable, but offer no example of a message after a submission is interrupted. The person building the site writes something at the last minute. That is when “Invalid request” moves into the elegant website, suitcase in hand and planning a long stay.
Understand the situation before choosing an adjective
Start with three questions: what was the person trying to do, what can the system confirm, and what can they do next? Choose the tone afterwards. An empty-field message needs a different explanation from a connection lost after sending. One generic sentence about “a little trouble” cannot honestly cover both.
Take a fictional brand selling workshop equipment. Its language is calm, friendly and practical. For an empty email field, it might say “Enter the email address we should reply to”. When the form detects a missing @ symbol, it might display “Check your email address. The @ symbol is missing”. A sending failure needs a separate message about the status of the enquiry, whether the text has been kept and how to retry.
These sentences belong to one brand, even though their rhythms differ. What they share is help with the task. Being recognisable does not require the same opening phrase in every message. An interface can show that “we're on your side” through its behaviour, without repeating that sentence beside every field.
Microsoft's brand voice guidance distinguishes a consistent voice from a tone adapted to the context and the customer's state of mind. That is a useful working distinction. It does not mean another business should adopt exactly the same traits or the same English habits of shortening sentences.
In Polish, there is also a choice about how to address the reader. Make that choice for the whole journey, rather than separately for the heading and the error. For example, if a Polish website moves from the equivalent of “Choose” to “Dear User, please carry out verification once again”, the reader may reasonably feel they have entered a different room in the same institution.
The rules should also cover service and product names. Brand architecture and offer naming help people recognise the scope of an offer. See the Polish-language article on brand architecture and offer naming (in Polish). An error message should use the same name as the form, the card and the confirmation. A moment of uncertainty is no time to set the reader a quiz on company terminology.
Rewrite one difficult moment from start to finish
Suppose a customer sends an enquiry about a shelving unit. After they press the button, the connection drops. The team is tempted to write “Something went wrong. Try again”. This leaves out the most important question: could the first message already have arrived? The message design depends on the answer the actual process can provide.
If the server confirmed acceptance, do not present the operation as a failure just because the next screen did not load. If there is no confirmation, say that confirmation is missing. This does not prove that the first enquiry failed to arrive. The team and the person implementing it should agree on the retry mechanism, including how to identify or handle possible duplicates, and on its wording. A copywriter cannot establish the status of an operation through optimism alone.
A possible message for an unconfirmed attempt is: “We don't have confirmation that your enquiry was accepted. Your description is still in the form. Try sending it again, or use the contact details provided”. Both options must actually exist. If the form does not keep the description, fix that behaviour or write a different message. The best tone cannot undo visible data loss.
Name the button for what it does. “Try sending again” describes an action. “Continue” makes people find out where it leads. An alternative contact method can have its own explanation of what information to include. Do not make someone tell the whole story again if a recognisable case reference can be provided.
GOV.UK's error message guidance recommends clearly explaining the problem and how to correct it, using language that matches the field label. This is a reference for errors in the information entered. A service failure needs a separate explanation: the person cannot repair it by changing their surname.
Look at the wording before the error, too. If an attachment requirement was hidden and a stern message about an unsupported format appears after submission, the problem concerns the whole journey. Add a short instruction where the person chooses the file. An error message should not be the first place a known rule is revealed.
Read the scene aloud, from the label to the retry. It becomes easier to notice that “input material” in one place means “attachment” in another, while an “enquiry” suddenly becomes an “application”. The team may regard these as synonyms. For someone trying to regain control, they become more questions to answer.

Apply the same approach to instructions for getting started with a product (in Polish). Here, too, people need to recognise the state they are in, take an action and check the result. Brand voice should help them do that, rather than decorate every step with commentary.
Humour has its place, but it does not belong in every error message
A light tone can suit voluntary exploration, sample data or an empty list from which someone can calmly begin work. It can help with a welcome or an explanation of a new feature. It is harder to defend when someone has incurred a cost, lost work or cannot tell whether they completed an important action.
Dividing messages into successes and errors is not enough. Successfully closing a complicated matter may call for a calm confirmation. An empty list of favourite products may leave room for a little lightness. What matters is the consequence of the event and the reader's situation, rather than the colour of the component.
A joke should be an addition you can remove without losing information. If deleting the joke leaves you unable to tell what happened, the message needs editing. A metaphor should not replace the name of an action, either. “Back on track” may suit the brand, but the button still needs to say whether it leads to the offer, the form or the previous page.
A 404 page that restores context (in Polish) makes the point well. It can have character and an interesting image, but it needs a clear route to the right content. People did not come solely to assess the company's sense of humour. Usually, they are looking for a particular document or service.
Allow the tone to become more restrained in a more difficult version of the same situation. An empty list before the first product is added can invite someone to browse the catalogue. For a saved-products list (in Polish), adapt that message to the absence of a first selection, and prepare a different one for lost access to earlier saved items. A list emptied by a failure needs an explanation of what is known about those items. The same screen without data does not tell the same story. The message library should therefore distinguish the cause of an empty state where the system can establish it reliably.
Avoid jokes that imply the reader is to blame. “Forgot your password again?” sounds like a remark from someone with too much time and too little to do. Simply name the option for recovering access. Friendly language does not require inventing a relationship the customer never agreed to.
The Aeneia Design offer can bring website design together with the work of organising interface content. Specific difficult states make a useful starting point for that conversation, rather than just a list of adjectives describing the brand's personality.
Replace “let's write like humans” with examples and decision rules
A short set of guidelines should include a few examples: the situation, the wording and the reason for choosing it. Add what the system confirms, whether the user can fix the problem and what action you suggest. The next person can then understand why the sentence works, rather than copy its rhythm into a case where it does not belong.
For an existing website, start by listing the messages people encounter in important tasks. Record the address, when the message appears and how to trigger it. A screenshot of the message alone may not show that the requirement was explained in the previous step, or that the button beside it leads somewhere else. Keep that context in the material prepared for editing. You can then assess the whole short conversation instead of polishing each sentence in isolation.
Keep examples with different consequences: an empty field, an incompatible file, no results, an interrupted attempt and confirmed acceptance. They do not need to be the same length. A message about one missing field can be short. An explanation of an uncertain operation may need another sentence. An equal character count is not a measure of consistency here.
Check the wording in the actual component. A long Polish word can change a message's height, while a button with a specific label may take two lines. Do not cut the meaning just to preserve the perfect rectangle in the mock-up. The design should accommodate the information people need, including when text is enlarged.
For translations, provide the situation and intended outcome, rather than an isolated sentence. The translator needs to know whether “Save” completes a step, creates a new version or merely keeps a draft. Other languages can then sound natural while still leading to the same decision.
Separate editing the wording from confirming that it is true. A content specialist can improve a sentence, but the process owner should verify information about timing, retained data and the next step. “We'll reply tomorrow” does not become true because it sounds good in Polish. If the team replies only on working days, review the confirmation sent on a Friday evening. Someone reading it should be able to identify the correct day to expect a response. That is a concrete case to settle with the team before the deadline goes into a shared template.
During review, ask a participant to explain what happened and what they will do next. Do not ask only whether the message feels friendly. If their answer does not match the actual state, fix the meaning first. Assess the warmth of the language afterwards. Writing copy for a service page (in Polish) similarly starts with knowing what needs to be said.
Review the thank-you page after a form submission (in Polish), too. A confirmation continues the same conversation; it is not a free space for a generic slogan. It should retain the name of the matter, the scope of what is confirmed and clear information about how it will be handled next.
Finally, decide who updates messages when the process changes. A new file limit, a different contact method or a changed response time is a reason to review the wording. Brand voice is not a frozen collection of attractive sentences. It remains recognisable when the brand continues to tell the truth in a way that helps people move forward.







