Customer reply in our tone
OfficialOfficial · updated Nov 4, 2026 · v1.0.1
Drafts a support reply in your team's tone: answers the question first, owns mistakes, drops jargon, and ends with one clear next step.
Sign up free to add this skill to your pod
You come back here after you sign in, and add it with one click.
When to use it
- A customer email, chat, or ticket needs a reply that sounds like your team
- A draft reply sounds cold, defensive, or too long
What you give it
- The customer's message and thread
- The facts of the answer
- Your tone guide or 3 past replies (optional; defaults included)
What you get
A ready-to-send reply in your tone, plus a list of facts to confirm before sending.
Changelog
- v1.0.1 · Nov 4, 2026 · Example: the input names who replies (Mira, Panlo support) and the next step the team can offer (check the account on the next billing date and email the customer), so the sign-off and the closing promise no longer invent them.
- v1.0.0 · Nov 4, 2026 · First release.
Sources
- Taking the Right Tone With Customers (2026-11-04)
- Writing an Effective Apology Letter to Customers (+ 5 Examples) (2026-11-04)
- Voice and Tone | Mailchimp Content Style Guide (2026-11-04)
- A to Z style guide - GOV.UK content and publishing guidance (2026-11-04)
Related skills
- Support ticket triage Triages incoming tickets into a table with category, S1 to S4 severity, routing, and a first reply for each, sorted by what to answer first.
- FAQ from support tickets Turns a batch of tickets or chats into an FAQ: questions in customer words, ranked by count, short answers, and flags for answers to confirm.
- Incident notice for customers Writes customer-facing incident notices by stage, from investigating to resolved, and a postmortem summary with a plain apology and what changes.
- Brand voice guide and rewrite Extracts a voice guide from 3 to 5 sample texts (traits with do and don't pairs, a word list, mechanics) and rewrites a draft in it.