Customer Support Email Templates: 24 Replies by Ticket Stage

A customer support email template is a reusable reply for a situation your team answers again and again, written so an agent can personalize it in under a minute. The best ones follow the life of a ticket: the first reply, the request for details, the update, the fix, the close, and the way back in. Below are 24 copy-ready templates in that order, with the rule for when to send each one.

Use this one today if you only need a single reply that works for most new tickets:

Subject: We have your request about [short issue summary] (#[ticket ID])

Hi [customer name],

Thanks for writing in. I'm [agent name], and I'm looking into
[short issue summary] now.

[One sentence on what you are checking first.]

You'll hear from me by [day and time, with time zone]. If anything
changes before then, just reply to this email and it stays with me.

[agent name]
[company] support

Key Takeaways

• Write templates by ticket stage, not by topic. The stage decides what the customer needs to hear; the topic only fills in the details.
• Every template needs a named person, the issue in the customer's words, the next step, and a time.
• Give a real time ("by Thursday 3 PM CET"), never "soon" or "shortly".
• Keep a template for the moment you cannot help. Most teams only write templates for good news.
• Personalize the first and last sentence of every template before you send it. The middle can stay the same.

What makes a good customer support email

A good support email tells the customer who is helping, what is happening, and when they will hear back, in that order and in plain words. Everything else is optional.

Read any template in this guide and you will find the same five parts:

1. A named sender. "I'm Alex" gets a reply. "The support team" gets forwarded.
2. The issue in the customer's words. If they wrote "my order hasn't moved in 5 days", write that back, not "shipment status inquiry".
3. What you did or will do. One concrete action: "I checked with the carrier", "I refunded the second charge".
4. A time. When the next update comes, or when the fix lands.
5. A way back. What the customer should do if the answer does not work.

Length matters less than people think. A reply can be three lines if it carries all five parts. It fails at three paragraphs if it skips the time.

Customer support email templates by ticket stage

Templates grouped by stage are faster to find during a busy shift and harder to misuse, because each stage has one job. The table shows the stages this guide covers and what each reply must achieve.

Stage 1: First reply templates

The first reply decides whether the customer waits calmly or writes again. Send it within your published response time, even when you do not have the answer yet.

Template 1. Acknowledge and set a time

Hi [customer name],

Thanks for getting in touch about [issue in their words]. I'm
[agent name] and I'll be handling this.

I'm checking [first thing you'll look at] now and will update you
by [day, time, time zone].

[agent name]

Template 2. Outside business hours

Hi [customer name],

Thanks for your message about [issue in their words]. Our team is
offline until [opening time, time zone], and your request is first
in line when we're back.

If it's urgent, [what counts as urgent] can reach us at [channel].

[agent name or team name]

Template 3. Moved from chat to email

Use this when a live chat conversation needs more time than the chat allows.

Hi [customer name],

Thanks for chatting with us today. As promised, I've moved your
question about [issue] to email so I can look into it properly.

You don't need to repeat anything: I have the whole chat. I'll write
back by [day, time, time zone].

[agent name]

Stage 2: Need-information templates

Ask for everything you need in one message. Every extra round trip waits on the customer's next reply, which can easily mean another day.

Template 4. Ask for details

Hi [customer name],

To fix [issue], I need two things from you:

1. [First item, with where to find it]
2. [Second item, with where to find it]

As soon as I have those, I'll [next action] and get back to you
the same day.

[agent name]

Template 5. Ask for a screenshot or recording

Hi [customer name],

Could you send me a screenshot of what you see when [action]? If it's
easier, a short screen recording works too.

On [device type], you can take one with [short instructions].

[agent name]

Template 6. Verify identity before sharing account details

Hi [customer name],

Before I share details about your account, I need to confirm it's
you. I've sent a one-time code to [masked email]. Reply with the
code, or enter it at [link], and I'll continue right away.

This keeps your account safe. I'll never ask for your password.

[agent name]

Stage 3: Update and delay templates

Send an update before the customer asks for one. A message that says "no news yet, here is what happens next" earns more patience than silence.

Template 7. Progress update

Hi [customer name],

A quick update on [issue]: [what you found or did].

