Capability template for customer support and service
Customer reply drafting
Every customer gets the reply your best person would write. Hand over the customer's message, your tone guide and your approved answers, and get back a draft in your voice where every statement and every promise traces to something you approved. A person on your team reads it, edits it and sends it.
The outcome
A customer writes in, and minutes later the person handling it has a reply ready to read: the answer first, in your company's voice, at the right length for the channel, with each next step dated and owned. Beside it sits a short list of what to confirm, what the draft promises and which of your rules allows each promise.
Nothing in the draft is made up. A question your approved answers do not cover is left unanswered and raised with the right person. A refund, credit or exception the sender cannot grant is never offered. The newest member of the team replies the way your best one does, and that is how a small team gives service that feels ten times its size.
Who starts the work, and when
A support agent, an account manager or the owner starts it when a customer message needs a considered reply: a question, a complaint, a billing problem, a request you have to decline, or bad news you have to deliver. It runs once per message. The same person reads the draft, changes what needs changing and sends it. Where your rules call for a second reader, such as a customer who says they may leave, the draft names that role and waits.
What they supply
- The customer's message, and the earlier thread if there is one.
- What is known and checked about the account: plan, order, charges, anything already promised.
- Your tone guide.
- Your approved answers: the policies, explanations and limits your team may state to customers.
- Who is sending, on which channel, and what that person may grant without asking.
What comes out
- What the customer raised. Every point in the message, numbered. Each question or request is marked as answered, held, declined or for a named role to decide, with its source. Each thing the customer says happened is marked as confirmed or not checkable.
- The draft reply. Written to your tone guide and sized to the channel.
- Before sending. Facts and actions to confirm, each promise with its date, owner and the rule that allows it, what was left out and why, and questions for colleagues.
A good draft answers the first thing the customer asked in its first lines, promises only what the sender can keep, and can be checked against your approved answers in a minute.
An invented example
Illustrative example with invented data. The company, the customer, the people, the charges and every document below are invented. Company T is an invented 25-person company that sells online booking software to independent fitness studios; Studio M is an invented customer. First come the inputs the support agent supplied, in full, then the draft the capability returned.
The inputs
CUSTOMER MESSAGE
Channel: email. Ticket 4471. Received Thursday 5 November 2026, 09:12.
From: Priya, owner, Studio M
Subject: Charged twice AGAIN??
Hi,
I upgraded to the Plus plan on Monday and you've charged my card twice,
$89 each time. This is the second billing problem this year. I want the
extra charge back and frankly a free month for the hassle.
While I have you: can I export class attendance to a spreadsheet? And
when is the waitlist feature coming? You told me "soon" back in the
summer.
If this isn't sorted this week I'll be looking at other options.
Priya
EARLIER THREAD WITH THIS CUSTOMER
3 March 2026. Priya reported a charge taken twice after a card update.
Support corrected it the same day.
14 July 2026. Priya asked when a class waitlist would be available.
15 July 2026. Support (Sam) replied: "It's on our list and coming soon."
ACCOUNT RECORD (checked by Jo, Thursday 5 November 2026, 09:40)
Customer since February 2025.
Plan: Plus, $89 a month, since Monday 2 November 2026. Before that:
Starter.
Charges on 2 November 2026: $89.00 at 10:02 and $89.00 at 10:03, same
card. The second is a duplicate.
Refund: not yet issued.
TONE GUIDE (TG-2, dated 1 September 2026)
1. Write as one person to another. First names. "I" for what I will do,
"we" for the company.
2. Give the answer first.
3. When we got it wrong, apologize once, for the specific thing. Never
"any inconvenience".
4. No exclamation marks. Never "unfortunately" or "as per".
5. Dates as day and date ("Monday 9 November"). Never "soon" or
"shortly".
6. Email: under 180 words. Chat: under 60.
7. Sign off with your first name, then "Company T support".
APPROVED ANSWERS (AA-7, reviewed 20 October 2026, owner: support lead)
A1. Duplicate charge. Confirm it in the account record first. Refund the
duplicate in full. A refund reaches the customer's card in 5 to 7
business days. A support agent may refund up to $200 without asking.
A2. Goodwill credits and free months. Decided by the support lead only.
Support agents do not offer, promise or hint at them. Tell the
customer the request has been passed on and when they will hear.
A3. Features not yet released. Give no date and never say "soon". Say
whether the feature is available today and offer the notify list for
it. Waitlist: not available today; a notify list exists.
A4. Follow-up promises. A support agent may promise a reply within two
business days and must record the promise on the ticket.
A5. Leaving. Any message in which the customer mentions cancelling or
leaving is read by the support lead before the reply goes.
A6. Class schedule export. The class schedule exports to a spreadsheet
file from Settings, then Export.
SENDER AND SETTINGS
Sender: Jo, support agent. Signs as "Jo". Support lead: Ren.
Review period: an approved answer stays current for 90 days after its
review date.
Send day: Thursday 5 November 2026.
Jo's note: "I'll issue the $89 refund right before I send. I haven't
asked Ren about the free month yet."
The output
CUSTOMER REPLY DRAFT: Priya, Studio M, ticket 4471
Status: Draft for Jo. Not sent. Review needed first: Ren, support lead,
under A5, because Priya writes that she will "be looking at other
options".
Channel: email. Situation: billing issue, with a complaint, two product
questions and a request above the sender's limit. Tone: TG-2; rules 2,
3 and 5 lead (the answer first, one specific apology, day-and-date
dates).
Sources: TG-2, 1 September 2026; AA-7, reviewed 20 October 2026, inside
the 90-day review period; account facts checked by Jo, Thursday
5 November 2026.
WHAT THE CUSTOMER RAISED
1. "I upgraded to the Plus plan on Monday." Confirmed by the account
record: Plus since Monday 2 November 2026.
2. "You've charged my card twice, $89 each time." Confirmed by the
account record: $89.00 at 10:02 and at 10:03 on 2 November, the
second a duplicate.
3. "This is the second billing problem this year." Confirmed by the
thread: a charge taken twice on 3 March 2026, corrected the same day.
4. "I want the extra charge back." Answered from A1: the duplicate is
refunded in full, and $89 is within Jo's $200 limit. The refund is
not yet issued.
5. "Frankly a free month for the hassle." For the support lead to
decide (A2). Nothing is offered or hinted at.
6. "Can I export class attendance to a spreadsheet?" Held: no approved
answer covers attendance. A6 covers the class schedule only and is
not stretched to fit.
7. "When is the waitlist feature coming?" Answered from A3: not
available today, no date, notify list offered.
8. "You told me 'soon' back in the summer." Confirmed by the thread:
Sam's reply of 15 July 2026 used that word.
9. "If this isn't sorted this week I'll be looking at other options."
Noted: the support lead reads first (A5). The reply does not respond
to it.
DRAFT REPLY
Subject: Your duplicate $89 charge is refunded
Hi Priya,
I have refunded the duplicate $89 charge from Monday 2 November in
full. It will reach your card in 5 to 7 business days. I'm sorry we
charged you twice, and you are right that this is the second billing
problem you have had with us this year.
I have passed your request for a free month to Ren, our support lead,
who decides these. You will hear from me by Monday 9 November.
Your two questions:
- Attendance export: I am confirming this and will tell you by Monday
9 November.
- Waitlist: it is not available today, and I can't give you a date. In
July we told you it was coming, without a date. I can add you to the
notify list for it. Would you like that?
Jo
Company T support
BEFORE SENDING
Do first:
- Issue the $89 refund. The draft says "I have refunded" and the
account record says the refund is not yet issued.
- Pass the free-month request to Ren. The draft says "I have passed
your request" and Jo's note says Ren has not been asked.
If either is not done, do not send this wording.
Review first: Ren, support lead, reads the draft before it goes (A5).
Confirm: "Monday 9 November" is two business days counted from the
send day, Thursday 5 November. If Ren's reading moves the reply to
Friday 6 November, both places become Tuesday 10 November. Check the
support calendar for a company holiday in the count.
Promises in this draft:
- A reply on the free month by Monday 9 November, owned by Jo. Allowed
by A2 (say when she will hear) and A4 (two business days). It is a
promise of a reply, not of Ren's decision. Record it on ticket 4471.
- A reply on attendance export by Monday 9 November, owned by Jo.
Allowed by A4. Record it on ticket 4471.
- Adding Priya to the waitlist notify list if she says yes, owned by
Jo. Allowed by A3.
- The refund reaching the card in 5 to 7 business days is not Jo's to
control, so it is not listed as a promise; it stays in A1's wording.
Not said, and why:
- No free month is offered or hinted at (A2).
- Nothing says attendance can or cannot be exported, and the schedule
export is not offered in its place. No approved answer covers
attendance, and a reader could take the schedule steps as a yes.
- No date for the waitlist (A3), and the word Sam used in July is not
repeated (A3; TG-2 rule 5).
- No judgement on the July reply. The thread shows what was said; no
approved answer says how to describe it.
- Nothing about her looking at other options, and nothing about "this
week". The refund is issued this week and reaches her card later.
Questions for Ren:
- Does Priya get a free month? Can you decide in time for Jo's reply on
Monday 9 November? If not, Jo's reply that day is an update.
- Can class attendance be exported? If it can, who writes the approved
answer?
- Do you want the reply to say anything more about the July reply, or
about her looking at other options?
Tone guide check: rule 1, first names, "I" and "we": applied. Rule 2:
the refund opens the reply. Rule 3: one apology, for charging twice.
Rule 4: no exclamation marks, no barred words. Rule 5: every date as
day and date, no barred words. Rule 6: 135 words from the greeting to
the sign-off, not counting the subject line, against a limit of 180.
Rule 7: signed "Jo", then "Company T support".
After sending: Jo records the promises on ticket 4471 (A4) and writes
to Priya by Monday 9 November on the free month and attendance export.
Jo adds her to the notify list only if she says yes.
Prepared for Jo. Nothing has been sent, refunded or recorded by the
assistant.
Not completed, and what is needed: whether attendance can be exported
(an approved answer from the support lead); the free month (Ren's
decision).
Where it fits
- Customer support and service, for the everyday queue and the hard message alike.
- Customer success and account management, where one careless promise costs a renewal.
- Software technology, where billing, bugs and feature questions arrive in the same message.
- E-commerce and retail, for orders, returns and delivery problems under a published policy.
- Professional services, where the reply comes from the person who holds the relationship.
- Hospitality, where a guest's complaint deserves a personal answer the same day.
- Established businesses, which already have the policies and want every reply to follow them.
What has to change for your company
Put your approved answers in one place, each with a review date and an owner; they are the only things a draft may state. Write down your tone guide, even one page of it. Set the limits: what an agent may refund or promise without asking, and how far ahead they may commit to a reply. Name the situations a second person reads before a reply goes, and who that person is. Decide which customer details the AI assistant may be shown, on ChatGPT, Claude, Copilot or Gemini. Your organization keeps control of what is said in its name.
What has been checked
Fully Powered AI wrote this capability template. It was editorially reviewed on 9 November 2026. It was tried on its invented example in Claude on 9 November 2026, and the record of those runs is published with the template. It has not yet been tested in a client environment. It has not yet been tested as a packaged version in ChatGPT, Claude, Copilot or Gemini.
Testing in your environment means running it on past messages your team has already answered, plus hard cases written in advance, each with its expected behavior: a question no approved answer covers, a request above the sender's limit, a customer who mentions leaving. Pilot acceptance-test preparation builds that test set, and What we test before we call an AI workflow ready shows the record.
The full capability template
Everything above is the outline. The complete capability template is the working version: the roles, the inputs, the procedure, the exceptions and stop conditions, the output format, the reviewer checklist, the acceptance tests, the instructions for an AI assistant and what to customize for your company. It comes with a download and the link to its folder in Fully Powered’s public repository.
Free with an account. Sign in by email: no password and no card.
Next step
Bring a real piece of this work to a call. We’ll walk through what it takes to fit this capability to your rules, prove it on your work and put it in the hands of the roles that own it.