A support ticket response template is a pre-written reply for an open ticket of a known type, such as where is my order, a refund, a damaged item or a subscription change. A good one answers the question, names the next step and when it happens, and uses the order facts the customer would otherwise have to ask for.
Which support ticket response template fits an online store?
Eight replies cover most store tickets: damaged or missing item, subscription change, where is my order, refund or return, wrong item, bug update, escalation and in-progress update. Each answers or states the decision, gives the next step with a date and uses the order facts the customer would otherwise have to ask for.
A response template is the reply to an open ticket. It is not the automatic receipt sent when the ticket is created (see the acknowledgement template) and not the final message (see closing tickets). This page is part of a wider set of support templates.
Each template has a line on when to use it, a block to copy with [placeholders] and a “watch for” note. Where a matching use-case page exists, the note links to it; the bug, escalation and in-progress replies have none. Replace every bracket from live data, and only promise what your team can keep.
Damaged or missing item
Use it when a customer reports an item that arrived broken, or did not arrive in the parcel.
Hi [first name],
I'm sorry your [item] from order [order number] arrived [damaged / missing from the parcel]. That should not have happened.
[If your policy needs it: Could you send a photo of the item and the packaging?]
I have already started a [replacement / refund] for you. [Replacement: it ships on [dispatch date] and you will get a new tracking link. / Refund: [refund amount] goes back to your [payment method] on [refund date].]
I will write again on [next update date] if anything changes.
[Agent name]
Ticket [ticket reference]Watch for: do not ask for photos and also promise a replacement in the same breath if your policy makes the replacement conditional on the photo. Say which comes first.
UK note: the short-term right to reject a faulty item runs for 30 days (Consumer Rights Act 2015, section 22), so check your own obligations before you word the remedy. In the EU, the cost of returning a defective product is the responsibility of the trader, according to Your Europe. More on this scenario in damaged items.
Subscription change
Use it to confirm a pause, skip, swap or cancellation.
Hi [first name],
Your subscription is updated. Here is exactly what changed:
Plan: [plan]
Change: [paused / skipped / swapped / cancelled]
Next charge date: [next charge date]
Next delivery date: [next delivery date]
If this was a mistake, reply here and we will undo it. [Or: you can undo it from [account link].]
[Agent name]Watch for: never confirm a change the subscription app has not saved yet. Read [next charge date] from the app, not from memory. More on this in subscription tickets.
Where is my order
Use it for orders in transit, delayed, or marked delivered but not received.
Hi [first name],
Order [order number] is with [carrier]. Tracking: [tracking link]. The latest estimate is [delivery estimate].
[If delayed: it is running late because [reason]. I will check again on [next update date].]
[If delivered but not received: please check [safe place] and with neighbours. If it has not turned up by [date], I will open a claim with [carrier] and update you.]
[Agent name]Watch for: a [delivery estimate] copied from the order confirmation instead of the live carrier status. UK note: goods stay at the trader’s risk until the customer physically has them (Consumer Rights Act 2015, section 29), so do not tell a UK customer that a lost parcel is the carrier’s problem. More on this in WISMO tickets.
Refund or return approved
Use it to state the decision first. A declined variant follows.
Hi [first name],
Your refund for order [order number] is approved: [refund amount] to your [payment method], issued on [refund date]. Banks can take [bank days] to show it.
To send the item back: [returns portal link]. Please return it by [return by date].
[Agent name]Declined variant:
Hi [first name],
I have looked at your return request for order [order number], and I cannot approve it because [reason from policy].
What I can do instead: [alternative, such as an exchange or credit]. If you think I have misread the situation, reply here and I will take another look.
[Agent name]Watch for: never confirm a refund before it is issued. [refund amount] comes from the payment record, so partial refunds show the right figure. For UK stores, distance sales must be refunded within 14 days of receiving the item back, including standard delivery if the customer paid for it, according to GOV.UK. EU buyers have a 14-day withdrawal right, per Your Europe. Check your own obligations; this is not legal advice. More in refund tickets.
Wrong item sent
Use it when the customer received something other than what they ordered.
Hi [first name],
You ordered [item ordered] but we sent [item received]. That was our mistake and I am sorry.
The wrong item: [keep it / use the prepaid return label [label link]].
The right item ships on [dispatch date], and I will send the tracking link then.
[Agent name]Watch for: a two-issue ticket (wrong item and a late order) answered with a one-issue template. Check your own obligations on who pays the return.
Bug or technical fault update
Use it for a checkout error, a discount code that will not apply or a login problem.
Hi [first name],
Here is where we are on [the issue]. What we know: [what you know]. Workaround for now: [workaround, or "none yet"]. What is not fixed yet: [what remains].
I will update you on [next update date].
[Agent name]Watch for: promise an update date, never a fix date you do not have.
Escalation to a specialist or another team
Use it when the ticket moves to someone else.
Hi [first name],
I have passed your ticket to [team or name], who now owns it. I included [what you passed on], so you do not need to repeat it.
You will hear from them by [next update date].
[Agent name]Watch for: an escalation reply that makes the customer repeat details you already have.
In-progress update
Use it when the work is still going and the customer is waiting.
Hi [first name],
An update on [the issue]. Since my last message: [what has happened]. Next: [what is next].
[If nothing has changed: nothing has changed since [date], and I am still waiting on [who or what].]
I will write again on [next update date].
[Agent name]Watch for: an update that says nothing new. If nothing changed, say so and give the next date. For how long customers tend to wait, see response time.
| Scenario | Use case page | Order facts the reply needs |
|---|---|---|
| Damaged or missing item | Damaged items | Order number, item, remedy, dispatch or refund date |
| Subscription change | Subscriptions | Plan, next charge date, next delivery date |
| Where is my order | WISMO | Carrier, tracking link, live delivery estimate |
| Refund or return | Refunds | Refund amount, payment method, return by date |
| Wrong item sent | Damaged items | Item ordered, item received, dispatch date |
| Bug, escalation, in-progress | None | Workaround, owner, next update date |
For email structure and issue-report templates, see email templates. For how an email becomes a ticket, see email tickets. For live chat replies, see chat examples.
Which order facts does each reply need, and where do they come from?
Each reply needs a handful of order facts, and each lives in a specific system: the help desk, the store platform, the carrier, the payment record or the subscription app. A template only works when the agent fetches those facts before sending.
Personalisation is not the first name. A customer who gets a reply that quotes their item, their order date and their own deadline reads it as written for them, and a reply with the wrong item or an empty bracket reads as a form.
| Field | Where it comes from | Example | What goes wrong if it is missing or wrong |
|---|---|---|---|
[first name] | Help desk requester profile | Sam | Greeting reads “Hi ,” or uses the wrong part of the name |
[order number] and [order date] | Store platform | #10482, 2 October | Customer must look it up and repeat it |
[item and variant] | Order line | Linen shirt, blue, M | Reply covers the wrong product |
[carrier] and [tracking link] | Fulfilment or carrier | Carrier name, link | Customer cannot check the parcel |
[delivery estimate] | Carrier | Thursday | A stale date creates a second ticket |
[refund amount] and [refund date] | Payment record, after the refund is issued | 24.50 on 15 October | A promised refund that has not happened |
[return by date] | Order date plus your return window | 30 October | A dispute over whether the return is valid |
[next charge date] | Subscription app | 1 November | A charge the customer thought was cancelled |
[ticket reference] and [agent name] | Help desk | 48213, Priya | Customer cannot quote the ticket |
[next update date] | The agent decides | Friday | A promise nobody owns |
Help desk caveats: placeholders reach only the fields your help desk stores. Carrier status, payment records and subscription dates sit in other systems, which is why agents tab between them. Name fields can depend on how the name is written on the profile, and line breaks can be lost when a macro inserts multi-line content, so test address and multi-line fields and check what your help desk shows when a field is empty. Zendesk’s placeholders reference is a useful model of the syntax.
Where does Engaige fit?
A template stays as it was written until someone rewrites it. A reply drafted from live store data and checked by your team can improve from every edit, because the difference between the draft and the sent message shows what to change.
Engaige (that’s us) isn’t a template library or a help desk: it’s the e-commerce AI support agent that works inside the helpdesk your conversations land in. Engaige AI configures the agent and proposes how to improve it. At Otrium, 60% of 120,000 annual tickets are resolved end to end, and HelloPrint has 80% of its tickets automated. Keep your helpdesk, replace the AI.
In Agent Assist, which goes live in hours, Engaige drafts the reply and suggested actions in the ticket, inside your help desk. Your team edits and sends.
Every reply your team sends becomes training data: Engaige AI compares what your team said with what the agent suggested, learns from the difference, and improves itself, under your supervision, you approve the changes. The draft comes from your store data, your storefront and any docs you add, not from a template library, and it works alongside the macros you keep.
Hello Potential New Client
What would you like to get done today?
Could you analyse this week's conversations and show me some automation opportunities?
Ask Engaige…
Could you analyse this week's conversations and show me some automation opportunities?
Searched and found 4 contact reasons · 2.4s
Your agent resolved 426 of 512 conversations. 86 were handed over, and one contact reason accounts for most of them.
What were the reasons for handover, and how can we improve?
Searched and found 1 policy · 1.6s
Delivery status hands over whenever tracking is older than 24 hours, which is 40 of those 46.
Fix it.
Editing Delivery status · 1.9s
Done. It now handles stale tracking itself. Those 40 a week stay with your agent.
What were the reasons for handover, and how can we improve?
Fix it.
Reply…
HelloPrint ran Agent Assist as a co-pilot that analysed a query and offered responses and actions, then automated: 80% of tickets automated, 90% faster first response, and from 100 to 28 agents. The HelloPrint case has the detail.
Engaige proved to be invaluable. Their hands-on support during the implementation phase resulted in significant improvements to our automated resolution rate and CSAT.
You flip ticket types to autonomous one at a time, most brands in about a week, up to 90% of supported tickets. Policy-governed control sets how it reasons, what process it follows and when it may act, and every answer shows why, with the source.
Template, macro or drafted reply: which fits which ticket?
A canned response, or template, is reply text. A help desk macro is a saved set of actions that can include that text. A drafted reply is written per ticket from the order data. Each fits a different kind of ticket, so the choice depends on how much the facts change from one order to the next.
Zendesk defines a macro as “a prepared response or action that an agent can manually apply when they are creating or updating tickets”. Macros only contain actions, not conditions, and agents apply them manually. An account can hold up to 5,000 shared macros, according to the same page. For setup, see Zendesk macros.
| Ticket situation | Template or macro | Drafted reply from store data |
|---|---|---|
| Same-facts tickets, such as opening hours or return steps | Fits well: the text never changes | Works, but adds nothing |
| Policy wording that must be exact, such as the return window | Fits well: one approved wording | Needs the wording supplied by policy |
| Facts that vary per order, such as stock, carrier exceptions or partial refunds | Fits badly: someone must edit every field | Fits well: reads the order |
| Emotional tickets, such as a damaged gift | Reads canned unless heavily edited | Fits well, with a person checking the tone |
| Tickets with two questions | Answers one and misses the other | Fits well: covers both |
If you want ChatGPT to draft replies, see AI prompts. For broader tips, see better responses. To see Engaige draft in your own help desk, book a demo.
Frequently asked questions
What is a support ticket response template?
A pre-written reply for an open ticket of a known type, such as where is my order, a refund, a damaged item or a subscription change. It states the answer or decision, the next step with a date and the order facts.
What should a reply to a support ticket include?
Three things: the answer or the decision, the next step and when it happens, and the order facts the customer would otherwise have to ask for, such as the order number, the item and the tracking link.
How do I reply to a customer whose order arrived damaged?
Apologise once, name the item and the order, and say which remedy has started: a replacement with its dispatch date or a refund with the amount and date. If your policy needs a photo first, ask for it and say which comes first.
How should a reply confirm a subscription pause, skip or cancellation?
State exactly what changed, with the plan, the next charge date and the next delivery date, and say how to undo it. Only confirm a change the subscription app has already saved, and read the dates from the app.
Which order details should a ticket reply pull in, and from where?
The order number and item come from the store platform, carrier and tracking from fulfilment or the carrier, the refund amount from the payment record, the next charge date from the subscription app, and the name and ticket reference from the help desk.
What is the difference between a canned response and a macro?
A canned response is reply text. A macro is a saved set of actions that an agent applies manually in the help desk, and it can include that reply text.
Should a reply template quote consumer law on refunds or returns?
No. State your own policy and check your own obligations; a template is not legal advice.
Does Engaige use my existing macros or templates?
No. Engaige drafts each reply from your store data, your storefront and the docs you add, inside your help desk, alongside the macros you keep.
How does an AI agent learn from the replies my team sends?
In Agent Assist, Engaige AI compares the draft with what your team sent and proposes policy changes. You approve each one.
