WhenA new chat or ticket you can start on right away.
Shortcut/hi
Personalize: Swap "pull up your details" for the thing you're actually checking (your order, your account, the error you mentioned) so the customer knows you read the message.
Canned responses are pre-written replies a support team saves and inserts with a shortcut. Here are 76 examples for chat and email, grouped by situation: order status, shipping delays, refunds, billing, account access, bugs, apologies, escalations and closing. Each one says when to send it and how to make it sound like you.
By Ray, pen name of the Asks founderUpdated 76 templates
Replace everything in {braces} before you send. Most help desks call these saved replies, macros or snippets; the idea is the same. The best ones answer the question completely, sound like a person, and leave room for one line that only applies to this customer.
The first reply sets the tone. Show you read the message, say what happens next, and give a time.
WhenA new chat or ticket you can start on right away.
Shortcut/hi
Personalize: Swap "pull up your details" for the thing you're actually checking (your order, your account, the error you mentioned) so the customer knows you read the message.
WhenYou need to check another system or ask a colleague before you can answer.
Shortcut/checking
Personalize: Give a real time ("10 minutes", "by 3 pm") instead of "shortly". If you're going to miss it, send an update before the deadline, not after.
WhenThe message is missing something you need before you can act.
Shortcut/details
Personalize: Ask for everything you need in one message. A second "one more thing" request feels like a runaround.
WhenThe issue is complicated and you want to check you've got it right before you start.
Personalize: Restate the problem in one sentence, in your own words. If you misread it, the customer corrects you now instead of after a wrong fix.
WhenThe question belongs to another team, such as billing or technical support.
Personalize: Only promise "you won't need to repeat yourself" if the handoff really carries the conversation over. If it doesn't, give the customer a reference number instead.
WhenA message arrives after your team has gone home.
Personalize: Point to the one self-serve link that answers most after-hours questions for your business: order tracking, the returns portal or the booking page.
"Where is my order?" is the most common question in e-commerce support. Lead with the facts the customer can verify: the date, the carrier and the link.
WhenThe order has shipped and tracking is live.
Shortcut/track
Personalize: Paste the carrier's estimate, not your standard shipping time. Customers open the tracking page and notice when the two disagree.
WhenThe order is paid but still being prepared.
Personalize: If you know why it's taking longer (a pre-order item, engraving, a busy week), say so. A reason makes a wait feel planned.
WhenThe carrier page shows no new scan for several days.
Personalize: Tell the customer what you did, not only what usually happens. "I've asked the carrier" is the line that calms people down.
WhenTracking says delivered and the customer says it isn't there.
Personalize: Give a specific date to come back and say now what you'll do then. It saves a second round of back-and-forth.
WhenThe customer wants a different shipping address and the order hasn't left yet.
Personalize: Paste the full new address back in the reply. Customers catch their own typos when they see the address written out.
WhenThe order already left and you can't change the address yourself.
Personalize: Check that your carrier offers redirects before you suggest it. Sending someone to a dead end costs more trust than the delay itself.
WhenA customer asks to cancel and the order hasn't shipped.
Personalize: Put the amount and the payment method in the message. "Your refund is processed" makes people log in to check; the number doesn't.
WhenThe order includes an item that isn't in stock yet.
Personalize: Only offer a split shipment if you're willing to pay for the second parcel. Decide that before the template goes live, not in the chat.
Late, lost, damaged or wrong. Own the problem, say what you've already done, and don't make the customer prove it twice.
WhenYou know an order will be late before the customer asks.
Personalize: Send it before the original date passes. The same news feels like good service when you send it first and like an excuse when the customer has to ask.
WhenThe carrier is held up by weather, strikes or peak volume.
Personalize: Don't make the carrier sound like someone else's problem. You chose the carrier; the customer chose you.
WhenThe carrier confirms the parcel is lost, or it's well past the latest delivery date.
Personalize: Decide in advance what happens if the original parcel turns up later, and add that sentence to the template so every agent says the same thing.
WhenThe customer reports a broken or damaged item.
Personalize: Only ask for photos if you or the carrier really need them for a claim. If you don't, skip straight to the fix.
WhenThe customer received something they didn't order.
Personalize: Ship the right item before the wrong one comes back. Making the customer wait for your return scan punishes them for your mistake.
WhenPart of the order wasn't in the box.
Personalize: Check the packing record before you send this. If it shows the item was packed, ask whether it may have shipped in a separate parcel first.
WhenAn international customer asks about duties or a fee to receive the parcel.
Personalize: Write the {duties_policy} sentence once per destination country and keep it exact. Vague answers about customs turn into chargebacks.
Refund replies are read twice and screenshotted. Put the amount, the method and the timeline in writing, and pair every "no" with something you can do.
WhenA customer asks how to send something back.
Shortcut/return
Personalize: If your returns portal handles everything, the link is the answer. Keep the steps to three lines; the portal has the details.
WhenYou've just processed a refund.
Personalize: Include the payment reference. It's the first thing a bank asks for if the money doesn't appear.
WhenThe customer says the refund hasn't arrived.
Personalize: Give the exact date you sent it. "It's been processed" sounds like a brush-off; "we sent it on Tuesday" sounds like a fact.
WhenThe customer asks to return something after the return period ended.
Personalize: Agree a short menu of alternatives in advance (store credit, a repair, a discount on a replacement) so every agent offers the same one.
WhenThe customer wants a different variant of the same product.
Personalize: Reserving stock is the detail that matters. If your system can't hold an item, say "while stock lasts" instead of implying it's saved.
WhenThe returned parcel has arrived and passed inspection.
Personalize: Send this the day the parcel arrives, even if the refund takes longer to process. Silence after a return is when customers start to worry.
WhenYou're refunding one item, not the whole order.
Personalize: Name the item the refund covers. A partial amount with no explanation looks like a mistake.
WhenYour policy excludes opened or used items.
Personalize: Link the policy instead of quoting it, and always leave the door open for a defect claim. It's often what the customer really means.
WhenStore credit is the agreed fix instead of a refund.
Personalize: State the expiry rule either way. "Doesn't expire" is a selling point; a hidden expiry date is a future complaint.
Money questions need precision. Quote the amount, the date and the last four digits of the card, and never ask for full card details in chat.
WhenThe customer sees two charges for one purchase.
Personalize: Check first whether it's really a pending authorization. If it's a true duplicate, refund it now and say so; don't make the customer wait out a bank cycle for your error.
WhenA renewal or invoice payment didn't go through.
Personalize: Say how long the grace period lasts and what happens after it. "Before anything changes" only reassures people when they know when that is.
WhenA customer needs an invoice or receipt.
Shortcut/invoice
Personalize: Offer the reissue up front. Finance teams almost always need a company name or tax number added.
WhenA customer asks to cancel.
Personalize: Ask why once, after you've confirmed the cancellation. Never make the answer a condition for cancelling.
WhenThe customer forgot to cancel and asks for the renewal back.
Personalize: Agree how many days after a renewal you'll refund without questions, and give every agent the same rule.
WhenThe customer doesn't recognize an amount on an invoice.
Personalize: Explain in the customer's words, not your billing system's. "Two extra seats you added on March 3" beats "seat proration".
WhenYou've moved a customer to another plan.
Personalize: Fill {proration_note} with exactly what is charged or credited today. Surprises on the next invoice cause more tickets than the change itself.
WhenThe customer says they'll dispute the charge with their bank.
Personalize: Don't threaten or lecture about chargebacks. A faster, better offer is the only thing that changes the customer's mind.
Security first, then speed. Verify before you change anything, and tell the customer exactly what you'll accept as proof.
WhenThe customer can't sign in.
Shortcut/reset
Personalize: Send the link to the address on the account, never to an address the customer gives you in chat.
WhenSomeone asks to change account details.
Personalize: Never ask for a password or a full card number. Name the exact detail you'll accept, so the customer doesn't guess and overshare.
WhenYou've updated the login email.
Personalize: Only keep the second sentence if your system really notifies the old address. If it doesn't, it should.
WhenToo many failed sign-in attempts locked the account.
Personalize: Explain that the lock protects them. People are calmer about a security measure than about a bug.
WhenA customer asks you to delete their account or data.
Personalize: Name what is deleted and what you're legally required to keep (invoices, for example). Make sure the wording matches your privacy policy.
WhenThe customer lost the phone or app they use for two-factor sign-in.
Personalize: Say why you can't do it in chat. "For your security" plus a clear path forward reads as care, not as a wall.
Technical replies earn trust by being specific: what you tested, what you found, and when you'll be back.
WhenYou've reproduced the problem the customer reported.
Personalize: "I reproduced it" is worth more than any apology. Only say it when you did.
WhenYou can't investigate without more information.
Shortcut/bugdetails
Personalize: Number the questions. Customers answer numbered lists completely and skip questions buried in a paragraph.
WhenA fix will take time but there's a way around the problem.
Personalize: Test the workaround yourself before you send it. A workaround that fails doubles the frustration.
WhenThe fix for a reported issue has shipped.
Personalize: Close the loop with everyone who reported it, not only the last person. It's the cheapest loyalty you'll ever buy.
WhenA known incident is affecting customers.
Shortcut/outage
Personalize: Don't promise a fix time unless engineering gave you one. Link the status page and let it carry the updates.
WhenEverything works when you test it.
Personalize: Never write "it works for me". Say what you tested, so the customer knows you actually tried.
WhenThe behavior is by design, even if the customer expected something else.
Personalize: Lead with the explanation, not with "this isn't a bug". Nobody likes being told their problem doesn't count.
WhenA stale page or session is the likely cause.
Personalize: Offer the private window as the easy option. Many people don't know how to clear a cache, and that's fine.
A good apology names the mistake, fixes it and says what changes. "Sorry for any inconvenience" does none of the three.
WhenYour company got something wrong.
Personalize: Name the mistake specifically. A vague apology sounds like you don't know what went wrong.
WhenThe customer went through real hassle and you want to make up for it.
Personalize: Match the gesture to the hassle. A tiny discount after a ruined gift reads as an insult, and a full refund for a one-day delay sets a costly precedent.
WhenThe customer is upset and says so.
Personalize: Don't match the tone or defend the company in the first message. Acknowledge, take ownership and commit to one concrete next step.
WhenA fix you made didn't hold.
Personalize: Admit the first fix failed. Pretending it's a new issue makes the customer explain everything again.
WhenYou said you'd reply by a time and didn't.
Personalize: Lead with the missed promise. Customers forgive a late update much faster when you say it before they do.
WhenSomeone posted about a bad experience and you're continuing in private.
Personalize: Reply publicly once and briefly, then move to a private channel for the details. Never argue facts in public.
The handoff is where customers decide whether your support works. Carry the context, name the person, give a time.
WhenThe question needs someone with deeper knowledge or permissions.
Personalize: Name the person and the team. "Someone will get back to you" sounds like a queue; a name sounds like a plan.
WhenThe customer asks to speak to someone more senior.
Personalize: Never refuse a manager request or make the customer justify it. Agree, and promise a real time.
WhenBefore you transfer, as a note only your team sees.
Personalize: This note is what saves the customer from repeating the story. Keep it to these six lines and fill in every one.
WhenA teammate takes over a conversation an AI agent was handling.
Personalize: Read the transcript before you send this, then prove it by mentioning one detail, like the product or the order number.
WhenA case is with another team and there's nothing new yet.
Personalize: A no-news update is still an update. Silence is what turns a waiting customer into an angry one.
WhenThe customer mentions a lawyer, an injury, a safety issue or a formal complaint.
Personalize: Don't speculate about fault or compensation in the first reply. Route it to the right people and confirm when they'll be in touch.
Feedback replies are a promise about the future. Only promise what your team actually tracks.
WhenA customer asks for something your product doesn't do.
Personalize: Keep "I'll let you know" only if your team records who asked. Otherwise, drop the promise.
WhenA customer says something nice.
Personalize: Ask for the review only when the praise is about the product or service, not just about you.
WhenA customer tells you what you're doing badly.
Personalize: Summarize their point in your own words. It proves you listened instead of pasting a thank-you.
WhenAt the end of a conversation that went well.
Personalize: Ask after resolved conversations only, and only once. Repeated survey requests lower the response rate for everyone.
End the conversation on purpose: confirm it's solved, say how to come back, and follow up when silence might mean the fix didn't work.
WhenThe customer confirmed the problem is solved.
Shortcut/done
Personalize: Make sure replying to a closed conversation really reaches your team before you promise it.
WhenYou've answered the question and want to make sure nothing is left.
Personalize: Ask once. If the customer says no or doesn't reply, close the conversation.
WhenYou sent a fix and haven't heard back.
Personalize: Say when you'll close it. Customers don't mind a conversation closing when they were told.
WhenThe follow-up got no answer.
Personalize: Keep it short and warm. This message is the last impression of the whole conversation.
WhenYou fixed something important and want to confirm it stayed fixed.
Personalize: Use this sparingly, for problems that really hurt the customer. That's what makes it feel personal.
WhenYour shift ends before the conversation does.
Personalize: Write the internal handoff note first (see above), then send this. The order matters.
WhenA difficult case is finally solved.
Personalize: Acknowledge the time it took. Ending as if it was a routine case erases the customer's experience.
In Asks, canned responses live under Settings and open from the inbox composer when you type /. Their content can use variables such as {{customer.name}} or {{ticket.number}} that fill in when inserted, and a response can set the ticket's status, priority or tags when you send it. The canned responses guide lists every variable.
Beyond templates
Canned responses make typing faster. They don't reduce the number of conversations. If the same handful of questions (where's my order, what's your return policy, do you ship to my country) make up most of your queue, a person pasting the same answer all day is the expensive part.
An AI agent answers those questions itself, from your own help center, policies and product pages, in your website chat, by email and on messaging apps. When it can't support an answer from your content, or the customer asks for a person, it hands the conversation to your team with the history attached. Your saved replies don't disappear: they become the source the agent learns from, and your team keeps them for everything else.
In Asks, you write a policy once as a knowledge-base article and the agent answers from it. AI Insights (on the Business plan and above) lists the questions it couldn't answer, so you know which answer to write next.
7-day free trial · card required · cancel anytime
The same question, answered from your returns policy



