Describe the voice with practical choices
Specify whether replies should be brief or detailed, conversational or formal, and which expressions the business avoids. Use examples from authorised business writing where available. Do not rely on a list of vague adjectives such as friendly and professional. Explain how the voice changes when a reviewer raises a problem rather than leaving praise. Keep the brief focused on public communication. A writing preference should not instruct the draft to invent personal familiarity, claim a remembered visit or add details that the team has not confirmed.
Use a simple positive-review example
For a fictional review saying the team explained the process clearly, a possible draft is: "Thanks for the feedback. We are glad the explanation was useful." The example acknowledges the stated point without inventing an outcome or repeating the whole review. Treat it as a demonstration of tone, not a template to paste under every comment. The real reviewer and context may call for different wording. Avoid adding a sales pitch or a new promise merely because the review is positive.
Acknowledge mixed feedback specifically
A fictional review might praise the service while saying the callback took longer than expected. A draft could say: "Thanks for the feedback on the service and callback. Please contact our office so the team can look into the delay." Use that wording only where the contact route and follow-up process are approved. Do not claim the cause is known or that the issue has been fixed. The tone brief should encourage attention to both parts of the comment rather than selecting only the praise.
Keep negative-review drafts factual
For a fictional comment saying the reviewer could not reach the team, a possible draft is: "Please contact our office through the details on our website so we can look into your enquiry." The business may choose different wording after reviewing the actual context. Do not add public account details, argue from an assumed customer match or promise a remedy the owner has not approved. The tone brief is about how to write; it does not determine what happened or which business decision should follow.
Define what the examples must not become
Examples should not be presented as real customer stories or proof of results. Avoid claiming that a certain phrase will remove a review, improve a rating or influence a platform ranking. Keep approved contact details and operational facts in a maintained source rather than embedding stale information in many templates. Do not let a tone rule override a factual correction. If the available context does not support a specific response, send the draft to the owner for clarification instead of forcing it into the nearest example.
Test the brief with a human reviewer
Ask a reviewer to compare drafts for fictional positive, mixed, vague and negative comments. Check whether the wording fits the brief while addressing only supported facts. Include a draft with an invented promise to confirm that it is rejected, even if its tone sounds appropriate. Record recurring edits and refine the brief. Keep final publication approval separate from approval of the writing guide itself. A useful tone brief reduces avoidable rewriting while preserving the judgement needed for each individual public response.