Write a client tone guide a virtual assistant can actually use

Start from messages the client already sends

A tone guide works when it starts from messages the client already sends rather than from adjectives such as friendly or professional. Collect ten recent replies across approvals, delays, and corrections, and remove customer names before sharing them. Read the samples together and note the greetings, sentence length, and closing lines the client repeats. Those habits give the assistant a real pattern to copy instead of a vague instruction.

Ask the client which samples still sound right and which ones they would rewrite today. A reply sent under pressure may not represent the voice the client wants for routine work. Mark the approved samples as the reference set and keep the rejected ones beside them with a short reason. That contrast teaches judgment better than a list of banned phrases.

Separate voice from rules

Voice covers greetings, warmth, pacing, and how directly the client states a problem. Rules cover commitments, pricing, refunds, legal language, and anything that needs approval before it reaches a customer. Write the two parts on separate pages so the assistant knows what to imitate and what to obey. Mixing them lets a stylistic choice look like permission to make a promise.

Keep a short list of phrases the client never wants to see, such as overly casual slang or absolute guarantees. Add the reason beside each phrase so the assistant can apply the principle to a new situation. A banned word without a reason becomes a guessing game when the next message uses different wording. The reason is the part that transfers to unseen work.

Write examples for the hard cases

Write model replies for a late delivery, a billing mistake, and a request the client must decline. Use the client's actual wording where possible and label the parts the assistant may change. Show how to apologize without admitting fault the client has not confirmed or investigated. The examples should demonstrate restraint while the facts remain incomplete.

Add one example where the correct action is to wait for approval instead of replying. Explain what the assistant should send in the meantime and who owns the next update. A tone guide that only shows successful replies will push the assistant to answer everything. The waiting example protects the client from a confident but unauthorized promise.

Set escalation and approval language

Give the assistant standard sentences for acknowledging a request, naming the owner, and setting the next update time. These sentences should work across clients with minimal edits. Include a version for a request that needs a specialist and a version for work outside the agreed scope. The assistant can then hold the relationship without inventing a commitment.

State which words require approval, such as compensation, legal, medical, or contractual language. Explain what to do when a customer uses those words first, including who reads the message before a reply goes out. The guide should make the pause feel routine rather than personal. Clear approval language reduces risky replies and unnecessary escalations at the same time.

Test the guide against real drafts

Ask the assistant to rewrite five real messages using the guide and compare the drafts with the approved samples. Score the greeting, the substance, the commitment language, and the close on a simple sheet. Review the differences together and note whether the guide was unclear or the assistant missed a rule. A test that only checks tone will miss the commitments that carry risk.

Run the test again after two weeks of live work and include messages the guide did not anticipate. Add the strongest new example to the guide and remove any rule that produced awkward replies. The goal is a document that improves with use rather than one that grows without limits. A short guide the team actually opens beats a comprehensive manual nobody reads.

Use the guide during onboarding

Give the tone guide to a new assistant before the first live reply and ask them to mark the sections that need an example. Their questions reveal where the guide assumes knowledge the assistant does not have. Add the missing example before the first client message goes out. Onboarding is the cheapest time to find a gap in the guide.

Pair the new assistant with one reviewer for the first week and review every outbound message against the guide. Keep the corrections in a shared note so the whole team learns from the same fixes. After the first week, move to a sample of messages and keep the note open. The guide and the review should reinforce each other rather than compete.

Keep the guide current

Review the tone guide when the client changes a product, a policy, or a customer segment. Ask the client to mark any sample that no longer represents the current voice. Update the version date and tell the assistant which examples changed. A guide that drifts from the client's current messages will teach the wrong habits.

Keep the guide in the same workspace as the task instructions so the assistant does not need a separate search. Link each rule to the approved sample that demonstrates it. Give one person responsibility for the next review and put the date at the top. The maintenance owner is what keeps a useful guide from becoming stale.

Review the guide after a client complaint or a message that needed a manager to rewrite it. Ask what the guide missed and whether the assistant had a rule that pointed the wrong way. Add the case as a short example rather than a long explanation. The guide earns trust when it changes after a real problem instead of only after a scheduled review.