A customer service email template is a ready-made email (subject line, body and sign-off) that an agent completes with the customer's details and sends. Below are 15 support email templates for the situations a consumer brand answers every day, from order status and delays to damaged items, cash on delivery and escalations. Each comes with a note on when to use it.
They rest on one idea that generic template lists skip: the [blanks] are facts from your order, courier and payment systems, and the email is only as good as those facts. For other formats and channels, see our customer service resources.
How to use these templates
- Keep the order number in the subject line, so replies stay on one ticket and the customer can find the email later.
- Replace every [blank] before sending. Each is a fact from a system or a decision from your policy.
- End every email with one next step and a date. If you don't have a date yet, say when you'll write again.
- For WhatsApp and live chat, use the short versions near the end; for one-line saved replies, see our canned response examples.
The templates at a glance
| # | Situation | Send it when |
|---|---|---|
| 1 | Request received | A customer emails and an agent will reply later |
| 2 | Asking for more information | You can't act without photos, an order number or an address |
| 3 | Order on its way | The order is moving and the date still holds |
| 4 | Order delayed | A customer asks about an order that is late |
| 5 | Delay notice | You know an order will miss its date, before the customer asks |
| 6 | Marked delivered, not received | Tracking says delivered; the customer says it isn't |
| 7 | Damaged item | The customer's photos confirm the damage |
| 8 | Wrong or missing item | The parcel doesn't match the order |
| 9 | Out of stock after ordering | An item in a paid order can't be shipped |
| 10 | Confirm a cash-on-delivery order | A COD order needs confirming before dispatch |
| 11 | Escalated to a specialist team | The case needs finance, the warehouse or a senior agent |
| 12 | Update on an escalated case | The specialist team needs more time |
| 13 | Follow-up after no reply | You asked for something two working days ago |
| 14 | Last follow-up before closing | Still no reply after the first follow-up |
| 15 | Closing the ticket | The issue is resolved |
What every support email template needs
A good template is short, and most of its words are facts. Whatever the situation, it has five parts:
- A subject line with the order number and the topic, such as "Order #48213: new delivery date", so replies stay on the same ticket.
- The answer in the first line. "Your refund of [amount] was sent today" comes before any thanks or apology.
- The facts, filled in: the item, the date, the amount, the tracking link, the reference number.
- One next step, with a date, and who takes it: "We'll email you by Friday" or "Reply with a photo of the label".
- A named sign-off. An agent's first name tells the customer who owns the case.
Where the blanks come from
Generic templates leave gaps such as "[state the status]" or "[solution]". In a consumer brand, each blank is a specific fact that lives in a specific system:
| Blank | Where the agent finds it | What goes wrong if it's guessed |
|---|---|---|
| [first name] | The store's customer record | A WhatsApp or Instagram display name, which may be a nickname |
| [order number], [items] | The store or order management system, such as Shopify | Details of the wrong order |
| [courier], [tracking link], [last scan] | The courier or logistics platform | "It's on its way" when it's stuck at a hub |
| [new delivery date] | The courier's revised estimate | A second missed promise |
| [refund amount], [refund method], [reference number] | The payment gateway or the refund record: a UTR for UPI and bank transfers, an ARN for card refunds | A refund the customer can't match to their statement, or an order number the bank can't trace |
| [return window], [eligible or not] | Your return policy, checked against the delivery date | A return approved that shouldn't be, or the reverse |
| [pickup date] | The reverse-pickup booking with the courier | A customer waiting in for a pickup that isn't booked |
| [what they've already sent] | The ticket history | Asking again for photos the customer already sent |
Every blank an agent fills from another tab costs time, and it is where a wrong number gets in.
We built Flowcall's AI Helpdesk so those facts are already on the ticket. Customer 360 shows the customer's orders, delivery, payments, refunds and past conversations from the systems you connect, and Agent Assist drafts the reply from the conversation, with your templates saved as canned responses for chat and email. Agents answer and act on a case without opening Shopify or a courier site.
Receiving a request
1. Request received
Use it when a customer emails and an agent will reply later, for example outside business hours. Send it automatically, and promise only the reply time your team meets on its busiest day (see first response time).
Subject: We've received your message (ticket #[ticket number])
Hi [first name],
Thanks for writing to us. Your request is logged as ticket #[ticket number], and one of our team will reply by [time and day].
If you're asking where an order is, you can see its latest status here: [tracking page link].
There's no need to write again: replies to this email go to the same ticket.
[Brand name] Customer Care
2. Asking for more information
Use it when you can't act without something from the customer. Ask for everything in one email and say why, because each extra round adds a day. Don't ask for anything the ticket already shows.
Subject: Order #[order number]: two things we need to sort this out
Hi [first name],
Thanks for letting us know about [the issue, in the customer's words]. To [arrange a replacement], we need:
- [A photo of the item that shows the damage]
- [A photo of the outer box with the shipping label]
You can attach them to a reply to this email. As soon as we have them, we'll [confirm your replacement] within [one working day].
[Agent first name], [Brand name] Customer Care
What to ask for, once:
| Situation | Ask for |
|---|---|
| Damaged item | A photo of the damage, a photo of the outer box, and the shipping label |
| Wrong item | A photo of the item received, with its label or tag showing |
| Item missing from the parcel | A photo of the opened parcel's contents and the packing slip |
| Address change | The full address with postcode or PIN code, a landmark if couriers need one, and a phone number for the courier |
Orders and delivery
"Where is my order?" questions, often shortened to WISMO, are the everyday work of ecommerce customer service. Check the courier's latest scan before you write, not the order page.
3. Order on its way
Use it when the order is moving normally and the expected date still holds.
Subject: Your order #[order number] is on its way
Hi [first name],
Your order shipped on [ship date] with [courier] and is due on [expected delivery date].
Its latest update was "[last tracking event]" in [city] on [date]. You can follow it here: [tracking link].
If it hasn't arrived by [expected date plus one day], reply to this email and we'll chase the courier for you.
[Agent first name], [Brand name] Customer Care
4. Order delayed
Use it when a customer asks about an order that has missed, or will miss, its date. Give the reason if you know it, the courier's new date, and what you've done.
Subject: Order #[order number]: sorry for the delay, new delivery date [date]
Hi [first name],
You're right, your order is late, and I'm sorry. It was due on [original date]. [The reason in one sentence, e.g. "The parcel was held at the courier's hub in [city] after the sale weekend."]
[Courier] now expects to deliver it on [new date]. I've [asked them to prioritise it / refunded your shipping fee of [amount]].
I'll check the tracking again on [date] and write to you if the date moves. If you'd rather cancel, reply to this email and I'll arrange a full refund instead.
[Agent first name], [Brand name] Customer Care
For wording that fits other failures, see our apology statements for customer service.
5. Delay notice
Use it when you know an order will miss its date and the customer hasn't asked yet. An email before the date passes answers the question before the customer has to write in.
Subject: Update on your order #[order number]: new delivery date [date]
Hi [first name],
We wanted to tell you before the date passed: your order won't arrive on [original date] as planned. [The reason, e.g. "Our warehouse is running two days behind after the sale."]
Your new expected delivery date is [new date]. You don't need to do anything.
If the new date doesn't work for you, reply to this email and we'll cancel the order and refund you in full.
[Brand name] Customer Care
6. Marked delivered, not received
Use it when tracking says delivered and the customer says it isn't. Don't sound doubtful: give them two quick checks, and say what you're doing with the courier meanwhile.
Subject: Order #[order number]: we're looking into your delivery
Hi [first name],
I'm sorry your order hasn't reached you. [Courier]'s tracking shows it as delivered on [date] at [time].
I've opened an investigation with [courier] today. In the meantime, could you check two things:
- Whether a neighbour, reception or the security desk took it in
- Whether anyone else at your address received it
I'll write to you by [date] with the courier's answer, and if the parcel isn't found, we'll [send a replacement / refund you in full].
[Agent first name], [Brand name] Customer Care
Much of this never needs to reach an agent. Flowcall's AI Agent checks current order and delivery data in your systems and answers "where is my order?" on WhatsApp, Instagram, Messenger, Live Chat and email with the same facts these templates ask for. On WhatsApp, Flowcall can also send shipped, delayed and delivered messages automatically when an order's status changes, so a delay notice like template 5 goes out without anyone writing it.
Returns and refunds
Return and refund emails have their own page: our return and refund email templates cover the request, the pickup, refunds by card, UPI or cash on delivery, partial refunds, store credit, late or failed refunds and ways of saying no. The rules behind them belong in your refund policy template.
Damaged, wrong or missing items
7. Damaged item
Use it when the customer's photos confirm the damage (template 2 asks for them). Offer the options your policy allows, and say what happens to the damaged item.
Subject: Order #[order number]: sorry about your damaged [item]
Hi [first name],
Thank you for the photos, and I'm sorry your [item] arrived damaged.
We'll send a replacement at no cost. It ships by [date] and should reach you by [date]; I'll email you the tracking link when it leaves. If you'd prefer a refund of [amount] instead, reply to this email and I'll arrange it.
[You don't need to send the damaged item back. / Our courier will collect the damaged item when they deliver the replacement, so please keep it in its box until then.]
[Agent first name], [Brand name] Customer Care
8. Wrong or missing item
Use it when the parcel doesn't match the order. The mistake is yours, so send the right item without waiting for the return if your policy allows. For an item missing from a multi-item order, check the tracking for a second parcel first.
Subject: Order #[order number]: the right [item] ships on [date]
Hi [first name],
You ordered [correct item, size, colour] and received [item received / the order without [missing item]]. I'm sorry for the mix-up.
The correct [item] ships on [date] and should reach you by [date]. You'll get the tracking link by email.
As for the item you received, [our courier will pick it up on [date], so please keep it in its packaging / please keep it, there's no need to return it]. You won't be charged for either.
[Agent first name], [Brand name] Customer Care
This is the kind of case Flowcall's AI Agent finishes itself, which is how Flowcall handles returns, refunds and exchanges: it assesses the damage photos the customer sends, applies your return rules, and creates the replacement in your order system once the required checks pass. When a check fails, the case reaches an agent with the photos and order on the ticket, and a ticket action does the rest: the AI fills the replacement form from the conversation and your systems, and the agent reviews it and clicks once.
When an item is out of stock
9. Out of stock after ordering
Use it when an item in a paid order can't be shipped. Give the customer the choice rather than deciding for them, and make each option a one-word reply.
Subject: Order #[order number]: [item] is out of stock, please choose an option
Hi [first name],
I'm sorry: [item, size, colour] sold out before we could pack your order. [The rest of your order shipped on [date]. / Nothing from your order has shipped yet.]
Please reply with 1, 2 or 3:
- Wait: it's back in stock on [date], and we'll ship it that day.
- Swap: we'll send [similar item] instead, at no extra cost.
- Refund: we'll refund [amount] to your [payment method] today.
If we don't hear from you by [date], we'll refund the item so your money isn't held.
[Agent first name], [Brand name] Customer Care
Cash on delivery
Cash on delivery (COD) means the customer pays the courier when the parcel arrives, in cash or, where the courier accepts it, by UPI. Where COD orders are a large share of sales, confirming the order before you ship it needs its own email. The refund email for a customer who paid on delivery is in our return and refund email templates.
10. Confirm a cash-on-delivery order
Use it when a COD order needs confirming before dispatch, so you don't ship a parcel nobody accepts. On WhatsApp this is a message with two buttons; the email below is for customers you reach by email.
Subject: Please confirm your cash-on-delivery order #[order number]
Hi [first name],
Thanks for your order of [items]. You'll pay [amount] on delivery, to:
[Delivery address]
Please confirm it's right: [Confirm order link] or [Cancel order link]. We'll ship it as soon as you confirm, and it should reach you by [date].
[Optional: Pay online now instead and get [incentive, e.g. free shipping]: [payment link]]
[Brand name] Customer Care
For Shopify stores, Flowcall confirms cash-on-delivery orders on WhatsApp and offers a discount to pay online in the same message, and the customer accepts or cancels in the chat, so template 10 gets its answer without an agent. It's part of Flowcall's WhatsApp Marketing, which uses the same customer data and AI as your support.
Escalations
An escalation email has two jobs: tell the customer who now owns the case, and give them a date. Our guide to escalation management covers the team side. When the customer is upset, see how to handle angry customers; for a formal complaint, use a complaint email response template.
11. Escalated to a specialist team
Use it when the case needs finance, the warehouse, the courier's claims team or a senior agent. Say what you've passed on, so the customer won't have to explain it again, and give a date even if the other team hasn't.
Subject: Order #[order number]: I've passed your case to our [team name] team
Hi [first name],
I've passed your case to our [finance / warehouse / senior support] team, because [the reason in plain words, e.g. "the refund needs approval from finance"].
They have everything you've sent us, including [your photos and the courier's report], so you won't need to explain it again. You'll have an answer by [date].
I'm staying on your case in the meantime, so keep replying to this email with anything you need.
[Agent first name], [Brand name] Customer Care
12. Update on an escalated case
Use it when the date you gave is close and the specialist team needs more time. Send it before the date passes: an update the customer didn't have to ask for keeps your next date believable.
Subject: Update on your case for order #[order number]
Hi [first name],
I promised you an answer by [date], so here's where things stand. Our [team name] team has [what's done, e.g. "confirmed the parcel was lost in transit"] and is now [what's pending, e.g. "waiting for the courier's claim decision"].
I expect a final answer by [new date]. [If you'd rather not wait, I can [refund you / send a replacement] now, and we'll settle it with the courier ourselves.]
Either way, I'll write again by [new date].
[Agent first name], [Brand name] Customer Care
Follow-ups and closing
When a ticket is waiting on the customer, a short sequence keeps it moving without nagging: a reminder after two working days, a last note three days later, then close. Adjust the timings, but write them down so every agent uses the same ones.
13. Follow-up after no reply
Use it when you asked the customer for something and two working days have passed. Repeat exactly what you need, so they don't have to scroll back.
Subject: Re: Order #[order number]: we still need [the photos of the damage]
Hi [first name],
Just checking in. We're ready to [send your replacement], and we only need [a photo of the damaged item and one of the shipping label].
You can attach them to a reply to this email, and we'll take it from there.
[Agent first name], [Brand name] Customer Care
14. Last follow-up before closing
Use it when there's still no reply after the first follow-up. Say when the request will close and that a reply reopens it.
Subject: Re: Order #[order number]: closing your request on [date]
Hi [first name],
We haven't heard back about [your damaged item], so we'll close this request on [date].
If you still need help, just reply to this email, even after that date, and we'll pick it up where we left off.
[Agent first name], [Brand name] Customer Care
15. Closing the ticket
Use it when the issue is resolved. Confirm what was done in one line, so the email also works as a record, and ask one rating question for your CSAT score. Thank-you notes after a purchase are a different email; see our thank you for your order messages.
Subject: Resolved: [your refund] for order #[order number]
Hi [first name],
[Your refund is complete], so I'm closing this request. [One-line record, e.g. "The refund reference is [number], and it should reach your card by [date]."]
How did we do? [Rating link, 1 to 5]
If anything else comes up with this order, reply to this email and the request will reopen with its full history.
[Agent first name], [Brand name] Customer Care
In Flowcall, the reminders run themselves. When a customer goes quiet, Flowcall reminds them what the AI Agent is still waiting for, such as a photo or an address, at increasing intervals, and picks up where it left off when they reply. In Flowcall's email ticketing, tickets waiting on the customer can have their own follow-up sequence, and after a resolution Flowcall asks for a rating and reports CSAT for the AI Agent and human agents separately, by channel and team.
The same templates on WhatsApp and live chat
Customers who write on WhatsApp or live chat want the same answers in fewer words. Three things change:
- No subject line or sign-off block. The first line does the subject's job.
- One point per message, with choices as buttons. The out-of-stock options in template 9 become three buttons.
- WhatsApp's reply window. When a customer messages you, a 24-hour customer service window starts. While it's open you can send any reply; after it closes, you can only send pre-approved WhatsApp message templates, which are a different thing from the email templates here (Meta's WhatsApp Business Platform documentation, checked on 30 September 2026). A delay update sent more than a day after the customer's last message needs one.
| Situation | Email subject | WhatsApp or live chat version |
|---|---|---|
| Order on its way | Your order #[order number] is on its way | Hi [first name], your order #[order number] is with [courier] and due on [date]. Track it here: [link] |
| Order delayed | Order #[order number]: sorry for the delay, new delivery date [date] | Sorry, [first name], your order is running late. [Courier] now expects to deliver it on [date]. [Keep my order] [Cancel and refund] |
| Asking for photos | Order #[order number]: two things we need to sort this out | To arrange your replacement, please send two photos here: the damaged item, and the box with its shipping label. |
| Out of stock | [Item] is out of stock, please choose an option | [Item] sold out before we could pack it. What would you like to do? [Wait until [date]] [Swap] [Refund] |
| Closing | Resolved: [your refund] for order #[order number] | Glad that's sorted, [first name]. How did we do? [1 to 5] |
For full back-and-forth chats, including how an agent opens and closes one, see our customer service conversation examples.
How to keep your templates accurate
Templates go wrong quietly: the return window changes, a courier is replaced, a refund timeline moves, and the old wording keeps going out. Give each template an owner, and check every one the day your shipping or return policy changes; our shipping policy template lists what the policy itself should state. How to name, review and measure the whole library, including which templates bring customers back, is covered in our canned response examples.
Reading a sample of sent emails only catches what you happen to read. Flowcall's AI Auto QA reviews every agent reply, or the ones you select, for inconsistent information and for asking again for details the customer already gave, and you can add your own standards, such as the current return window, so a reply quoting an old policy is flagged. Each finding quotes the conversation and names the agent, and it works on Flowcall or on top of the helpdesk you already use.
How Flowcall handles these emails
Templates make an agent's reply faster and more consistent. Flowcall takes the same situations further: its AI Agent answers order, delivery, return and refund requests on email, WhatsApp, Instagram, Messenger and Live Chat from your systems and completes the work your rules allow, and it answers questions before purchase by recommending products from your catalogue. When a case needs an agent, it creates the ticket with the conversation, a summary, the order and what's left to do, and back-office work for finance or the warehouse goes into child tickets while the customer's ticket stays open and owned.
To see Flowcall answer a damaged-item email with the order, the photos and the replacement on one ticket, book a demo.
Frequently Asked Questions
How do I write a good customer service email?
Put the answer in the first line, then the facts the customer needs (dates, amounts, tracking, reference numbers), then one next step with a date and who takes it. Use a subject line with the order number, sign with a first name, and check that every question the customer asked has an answer before you send.
What are the 5 C's of email etiquette?
There isn't one agreed list. Versions draw on words such as clear, concise, correct, courteous, complete and considerate. For support email, complete matters most: an email that answers every question and gives the next step saves a second round.
What is the 3 email rule?
It's a rule of thumb, not a standard: if a question isn't settled after three emails back and forth, stop writing and switch to a call or a chat. In support, a long thread is a sign the first reply asked for too little or answered too little; asking for everything once (template 2) is the fix.
How do I say an issue is resolved in an email?
Say what was done, give the one fact the customer may need later (a reference number or a date), and tell them how to reopen the request if something else comes up. Template 15 does all three in four lines.
Should support emails come from a named agent or a team address?
Both. Send from the team address, so replies land on the ticket even when the agent is away, and sign with the agent's first name, so the customer knows who owns the case.