FAQ
A canned response is a pre-written reply that a support agent saves once and inserts into a conversation with a click or a shortcut, then edits before sending. Help desks also call them saved replies, macros, snippets or quick replies.
Start with the 20 to 30 situations your team answers most often, which usually cover the bulk of your volume. Add more only when a new situation keeps coming up, and delete the ones nobody uses. A library of hundreds is hard to search mid-conversation.
Only when they're sent unedited or written in a corporate voice. Write them the way your team talks, leave a placeholder for one detail that is specific to the customer, and fill it in every time.
In many help desks a canned response is only text, while a macro is text plus actions, such as setting the status, adding a tag or assigning the ticket. Asks attaches these as ticket actions on a canned response, applied when you send the reply.
Yes. They are written to be copied and adapted in any help desk, email client or chat tool, with no sign-up. Replace the placeholders in braces with your tool's variables or with the real details.
For the repetitive questions, an AI agent that answers from your knowledge base can resolve them without a person. Your team still needs saved replies for the conversations the agent hands over, such as exceptions, complaints and anything sensitive.
Written for asks.app and published under Ray's byline. Every template is original: drafted with AI assistance from common support situations and reviewed for accuracy and tone before publishing, not copied from other template lists. Details about Asks were checked against the product and its documentation on November 16, 2026. How we write and correct pages is in our editorial policy.

Asks learns your website and help center, answers customers on chat, email and messaging apps, and hands the rest to your team in one inbox.
7-day free trial · card required · cancel anytime