75+ Canned Responses: Templates & Guide to Scale Support

Customers expect instant answers, but rushing through support tickets usually leads to typos and impersonal service. Balancing speed and empathy is the hardest part of support, especially during peak seasons.

Fortunately, canned responses help you maintain that balance by handling repetitive work for you. We have compiled a comprehensive guide to using them effectively, along with 75+ ready-to-use scripts for billing, technical issues, and difficult conversations. Let’s check them out!

What are canned responses?

Canned responses are pre-written text templates that support agents use to answer repetitive questions efficiently. Also known as saved replies or macros, these tools let your team insert accurate, policy-compliant answers into a conversation without retyping the same explanation every time. The goal is to speed up the workflow while maintaining consistent communication across the entire support team.

You will typically find canned responses used in high-volume channels where speed is critical:

• Live chat: To instantly answer common queries like shipping times or hours of operation.
• Email: To provide standardized, detailed explanations for complex issues like refunds or technical troubleshooting. This is where having a library of customer service email templates becomes invaluable for maintaining professionalism.
• Social media: To quickly acknowledge public comments or direct messages before moving them to a private channel.

It is important to distinguish canned responses from other automation tools, as they serve different purposes within the support ecosystem.

Feature	Canned responses	Auto-replies	AI Replies
Who triggers it?	The human agent selects and sends it.	The system sends it automatically based on rules.	The AI suggests a draft for the agent.
Customization	Editable by the agent before sending.	Fixed content (usually cannot be changed per case).	The agent reviews and edits the draft.
Primary goal	Efficiency with a human touch.	Immediate acknowledgment or expectation setting.	Predicting answers to save drafting time.

You can see that canned responses offer a strategic balance between speed and quality. Unlike auto-replies, which are purely robotic, or AI suggestions, which can sometimes hallucinate incorrect information, canned responses give your agents a reliable foundation to personalize for each customer.

Benefits of canned responses

Here are 3 benefits of canned responses:

• Faster response times, lower FRT & AHT: Agents do not have to retype the same answers for repeat questions like order status, policies, or basic troubleshooting. That saves minutes across a shift and helps customers get answers sooner. This matters because HubSpot found that 90% of customers rate an “immediate” response as important, and 60% define “immediate” as 10 minutes or less.
• More consistent, higher quality replies: A shared template library keeps wording, policy details, and tone aligned across agents. It also reduces mixed messages when customers switch between channels. Salesforce Research reports that 79% of consumers expect consistent experiences across all their engagements.
• Easier onboarding and coaching: TechTarget notes that new call center agents can take 2-8 months to reach proficiency, depending on complexity. Canned responses help shorten the ramp by giving new agents approved wording for common cases, reducing the number of avoidable mistakes while they learn. Coaching also gets easier because leads and QA can review one specific template, then tell the agent exactly what to personalize and when to use a different macro.

75+ Best canned response templates

Below is a comprehensive library of canned response templates categorized by common support scenarios. You can copy, paste, and customize these scripts to fit your brand voice immediately.

Greetings, triage & routing

The opening of a conversation sets the tone and controls the flow. A strong greeting should immediately guide the customer toward a solution, avoiding back-and-forth “ping-pong” messaging. The goal is to ask for essential details, such as an Order ID or email address, early so you can categorize the issue quickly. If you need time to investigate, always send a brief acknowledgment with a time estimate before you go silent.

Welcome & opening

• Standard welcome: “Hi there! Thanks for reaching out to [Company Name]. My name is [Agent Name]. How can I help you today?”
• Returning customer: “Welcome back, [Customer Name]! Good to see you again. What can I do for you today?”
• During high volume: “Hi! Thanks for contacting us. We are experiencing higher than normal volume today, but I will be with you in about [Time] minutes.”

Acknowledge + set expectations (queue/ETA)

• Standard acknowledgment: “I understand you are having an issue with [Issue]. Let me check that for you right now.”
• Investigating: “I need to look into your account details to see what happened. Please give me 2-3 minutes to check our records.”
• Complex issue: “This might take a bit of investigation. I will need to check with our [Department] team. I will get back to you within [Timeframe].”

Clarifying questions (collect essentials)

