Narratology

Tone of voice in financial UX writing

Give financial UX content a tone that suits the situation. Define practical guidance for routine tasks, important decisions and moments when customers need help.

A financial app can use clear instructions and still feel distant from the people using it. The wording may explain the task accurately while giving little attention to the circumstances in which somebody encounters it. A routine account update and a request for help with a difficult decision need different treatment. Tone of voice helps a team make those choices deliberately.

That requires more guidance than an instruction to sound friendly. The writer needs to understand the task, the relationship with the customer and what the service can actually offer. From there, the team can decide how much explanation is needed and which language suits the situation. The same brand can sound consistent while responding differently to different needs.

Begin with the situation

Before deciding on a tone, consider what the person is trying to do and what they already understand. Someone completing a familiar task may need only a clear account of the result. Someone considering an unfamiliar financial option may need more explanation and time to compare it with the alternatives. The content should give them that support without assuming how they feel.

This distinction is useful when reviewing messages that announce a successful action. A service can complete a small administrative task without treating it as a major achievement. A more significant event may warrant greater acknowledgement, depending on the customer and the context. Agreeing these distinctions helps writers choose an appropriate tone across the service.

Translate brand guidance into writing decisions

Words such as warm, professional and reassuring can mean different things to different people. To make them useful, connect them with choices a writer can apply and a reviewer can discuss. Guidance might explain how the organisation addresses customers and when to use contractions. It should also show how much technical knowledge a particular explanation can assume.

Examples help when they demonstrate the reason for a choice. A team reviewing a difficult message needs to understand which wording supports the reader and which factual limits must remain clear. This is especially important when the draft aims to reassure somebody. The service needs to be able to support any assurance the wording gives.

Keep the explanation useful when something goes wrong

When a service fails, the person using it needs to know what has happened and what they can do next. A friendly phrase cannot supply information that the message has left out. Begin by establishing the facts, including whether the person needs to act or wait. Then consider how to explain those facts in language that fits the situation.

The tone should help someone follow that explanation without feeling blamed for a problem they cannot control. If the next step involves contacting support, make the route clear and explain what help is available. If the outcome is still uncertain, the wording needs to preserve that uncertainty. This gives the reader a realistic account of the situation.

Make tone guidance part of the content system

A tone guide becomes easier to use when it sits alongside the patterns a team already needs for product content. Writers can then review the purpose, required facts and tone of a message together. Product and design colleagues also need to understand those decisions, because presentation and timing affect how the wording is experienced. A message that suits one moment may be intrusive in another.

Start with a small set of frequently used messages and agree why the examples work. Record the context in which each pattern applies, including situations that require a different approach. Testing can then investigate whether people understand the message and interpret its tone as intended. As the team learns more, the guidance can become more specific.

Develop a voice your team can use

We help teams turn brand intentions into practical guidance for the content they write. Our work connects tone with plain language, so a distinctive voice still gives readers the information they need. Explore our brand voice and tone training or contact Narratology to discuss your product content.

About Frances Gordon

Frances Gordon is Director of Narratology and UK Ambassador for PLAIN. She contributes to plain language standards through the British Standards Institution.

Her work focuses on clear communication in regulated environments, accessibility and financial inclusion. Read Frances's profile.