Thanks — looking into it
Hi there,
Thanks for getting in touch! I'm looking into this now and will update you here as soon as I know more.
Best regardsA working library of replies for the tickets you answer every day: refunds, logins, bugs, escalations, angry customers and closing the loop. Copy one with Zendesk placeholders and paste it into a macro, or bring the whole set into FlashType and type /refund-ok in any reply box.
Already have FlashType? Update to 1.4 or newer (Chrome usually does it on its own within a day, or click Update in chrome://extensions with Developer mode on), then reload this page to add all 33 in one click.
Grouped by situation. Highlighted parts are the bits you change for each person. Every template also has a FlashType shortcut, shown at the bottom of its card.
Swaps the customer name, your name and the ticket number for Zendesk placeholders. Anything else in [brackets] is something only you know — fill it in before you submit.
Set expectations in the first reply so the customer stops refreshing their inbox.
Hi there,
Thanks for getting in touch! I'm looking into this now and will update you here as soon as I know more.
Best regardsHi {{ticket.requester.first_name}}, Thanks for getting in touch. I've got your request (ticket #{{ticket.id}}) and I'm looking into it now. I'll update you by [When] at the latest. Best, {{current_user.first_name}}
Hi {{ticket.requester.first_name}}, Thanks for your patience. We're handling more requests than usual right now, so replies are taking around [Wait time]. Your ticket is in the queue and you don't need to send it again — I'll be back with you as soon as I can. Best, {{current_user.first_name}}
Hi {{ticket.requester.first_name}}, I want to get this right, so I need a couple of details first: 1. [Question one] 2. [Question two] As soon as I have those, I'll take it from there. Thanks, {{current_user.first_name}}
Hi {{ticket.requester.first_name}}, Could you send me a screenshot of what you're seeing? Please include the whole window if you can, so I can see the address bar and any error message. That will help me find the cause much faster. Thanks, {{current_user.first_name}}
Hi {{ticket.requester.first_name}}, Thanks for reaching out. This one is handled by our [Team] team, so I've passed your ticket straight to them with everything you've told me — you won't need to repeat yourself. They'll reply here within [Timeframe]. Best, {{current_user.first_name}}
Hi {{ticket.requester.first_name}}, Here's how to reset your password: 1. Go to [Login page link] and click "Forgot password". 2. Enter the email address on your account. 3. Open the reset email (check spam if it isn't there within a few minutes) and choose a new password. If the email doesn't arrive, reply here and I'll send it from my side. Best, {{current_user.first_name}}
Hi {{ticket.requester.first_name}}, Your account was locked after several unsuccessful sign-in attempts — that's an automatic security measure. I've unlocked it, so you can sign in again now. If you don't remember your password, the "Forgot password" link on the sign-in page will get you a new one. Best, {{current_user.first_name}}
Hi {{ticket.requester.first_name}}, To protect your account, I need to confirm it's you before I make this change. Please reply from the email address on the account, or send me [Verification detail]. Thanks for understanding, {{current_user.first_name}}
Hi {{ticket.requester.first_name}}, Done — the email on your account is now [New email]. You'll use it to sign in from now on, and all receipts and notifications will go there. Your old address won't receive anything further. Best, {{current_user.first_name}}
Hi {{ticket.requester.first_name}}, As requested, your account and its data have been scheduled for deletion. This is completed within [Timeframe] and can't be undone after that. If you change your mind before then, just reply to this email. Thanks for having been with us, {{current_user.first_name}}
Hi {{ticket.requester.first_name}}, Good news — I've approved a refund of [Amount] to your original payment method. Banks usually take [5–10] business days to show it on your statement. Is there anything else I can help with? Best, {{current_user.first_name}}
Hi {{ticket.requester.first_name}}, Thanks for explaining what happened. Your purchase on [Purchase date] is outside our [Refund window] refund window, so I can't refund it. What I can do is [Alternative offer] — would that help? I'm sorry it isn't the answer you hoped for. Best, {{current_user.first_name}}
Hi {{ticket.requester.first_name}}, You're right — you were charged twice for [Item or plan]. I've refunded the duplicate charge of [Amount]. If your bank shows it as "pending", it will drop off within a few days without you needing to do anything. Sorry for the worry, {{current_user.first_name}}
Hi {{ticket.requester.first_name}}, Your last payment didn't go through, usually because a card has expired or the bank flagged it. You can update your card at [Billing page link]. Your account stays active until [Grace period end], so there's no rush today. Best, {{current_user.first_name}}
Hi {{ticket.requester.first_name}}, I've attached the [Invoice or receipt] for [Month or order]. You can also download past invoices any time from [Billing page link]. Best, {{current_user.first_name}}
Hi {{ticket.requester.first_name}}, Your subscription is cancelled and you won't be charged again. You keep full access until [End of billing period]. If there was something we could have done better, I'd genuinely like to hear it. Best, {{current_user.first_name}}
Hi {{ticket.requester.first_name}}, Thank you — I was able to reproduce this, so it's definitely a bug on our side and not something you did. I've logged it with our engineers with your steps attached. I'll update this ticket when there's a fix. Best, {{current_user.first_name}}
Hi {{ticket.requester.first_name}}, This is a known issue and our team is working on it. Until it's fixed, this workaround should get you going: [Workaround steps] I've linked your ticket to the issue, so you'll hear from us as soon as it's resolved. Best, {{current_user.first_name}}
Hi {{ticket.requester.first_name}}, Could you try these two quick steps? They fix this kind of issue more often than you'd expect: 1. Sign out, then clear your browser's cache and cookies for our site. 2. Sign back in using a private/incognito window. If it still happens, let me know which browser and version you're using and I'll dig deeper. Thanks, {{current_user.first_name}}
Hi {{ticket.requester.first_name}}, The fix for the issue you reported went live on [date]. Could you try again and let me know if everything works as expected now? Thanks again for reporting it — it helped us fix it for everyone. Best, {{current_user.first_name}}
Hi {{ticket.requester.first_name}}, We're currently having an issue affecting [Affected feature]. Our engineers are on it, and you can follow live updates at [Status page link]. Your data is safe. I'll reply here as soon as it's resolved. Sorry for the disruption, {{current_user.first_name}}
Hi {{ticket.requester.first_name}}, I've escalated your ticket to our [Specialist team] team, who can look at this in more depth than I can. They have the full history, so you won't need to explain it again. You can expect to hear from them within [Timeframe]. Best, {{current_user.first_name}}
Handoff — [date] Issue: [One-line summary] Tried so far: [What you tried] Customer expects: [Promise made and when] Next step: [Next step]
Hi {{ticket.requester.first_name}}, A quick update so you're not left wondering: I'm still working on this with [Team]. We've [Progress so far], and I expect to have an answer by [Date]. I'll be in touch then, or sooner if I have news. Best, {{current_user.first_name}}
Hi {{ticket.requester.first_name}}, That's a great suggestion, and I've passed it to our product team with your use case. I can't promise if or when it will be built, but requests like yours are exactly what they use to decide what comes next. Thanks for taking the time, {{current_user.first_name}}
Short, specific and human beats long and scripted when someone is upset.
Hi {{ticket.requester.first_name}}, I'm sorry. You shouldn't have had to [What went wrong], and I understand why you're frustrated. Here's what I've done to put it right: [What you did]. If anything else isn't right, reply to me directly and I'll handle it personally. {{current_user.first_name}}
Hi {{ticket.requester.first_name}}, I've looked into this carefully, and unfortunately we can't [Request] because [Honest reason]. I know that's frustrating. What I can do instead is [Alternative]. Would that work for you? Best, {{current_user.first_name}}
Hi {{ticket.requester.first_name}}, I want to help you resolve this, and I'm going to keep working on it. I do need our conversation to stay respectful so I can do that. Here's where things stand: [Current status]. {{current_user.first_name}}
Hi {{ticket.requester.first_name}}, This might be quicker to sort out by talking it through. Would a short call work? I'm free [Two or three time options] — reply with the one that suits you, and the best number to reach you on. Best, {{current_user.first_name}}
Hi {{ticket.requester.first_name}}, Glad that's sorted! I'm marking this ticket as solved. If anything else comes up, just reply to this email and it will reopen with me. Have a great [day or week], {{current_user.first_name}}
Hi {{ticket.requester.first_name}}, Just checking in — did the steps I sent help? If you're all set, no need to reply and I'll close this in a few days. If not, tell me what you're seeing and I'll keep going. Best, {{current_user.first_name}}
Hi {{ticket.requester.first_name}}, I haven't heard back, so I'll assume things are working and close this ticket for now. If you still need help, simply reply here — it will reopen and come straight back to me. Best, {{current_user.first_name}}
In Zendesk, a canned response is a macro. A macro is a saved set of actions an agent applies to a ticket by hand: add a public reply or internal note, set the status, add tags, change the group or assignee. Admins create shared macros for the whole team; depending on your role and plan, agents can also create personal macros only they can use.
Macros can include placeholders such as {{ticket.requester.first_name}} or {{ticket.id}}, which Zendesk fills in from the ticket when the macro is applied. That makes them good for the structured part of a reply. Everything else — the order number the customer pasted, the refund amount, the date you promised — you still type or edit by hand after applying the macro.
Menu names move around between Zendesk versions. If a step doesn't match what you see, Zendesk's own help centre has the current path.
Keep your macros for what they are best at: changing ticket fields and keeping shared answers consistent. Use FlashType for the typing. Type /refund-ok in the Zendesk reply box and the reply appears instantly with the blanks highlighted; Tab through the amount and the date, press Enter, done. No menu, no search.
Because FlashType works in any text box in Chrome, the same /refund-ok works when you follow up in Gmail, answer in Slack, or leave a note in Shopify. It is free with unlimited snippets, so every agent can keep their whole personal library — not just the 20 that fit on a free plan elsewhere.
/ackHi First name, Thanks for getting in touch. I've got your request (ticket #Ticket number) and I'm looking into it now. I'll update you by When at the latest. Best, Your name
Using these with a team? Add them once, open the “Zendesk support replies” folder, edit anything you like, then click “Share with team” and send your teammates the link. They join without an account, everyone sends the same replies with their own name and the customer's name filled in, and when you edit a reply their copy updates within about 30 minutes. How team sharing works.
FlashType inserts text. It doesn't send messages, change ticket fields or read your inbox. It runs in Chrome and other Chromium browsers on a computer, so it won't work in desktop or phone apps — only in Zendesk in the browser. And it doesn't have a formula or scripting language; if you need snippets that calculate or branch, our Text Blaze comparison explains where Text Blaze is the better pick.
Comparing text expanders? Read FlashType against Text Blaze, Magical and TextExpander, or see everything it does on the FlashType page.
FlashType is a free Chrome text expander with unlimited snippets and fill-in blanks. Add all 33 replies in one click, use them in Zendeskand every other tab, and share them with your team — teammates don't need an account.