“Friendly but professional” appears in many voice guides, yet it does not tell an editor how to write a support message or product headline. I find a brand voice useful when it helps choose between two sentences in a specific situation. A list of attractive adjectives needs to become a set of observable writing decisions.
Keep the voice stable and adapt the tone
Voice carries character; tone responds to the reader’s situation. A collection announcement can be curious and energetic. A delivery problem needs a different emotional register. Consistency does not mean expressing the same mood everywhere.
Choose three characteristics and translate them into behaviours. Clear can mean explaining unfamiliar terminology and stating an outcome directly. Considerate can mean preserving context so a person need not repeat a problem. Warm does not require an exclamation mark or affectionate greeting in every sentence.
Write before-and-after examples
| Vague wording | Clearer alternative | Why it helps |
|---|---|---|
| Discover an exclusive experience | Explore the collection’s materials | Describes what the click offers |
| Your request has been processed | I’ve received your message and will review the details | Makes the action understandable |
| Our product is unique | See dimensions and usage details | Replaces an unsupported superiority claim |
These examples need to fit the actual process. I would not promise a reply within 24 hours without an agreed response time. Professional copy describes what will happen reliably; it does not invent reassurance the operation cannot support.
Treat microcopy as editorial work
Buttons, error messages and empty states determine what someone does next. “View project details” or “Send message” can be more useful than a generic “Continue.” If a field is incomplete, say which information is needed instead of displaying an unexplained error.
Contact subject options also shape the experience. Clear categories such as brand strategy, content project or creator collaboration help people place their enquiry. Visitors should not need to understand internal department names or production shorthand before they can get in touch.
Write Turkish and English for the same intention
Literal translation can preserve meaning while changing the tone. First identify the sentence’s job: does it explain, invite or resolve an error? Its English equivalent should perform that job with equal clarity. Turkish sentence structure and politeness conventions do not need to be reproduced word for word.
Maintain a terminology list containing brand names, category names and concepts that should stay consistent. If one page says creator and another says influencer, check whether that difference is intentional. Explain the distinction when the two terms refer to different roles.
Test the guide with two editors
Give two editors the same short text and ask them to work independently. Each should identify which rule supports each change. The goal is not an identical sentence. Different wording can be acceptable when both versions communicate the same facts, stay within the same promise and explain the reader’s next step.
For a fictional form, take “Great! Your request has been processed.” If the system has only confirmed receipt, “processed” may imply a later stage. One editor might write “We received your message”; another might choose “Your application is approved.” This is more than a tonal difference: the second version introduces a new claim about the process. It cannot be used unless approval really occurred. These are exercise examples, not notifications describing this website’s operations.
Keep three fields in the comparison note:
| Field | Decision to record |
|---|---|
| Preserved information | The fact the product or system actually confirms |
| Acceptable variation | Forms of address and sentence choices that retain the meaning |
| Rule to add | For example, do not imply approval or a response deadline in a receipt message |
When resolving a disagreement, keep more than the selected sentence. Explain why it was chosen and where it would be inappropriate. Add a date and guide version; when the process changes, check whether the old example is still accurate. Reading aloud can reveal awkward phrasing, but cannot by itself verify the underlying process.
Mailchimp’s voice and tone guide prioritises clarity over entertainment in its own writing approach. The two-editor exercise above is an original application developed for this article, not a method copied from that guide or a compulsory standard for every brand.
Connect this exercise to the team’s implementation of the brand communication guide. See brand voice beyond repetition for preserving a promise across contexts, and message architecture for deciding which information takes priority.