Canned responses for customer service

Eighteen reusable replies for refunds, delivery delays, billing, bugs, account access, and follow-up—plus the parts that should never be sent without checking.

By Rex (Kuan Hsiung Chen) · Updated 24 September 2026

What belongs in a customer service canned response?

Save the part of a support reply that remains accurate across many tickets: what information to collect, which step comes next, how a standard process works, or how you will follow up. Do not save facts that change without making them visible variables.

A reliable response usually contains four pieces: acknowledgement, one specific detail from the current conversation, the next action, and a realistic timeframe. If the situation is emotional or unusual, use the template only for structure and write the important paragraph manually.

Refund and billing responses

1. Refund approved

Hello {{customer_name}}, we’ve approved the refund for {{order_or_invoice}} and returned {{amount}} to the original payment method. It should appear within {{timeframe}}. If it has not arrived after that date, reply here and we’ll check the transaction.

2. More information needed

Hello {{customer_name}}, we can review the refund request as soon as we have the order number, purchase date, and reason for the request. Please reply with those details; do not send a full payment-card number.

3. Duplicate charge

Thanks for flagging the duplicate charge on {{date}}. We’re checking the two transaction references now. We’ll confirm whether one is a temporary authorization or whether a refund is required by {{timeframe}}.

4. Invoice request

We can provide the invoice for {{purchase}}. Please confirm the billing name and any company or tax details that must appear on it, and we’ll send the completed document to {{delivery_address}}.

Delivery and order responses

5. Shipment delayed

I’m sorry {{order_number}} has not arrived when expected. The latest confirmed status is: {{carrier_status}}. We will check again by {{next_update}} and reply in this thread with the next step.

6. Order shipped

Your order {{order_number}} shipped on {{ship_date}}. You can follow it with {{tracking_link}}. The current estimated delivery window is {{delivery_window}}.

7. Item missing from an order

Thanks for telling us that {{missing_item}} was not in the package. Please send a photo of the items and packing slip you received. Once we verify the shipment, we’ll confirm a replacement or refund.

Technical support responses

8. Bug report received

Thanks for the clear report. We recorded the issue as {{ticket_id}} with these details: {{specific_detail}}. The team is investigating, and we’ll follow up when we have a confirmed fix or workaround.

9. Steps to reproduce needed

We haven’t been able to reproduce the problem yet. Could you send the page or feature you were using, the exact steps before the error, the browser and version, and a screenshot with private information removed?

10. Known issue with workaround

This is a known issue affecting {{affected_area}}. Until the fix is released, the current workaround is: {{workaround}}. We’ll update this conversation when the permanent fix is available.

11. Issue resolved

We released a fix for {{issue}} on {{date}}. Please refresh the page and try the same action again. If the problem continues, reply with what you see now so we can reopen the investigation.

Account and access responses

12. Password reset

Use the password-reset link on {{login_page}} and check the inbox for {{account_email}}. The link expires after {{timeframe}}. We will never ask you to send your password in a support message.

13. Identity verification required

Before changing the account, we need to verify ownership. Please complete {{approved_verification_step}}. Do not send passwords, recovery codes, or full payment-card details.

14. Account change completed

The requested change to {{account_detail}} is complete. Please sign out and back in before checking it. If the old value still appears, reply with a screenshot and the page URL.

Expectation-setting and follow-up

15. Escalated to another team

I’ve sent this to {{team_name}} with the conversation history and the details you provided. You do not need to repeat the issue. We expect the next update by {{timeframe}}.

16. No immediate answer

I don’t want to guess at the answer. I’m checking {{question}} with the right person and will reply by {{timeframe}}, even if the update is that we still need more time.

17. Waiting on the customer

When you have a moment, please send {{missing_information}} so we can continue. We’ll keep the request open until {{date}}; after that, you can reply to reopen it.

18. Closing the conversation

It looks like {{issue}} is now resolved. We’ll close this request, but replying here will reopen the conversation if anything remains.

Template, AI draft, or manual reply?

How to use one library across support tools

Help desks usually keep macros inside their own product. That works until the conversation moves to a CRM, social message, community, or web form. A browser text expander keeps the reusable text at the field level instead. The same personal library can then appear in standard textareas and rich-text fields across normal websites.

Keyjot combines that library with AI drafting. Use a number key when the approved wording already exists. When the answer is new, select the relevant message, add one line of intent, and generate the changing part without leaving the reply field.