Free template library60 templates · 10 categories

60 canned response examples,ready to paste into any helpdesk.

A free library of canned responses for customer support - refunds, shipping delays, billing, account access, escalation, and more. Copy any template, swap the merge tokens, ship the reply.

Templates
60
Categories
10
Signup
None
Price
$0

What is a canned response?A pre-written reply your team reuses for the same recurring question.

A canned response is a saved customer service reply your support team can paste into a ticket, live chat, or email instead of retyping the same answer for the tenth time today. Different helpdesks call them different things - Intercom calls them "saved replies," Zendesk calls them "macros," Front calls them "templates," KalTalk just calls them canned responses - but they all do the same job. Used well, canned responses cut response time, keep your tone consistent, and free agents to spend their thinking on the cases that actually need it.

Used badly, they sound like a wall of pasted boilerplate. Every customer service canned response below is written to be edited - merge tokens like {first_name} and {order_id} are deliberate placeholders, and the supporting line above each example tells you exactly when to use it.

Browse by category, copy what you need, and adapt the voice to match your brand. Every example here is free to use - no signup, no email gate.

60 canned response examples.Browse, filter, copy. Free, no signup.

  • Greetings & first replies

    Live chat welcome

    First message in a live chat session.

    Hi {first_name}, thanks for reaching out to {company}. I'm {agent_name} - happy to help. What's going on?
    • chat
    • first-touch
  • Greetings & first replies

    Email reply opener

    Standard opener for a support email.

    Hi {first_name},
    
    Thanks for getting in touch. I read through your message and I want to make sure we get this sorted today.
    • email
  • Greetings & first replies

    Returning customer

    When the customer has contacted you before.

    Hey {first_name}, good to hear from you again. Looks like you were last in touch about {previous_topic} - is this related, or a new question?
    • chat
    • loyalty
  • Greetings & first replies

    After-hours auto-reply

    Set as the auto-reply when your team is offline.

    Thanks for your message, {first_name}. Our team is offline right now (we work {hours}, {timezone}). We'll reply first thing in the morning - usually within an hour of opening. If this is urgent, reply with the word URGENT and we'll prioritise you.
    • auto-reply
    • offline
  • Greetings & first replies

    Holiday auto-reply

    Set during a holiday closure.

    Hi {first_name}, thanks for reaching out. Our team is closed for {holiday_name} and we'll reopen on {return_date}. We'll reply to your message in the order it was received once we're back. Wishing you a great {holiday_name}.
    • auto-reply
    • holiday
  • Greetings & first replies

    AI to human handoff

    First message a human agent sends after taking over from an AI agent.

    Hi {first_name}, this is {agent_name} jumping in - I've read through the chat above so you don't need to repeat anything. Let me pick this up from here.
    • chat
    • handoff
  • Acknowledgments

    Got your message

    Confirm receipt before you have a full answer.

    Hi {first_name}, just confirming we got your message. I'm pulling the relevant details now and I'll have a real answer for you within the next {response_window}. Thanks for the patience.
    • email
  • Acknowledgments

    Need more info

    Ask for missing details without making it sound like a checklist.

    Thanks {first_name}. To get this fixed I'll need a couple of things from you:
    
    1. {detail_1}
    2. {detail_2}
    3. {detail_3}
    
    Once you send those over I'll dig in.
    • info-request
  • Acknowledgments

    Investigating

    Letting the customer know you have not forgotten while you investigate.

    Hey {first_name}, quick update - I'm still digging into this with the {team_name} team. No new info yet but I haven't dropped it. I'll be back to you by {next_update_time} either way.
    • update
  • Acknowledgments

    Issue confirmed

    Confirm a customer-reported issue is real.

    Hi {first_name}, you're right - I can reproduce what you're seeing. Apologies for the friction. Our engineers are looking at it now and I'll let you know the moment we have a fix in your hands.
    • bug
  • Acknowledgments

    Apology - delayed reply

    Open a reply that took longer than your normal SLA.

    Hi {first_name}, sorry for the slow turnaround on this one. Your message came in over the weekend and I should have caught it sooner. Here's what's going on:
    • apology
    • sla
  • Acknowledgments

    Thanks for the bug report

    When a customer flags a real bug.

    Thanks for catching this, {first_name}. Reports like yours are how we find the rough edges - I've logged it as {ticket_id} and routed it to engineering. I'll come back here with an update as soon as I have one.
    • bug
    • thanks
  • Refunds & returns

    Refund approved

    Confirm a refund has been processed.

    Hi {first_name}, your refund of {refund_amount} for order {order_id} has been processed. Depending on your bank it'll appear in your account within {refund_window}. Anything else I can do for you?
    • refund
    • approved
  • Refunds & returns

    Refund - outside policy

    Decline politely when the request falls outside your refund window.

    Hi {first_name}, I checked on this for you. Your order shipped on {ship_date}, which puts it outside our {refund_window} return window, so I'm not able to issue a full refund here. What I can do is {alternative_offer} - want me to set that up?
    • refund
    • declined
  • Refunds & returns

    Partial refund offer

    Offer a partial refund as a goodwill gesture.

    Hi {first_name}, I hear you. While I can't refund the full {full_amount}, I can credit {partial_amount} back to your card today as an apology for the experience. Let me know if that works and I'll get it processed.
    • refund
    • goodwill
  • Refunds & returns

    Return label sent

    Confirm a return label has been emailed.

    Hi {first_name}, you'll find a prepaid return label in your inbox - it's been sent to {customer_email}. Pop the item in any {carrier} drop-off and we'll refund {refund_amount} as soon as the package is scanned in.
    • return
    • shipping
  • Refunds & returns

    Refund eligibility check

    Acknowledge a refund request and explain next steps.

    Thanks for letting us know, {first_name}. Refund eligibility for {product} depends on {policy_factor} - I'm pulling your order now and I'll have an answer in the next few minutes.
    • refund
    • investigating
  • Refunds & returns

    Subscription cancellation refund

    Customer cancelled and is asking for a prorated refund.

    Hi {first_name}, I've cancelled your {plan_name} subscription effective today. Since you're {days_remaining} days into the billing cycle, I've credited {prorated_amount} back to your card - it should land within {refund_window}.
    • refund
    • subscription
  • Shipping & delivery

    Shipping delay

    Acknowledge a delay before the customer has to ask twice.

    Hi {first_name}, thanks for your patience on this one. Your order {order_id} is delayed in transit - latest tracking shows it at {last_location}. I've flagged it with the carrier and the new estimated delivery is {new_eta}.
    • shipping
    • delay
  • Shipping & delivery

    Lost package

    Confirm a package is officially lost and the next step.

    Hi {first_name}, after working with {carrier} I'm calling order {order_id} as lost in transit. Sorry about that. Two options: I can resend the order today on next-day shipping, or refund {refund_amount}. Which would you prefer?
    • shipping
    • lost
  • Shipping & delivery

    Tracking link

    Send the tracking number when a customer asks where their order is.

    Hi {first_name}, your order {order_id} shipped on {ship_date} via {carrier}. You can follow it here: {tracking_url}. Current ETA is {eta}.
    • shipping
    • tracking
  • Shipping & delivery

    Address change

    Confirm or decline a shipping address change.

    Hi {first_name}, I've updated the shipping address on order {order_id} to {new_address}. The order hasn't left the warehouse yet so this'll go to the new address. You'll get a fresh confirmation email shortly.
    • shipping
    • address
  • Shipping & delivery

    Address change - too late

    When the package has already shipped to the original address.

    Hi {first_name}, unfortunately order {order_id} was already picked up by {carrier} this morning, so I can't redirect it from our end. Your best bet is to file a redirect with {carrier} directly here: {carrier_redirect_url}. Let me know if it doesn't work and I'll figure something out.
    • shipping
    • address
  • Shipping & delivery

    Damaged on arrival

    Customer received a damaged item.

    Hi {first_name}, sorry your {product} showed up in that state - that's not the experience we want. Could you send a quick photo of the damage and the packaging so I can get a replacement on the way today? No need to return the original.
    • shipping
    • damaged
  • Account & login

    Password reset link

    Send a password reset link.

    Hi {first_name}, I've sent a password reset link to {customer_email}. It expires in 60 minutes - if it doesn't arrive within a couple of minutes check your spam folder, and let me know if you'd like me to resend.
    • account
    • password
  • Account & login

    Locked out account

    Customer hit too many failed login attempts.

    Hey {first_name}, your account was temporarily locked after several failed sign-in attempts - that's our system trying to protect it. I've unlocked it just now, so you can try signing in again.
    • account
    • security
  • Account & login

    Email change request

    Customer wants to change the email on their account.

    Hi {first_name}, happy to help. To switch your account email from {old_email} to {new_email}, I need to verify you own both addresses. I just sent a confirmation link to {new_email} - click it and you're done.
    • account
    • email
  • Account & login

    2FA recovery

    Customer lost their 2FA device.

    Hi {first_name}, sorry you've lost access to your 2FA codes - that one always sucks. For security I'll need to verify you in another way before I can reset it. Can you reply with the last 4 digits of the card on file plus the email on the account?
    • account
    • 2fa
    • security
  • Account & login

    Delete account confirmation

    Confirm an account deletion request.

    Hi {first_name}, I've confirmed your account deletion request. Your data will be wiped on {deletion_date} ({grace_period} grace period). If you change your mind before then just reply here and I'll cancel the deletion - after that, it's gone.
    • account
    • delete
  • Account & login

    Reactivation

    Customer wants to reopen a closed or deleted account.

    Welcome back, {first_name}. I've restored your account. All your {data_type} is back in place and your last sign-in was {last_login}. Let me know if anything looks off.
    • account
    • reactivation
  • Billing & payments

    Failed payment

    Tell a customer their card was declined and what to do.

    Hi {first_name}, your most recent payment of {amount} was declined by your bank. The most common reasons are an expired card, a billing address mismatch, or your bank flagging the charge. You can update your card here: {billing_url}.
    • billing
    • failed-payment
  • Billing & payments

    Plan upgrade confirmation

    Confirm a plan upgrade.

    Hi {first_name}, you're on {new_plan} as of today. The prorated charge of {prorated_amount} hit your card just now, and your next full bill of {next_amount} will be on {next_billing_date}.
    • billing
    • upgrade
  • Billing & payments

    Plan downgrade

    Confirm a plan downgrade.

    Hi {first_name}, I've moved you down to {new_plan}. The change kicks in on {effective_date} so you keep your current limits until then. Your next bill on {next_billing_date} will be {new_amount}.
    • billing
    • downgrade
  • Billing & payments

    Invoice request

    Send a copy of an invoice.

    Hi {first_name}, I've attached the invoice for {invoice_period} to this reply. You can also pull all your invoices any time from {billing_portal_url}.
    • billing
    • invoice
  • Billing & payments

    Duplicate charge

    Customer reports a duplicate charge.

    Hi {first_name}, I checked your account and you're right - {charge_amount} was charged twice on {charge_date}. I've refunded the duplicate just now. It should clear in {refund_window}, and if it isn't back by then send me a screenshot of your statement and I'll dig in.
    • billing
    • duplicate
  • Billing & payments

    Cancellation - retain

    Soft retention reply to a cancellation request.

    Hi {first_name}, sorry to see you thinking about cancelling. Before I process it - is there a specific thing that didn't work out? If it's {common_reason_1} or {common_reason_2}, I might have a fix or a discount that helps. Either way, just say the word and I'll cancel.
    • billing
    • cancellation
    • retention
  • Bug reports & tech issues

    Asking for repro steps

    Get the details engineering will need.

    Hey {first_name}, to get this in front of our engineers fast, can you send:
    
    - The exact steps you took before it happened
    - A screenshot or short screen recording
    - Your browser + OS
    
    With those three I can usually have a fix scheduled the same day.
    • bug
    • info-request
  • Bug reports & tech issues

    Bug logged

    Confirm a bug has been logged.

    Thanks {first_name}, I've logged this as {ticket_id} and it's in front of engineering now. I'll comment back here as soon as it's fixed - usually that's a few days for something this size.
    • bug
  • Bug reports & tech issues

    Bug fix shipped

    Tell the customer their bug has been fixed.

    Hi {first_name}, the fix for {bug_summary} shipped this morning. You shouldn't need to do anything - just reload the page. Let me know if you're still seeing the same behaviour, and thanks again for catching it.
    • bug
    • resolved
  • Bug reports & tech issues

    Known issue

    Customer hit something already on the bug board.

    Hey {first_name}, this one's a known issue on our side - we're tracking it as {ticket_id}. The fix is in QA and we expect it to ship by {eta}. Sorry for the friction in the meantime.
    • bug
    • known-issue
  • Bug reports & tech issues

    Cannot reproduce

    When the issue does not reproduce on your end.

    Hi {first_name}, I tried to reproduce this on my end and everything looked normal - which usually means it's environment-specific. Could you send me a screen recording of the steps when you next see it? That'll let me match exactly what your browser is doing.
    • bug
  • Bug reports & tech issues

    Outage update

    Update during an active outage.

    Hi {first_name}, we're aware of {service_name} being down right now. Our team is already on it and we're posting live updates at {status_page_url}. I'll come back here the moment it's resolved.
    • bug
    • outage
  • Feature requests

    Logged feature request

    Confirm a feature request has been logged.

    Thanks {first_name}, that's a good idea - I've logged it on the roadmap. We can't promise everything we log will ship, but the team reviews this list every quarter. I'll let you know if it's picked up.
    • feature
  • Feature requests

    On the roadmap

    Tell a customer the feature is coming.

    Good news {first_name} - {feature_name} is already on our roadmap for {target_quarter}. I'll add you to the early-access list so you hear about it the day it ships.
    • feature
    • roadmap
  • Feature requests

    Feature exists - here is how

    Customer asked for a feature that already exists.

    Hey {first_name}, good news - this is already a thing. You can find {feature_name} at {feature_path}. Quick walkthrough: {short_steps}.
    • feature
    • discovery
  • Feature requests

    Polite decline

    Politely decline a feature request that does not fit.

    Thanks for the suggestion, {first_name}. {feature_name} isn't something we plan to build - it sits outside what we want {company} to be. I know that's not the answer you were after. If you'd like to share more about the underlying problem you were trying to solve, I might be able to point you at a workaround or a tool that does fit.
    • feature
    • decline
  • Feature requests

    Beta access invite

    Invite a customer to a private beta.

    Hi {first_name}, you've been bumped to the front of the queue for the {feature_name} beta. Here's your access link: {beta_url}. We'd love your honest feedback - good, bad, or weird. Reply here any time.
    • feature
    • beta
  • Feature requests

    Roadmap link

    Point a customer at your public roadmap.

    Hey {first_name}, the easiest way to track what we're working on is our public roadmap: {roadmap_url}. You can upvote requests there and you'll see new ones land as we plan them.
    • feature
    • roadmap
  • Escalation & handoff

    Offer human handoff

    Offer to route the conversation to a human teammate (do not assume - ask first).

    Hey {first_name}, I want to make sure you get the right help here. Want me to bring in one of our human teammates? They're online and can pick this up in a few minutes.
    • escalation
    • handoff
  • Escalation & handoff

    Routing to specialist

    Hand off to a specialist team.

    Hi {first_name}, this one is best handled by our {specialist_team} team - they have the access and the context to fix this properly. I'm looping them in now and they'll reply on this thread within {sla_window}.
    • escalation
  • Escalation & handoff

    Manager escalation

    Customer asked to speak to a manager.

    Hi {first_name}, completely understand. I've looped in {manager_name}, our {manager_role} - they'll be in touch within {sla_window}. They'll have the full thread context so you won't need to start over.
    • escalation
    • manager
  • Escalation & handoff

    Engineering escalation

    Hand off a technical issue to engineering.

    Hey {first_name}, this is past what I can fix from support - I've escalated to engineering. They have the logs and your account context, and they'll reply directly here. Expected first update by {next_update_time}.
    • escalation
    • engineering
  • Escalation & handoff

    After-hours escalation

    Acknowledge an urgent message during off-hours.

    Hi {first_name}, I've flagged this as urgent and our on-call engineer has been paged. They'll be in touch within {oncall_sla}. Sorry for the timing - you're not alone on this.
    • escalation
    • urgent
  • Escalation & handoff

    Confirming customer wants escalation

    Asking the customer to confirm they want a human or manager handoff.

    Hey {first_name}, I can keep helping or I can hand this to {next_step_owner} - whichever you'd prefer. Just say the word.
    • escalation
  • Closing & follow-up

    Resolved - close ticket

    Wrap up a resolved ticket.

    Glad we got that sorted, {first_name}. I'll go ahead and close this ticket - if anything else comes up, just reply here and it'll reopen on my desk.
    • closing
  • Closing & follow-up

    Anything else

    Check before closing.

    Hi {first_name}, anything else I can help with on this one before I close it out?
    • closing
  • Closing & follow-up

    Awaiting reply - close

    Close after a long silence.

    Hi {first_name}, I haven't heard back so I'm going to close this out for now. If the issue is still happening just reply here any time and we'll pick it back up - no need to start a new ticket.
    • closing
    • stale
  • Closing & follow-up

    Feedback request

    Ask for a CSAT rating after resolution.

    Thanks for sticking with me on this one, {first_name}. If you've got 10 seconds, we'd love a quick rating on how this conversation went: {csat_url}. Either way, glad we got you sorted.
    • closing
    • csat
  • Closing & follow-up

    Follow-up check-in

    Soft follow-up a few days after resolution.

    Hey {first_name}, just checking back in - is {issue_summary} still working as expected? Happy to keep helping if anything's off.
    • closing
    • follow-up
  • Closing & follow-up

    Resolved - feature unlocked

    Close a ticket where the resolution was a feature or setting unlock.

    Hi {first_name}, you should be all set - {feature_name} is now active on your account. I'll close this ticket out, but reply here any time if you bump into anything else.
    • closing
    • resolved

