Canned Response Examples for Customer Service

Customer service canned responses are pre-written messages that support agents insert into a help desk reply to answer common questions consistently and fast. Depending on the tool, the same feature is called saved replies, macros, response templates, canned messages, snippets, or quick replies. Below are 50 ready-to-use templates organized by the scenarios that drive most e-commerce support volume — order status, refunds, cancellations, complaints, billing, and feedback. Each one includes a one-line note on when to use it and a copy-paste block with variables in place.

A good template carries the routine sentences for the agent, leaves room for one or two case-specific lines, and uses placeholders that pull live ticket data. None of the templates below should be sent verbatim. The bracketed cue inside each one is where the agent's own sentence belongs.

Greetings and acknowledgements

Use these on the first reply. The point is to confirm receipt and set a realistic expectation for what comes next.

1. New ticket acknowledgement

When to use: New ticket where the full answer needs more than a few minutes of research.

Subject: We received your message (Ticket #{{ticket_number}})

Hi {{customer_first_name}},

Thanks for reaching out. We have your message and will look into it shortly.

[Insert one sentence confirming what the customer asked about.]

Replies stay attached to this ticket.

Best,
{{agent_first_name}}

2. Holiday or peak-period acknowledgement

When to use: Black Friday, holiday season, or any time response times are running slower than usual.

Subject: We received your message (Ticket #{{ticket_number}})

Hi {{customer_first_name}},

Thanks for writing in. We are handling a higher volume than usual and are working through messages in the order they arrived.

[Insert one sentence about the customer's question if you can answer it quickly.]

Current response time is approximately {{store_business_hours_response}}.

Best,
{{agent_first_name}}

3. Returning customer greeting

When to use: Customer has a prior ticket on file and you want to acknowledge them without sounding generic.

Hi {{customer_first_name}},

Good to hear from you again. I have your previous order {{order_previous_number}} from {{order_previous_date}} on file.

[Insert one sentence about the current question, referencing prior context only if you are sure it is related.]

Best,
{{agent_first_name}}

4. Live chat first-touch greeting

When to use: Customer has just opened a chat and you need a friendly opener while you read the question.

Hi {{customer_first_name}}, thanks for chatting with us. Give me a moment to pull up your account.

5. Complex issue holding reply

When to use: Ticket needs investigation across systems and you cannot answer in the first reply.

Subject: We are looking into your request (Ticket #{{ticket_number}})

Hi {{customer_first_name}},

I have your message and the case needs some digging on our side. I am checking with [warehouse / carrier / billing] and will reply within {{ticket_next_update_hours}} hours.

[Insert one sentence reflecting what the customer said back so they know you read it.]

Best,
{{agent_first_name}}

Order and shipping updates

These cover WISMO — "where is my order" — and related fulfillment questions. According to Shopify's WISMO data, shipping inquiries account for 30–40% of support tickets normally and over 50% during peaks like Black Friday, making this the highest-volume category.

6. WISMO with tracking link

When to use: Order has shipped and you have a tracking number.

Subject: Tracking for your order #{{order_number}}

Hi {{customer_first_name}},

Your order is on its way.

Carrier: {{order_carrier}}
Tracking: {{order_tracking_url}}
Estimated delivery: {{order_estimated_delivery}}

[Insert one sentence if there is anything unusual — delay, split shipment, signature required.]

If tracking has not updated in 48 hours, let us know and we will follow up with the carrier.

Best,
{{agent_first_name}}

7. WISMO — still processing

When to use: Order is in the warehouse queue but has not been picked up by the carrier yet.

Subject: Update on your order #{{order_number}}

Hi {{customer_first_name}},

Your order is being prepared at our warehouse and has not yet shipped. You can expect a shipping confirmation within {{order_processing_window}} business days.

[Insert one sentence if the customer mentioned a needed-by date, addressing whether that is realistic.]

You will get an automatic email the moment the carrier scans the package.

Best,
{{agent_first_name}}

8. Shipping delay — carrier side

When to use: Tracking shows the package stalled with the carrier.

Subject: Update on order #{{order_number}}

Hi {{customer_first_name}},

I checked your order and the package is held up at {{order_tracking_last_location}}. The delay is on the carrier's side.

[Insert one sentence on what you have done — escalated, opened a trace request, etc.]

I will email again as soon as it moves, or by {{ticket_next_update_date}} at the latest.

Best,
{{agent_first_name}}

9. Shipping delay — weather or peak season

When to use: A regional event (weather, holiday surge) is slowing shipments broadly.

Subject: Heads-up on order #{{order_number}}

Hi {{customer_first_name}},

Your order is moving, but carriers in {{order_destination_region}} are reporting delays of {{order_delay_window}} days due to {{order_delay_cause}}.

[Insert one sentence reassuring the customer of the package's current location.]

Latest tracking: {{order_tracking_url}}

Best,
{{agent_first_name}}

10. Order shipped confirmation

When to use: Manual shipping confirmation, often after a delayed dispatch.

Subject: Your order #{{order_number}} has shipped

Hi {{customer_first_name}},

Your order is on its way as of today.

Carrier: {{order_carrier}}
Tracking: {{order_tracking_url}}
Estimated delivery: {{order_estimated_delivery}}

[Insert one sentence if the dispatch was later than originally promised.]

Best,
{{agent_first_name}}

11. Delivery exception (failed attempt)

When to use: Carrier attempted delivery and could not complete it.

Subject: Delivery attempt — order #{{order_number}}

Hi {{customer_first_name}},

The carrier attempted delivery today and could not complete it. Tracking shows: {{order_tracking_last_status}}.

[Insert one sentence on what action the customer needs to take — reschedule, pick up, confirm address.]

Tracking: {{order_tracking_url}}

If the package is returned to us, we will reach out about reshipping or refunding.

Best,
{{agent_first_name}}

12. Lost package — investigation started

When to use: Package missing past the carrier's investigation threshold.

Subject: Investigating your order #{{order_number}}

Hi {{customer_first_name}},

I am sorry your order has not arrived. I have opened a trace request with {{order_carrier}}. These usually take {{carrier_trace_window}} business days.

[Insert one sentence confirming details the customer gave — address, neighbors checked, last known location.]

I will email the moment we hear back, or by {{ticket_next_update_date}}.

Best,
{{agent_first_name}}

13. Damaged item on arrival

When to use: Item arrived damaged. Use after photos are received.

Subject: Re: damaged order #{{order_number}}

Hi {{customer_first_name}},

I am sorry your order arrived damaged. From the photos, I can see what happened and will get this sorted.

[Insert one sentence describing what you are doing — replacement, refund, or what info you still need.]

You do not need to send the damaged item back unless we request it.

Best,
{{agent_first_name}}

Refunds and returns

Refund language needs to be unambiguous. State the status in the first sentence, give the exact amount and payment method, and pin a concrete timeline.

14. Refund processed

When to use: Refund has been issued in your payment processor.

Subject: Refund processed for order #{{order_number}}

Hi {{customer_first_name}},

Your refund of {{refund_amount}} has been processed to your {{refund_payment_method}}. You should see it in your account within 3 to 10 business days, depending on your bank.

[Insert one sentence acknowledging the reason — return received, cancellation, goodwill, etc.]

If you do not see the refund after 10 business days, reply with your bank's name and we will follow up.

Best,
{{agent_first_name}}

15. Refund initiated

When to use: Returned item has arrived and the refund is being processed.

Subject: Refund initiated for order #{{order_number}}

Hi {{customer_first_name}},

We have received your return and the refund of {{refund_amount}} is being processed. You should see it on your {{refund_payment_method}} within 5 to 10 business days.

[Insert one sentence on the return condition — complete and good, or any issues found.]

Best,
{{agent_first_name}}

16. Return label sent

When to use: Return label has been generated for the customer.

Subject: Return label for order #{{order_number}}

Hi {{customer_first_name}},

Your return label is attached and linked here: {{return_label_url}}.

Pack the item securely, attach the label, and drop it at any {{return_carrier}} location within 14 days. Once we receive it, your refund of {{refund_amount}} will process within 5 to 10 business days.

[Insert one sentence if anything is specific to this return — missing pieces, condition note, exchange.]

Best,
{{agent_first_name}}

17. Return received, refund coming

When to use: Warehouse has logged the return but the refund has not been issued yet.

Subject: Return received — order #{{order_number}}

Hi {{customer_first_name}},

Your return arrived today. The refund of {{refund_amount}} will process within {{refund_processing_window}} business days, and you will get a confirmation email when it goes out.

[Insert one sentence acknowledging any specific concern the customer raised.]

Best,
{{agent_first_name}}

18. Refund denied — outside return window

When to use: Order is past your stated return policy window.

Subject: Re: return request for order #{{order_number}}

Hi {{customer_first_name}},

I checked your order and it was delivered on {{order_delivery_date}}, past our {{store_return_window_days}}-day return window: {{store_return_policy_url}}.

[Insert one sentence acknowledging the reason given, and whether you can offer store credit or another accommodation.]

I am sorry we cannot process a full refund in this case.

Best,
{{agent_first_name}}

19. Exchange initiated

When to use: Customer wants an exchange for a different size, color, or variant.

Subject: Exchange started for order #{{order_number}}

Hi {{customer_first_name}},

I have set up your exchange. Once we receive your original item, we will ship the {{exchange_replacement_item}} in {{exchange_variant}}.

Return label: {{return_label_url}}

[Insert one sentence on stock status of the replacement.]

Best,
{{agent_first_name}}

Cancellations and address changes

The deciding factor for both is whether the order has shipped. Templates split into pre-ship (do-able) and post-ship (carrier-side action).

20. Order cancellation confirmed (pre-ship)

When to use: Customer requested cancellation; order has not shipped.

Subject: Order #{{order_number}} cancelled

Hi {{customer_first_name}},

Your order has been cancelled before it shipped. A refund of {{refund_amount}} will be issued to your {{refund_payment_method}} within 3 to 10 business days.

[Insert one sentence acknowledging the reason if given, without pushing to re-order.]

Best,
{{agent_first_name}}

21. Order cancellation — already shipped

When to use: Customer wants to cancel but the order has shipped.

Subject: Re: cancellation for order #{{order_number}}

Hi {{customer_first_name}},

Your order has already shipped, so we cannot cancel from our side. Tracking: {{order_tracking_url}}.

You have two options once it arrives:

1. Refuse the package at delivery. The carrier returns it and we refund {{refund_amount}} within 5 to 10 business days of receipt.
2. Accept the package and return through our portal: {{store_return_portal_url}}.

[Insert one sentence on which option fits the situation.]

Best,
{{agent_first_name}}

22. Address change confirmed (pre-ship)

When to use: Customer needs to update the address; order has not been picked up.

Subject: Shipping address updated for order #{{order_number}}

Hi {{customer_first_name}},

The shipping address on your order has been updated to:

{{order_new_address_block}}

[Insert one sentence confirming the order is still in the warehouse queue.]

You will get the usual tracking email when it ships.

Best,
{{agent_first_name}}

23. Address change — cannot do (already shipped)

When to use: Order is already in transit.

Subject: Re: address change for order #{{order_number}}

Hi {{customer_first_name}},

Your order has left the warehouse and is in transit with {{order_carrier}}, so we cannot change the destination. Some carriers allow recipients to redirect mid-route through the tracking page: {{order_tracking_url}}.

[Insert one sentence on the specific carrier's redirection options if known — UPS My Choice, FedEx Delivery Manager, USPS Hold Mail.]

If the package returns to us undelivered, we can refund or reship.

Best,
{{agent_first_name}}

Stock and availability

For sold-out, backordered, or pre-order items. The customer mainly wants a date and a way to be notified.

24. Out of stock — no restock date

When to use: Product is sold out and you do not have a confirmed restock date.

Subject: Re: {{product_name}} availability

Hi {{customer_first_name}},

The {{product_name}} is currently sold out and we do not yet have a confirmed restock date.

To get notified when it comes back, add your email to the notification list on the product page: {{product_url}}.

[Insert one sentence on a similar in-stock product, only if it is a close match.]

Best,
{{agent_first_name}}

25. Out of stock — restock date known

When to use: You have a confirmed restock date.

Subject: Re: {{product_name}} restock

Hi {{customer_first_name}},

The {{product_name}} is expected back around {{product_restock_date}}.

To be emailed the moment it goes live: {{product_url}}.

[Insert one sentence on whether the date is firm or estimated.]

Best,
{{agent_first_name}}

26. Backorder confirmation

When to use: Customer ordered a backordered item.

Subject: Your order #{{order_number}} — backorder timing

Hi {{customer_first_name}},

The {{product_name}} on your order is on backorder. Based on our supplier's timeline, we expect to ship it around {{product_backorder_ship_date}}.

[Insert one sentence on whether the rest of the order can ship separately now, if applicable.]

You can cancel any time before it ships.

Best,
{{agent_first_name}}

27. Pre-order timeline update

When to use: Customer asking about a pre-order they already placed.

Subject: Pre-order update — {{product_name}}

Hi {{customer_first_name}},

Quick update on your pre-order. Current estimated ship date is {{product_preorder_ship_date}}.

[Insert one sentence on whether this matches the original estimate or has changed, and why.]

You will get a shipping confirmation when it goes out.

Best,
{{agent_first_name}}

Complaints and apologies

These templates are the most worth investing in and the most dangerous to send unedited. A complaint that gets a stock apology with the first name swapped in usually escalates. The category uses a two-track structure: a holding reply that buys you time, and a follow-up with the resolution.

28. Complaint holding reply (first hour)

When to use: Complaint just arrived and you need to acknowledge it before you have a resolution.

Subject: We have your message — Ticket #{{ticket_number}}

Hi {{customer_first_name}},

I read your message and I am sorry about what happened.

[Insert two to three sentences paraphrasing the specific issue back so the customer knows you understood it.]

I am looking into this now and will email with a proper response by {{ticket_next_update_date}}.

Best,
{{agent_first_name}}

29. Apology with resolution

When to use: Follow-up to a complaint, with cause and fix.

Subject: Re: your order #{{order_number}}

Hi {{customer_first_name}},

Thanks for your patience. Here is what I found:

[Insert two sentences on the actual cause, in plain language, without hedging.]

Here is what we are doing about it:

[Insert two to three sentences on the concrete fix — refund, replacement, store credit — with amounts and timing.]

If anything above is not quite right, reply and I will adjust.

Best,
{{agent_first_name}}

30. Service failure with goodwill credit

When to use: A failure that goes beyond what a refund alone covers.

Subject: Re: order #{{order_number}}

Hi {{customer_first_name}},

I am sorry. {{ticket_failure_description}} should not have happened.

We are issuing a refund of {{refund_amount}} to your {{refund_payment_method}}, plus a store credit of {{credit_amount}} you can apply to a future order using code {{credit_code}}.

[Insert one sentence on what we are doing internally so this does not happen again.]

Best,
{{agent_first_name}}

31. Damaged item replacement

When to use: Item arrived damaged and you are sending a replacement instead of refunding.

Subject: Replacement for your damaged order #{{order_number}}

Hi {{customer_first_name}},

I am sorry your order arrived damaged. A replacement has been queued and ships today with priority shipping. You should have it by {{replacement_estimated_delivery}}.

You do not need to send the damaged item back.

[Insert one sentence on what is on the replacement order if it differs from the original.]

Best,
{{agent_first_name}}

32. Wrong item shipped

When to use: Warehouse picked the wrong item.

Subject: Re: wrong item on order #{{order_number}}

Hi {{customer_first_name}},

I am sorry — the wrong item was packed. The correct {{order_original_item}} is shipping today with priority shipping and should arrive by {{replacement_estimated_delivery}}.

For the item you received in error, the prepaid return label is here: {{return_label_url}}.

[Insert one sentence on goodwill if appropriate.]

Best,
{{agent_first_name}}

33. Escalation acknowledgement

When to use: Customer escalated to a manager or through a public channel.

Subject: Your case is being reviewed — Ticket #{{ticket_number}}

Hi {{customer_first_name}},

Your case has been passed to {{escalation_owner_name}}, our {{escalation_owner_title}}, who is reviewing it now.

[Insert one sentence reflecting the specific issue back so the customer knows it was understood.]

You will hear from {{escalation_owner_name}} directly by {{escalation_next_update_date}}.

Best,
{{agent_first_name}}

Billing and payment

Money questions need exact numbers. State the amount, the payment method, and the timeline.

34. Payment failed — retry

When to use: Payment was declined or did not capture.

Subject: Payment issue on order #{{order_number}}

Hi {{customer_first_name}},

Your payment did not go through. Common causes:

1. The billing address does not match the card.
2. The bank flagged the transaction.
3. The card is expired or has insufficient funds.

Retry here: {{order_payment_retry_url}}. The order is held for 48 hours before it cancels automatically.

[Insert one sentence if you can see anything specific in the failure code.]

Best,
{{agent_first_name}}

35. Double charge investigation

When to use: Customer reports two charges for the same order.

Subject: Re: double charge on order #{{order_number}}

Hi {{customer_first_name}},

In most cases, a duplicate charge is a temporary authorization hold from your bank rather than two captures, and it usually drops off within 3 to 5 business days.

I checked our system and we captured only one payment of {{order_total}}.

[Insert one sentence with the specific dates and amounts the customer mentioned.]

If the second charge has not dropped off after 5 business days, reply with a screenshot of your statement.

Best,
{{agent_first_name}}

36. Invoice copy request

When to use: Customer needs a PDF invoice, often for reimbursement.

Subject: Invoice for order #{{order_number}}

Hi {{customer_first_name}},

Attached is the invoice for your order. You can also download it any time from {{store_account_invoices_url}}.

[Insert one sentence if there is anything specific to call out — VAT, business name on file.]

Best,
{{agent_first_name}}

37. Subscription billing question

When to use: Question about a recurring subscription charge.

Subject: Re: your subscription charge

Hi {{customer_first_name}},

Your subscription {{subscription_product_name}} renewed on {{subscription_last_charge_date}} for {{subscription_amount}}, billed to your {{subscription_payment_method}}. Next renewal: {{subscription_next_charge_date}}.

You can manage, pause, or cancel from {{subscription_management_url}}.

[Insert one sentence addressing the specific question — cancel, pause, or just confirm.]

Best,
{{agent_first_name}}

Follow-ups and feedback requests

Follow-ups close out tickets and gather data. Response rates and recall accuracy both fall off quickly when the survey lands days after the conversation — Zendesk's CSAT automation defaults to sending the survey 24 hours after the ticket is solved, when the interaction is still fresh.

38. Post-resolution check-in (24 hours after close)

When to use: Confirming a complex fix held.

Subject: Following up on your order #{{order_number}}

Hi {{customer_first_name}},

Quick follow-up on the {{ticket_subject_summary}} we sorted out yesterday. I wanted to confirm everything is still working on your side.

[Insert one sentence on the specific resolution so the customer remembers the context.]

If anything is still off, reply and we will pick it back up.

Best,
{{agent_first_name}}

39. CSAT survey request (immediate post-close)

When to use: Capture CSAT while the interaction is fresh.

Subject: How did we do? (Ticket #{{ticket_number}})

Hi {{customer_first_name}},

If you have 10 seconds, we would appreciate your rating:

[Rate this conversation]({{csat_survey_url}})

[Insert one sentence reminding the customer what was resolved.]

Best,
{{agent_first_name}}

40. NPS survey request

When to use: Periodic NPS pulse, no more than once per 90 days per customer.

Subject: Quick question for {{customer_first_name}}

Hi {{customer_first_name}},

How likely are you to recommend {{store_name}} to a friend?

[Take the 30-second survey]({{nps_survey_url}})

[Insert one sentence anchoring it to a recent moment — last order, purchase anniversary — if it fits.]

Best,
{{agent_first_name}}

41. No-response nudge

When to use: Customer has not replied in 3 days and the ticket needs their input.

Subject: Following up on Ticket #{{ticket_number}}

Hi {{customer_first_name}},

Following up on my message from {{ticket_last_agent_reply_date}}. I asked for [insert what you asked for — photo, address, order number] and have not heard back.

[Insert one sentence reminding the customer what the issue was.]

If you can reply when you have a moment, I can keep things moving.

Best,
{{agent_first_name}}

42. Closing for inactivity

When to use: No response after a nudge.

Subject: Closing Ticket #{{ticket_number}} for now

Hi {{customer_first_name}},

I have not heard back, so I am closing this ticket. Nothing on your end has been lost.

[Insert one sentence on what we still need if they want to pick it back up.]

Replying to this email reopens the ticket automatically.

Best,
{{agent_first_name}}

Closing messages

These wrap up a resolved conversation. Be clear about what happens next without being verbose.

43. Standard ticket closing

When to use: Issue resolved, no further action needed.

Hi {{customer_first_name}},

Glad we got that sorted. I am marking this ticket as resolved.

[Insert one sentence summarizing the outcome.]

Reply any time to reopen.

Best,
{{agent_first_name}}

44. Resolution with help article link

When to use: Answer is a standard process and you want to point to the documentation.

Hi {{customer_first_name}},

Here is the full walk-through for future reference: {{help_article_url}}.

[Insert one sentence with the specific answer to the question, not just the link.]

Let me know if anything is unclear.

Best,
{{agent_first_name}}

45. "Anything else?" close

When to use: Answered the question but want to check before closing.

Hi {{customer_first_name}},

[Insert one or two sentences with the actual answer.]

Anything else you needed help with, or are we good to wrap this one up?

Best,
{{agent_first_name}}

46. Thank-you-for-patience close

When to use: A long ticket finally resolved.

Hi {{customer_first_name}},

Thanks for sticking with us on this one — I know it took longer than it should have.

[Insert one sentence summarizing the final resolution and any compensation owed.]

Closing the ticket now.

Best,
{{agent_first_name}}

Out-of-office and holiday

Auto-replies that fire when no agent is available. Keep them short.

47. After-hours auto-response

When to use: Ticket arrived outside business hours.

Subject: We received your message (Ticket #{{ticket_number}})

Hi {{customer_first_name}},

Our team is offline. We are back online {{store_next_business_day}} at {{store_business_hours_open}} and will reply in the order messages arrived.

Order tracking: {{store_tracking_url}}.

Best,
{{store_name}} Support

48. Holiday hours notice

When to use: Around a public holiday or scheduled closure.

Subject: We received your message (Ticket #{{ticket_number}})

Hi {{customer_first_name}},

Our team is closed for {{store_holiday_name}} and will be back on {{store_holiday_return_date}}.

For order tracking any time: {{store_tracking_url}}.

Best,
{{store_name}} Support

49. Weekend reduced coverage

When to use: Reduced weekend capacity.

Subject: We received your message (Ticket #{{ticket_number}})

Hi {{customer_first_name}},

Our team has reduced coverage on weekends. We will get back to you on Monday at the latest.

Self-service tracking and returns: {{store_self_service_url}}.

Best,
{{store_name}} Support

50. Brief team outage

When to use: Planned all-hands meeting or short outage.

Subject: We received your message (Ticket #{{ticket_number}})

Hi {{customer_first_name}},

Our team is briefly off the queue for an internal meeting and will be back by {{store_outage_end_time}}.

Best,
{{store_name}} Support

How to personalize customer service canned responses with variables

Variables (also called placeholders, merge tags, or dynamic tokens) pull live ticket data into the reply on insert. Every major help desk supports them, though the syntax differs — Help Scout's saved replies use {%customer.firstName%}, Zendesk's macro variables use {{ticket_requester_name}}, and Freshdesk's reply editor provides an in-editor placeholder picker.

Map the generic {{variable_name}} syntax above to your help desk's actual placeholders before saving:

Generic placeholder	Help Scout	Zendesk	Freshdesk
{{customer_first_name}}	{%customer.firstName%}	{{ticket_requester_first_name}}	Placeholder picker
{{ticket_number}}	{%conversation.number%}	{{ticket_id}}	Placeholder picker
{{agent_first_name}}	{%user.firstName%}	{{current_user_first_name}}	Placeholder picker
{{order_number}}	Custom field / app	Custom field / app	Custom field / app

Three things break variables more often than the syntax does:

1. Empty data. Hi {{customer_first_name}}, resolves to Hi , when the field is empty. Set a fallback default on every name field.
2. Wrong order. If a customer has multiple open orders, {{order_number}} may pull the most recent one. Use ticket-to-order linking if your tool supports it; otherwise the agent confirms the order in their case-specific sentence.
3. Visible misspellings. A typo prints literally. Preview every template once before saving.

Variables save typing. They do not replace the agent reading the ticket.

How to organize your canned response library

A library with 40 well-named templates and one owner outperforms a library with 200 unnamed templates and no owner. Three habits keep it usable as the team grows.

• Naming convention. Prefix each template with its category: GREET-01 New ticket ack, SHIP-01 WISMO with tracking, REFUND-01 Refund processed. Agents searching for "ship" or "refund" pull the right cluster in one search.
• A single owner. One person owns the library and reviews it on a defined cadence. Without an owner, near-duplicates accumulate and no one knows which version is current.
• Quarterly audit. Every three months, the owner walks the full list. Anything used fewer than five times in the quarter is a candidate for deletion. Anything that quotes a policy is checked against the current policy document, because policy language drifts faster than templates do.
• Personal vs shared scoping. Help Scout, Freshdesk, and Zendesk all let agents save personal templates separately from the shared library. Personal templates are useful but should not appear in the team-wide search by default.

For Shopify and Magento stores running Helpdesk MX canned responses, order data variables like order number, tracking number, and order status pull live from the store on insert, so the templates above resolve without manual lookups.

For more category-depth, see the cluster pages on technical support canned responses and canned responses for live chat, where the tone and structure shift significantly from the email-focused templates here.