• Order ID request: “To help me find your order quickly, could you please provide your Order ID (it starts with #)?”
• Account email: “Could you confirm the email address associated with your account so I can pull up your details?”
• Device details: “To better understand the issue, what device and browser are you currently using?”

Transfer/handoff to teammate

• Department transfer: “I am going to connect you with our [Specialist Team], who can better assist with this technical issue. Hold on just a moment.”
• Manager handoff: “I see this requires further approval. I will escalate this to my manager, [Name], who will be in touch shortly.”
• Shift change: “My shift is ending, so I am passing your case to my colleague [Name]. They have all the context and will continue helping you right away.”

After-hours/offline routing

• Standard offline: “Thanks for your message! We are currently closed. Our hours are [Hours]. We will get back to you first thing tomorrow morning.”
• Weekend message: “Hi! We are out of the office for the weekend. We will respond to your message on Monday. In the meantime, check out our Help Center here: [Link].”
• Holiday closure: “Happy Holidays! Our team is taking a break to celebrate. We will be back on [Date] and will reply to you then.”

Order & Delivery

When a customer asks you about their order, they want reassurance, not vague promises. The goal here is to reduce anxiety by providing a specific status and the next update time. Remember to always include a tracking link when available, and avoid guaranteeing delivery dates unless the carrier has confirmed them.

Order status/tracking request

• Standard status: “I checked your order #[ID], and it is currently [Status]. You can track the full progress here: [Tracking Link].”
• Pre-shipment: “Your order is being packed right now! You will receive an email with the tracking number as soon as it ships, likely by [Date].”
• In transit: “Great news! Your package is on its way and is currently at [Location]. The estimated delivery date is [Date].”

Shipping delay updates

• Proactive update: “We wanted to let you know that your order #[ID] is slightly delayed due to [Reason]. We now expect it to arrive by [New Date].”
• Weather delay: “Due to severe weather in [Area], carriers are experiencing delays. Your package is safe but might arrive 1-2 days later than expected.”
• Apology for the delay: “I am sorry for the wait. It looks like your package is stuck at [Location]. I have contacted the carrier for an update and will let you know as soon as I hear back.”

Delivered but not received

• Initial check: “I see the tracking says ‘Delivered,’ but I understand you haven’t received it. Could you please check with neighbors or your front desk? Sometimes carriers mark items as delivered a few hours early.”
• Investigation start: “Since you still can’t find the package, I will open an investigation with the carrier. This usually takes [Number] days. I will keep you posted.”
• Replacement offer: “It appears your package was lost in transit. I can ship a replacement to you immediately or issue a full refund. Which would you prefer?”

Change address/cancel order

• Address change (success): “I have successfully updated your shipping address to [New Address]. You will see this reflected in your confirmation email shortly.”
• Address change (too late): “I am sorry, but since the order has already shipped, I cannot change the address now. I recommend contacting the carrier directly here: [Link].”
• Cancellation success: “I have cancelled your order #[ID] as requested. You will not be charged, and a confirmation email is on its way.”

Close + recap

• Standard close: “Is there anything else I can help you with regarding your order today?”
• Recap: “Just to recap: I have updated your address and resent the tracking link. Let me know if you need anything else!”
• Friendly sign-off: “Thanks for shopping with us! We hope you enjoy your [Product]. Have a great day!”

Returns & Refunds

Clear communication is key when handling returns. You need to be firm on policy while maintaining a helpful tone. Structure your response: first check eligibility, then explain the steps and timeline. Even if you must deny a request, try to offer an alternative solution.

Eligibility check

• Policy check: “To start the return process, could you confirm if the item is still in its original packaging and unused?”
• Timeframe check: “I see your order was delivered on [Date]. Our return policy covers 30 days, so you are still eligible for a full refund.”
• Item condition: “Could you please send a photo of the item? This helps us confirm the condition and speed up your return approval.”

Return instructions

• Standard instructions: “Please pack the item securely and attach the prepaid label I just emailed you. Drop it off at any [Carrier] location.”
• Self-ship: “Please mail the return to [Address] and keep your receipt. Once we receive it, we will process your refund.”
• In-store return: “You can also return this item to any of our physical stores. Just show your order confirmation email to the cashier.”

Refund timeline + confirmation

• Refund processed: “I have processed your refund of $[Amount]. It should appear on your original payment method within [Number] business days.”
• Refund initiated: “We have received your return! I have initiated the refund process, and you will see the funds shortly.”
• Partial refund: “As discussed, I have issued a partial refund of $[Amount] for the damaged item. Let me know if you have any other questions.”

Out-of-policy refund

• Denial with alternative: “I am afraid I cannot offer a refund since this purchase was made over [Number] days ago. However, I can offer you a store credit for future use.”
• Final sale: “Since this item was marked as ‘Final Sale,’ it is not eligible for return. I apologize for any inconvenience this causes.”
• Exception (one-time): “Although this is outside our normal policy, I can make a one-time exception and process a refund for you as a courtesy.”

Close + case ID/next steps

• Next steps: “Once you drop off the package, keep an eye on your email for the refund notification. Let me know if you need help with anything else.”
• Case ID: “For your reference, your case ID is #[ID]. Feel free to quote this if you contact us again.”
• Feedback request: “I am glad I could help sort this out. If you have a moment, we would love to hear your feedback on our support.”

Billing & Account security

When dealing with money and data, trust is paramount. Explain charges clearly and never ask customers to share sensitive payment details, such as full credit card numbers, in chat. Always redirect them to a secure portal for updates.

Invoice/receipt request

• Send invoice: “I have attached a PDF copy of the invoice for order #[ID] to this chat. Let me know if you need anything else.”
• Resend email: “I have just resent the receipt to [Email Address]. Please check your spam folder if you don’t see it in a few minutes.”
• Past invoices: “You can view and download all your past invoices by logging into your account and going to ‘Order History’.”

Charge explanation

• Breakdown: “The total of $[Amount] includes $[Product Price] for the item, $[Tax] for tax, and $[Shipping] for shipping. Does that clarify the charge?”
• Subscription charge: “This charge is for your monthly subscription renewal on [Date]. It renews automatically unless cancelled.”
• Double charge: “I see two pending charges. One is likely a temporary hold that will disappear in a few days. If it posts, please let us know.”

Update billing details

• Secure link: “To update your card on file, please use this secure link: [Link]. For your security, do not share your card details here in the chat.”
• Failed payment: “It looks like the payment failed. Please update your billing information in your account settings and retry the transaction.”
• Expiry update: “Your card on file is expiring soon. You can update the expiration date easily in your ‘Billing’ tab.”

Account verification/ownership check

• Security question: “For security purposes, could you please confirm the last four digits of the card used for the purchase?”
• Email verification: “I have sent a verification code to [Email]. Please provide that code here so I can access your account.”
• Identity check: “Before we proceed with this change, can you confirm your full billing address and phone number?”

Payment safety redirect

• Do not share: “Please do not type your full credit card number here. It is not secure. Use our encrypted payment portal instead.”
• Portal redirect: “I cannot take payment over chat. Please complete your purchase securely at this link: [Link].”
• Phishing warning: “We will never ask for your password or full card number via email or chat. Please stay safe!”

Technical support

Technical issues can be frustrating, so the goal is to diagnose the problem quickly. Let’s use a standard checklist to gather environment details (device, browser) and steps to reproduce the bug. In addition, focus on collaborative language, such as “let’s try,” rather than blaming the user.

Bug acknowledgment (set expectations)

• Standard ack: “Thanks for reporting this. I am sorry you are experiencing this glitch. Let’s see if we can get it fixed together.”
• Known issue: “We are aware of this issue, and our engineering team is already working on a fix. I will notify you as soon as it is resolved.”
• Investigation: “That sounds frustrating. I need to ask a few questions to understand exactly what is happening.”

Gather details

• Browser/device: “Could you tell me which browser (e.g., Chrome, Safari) and device you are using? This helps us narrow down the cause.”
• Screenshots: “If possible, could you share a screenshot or screen recording of the error message? That would be very helpful.”
• Steps to reproduce: “What specific steps were you taking right before the error occurred? This helps us recreate the issue.”

Troubleshooting checklist

• Cache clear: “Please try clearing your browser cache and cookies, then refresh the page. Does that resolve the issue?”
• Incognito mode: “Could you try opening the page in an Incognito/Private window? This tells us if a browser extension is interfering.”
• Update app: “Please ensure you are using the latest version of our app. Updating often fixes these types of bugs.”

Escalate to engineering

• Escalation: “I have gathered all the details and am escalating this to our technical team for a deeper look. Your ticket ID is #[ID].”
• Timeline: “Our engineers will review this. While I don’t have an exact fix time, I will update you within [Number] hours.”
• Priority: “Since this is affecting your ability to log in, I have marked this as high priority for our developers.”

Close + follow-up plan

• Follow-up: “I will keep this ticket open and email you as soon as I have an update from the tech team.”
• Interim solution: “In the meantime, you can use [Workaround] to access the feature. Thanks for your patience!”
• Resolved: “It looks like the fix worked! Is everything running smoothly for you now?”

Service recovery & Boundaries

These templates are for difficult moments where tensions run high. The goal is to de-escalate emotions while protecting your company’s policies. You ought to acknowledge the customer’s frustration without over-apologizing, while still acknowledging legal liability.

This is where applying strong conflict resolution tips for excellent customer service can turn a negative experience into a positive customer retention opportunity. Always offer a constructive path forward, whether it is a discount or an escalation. For a deeper look at proven techniques, see our guide on dealing with angry customers.

Apology + accountability

• Sincere apology: “I am truly sorry about this experience. This is not the level of service we aim to provide.”
• Owning the mistake: “You are right, we dropped the ball on this one. I apologize for the oversight and want to make it right.”
• Empathy: “I completely understand why you are frustrated. I would be too if I were in your shoes.”

De-escalation for angry customers

• Listening: “I hear your frustration, and I want to help resolve this. Let’s look at what options we have available.”
• Calm reassurance: “Please know that I am here to help you. I am going to do everything I can to sort this out for you.”
• Focus on solution: “Let’s focus on how we can fix this. I can offer [Option A] or [Option B]. Which works better for you?”

Discount request handling

• Approval: “As a thank you for your patience, I can offer you a [Number]% discount on your next order. Here is the code: [Code].”
• Denial: “We typically don’t offer discounts on request, but you can check our ‘Sale’ page for current deals.”
• Conditional: “If you subscribe to our newsletter, you will receive a welcome discount code immediately.”

Escalation to manager

• Handover: “I understand you would like to speak to a supervisor. I will pass your contact info to my manager, [Name].”
• Timeframe: “My manager will review your case and contact you via email within [Number] hours.”
• Policy firmness: “While I can pass this to a manager, please note that they will likely confirm the same policy regarding [Issue].”

Retention/win-back

• Save attempt: “I am sorry to hear you want to cancel. Is there anything we could do to improve your experience and keep you with us?”
• Feedback: “We value your business and would hate to lose you. Could you tell us more about why you are leaving so we can do better?”
• Win-back offer: “If you decide to stay, I can apply a free month of service to your account right now.”

Best practices for canned responses

Using canned responses effectively requires more than just copying and pasting text. To keep your support feeling human while maintaining speed, follow these guidelines:

• Treat them as drafts, not final answers: Never send a macro without reading it first. Always personalize at least one detail, such as the customer’s name or a reference to their specific product, to ensure the message feels tailored to their situation.
• Keep it concise and scannable: Customers often skim messages, especially in live chat. Break complex explanations into bullet points or numbered steps, and avoid long walls of text that can be overwhelming on mobile devices. Following proper customer service chat etiquette also helps keep your messages focused and professional.
• Empathize and apologize: Your responses should never be robotic, so use appropriate customer service phrases, genuinely empathetic language, and an apologetic tone when necessary. Even when using a script, showing emotional intelligence in customer service can make the difference between a satisfied customer and a churned one.
• Regularly audit and update: Your policies and product features change, and your saved replies should too. Set a quarterly reminder to review your most-used templates to ensure they still align with your current brand voice and operational procedures.
• Don’t rely solely on tools: Remember that canned responses are just one part of the equation. Your agents still need to develop soft skills in customer service, like active listening and adaptability, to handle complex cases where a template just isn’t enough.

How Chatty helps you deploy canned responses faster

If you run a Shopify store, efficiently managing support requests is critical to keeping sales moving. Chatty is a dedicated live chat app built for Shopify merchants that streamlines how you handle customer conversations. Beyond basic messaging, it integrates deeply with your store data to help you respond faster and more accurately.

Here is how Chatty optimizes your workflow:

• Customizable quick replies: You can build a library of “Quick Replies” for your most frequent questions. Assign shortcuts and categories to organize them, and easily edit or toggle them off as your store policies evolve.

• Direct FAQ insertion: Access your entire FAQ Hub directly within the chat interface. This allows agents to insert detailed, pre-approved answers without creating hundreds of separate macros.

• Instant discount & product sharing: When a customer asks for a deal or product recommendation, you can send a discount code or product card with a “Shop Now” button directly in the chat. This removes friction and helps convert inquiries into sales immediately.

• Internal coaching tools: The “Notes” feature allows team leads to leave private feedback or @tag specific members. This enables real-time coaching on live tickets without the customer ever seeing the internal discussion.

Used well, these features help your team reply faster while keeping wording, links, and offers more consistent from one agent to the next.

The Bottom Line

Canned responses are about working smarter, not harder. We know that support can get chaotic, but having these reliable scripts at your fingertips brings order to the noise and keeps your customers satisfied. Give them a try, and you will wonder how your team ever managed without them!

FAQ