How to use thesewithout sounding like a bot.

  1. Edit every send.

    Canned responses are a starting line, not a finished reply. Open every template, swap the merge tokens, add the one-line of personal context, then send. The minute customers can tell they're getting boilerplate, the template stops doing its job.

  2. Match your brand voice.

    If your support voice is warm and casual, rewrite the formal templates in this library to match before you save them. If it's clinical and precise, do the opposite. Consistency between marketing copy and support copy is what makes a brand feel coherent.

  3. Surface the next step.

    Every reply should end with a clear next step - a question, an action, a timeframe. "Let me know if anything else comes up" is a non-answer. "I'll be back to you by 4pm with an update either way" is a commitment.

  4. Do not auto-fire on edge cases.

    Refunds, escalations, and account deletions are reversible only at cost. Templates for these flows should require a human click before sending - never wire them into a fully automated trigger.

  5. Audit quarterly.

    The product changes, the policy changes, the team changes. Re-read every canned response in your library every quarter and kill the ones that no longer reflect how you operate. Stale templates do more damage than missing ones.

Frequently asked questions.Quick answers from the team.

  • What is a canned response?

    A canned response is a saved customer service reply your team can paste into a chat, ticket, or email instead of retyping the same answer every time. The best teams treat them as starting drafts - they get edited before sending, not blasted out as-is.

  • How many canned responses should we have?

    Most support teams run between 30 and 80 active templates. More than that and agents stop being able to find the right one; fewer than that and you end up retyping the same answers. Track which templates are actually used and prune the dead ones every quarter.

  • Are these canned response examples free to copy?

    Yes. Every example on this page is free to copy, paste, edit, and use commercially. No attribution required. They are written to be a useful starting point - the actual brand voice should be yours.

  • Should AI agents use canned responses?

    AI agents should be grounded on your knowledge base, not on rigid canned templates. The right pattern is: AI generates the reply from your real policies and product docs, and falls back to a human if it isn't confident. Canned responses are a tool for human agents, not a leash for an LLM.

  • What is the difference between a canned response and a saved reply?

    Functionally, nothing - different vendors call them different things. Intercom calls them "saved replies," Zendesk calls them "macros," Front calls them "templates," KalTalk just calls them canned responses. They all do the same job: a saved chunk of text you can fire into a conversation in a click.

More from the toolbox.Free, no signup, no email gate.

Stop retyping. Start shipping replies.Drop these straight into KalTalk and your team is live in minutes.

KalTalk gives your support team one inbox, one AI agent grounded on your knowledge base, and a canned-response library out of the box - on a flat tier, with no per-resolution surcharge. Free tier available, no credit card.