Your Customer Service Voice and Rules, Written Once
10 min read
A customer service tone of voice that lives only in your head can't be handed to AI or to a new hire. This lesson gets yours onto one page, along with the rules a reply must follow.
Ask any assistant for a customer reply with no background and you get the same thing every business gets: "We sincerely apologize for any inconvenience this may have caused." Customers have read that sentence a thousand times. It tells them a template is talking.
The fix takes about twenty minutes, once. You write a support brief: a single page with how you sound, what your policies are, and what no reply may promise. Every prompt from here on starts by pasting it in.
The four parts of a support brief
1. Who you are, in two lines. "We're a six-person HVAC company in Windsor. Most customers are homeowners, often stressed because something broke."
2. How you sound. Skip adjectives like "friendly and professional". They describe every business on earth. Give examples instead: three real replies you were happy with, pasted in full. Then add a short do and don't list. Do: use first names, short sentences, say what happens next. Don't: say "inconvenience", use exclamation marks, write more than six sentences.
3. The policies that come up. Returns, refunds, cancellations, deposits, warranty, delivery times, service area, hours. Plain words, real numbers. "Refunds within 14 days with receipt. After that, store credit, manager can approve exceptions."
4. The never list. What a reply must not do without you: promise a refund, quote a price not on the list, give a delivery date, admit legal fault, diagnose a problem sight unseen. This part protects you on the day you're tired and approve a draft too fast.
Let AI interview you for it
Staring at a blank page is where this task dies. Have the assistant ask the questions:
I run a [TYPE OF BUSINESS] and I want a one-page customer
support brief that I can paste in front of future prompts.
Interview me. Ask one question at a time, wait for my answer,
and keep going until you can write these four sections:
1. Who we are and who our customers are
2. How we sound (I will paste three real replies I liked)
3. The policies customers ask about, with real numbers
4. Things a reply must not promise without my approval
When you have enough, write the brief in plain language,
under 400 words. If I gave a vague answer, ask again rather
than filling the gap yourself.Answer out loud with voice typing if that's faster. Fifteen questions later you have a draft. Read it as if you were a new employee on day one: could you answer a customer from this page alone? Fix what's missing.
Where to keep it so you stop pasting
Pasting the brief into every chat works, and it gets old by Thursday. Free options that remember it for you, as of September 2026:
| Where | What it does | Cost |
|---|---|---|
| A pinned note or Google Doc | Copy and paste at the start of a chat | $0 |
| Claude Projects | Keeps the brief as project knowledge for every chat in that project | Free plan includes a small number of projects |
| ChatGPT custom instructions or a project | Applies your standing context to new chats | Available on the free plan, limits vary |
| A Vexlo support skill | A full instruction file with a setup interview built in | $0 |
One warning. Custom GPTs used to be the standard advice for this. OpenAI has stopped letting personal accounts create new ones and has announced their retirement, so don't build your support setup on one. A plain document you can paste anywhere outlives every product change.
If you want the structured version, install the Customer Support Autopilot. Its setup interview collects the same four parts and then drafts against them. The course AI Skills for Small Business walks through installation in about five minutes.
Test it on a real message
Take a Pile 2 message from the last lesson and run:
Here is my support brief:
[PASTE BRIEF]
Draft a reply to the customer message below. Follow the
brief's voice and policies. Use only facts from the brief
and from my notes. If something needed is missing, stop and
list what you need instead of guessing.
My notes on this case: [WHAT HAPPENED, WHAT YOU DECIDED]
Customer message: [PASTE, WITH PERSONAL DETAILS REMOVED]Compare the draft with what you'd have written. If it sounds stiff, add one more example reply to the brief. If it promised something, add a line to the never list. Two or three rounds and the drafts start needing only light edits.
For ten ready-made prompts covering delays, refunds and angry emails, see 10 AI Prompts for Customer Service Replies. Each one works better with your brief pasted above it.
Where this breaks
A brief goes stale. Prices change in March, the return window changes in June, and the brief still says what was true in January. Put a recurring reminder on the first Monday of each quarter: reread the brief, fix what changed. It's five minutes, and it's the difference between a helpful draft and a wrong one sent with confidence.
Try it now
Run the interview prompt and save the result where your whole team can find it. Then test it on two real messages. Keep the brief open in a tab for the rest of this course, because every later prompt begins with it.