Start from real client messages
Collect twenty recent client messages before writing any tone rule. Choose a mix of routine updates, scheduling notes, problem reports, and replies to complaints. Remove names and account details, then mark the passages that sound right for the client. The examples show the voice the business actually uses, not the voice a style guide claims it uses. Keep the sample small enough that the client can review it in one sitting.
Ask the client which two messages they would send again unchanged. Ask which one made them wince and why. Write the reason beside the message instead of a vague label like friendly or professional. Those reasons become the first entries in the guide and give a new assistant something concrete to copy. Store the approved examples where the assistant can find them during a shift.
Define the default voice in one page
Write the default voice in plain terms that a reviewer can check. State whether the team uses contractions, first names, exclamation points, and short paragraphs. Give one greeting and one sign-off rather than a menu of options. A short default reduces the chance that a new assistant invents a tone the client never approved. Put the page at the top of the role's writing folder so it is easy to reopen.
Keep the page to the choices that appear every day. Cover how to open a message, how to deliver a routine update, and how to close a request. Leave rare situations for the examples section. A guide that tries to describe every emotion becomes too abstract for anyone to apply under deadline. Review the page after the first ten live messages and remove anything that caused confusion.
Show the line between warm and informal
Warmth usually comes from naming the person and the next step. Informality comes from slang, jokes, and promises the team cannot keep. Put two versions of the same reply side by side and mark which one the client approved. The contrast teaches judgment faster than a list of banned words. Ask the client to mark any phrase that would feel wrong from a new person.
Include phrases that are acceptable in chat but wrong in email. Include phrases that sound cold even when the facts are correct. A new assistant needs to see the boundary in the client's own language. Review the examples with the client so the guide reflects a real decision rather than one manager's preference. Update the examples when the client changes a greeting or a sign-off.
Write replacement phrasing for hard moments
Draft approved wording for a delay, a mistake, a missed deadline, and a request the team must decline. Each note should say what happened, what happens next, and when the client will hear again. Avoid apologies that promise a fix the team has not approved. The assistant should not have to improvise during the most sensitive exchange of the week. Give the assistant permission to ask for a different template when the facts do not fit.
Keep the replacement lines short enough to adapt without sounding copied. Add a blank for the specific date, owner, or document. Tell the assistant which details must never be omitted. A good template gives structure to an honest message and leaves the facts in the hands of the person who knows them. Review the hard-moment templates with the client before the first one is used.
Set channel-specific rules
Email, chat, and call notes carry different expectations. Email can hold a complete update, while chat usually needs the decision first and the detail second. Call notes need a clear owner and a next action. Write one rule for each channel the assistant actually uses, and name the channel where sensitive news must travel. Write down which channel the client checks least often so the assistant does not send urgent news there.
Set a response window for each channel and state what counts as an acknowledgement. A quick reply that says the request was received is not the same as an answer. Tell the assistant when to send the holding note and when to wait for the full response. The client should never have to guess whether a message was seen. Put the response window in the same document as the channel rules.
Review tone during the first week
Sample three outgoing messages each day during the first week. Review them before they are sent, not after the client replies. Mark one thing that worked and one thing to change. Keep the notes short so the review does not become a second job for the manager. Keep the reviewed messages in a folder the client can inspect. Review the folder at the end of the week.
Do not correct only grammar. Ask whether the message gave the client a clear next step and an honest expectation. If the same correction appears twice, update the guide instead of coaching the same point again. The review is evidence that the written standard is reaching the work. Ask the assistant which message felt hardest to write and why. Use the answer to revise one example.
Update the guide from corrections
Give the guide a named owner and a version date. Add a new example only when a real message required a decision that the current page did not cover. Remove examples that the client no longer endorses. A guide that grows without review becomes a pile of contradictory advice. Put the version date at the top so nobody works from an old copy.
Tell the assistant how to suggest a change. A short note with the message, the problem, and the proposed wording is enough. The owner decides whether the change applies to one client or the whole team. Record the decision so the next assistant does not reopen the same question. Review suggestions at the weekly check-in instead of changing the guide mid-task.
Hand the guide to reviewers and clients
Share the guide with anyone who reviews the assistant's messages. A reviewer who has not read it will enforce a different standard and confuse the new hire. Put the guide beside the task instructions, not in a folder nobody opens. Add the link to the first-week checklist. Give every reviewer the same link so the standard does not fork. Replace old copies when the guide changes.
Ask the client to confirm the guide at the start of the engagement and again after a major change. Keep their approval with the version they reviewed. When the client's tone shifts, update the examples before the next batch of messages goes out. The guide is working when a new assistant can send a routine reply without asking which voice to use. Record the client's confirmation with the version it applies to.
Continue building the workflow
Related support: onboarding operations support, contact us. The U.S. Small Business Administration — Hire and manage employees guidance on hiring, managing, and communicating expectations with employees.
Related reading
A quality sampling plan for a virtual assistant's first month
A first-month quality sampling plan that sizes reviews by risk, scores with a short rubric, and turns repeat defects into process fixes.
An escalation matrix a virtual assistant can actually use
A usable escalation matrix with observable triggers, named owners, response windows, and a test plan for the first month.
Write a task documentation standard before the VA starts
A documentation standard that gives a virtual assistant the inputs, decisions, examples, and review rules needed to finish work without guessing.
