“Confident, warm, and premium” sounds like a voice guide until someone has to answer a late delivery complaint or explain an unfamiliar service. The adjectives do not tell a teammate which fact comes first, which terms need explaining, or what a claim may promise. Build the guide from the conversations the business actually has.
The UK Department for Education's plain-language guidance recommends using the language users use and explaining technical terms when they are needed. Its context is public service content, but the method transfers: collect the words customers use before writing a rule for how the brand speaks. A voice can be distinctive while remaining precise.
Start with ten real questions
Gather a small sample from enquiries, sales calls, reviews, support tickets, and search within the site. Remove personal information. Group the questions by task: deciding if the offer fits, comparing options, ordering, and getting help. For each group, write the answer a customer needs before adding any brand phrasing.
Then create a matrix that a writer can use in a minute:
| Situation | Answer first | Voice rule | Avoid |
|---|---|---|---|
| “Is this service for my business?” | Eligibility and scope | Direct, specific, one example | “We serve everyone” |
| “Why does it cost more?” | What is included and why it matters | Calm, concrete, no apology for the price | Unverifiable “best quality” |
| “My order is late” | Status and next update | Accountable and helpful | A cheerful campaign slogan |
| “What happens after I enquire?” | Next step and timing | Plain and reassuring | Internal process jargon |
The examples are illustrative. Replace them with the company's actual terms, policies, and customer language. This is a working tool, not a list of approved adjectives.
Define what stays consistent and what can change
Write two or three durable rules: how the brand names the customer, how it explains a benefit, and how it handles uncertainty. Then show how tone changes with the situation. A social launch line may be energetic; a support response needs to be exact. The underlying promise should remain recognisable in both.
Use paired examples. Show an existing sentence and a better version, then explain the decision. “Our innovative ecosystem transforms your workflow” might become “See the next booking, assign a technician, and tell the customer when to expect them” if those are verified product capabilities. The second sentence is useful because it lets a reader picture an action; it should not be used if the product cannot do those things. Government content guidance on tone also separates clear, direct writing from a faceless or needlessly formal style. The brand's own personality still needs to come from its customers and offer.
Test the guide with an unfamiliar writer
Give a teammate a fresh customer question and the voice guide. Ask them to draft a social reply, an email subject and first paragraph, and a support answer. If they all sound like the same company and answer the question accurately, the rules are usable. If the guide works only when its author explains it aloud, add examples at the decision point where the writer got stuck.
Assign an owner to review new examples when products or policies change. Keep dated examples and a short list of words the business must define, such as a technical service term. ARCHV's identity and campaign work can include this verbal layer so its visuals and content carry one understandable promise. For the separate task of removing technical-founder jargon from a SaaS page, use the more focused page guide; this article is about an operating voice across channels.