Next, [next step and who does it]. I'll update you again by
[day, time, time zone], or sooner if it's fixed.

[agent name]

Template 8. It will take longer than promised

Hi [customer name],

I told you I'd have [issue] fixed by [original time], and it's going
to take longer. [One honest sentence on why.]

The new time is [day, time, time zone]. In the meantime, you can
[workaround, if there is one].

I'm sorry for the wait.

[agent name]

Template 9. Waiting on a third party

Hi [customer name],

I've contacted [carrier, bank, partner] about [issue] and I'm waiting
for their answer. They usually reply within [typical time].

I'm keeping your request open and will follow up with them on
[day] if I haven't heard back.

[agent name]

Stage 4: Solved templates

Tell the customer what changed and ask them to check it. "It should work now" invites a second ticket if it does not.

Template 10. Issue fixed

Hi [customer name],

Good news: [issue] is fixed. [One sentence on what you changed.]

Could you [simple check] and let me know it works on your side? If
anything looks off, reply here and I'll pick it straight back up.

[agent name]

Template 11. Answering a how-to question

Hi [customer name],

Here's how to [task]:

1. [Step]
2. [Step]
3. [Step]

There's also a guide with screenshots here: [help article link].

[agent name]

Template 12. The answer is no

Hi [customer name],

Thanks for asking about [request]. [Product] doesn't [do this] today,
and I'd rather tell you clearly than leave you waiting.

What you can do instead: [workaround or alternative]. I've also shared
your request with our product team.

[agent name]

Stage 5: Billing and refund templates

Billing replies need exact amounts, dates and the last four digits of the card, never "the charge" or "soon".

Template 13. Refund issued

Hi [customer name],

I've refunded [amount and currency] to the card ending in [last four]
on [date]. Your bank usually shows it within [number] business days.

The refund reference is [reference]. If it hasn't appeared by
[date], reply with this email and I'll chase it with our processor.

[agent name]

Template 14. Duplicate or unexpected charge

Hi [customer name],

I checked your account. On [date] you were charged [amount] for
[reason]. [It was a duplicate and I've refunded it / It was for X,
here is the invoice: link].

If you still don't recognize it, reply and I'll walk through it
with you line by line.

[agent name]

Template 15. Refund not possible

Hi [customer name],

I looked into a refund for [order or plan]. Our [refund policy link]
covers [what it covers], and this [order or charge] falls outside it
because [specific reason].

What I can do: [credit, exchange, extension, partial refund].
Would that help?

[agent name]

Stage 6: Bug and escalation templates

When a ticket leaves the first line of support, the customer needs to know who owns it now and how they will hear back.

Template 16. Bug confirmed

Hi [customer name],

Thanks for the details. I reproduced the problem with [feature] and
reported it to our engineers as a bug.

Until it's fixed, [workaround]. I'll email you as soon as the fix
is live, and you don't need to follow up.

[agent name]

Template 17. Escalated to a specialist

Hi [customer name],

[Issue] needs someone from our [team] team, so I've handed it to
[specialist name]. They have the full conversation, so you won't need
to explain anything again.

They'll reply by [day, time, time zone].

[agent name]

Template 18. Service incident

Hi [customer name],

You're right: [feature] isn't working for some customers right now.
Our team is on it, and you can follow updates at [status page link].

You don't need to do anything. We'll email you when it's resolved.

[agent name]

Stage 7: No response and closing templates

Closing a ticket after silence is normal. Tell the customer before it happens, give a date, and explain how to come back. The full sequence, with 12 variations and timing rules, is in our guide to closing a ticket due to no response.

Template 19. Gentle follow-up

Hi [customer name],

Just checking in on [issue]. Did [the fix or the steps] work for you?

If you still need help, reply here and I'll pick it up. If I don't
hear back by [date], I'll assume it's sorted and close this request.

[agent name]

Template 20. Closing due to no response

Hi [customer name],

We haven't heard back about [issue] since [last contact date], so I'm
closing this request for now.

If you still need help, just reply to this email. The conversation
history stays attached, so you won't have to start over.

[agent name]

Template 21. Closing after a solved ticket

