Summary
Read the whole thread before you type, including what the customer already tried.
Answer the question in your first line, before the greeting and the apology.
Give one next step, with who does it and by when.
Write it so it can’t be misread, with numbered steps, one question per reply, and the exact help article section.
Close the loop, and log every reply you’ve typed three times this week.
A good support ticket reply answers the customer’s question in its first line and ends with one next step.
The greeting, the apology, and the policy come second, or not at all.
Templates give that shape to the replies you send every day. The replies you send three times a week need a help center article instead, where customers and an AI agent find the answer before they write in.
Jortt, a Dutch accounting platform, resolves about 92% of roughly 30,000 monthly inquiries without a person. By that count, about 2,400 a month, the 8% of 30,000, still need a person.
How do you answer a support ticket?
Read the whole thread, answer the question in your first line, give one next step with a time, write it so it can’t be misread, and close the loop.
A customer reads a reply in one order, asking “Is my problem solved, and what happens next?”
To respond to support tickets, follow that order.
1. Read the whole thread first
Before you type, read every message in the ticket. Then check your inbox or ticketing system for earlier tickets from the same customer.
You’re looking for three things:
what they asked, in their own words
what they’ve already tried
any earlier ticket about the same problem
If the ticket came from an AI agent’s handover, read the chat that came with it first. In Wonderchat, a handover arrives as a ticket with the full conversation attached, so nobody asks the customer to start again.
Reading first means you never ask for something the customer already sent, which costs a whole extra round of email.
2. Answer the question in your first line
Put the answer in the first sentence. The greeting and the apology can follow, or be left out.
For example, compare two replies to the same ticket about exports.
Before | After |
|---|---|
Hi Sam, thanks so much for reaching out, and sorry for the trouble. Exports work a little differently depending on your account settings and the size of the file. Under our fair use terms, very large files are split. You can export up to 1,000 rows at a time. | Hi Sam, exports stop at 1,000 rows at a time. To get the rest, filter by month and export each month separately. I’ll check in tomorrow to make sure you have everything. |
The second reply answers first. Then it gives the next step and says when you’ll check back.
A reply that gets no follow-up puts the answer first, then one next step, then who does what next and when.
All 30 templates follow that shape.
3. Give one next step, with a time
End with one next step and who takes it. “I’ll update you by 3 p.m. on Thursday” tells the customer when to stop checking their inbox.
“We’ll look into it” tells them nothing, so they write back to ask.
Pick a time you can keep, even if it’s later than you’d like. A missed promise turns one ticket into two.
If the next step belongs to the customer, say exactly what to send or click.
4. Write it so it can’t be misread
A correct reply can still be challenging to act on. Four habits fix that.
Number the steps for anything that takes more than two clicks.
Ask one question per reply when you need information. Number them if you need several.
Link the exact section of the help article that answers it.
Never send a link on its own. Answer in two lines, then link the details.
5. Close the loop and log the repeats
Handling a support ticket ends when the fix is confirmed. Say so, set the ticket’s status and close it. If the customer goes quiet, send one check-in before closing (template 29).
Before the next ticket, check whether this is the third time this week you’ve typed this answer.
If it is, add it to a list. Those are the replies you can stop typing altogether.
Why do customers write back after a reply?
Customers write back when they still can’t act on the reply. Each of these four causes has a fix you can make before you press send.
Cause | What the customer reads | The fix |
|---|---|---|
No next step | “We’ll look into it.” | Name who does what, and by when. |
Two questions in one reply | Two asks in one paragraph, so they answer the easier one | One question per reply, or number them. |
Policy before the answer | Three lines of terms before the word “yes” | Answer first, then the policy, if it’s still needed. |
A link instead of an answer | “Please see this article.” | Answer in two lines, then link the exact section. |
The last one matters more than it looks.
In a Gartner survey of 5,728 customers, run in December 2023, 73% used self-service at some point while getting help. Only 14% of customer service and support issues were fully resolved there.
A bare link sends the customer back to the place that didn’t solve it the first time.
30 support ticket response examples and canned responses
The 30 support ticket response templates are canned response examples you can copy. The shape stays the same, and you fill in the details.
Replace everything in {braces}, and fill the braces last, so a half-filled template never goes out. Each customer service reply template keeps the answer in the first line, with notes on when to send it and when not to.
Six questions point a ticket to its templates, and the rest take a first reply or a how-to answer.
First reply and acknowledgment templates
1. Answer in the first reply
Hi {name},
Yes, you can {do the thing}. Open {section} in {Settings} and click {button}. It takes effect right away.
If it doesn’t show up for you, send me a screenshot, and I’ll check your account.
Use it when: you can solve it now.
Don’t use it when: you need to investigate first. Send template 2 instead.
2. Received, answer coming
Hi {name},
Thanks for the details on {issue}. I’m checking it with {team} now and will write back by {day, time}, even if it’s only an update.
Use it when: the ticket needs investigation.
Don’t use it when: you can’t keep that time. Choose a later one you can keep.
3. Out of hours
Hi {name},
Your message reached us outside our support hours. Someone will reply by {time} on {day}. If your question is about {common topic}, this article has the answer: {link}.
Use it when: nobody is online.
Don’t use it when: the issue is urgent and someone is on call. Wake them instead.
4. Duplicate ticket merged
Hi {name},
You wrote to us twice about {issue}, so I’ve combined both messages into this ticket. Every reply will come here, so you won’t miss anything.
Use it when: the same person sends the same problem twice.
Don’t use it when: the second message raises a new problem. Keep that one separate.
Templates for asking for more information
5. Steps to reproduce
Hi {name},
I want to fix this, and I can’t make it happen on my side yet. Could you answer three quick questions?
What did you click just before the error?
What does the error message say, word for word?
Which browser and device are you using?
Use it when: you can’t reproduce a bug.
Don’t use it when: your own logs can tell you. Check them first.
6. Account or order details
Hi {name},
I can’t find an account under {email}. Which email address or workspace name did you sign up with?
Please don’t send your password. I’ll never need it.
Use it when: you can’t find the customer.
Don’t use it when: you’d be asking for passwords or full card numbers. Never ask for those.
7. Screenshot or screen recording
Hi {name},
A screenshot of the page where this happens would help me find it fast. If something moves or flickers, a short screen recording works even better.
Use it when: the problem is visual.
Don’t use it when: the customer has already sent a lot. Ask for one thing only.
How-to question templates
8. Answer plus the exact help article
Hi {name},
You can {do it} from {location}: {two-line answer}.
This article has the full steps with screenshots: {link to the exact section}.
Use it when: a current article covers it.
Don’t use it when: the article is out of date. Fix the article first.
9. Answer when the help center doesn’t cover it
Hi {name},
To {do it}, {steps}.
This isn’t in our help center yet, so thanks for asking. We’re adding it this week.
Use it when: no article exists.
Don’t use it when: you’ve typed this three times already. Publish the article today.
10. Walkthrough in numbered steps
Hi {name},
To set up {feature}, follow these steps:
Open {page}.
Click {button}.
Choose {option} and save.
You should now see {result}. If you don’t, tell me which step looked different.
Use it when: the task takes more than two clicks.
Don’t use it when: a short GIF in your help center would show it better.
11. It’s on another plan
Hi {name},
{Feature} is part of the {plan} plan, and your account is on {current plan}. If you’d like to try it, {how to upgrade or start a trial}. Everything you use today keeps working either way.
Use it when: the feature exists, just not on their plan.
Don’t use it when: you’re not sure which plan includes it. Check before you reply.
Bug and outage templates
12. Bug confirmed, with a workaround
Hi {name},
You’re right, this is a bug on our side, and our team is fixing it. Until the fix ships, you can {workaround}. I’ll write to you as soon as it’s live.
Use it when: a safe workaround exists.
Don’t use it when: the workaround risks losing data.
13. Bug confirmed, no fix date yet
Hi {name},
I’ve confirmed the bug and passed it to our engineers with your example. I don’t have a fix date yet, and I’d rather not guess one. I’ll update you by {date} either way.
Use it when: the fix isn’t scheduled.
Don’t use it when: you’re tempted to invent a date. Customers remember dates.
14. Outage acknowledged
Hi {name},
{Feature} isn’t working for some customers right now, and our team is on it. You can follow live updates on our status page: {link}. We’ll post there the moment it’s fixed.
Use it when: many customers are affected.
Don’t use it when: only one account has the problem. Treat that as a bug.
15. Bug fixed, please check
Hi {name},
The fix for {bug} went live today. Could you try {action} again and let me know if it works? If it doesn’t, reply here and I’ll pick it up right away.
Use it when: the fix has shipped.
Don’t use it when: you haven’t checked it on their account yet.
Billing, refund, and cancellation templates
16. Refund approved
Hi {name},
I’ve refunded {amount} to the card ending in {last four digits}. Banks usually take {number} business days to show it. Your account stays active until {date}.
Use it when: your policy allows the refund.
Don’t use it when: someone else has to approve it. Send template 2 first.
17. Refund declined, with an alternative
Hi {name},
I can’t refund this charge, because {plain reason from your policy}. What I can do is {alternative, such as pausing the account or switching to monthly billing}. Would that help?
Use it when: your policy says no.
Don’t use it when: the charge was your mistake. That’s template 24.
18. Cancellation confirmed
Hi {name},
Your subscription is canceled, and you won’t be charged again. You can keep using {product} until {date}. To keep a copy of your data, export it from {location} before then.
Use it when: they asked you to cancel.
Don’t use it when: they only asked how canceling works. Answer the question instead.
19. Invoice or receipt
Hi {name},
Your invoice for {month} is attached. You can download every past invoice from {Invoices} under {Billing} whenever you need one.
Use it when: they need a document today.
Don’t use it when: you send this every week. Publish the steps in your help center.
Templates for saying no
20. Feature request logged
Hi {name},
Thanks for suggesting {feature}. I’ve added your use case to our request list, which the product team reviews every {week or month}. I can’t promise if or when it will ship, but I’ll tell you if it does.
Use it when: the request is fair and still open.
Don’t use it when: your reply could sound like a promise of a date.
21. Feature declined
Hi {name},
We won’t be building {feature}, because {honest reason}. The closest option today is {workaround}, which covers {what it covers}.
Use it when: the decision is final.
Don’t use it when: you aren’t sure. Send template 20 instead.
22. Out of scope
Hi {name},
This one is outside what {product} does. {Other tool or team} handles {task}, and you can reach their support team at {link}. If it touches {product} too, send me the details and I’ll check our side.
Use it when: it really isn’t your product’s job.
Don’t use it when: it might be a bug in disguise. Rule that out first.
Templates for upset customers and your own mistakes
23. Frustrated customer
Hi {name},
You’ve lost {time or work} because of {problem}, and fixing it is on us. So far I’ve {action}. Next, {next step} by {time}.
Use it when: they’re angry about a real problem you’ve found.
Don’t use it when: you haven’t found the problem yet. Ask first, with template 5.
24. When the mistake is yours
Hi {name},
We charged you twice for {month}, and that was our error. I’ve refunded the extra {amount} today, and we’ve {fixed the cause}. Sorry for the trouble this caused.
Use it when: the error was yours.
Don’t use it when: you’re apologizing for a policy you’re keeping.
25. Sorry for the slow reply
Hi {name},
Sorry for the slow reply. Here’s the answer: {answer}. {One next step.}
Use it when: you were late.
Don’t use it when: you’d promise never to be late again.
26. They say they’ll leave
Hi {name},
I understand {product} isn’t working for you right now because of {reason}. Before you decide, {one concrete fix or option}. If you’d still like to cancel, reply “cancel” and I’ll do it today.
Use it when: a customer says they’re leaving.
Don’t use it when: you’d offer a discount you’re not allowed to give.
Escalation, follow-up, and closing templates
A good handover means the customer never explains the problem twice.
The glossary entry on escalation and handoff lists what the person receiving it needs.
27. Handing over to a teammate
Hi {name},
{Teammate} looks after {area}, so I’ve passed your ticket to them with everything you’ve told me. You won’t need to explain it again. Expect their reply by {time}.
Use it when: someone else owns the problem.
Don’t use it when: they’d have to start over. Pass the whole thread.
28. Status update while waiting
Hi {name},
There’s no fix for {issue} yet, and it’s still at the top of {team}’s list. I’ll update you again by {date}.
Use it when: it’s taking longer than you said.
Don’t use it when: you’d send it with no date. Always give the next one.
29. Checking in before closing
Hi {name},
I haven’t heard back, so I hope {issue} is fixed. If it isn’t, reply to this email and the ticket reopens. Otherwise I’ll close it on {date}.
Use it when: the customer went quiet after your answer.
Don’t use it when: you know the issue isn’t solved.
30. Closing and asking for feedback
Hi {name},
Glad {issue} is fixed. I’m closing this ticket now. If you have a minute, how did we do? {one-click rating link}
Use it when: the customer confirmed it’s solved.
Don’t use it when: they’re still upset. Fix that first.
Which replies should you type, template, or publish?
Not every reply deserves the same effort. Some need your judgment every time, some only need new details in a familiar shape, and some have the same answer for every customer.
Situation | How to send it | Why |
|---|---|---|
First reply and acknowledgment | Template | Only the name, the issue, and the time change. |
Asking for more information | Template | The questions repeat, and only the details change. |
How-to questions | Publish | Every customer gets the same answer, so one help center article can answer it before anyone writes in. |
Bugs | Template | The shape stays the same, and only the workaround and the date change. |
Outages | Status page | One post reaches every affected customer at once. |
Billing policy and invoices | Publish | The policy is the same for everyone. |
Refund decisions | Type | Each one is a judgment call on one account. |
Saying no | Type, starting from a template | The reason has to fit this customer. |
Upset customers and your mistakes | Type, starting from a template | The template gives the order, and the apology has to be your own. |
Escalation, follow-up, and closing | Template | The steps are fixed, and only names and dates change. |
Which replies shouldn’t you be typing at all?
Stop typing any reply that has the same answer for every customer. Templates make those replies faster to send, and publishing them means fewer customers need to ask.
In Wonderchat’s study of 5,848,078 conversations, 58.5% of a random sample of 5,000 unresolved conversations asked for an answer that was never documented anywhere the agent could reach. Publishing the missing answer is the first fix to try, before typing faster.
1. Spot the repeats in your last 30 tickets
Look back over your last 30 tickets and mark every reply you’ve typed before. Anything you’ve sent three times in a week goes on the list.
The usual ones are how-to answers (templates 8 to 10), plan questions (template 11), and invoice requests (template 19).
None of them needs your judgment. They need to be easy to find.
At 40 support emails a week, about 173 a month, start with Wonderchat’s free plan. The free plan refills 50 AI replies every month, about a dozen emails a week at one reply each, and shows which repeats the agent answers before you pay.
Plan for Starter, at $39 a month, billed monthly, when more than about a dozen of your weekly emails are repeats your help center covers. Starter’s 500 AI replies come to about 2.9 per email at 173 a month, and the pricing page estimates about 160 resolutions a month on Starter.
You don’t need a separate ticketing system to start. Wonderchat’s help desk comes with every plan, with tickets that carry the full chat, a shared inbox, and live chat, and the free plan includes 2 team seats.
2. Publish each answer once
Write each one as a help center article, and use the customer’s words in the title. A title like “How do I export to CSV?“ gets found, and “Data portability options“ doesn’t.
Customers find it when they search, and so does an AI agent that answers from your help center.
That second reader changes the numbers. Wonderchat resolves about 75% of evaluated conversations without a person, a long-run average across all accounts.
About three in four evaluated conversations across Wonderchat’s customers end without a person, a long-run average.
Expect the numbers to move on average, and plan for your own to vary. In Wonderchat’s study, 84 businesses that added missing documentation went from 75.4% to 80.8% resolved in three months, +5.4 points on average, while 57% improved and 23% got worse.
The tickets left over are the ones the 30 templates are for, such as bugs, refunds, upset customers, and questions nobody has asked before.
3. Retire the old version the same day
When you publish a new answer, delete or archive the old article and the old template the same day.
The failure Wonderchat’s support team sees most often is retrieval pulling an archived policy and answering from it correctly.
The answer matches the page it found. The page is out of date.
Old canned responses do the same thing to a human team. A template written before your last pricing change keeps quoting the old terms until someone deletes it.
When is Zendesk, Freshdesk, or Help Scout the better choice?
Zendesk, Freshdesk, or Help Scout is the better choice if your team runs on macros, SLA timers, and assignment rules.
Zendesk macros add a reply and change ticket fields when you apply one, and they can assign the ticket too.
Freshdesk SLA policies set a response target for every ticket on its Growth, Pro, and Enterprise plans.
Help Scout’s routing assigns new conversations automatically on its Plus and Pro plans.
Wonderchat’s help desk does less. Every plan has tickets with the full chat attached, a shared inbox, and live chat, while routing and assignment rules need Scale.
If Zendesk macros already run your queue, keep them and put the agent in front. Wonderchat syncs tickets with Zendesk and Freshdesk from Basic, capped at 50 tickets until Scale.
If templates are all you need, Help Scout’s saved replies and Freshdesk’s canned responses already do that job.
How does Wonderchat answer the tickets you keep typing?
Answer first, template the shape, and publish the replies you keep retyping. Wonderchat answers from what you publish.
Wonderchat is an AI customer service agent and AI helpdesk in one, for teams adopting their first AI customer service software, whatever their size. Ask it how to export to CSV, and it answers from your help center and shows the article as its source.
When no page covers a question, it says so, offers a person, and puts the question in the review inbox, where you write the answer once.
When no help center page covers a question, the agent says so and offers a person.
Start for free with a plan that refills 50 AI replies every month, no credit card and no per-seat cost, or book a demo to see it answer questions from your own help center.
Frequently asked questions
How do I reply to a support ticket?
Read the whole thread, then answer the customer’s question in your first line. Give one next step with a time, use numbered steps for anything over two clicks, and link the exact help article section. Confirm the fix before you close the ticket.
Can you provide some examples of customer service responses?
A first reply can read “Thanks for the details. I’m checking this now and will write back by 3 p.m. today.“ A closing reply can read “Glad that’s fixed. I’m closing this ticket, so reply here if it comes back.“ All 30 templates cover common situations, grouped by type.
What do you do with a support ticket?
Read it, decide if you can answer now or need more information, then reply or pass it to the teammate who owns that area. Set its status, follow up when you promised, and close it once the customer confirms the problem is solved.
How fast should you reply to a support ticket?
Send the first reply as soon as you can, even if it’s template 2 with a time you can keep. A fast first response time matters less than the time you promise, because a missed promise turns one ticket into two.
Should support replies be templated?
Yes, template the shape of the reply. A template keeps structure and tone consistent while you fill in this customer’s details. If you send the same answer three times a week, publish it in your help center instead, where customers and an AI agent can find it.