Hi [customer name],

I'm marking [issue] as solved. Thanks for your patience while we
sorted it out.

If it comes back, reply to this email any time and I'll reopen it.

[agent name]

Stage 8: Feedback and reopening templates

Template 22. Ask for feedback

Hi [customer name],

How did we do with [issue]? One click tells us:
[Great] [Okay] [Not good]

If something could have gone better, reply and tell me. I read
every answer.

[agent name]

Template 23. Replying to a complaint

Hi [customer name],

You're right to be frustrated. [Specific thing that went wrong] isn't
the experience we want you to have.

Here's what I've done: [action]. Here's what happens next: [step and
time]. I'll stay on this until it's resolved.

[agent name]

Template 24. Reopened ticket

Hi [customer name],

Thanks for letting me know [issue] is back. I've reopened your
request, and I can see everything we tried last time.

I'm starting with [next thing to check] and will update you by
[day, time, time zone].

[agent name]

Subject lines for support emails

A support subject line should name the issue and carry the ticket number, so the customer finds it in their inbox and your help desk threads the reply.

Avoid subject lines that say only "Re: Support" or "Your ticket". They look like every other automated email and get skipped.

Templates, canned responses and AI drafts compared

Templates, canned responses and AI drafts solve different problems, and most support teams use all three. The difference is how much of the reply a person writes.

In Conecto's shared inbox, AI compose drafts a reply from your knowledge base for an agent to review, and a finished reply can be scheduled to send later. Automations send a follow-up when a conversation goes quiet, so templates 19 and 20 do not depend on someone remembering. For the chat side of support, where replies are shorter and faster, use our live chat scripts. When a conversation starts in chat and a bot hands it over, the wording of that moment matters as much as any email; we collected the lines that work in chatbot handoff message examples.

How to personalize a template in 30 seconds

Personalizing a template means changing the parts a customer would notice were generic, and leaving the structure alone.

1. Rewrite the first sentence in response to what they actually said.
2. Use their words for the issue.
3. Replace every placeholder and search the draft for [ before sending.
4. Add one detail only you know: the order number, the setting you changed, the date you spoke.
5. Match their tone. A two-line question gets a short reply. A long, upset message gets a longer, calmer one.

Common mistakes with support email templates

1. Leaving a placeholder in the email. "Hi [customer name]" tells the customer nobody read their message. Make the placeholder search part of sending.
2. Promising a time you can't keep. Give the time you are confident in, then beat it.
3. Apologizing for everything. One sincere apology where you got something wrong beats "sorry for any inconvenience" in every email.
4. Hiding the answer. Put the answer in the first two lines. Customers read emails on phones.
5. Using the same template for good and bad news. "Great news!" at the top of a refusal reads as sarcasm.
6. Never updating the templates. Review them when your product, policy or prices change, and at least once a quarter.

Frequently asked questions

How many customer support email templates does a team need?

Most small teams start with 10 to 15 templates covering the stages above, then add one whenever the same reply is written by hand three times in a week.

Should support emails be formal or casual?

Match your brand and the customer. Clear, friendly and specific works for almost every business. Formal language is fine as long as the reply still names a person and a time.

Can I send these templates automatically?

Send follow-ups, reminders and closing notices automatically on a schedule, and stop the sequence the moment the customer replies. Keep first replies to complaints, refusals and billing problems for a person.

How long should a support email be?

As short as it can be while carrying the five parts: a named sender, the issue, the action, a time and a way back. That is often four to eight lines.

What's the difference between a canned response and a template?

A canned response is a fixed snippet inserted as is, like your opening hours. A template is a full reply with gaps the agent fills in for each customer.

Should the ticket number be in the subject line?

Yes. It lets the customer find the thread and lets your help desk attach their reply to the right ticket instead of opening a new one.

Build your template library from real tickets

Export last month's tickets, sort them by stage, and write a template for each stage where your team typed the same reply more than three times. Start with templates 1, 4, 10 and 20 from this guide, then add the billing and escalation replies your queue actually needs. To run them from one inbox, schedule the follow-ups and see which tickets close, start a Conecto workspace and set up your ticketing system, included from the Lite plan.