English

Free tool

Support ticket response examples and templates

Copy-ready replies for every kind of ticket, sorted by type. Fill the [slots] yourself, or let the AI fill them for your business and customer.

BrowseRewrite my reply

Acknowledgement and first response

Send one of these within your first-response target, even before you have the answer. Each one confirms the ticket, sets a time and asks for anything you need.

Ticket received, with a timeAny new ticket you cannot solve in the first reply
Hi [customer name], Thanks for writing in. Your request is logged as ticket [ticket number], and [agent name] is looking into it now. You will hear from us by [time and day], sooner if we solve it first.
Received, but we need detailsThe ticket is missing what you need to start
Hi [customer name], Thanks for reporting this. So we can look into it, please reply with [detail 1] and [detail 2]. As soon as we have them, we will pick up ticket [ticket number] and reply within [time].

Bug reports

Thank the person for the report, say what you reproduced, and say what happens next. Never promise a fix date you do not have.

Bug confirmedYou reproduced the problem
Hi [customer name], Thanks for the clear steps. We reproduced the problem: [what happens] when [action]. I have passed it to our engineers as [internal bug ID], and I will update ticket [ticket number] when a fix is scheduled.
Cannot reproduce yetYour tests do not show the problem
Hi [customer name], We tried [steps you tried] on [browser, app or device] and have not seen the error yet. Could you send a screenshot or a short screen recording, the time it last happened, and your [browser or app version]? That usually shows us what is different on your side.

How-to and feature questions

Answer in numbered steps, link the help article, and check that the steps match what the customer sees on their plan and device.

Step-by-step answerThe feature exists and the steps are short
Hi [customer name], You can do this in three steps: 1. Go to [page or menu]. 2. Select [option]. 3. [Final step]. The full guide with screenshots is here: [help article link]. If anything looks different on your screen, send a screenshot and I will walk you through it.
Point to the right articleA help article already answers it
Hi [customer name], This article covers it: [help article link]. The part you need is under [section name]. If it does not match what you are trying to do, tell me a little more about [goal] and I will find the right way.

Billing and invoices

Billing tickets need exact facts. Take every amount and date from your billing system, and never ask for a full card number.

Copy of an invoiceThe customer needs an invoice for their records
Hi [customer name], I have attached invoice [invoice number] for [period]. You can also download all your invoices any time from [billing page link]. If you need a different company name, address or tax number on it, send me the details and I will check how we can update it.
Charged twiceA duplicate payment
Hi [customer name], I am sorry about the duplicate charge. I can see two payments of [amount] on [date]. I have refunded the second one today, and your bank should show it within [number] business days.

Account access and security

Confirm who you are talking to before you change anything. Never ask for a password, a one-time code or a full card number.

Password resetThe customer cannot sign in
Hi [customer name], You can reset your password here: [reset link]. The link works for [time]. If the email does not arrive, check your spam folder and make sure you use the address on your account. Our team will never ask you for your password.
Account lockedToo many failed sign-ins or a security block
Hi [customer name], Your account was locked after [reason, such as several failed sign-ins]. To protect it, I need to confirm it is you: please reply from the email address on the account, or [other verification step]. Once that is done, I will unlock it and let you know.

Feature requests

Thank the person, say honestly what happens to the request, and offer what works today.

Request loggedA new idea you cannot promise
Hi [customer name], Thanks for the idea. I have added [feature] to our product feedback with your use case: [one-line summary]. We cannot promise if or when it will be built, but I have linked this ticket to it, so you will hear from us if it is planned.
Request, with a workaroundSomething close is possible today
Hi [customer name], [Feature] is not available yet, and I have passed your request to our product team. Until then, you can get close with [workaround]. Here is how: [short steps or help article link].

Escalation and handover

Tell the customer who has the ticket now, why, and when they will hear back. They should never have to explain the problem twice.

Moving to a specialist teamThe ticket needs other skills or permissions
Hi [customer name], This needs our [team name] team, so I have passed ticket [ticket number] to [name or team] with everything you have told us so far. You will not need to repeat it. They will reply by [time and day].
Escalated to engineeringA bug or outage needs engineers
Hi [customer name], I have escalated this to our engineers with the steps, screenshots and account details from this ticket. I am still your contact, and I will update you by [time and day], or sooner if they find the cause.

Waiting on the customer

Follow up before you close. Make the reply easy to write, and say what happens if you do not hear back.

First follow-upNo reply after your first request
Hi [customer name], Just checking in on ticket [ticket number]. To move forward, we still need [missing item]. Reply to this email with it and I will take it from there.
Second follow-upStill no reply
Hi [customer name], I have not heard back about [issue], so I want to make sure this did not get lost. Is it still a problem? If so, [missing item] is all I need. If it is solved, a quick reply saying so helps too.

Resolution and closing

Say what was done, how to check it, and how to come back. Ask for feedback once, not in every reply.

Resolved, with a summaryThe problem is fixed
Hi [customer name], To sum up: [problem] was caused by [cause], and we fixed it by [fix]. You should now be able to [result]. If anything else comes up, reply here and we will pick it up again.
Check before closingYou think it is fixed and want them to confirm
Hi [customer name], It looks like [issue] is fixed on our side. Can you confirm it works for you too? If we do not hear back by [date], we will mark ticket [ticket number] as solved, and you can reopen it any time by replying.

SLA breach and apology

When you miss a promised time, say so first, give a new time you can keep, and then keep it.

Late first responseThe ticket waited longer than your target
Hi [customer name], I am sorry it took us [time] to answer. That is longer than we aim for. I have read your message, and [answer or first step]. I will update you by [time] with the next step.
Missed a promised updateYou said you would write and did not
Hi [customer name], I said I would update you by [time], and I did not. I am sorry. Here is where things stand: [status]. My next update will be by [time], and I have set a reminder so it happens.

Put this on your website

Build a support agent from your site

Your own AI agent answers questions like this on your website, day and night, from your own pages and documents, and passes the hard ones to you. Paste your address to see it learn your site. No account needed.

What a good support ticket response looks like

A good support ticket response confirms the ticket, answers the question or names the next step, and says when the customer will hear back. Use their name, restate the problem in one line, give the steps or facts, and end with one clear action. The 60 examples above are sorted by ticket type, from the first response to closing, with [slots] for ticket numbers, dates and names.

Find the ticket typeUse the situation chips above the library, or search for a word such as "refund", "locked" or "bug".
Copy it, or personalize itCopy a template and fill the [slots] yourself. Or open the personalize form under any entry, add the customer's name, your business and the facts, and the AI fills the slots it can.
Check every fact before you sendAmounts, dates, links and ticket numbers come from your own systems. Search your reply for "[" so no slot goes out unfilled.
Or improve a reply you already wroteOpen the "Rewrite my reply" tab, paste your draft, and get a clearer version that keeps your facts and promises and ends with one next step.

How to structure a support ticket reply

Most good ticket replies have the same five parts. Short replies can merge two of them, but none should go missing.

Part	What it does	Example
Greeting with their name	Shows a person read this ticket	"Hi Priya,"
The problem in one line	Proves you understood, and catches misunderstandings early	"Since this morning, invoice exports to CSV come out empty."
The answer or the next step	The reason the reply exists	"Here is how to export them while we fix it: ..."
When they will hear from you	Ends the "did anyone see this?" worry	"I will update you by 3 p.m. on Thursday."
One action for them, if any	Makes the reply easy to answer	"Could you reply with a screenshot of the error?"

Keep one ticket to one topic. Put steps in a numbered list, link the help article instead of pasting it, and ask all your questions in one place. If you need three things from the customer, ask for all three in the same reply, not one per day.

First response time: what to send first

First response time is how long a ticket waits before a person replies. It matters because until someone answers, the customer does not know whether anyone has seen the ticket. There is no single right number. Set a target for each priority and channel that your team can actually meet, and publish it in your help center so customers know what to expect.

A fast first reply that sets a time beats a slow, perfect answer.
An automatic "we got your email" message confirms receipt. It is not a first response, because it does not move the ticket forward.
If you can solve it in the first reply, do. If you cannot, say what you are doing and when you will write again.
Count nights and weekends if you promise support around the clock. Otherwise, say your hours in the auto-reply.

First response when you do not have the answer yet

Hi [customer name],

Thanks for the details on [problem]. I have checked [what you checked] and passed it to [team], who can see [the system involved]. I will update you on ticket [ticket number] by [time and day], sooner if we find the cause first.

Macros versus personalization

A macro (also called a canned response or saved reply) saves typing. A reply that reads like a macro to a frustrated customer costs trust. Use both, on purpose.

Send the template as it is

Password reset links
Invoice copies
Updates on a known outage
Closing after no reply
Booking a call

Personalize it first

An upset or repeat customer
A bug report with their own steps
Any refund or billing decision
Any reply that says no
A second reply on the same ticket

A simple rule: keep the template's structure and facts, and rewrite the first line so it shows you read their ticket. "Thanks for the clear steps to reproduce the export error" says more than "Thank you for contacting support", and it takes ten seconds.

Before and after: three ticket replies

The weak versions below are common. The stronger ones use the same facts.

Bug report. Weak: "Thanks for contacting us. We have forwarded your issue to the relevant team." The customer still does not know whether anyone reproduced the bug, who has it, or when they will hear back.

Bug report, stronger

Hi Tomasz,

Thanks for the clear steps. We reproduced it: the Save button stays gray when a product has more than 20 variants. Our engineers have it now. Until the fix ships, you can save by editing variants in smaller groups. I will update this ticket by Friday, sooner if the fix is out.

Refund request. Weak: "Unfortunately, as per our policy, we are unable to process your request." It refuses without a reason and offers nothing.

Refund request, stronger

Hi Grace,

Thanks for explaining. Your order was delivered on [date], and our policy allows refunds within [number] days of delivery ([policy link]), so I cannot refund it now. What I can do is [alternative, such as store credit or an exchange]. If you would like that, reply "yes" and I will set it up today.

Waiting on the customer. Weak: "Following up on this. Please advise." It does not say what is needed or what happens next.

Follow-up, stronger

Hi Kenji,

To finish setting up your domain, I still need one thing: a screenshot of your DNS settings page. Once I have it, the rest takes about ten minutes on our side. If I do not hear back by [date], I will close this ticket, and you can reply any time to pick it up again.

Which templates to start with, by team

Team	Tickets you see a lot	Start with these groups
Online store	Where is my order, returns, damaged items, payment problems	Acknowledgement, Billing and invoices, Waiting on the customer
Software (SaaS)	Bugs, how-to questions, plan changes, feature requests	Bug reports, How-to, Feature requests
IT help desk	Password resets, access requests, hardware and software issues	Account access, Escalation and handover, Resolution and closing
Agencies and services	Scope questions, invoices, deadlines	Billing and invoices, Waiting on the customer, SLA breach
Apps and marketplaces	Locked accounts, suspicious activity, disputes	Account access, Escalation and handover, SLA breach

Every team needs the first-response and closing groups. Add the rest as your ticket types show up.

Common mistakes in ticket replies

Promising a date you do not control, such as a fix date engineers have not set.
Asking for information that is already in the ticket.
Spreading questions across paragraphs. Ask them together, in a numbered list.
Closing a ticket without saying what was fixed or how to come back.
Sending a reply with an unfilled [slot]. Search for "[" before you send.
Apologizing three times in one reply. Apologize once, for what actually went wrong.
Asking for a password, a one-time code or a full card number. No support reply ever needs one.
Passing a ticket to another team without the history, so the customer has to explain it again.

How an AI agent handles the same tickets on your website

Many tickets are questions your website already answers: how to do something, where to find an invoice, what the refund policy says. An AI support agent built from your own website pages can answer those in the chat as they are asked, at 2 a.m. as well as at noon, so fewer of them become tickets.

When it cannot resolve something, or the visitor asks for a person, it hands the chat to your team. You choose topics that always go to a person, such as "refund" or "complaint". Your team gets an email alert, sees the whole chat and can take over, so the customer does not repeat themselves. Outside your business hours, it tells the visitor when a person will reply.

A how-to answer, then a billing question handed to a person

How do I add a teammate to my account?

Go to Settings, then Team, and select Invite. Enter their email and choose a role. They get an email to join.

From the page: Managing your team

Thanks. Also, I think I was charged twice this month.

I am sorry about that. I have passed this chat to our billing team with your message, and a person will reply here and by email.

Handed to a person: billing

Answer repeat questions before they become tickets

Build a support agent from your website. It answers from your own pages and hands the rest to your team.

See the AI customer service agent

Questions people ask

What should a first response to a support ticket include?

Confirm you have the ticket, restate the problem in one line, and either answer it or say what you are doing next and when the customer will hear from you. If you need more information, ask for all of it in that first reply.

How quickly should you respond to a support ticket?

There is no single standard. Set a first-response target for each priority and channel that your team can meet every day, publish it, and measure against it. A quick reply that sets a time is better than a slow, complete one.

How do you write a ticket closing message?

Say what the problem was, what fixed it and how the customer can check, then tell them how to come back if it happens again. If you ask for feedback, do it once, with one link.

What is the difference between a macro and a canned response?

In everyday use they are the same thing: a saved reply you insert instead of typing. In some help desks, such as Zendesk, a macro can also change the ticket itself, for example its status, tags or assignee.

Can I use these templates in Zendesk, Freshdesk, Gmail or Outlook?

Yes. They are plain text. Save them as saved replies or macros, and replace our [square-bracket] slots with your help desk's own placeholders where it has them, such as the ticket number or the customer's first name.

Keep reading

For AI agents

Build it with your AI agent

Give an agent your site and it can create the chatbot, read your pages and test it through LuckPanda's API and MCP. It prepares the work; going live stays with you.

Use LuckPanda's MCP server (https://luckpanda.app/mcp) to build a website chatbot for me. Ask for my website address, call chatbot_create_from_website with it, wait until the pages are learned (chatbot_source_list), then run a few test questions with chatbot_test_message and show me the answers. Do not put it live: I will do that myself.

Instructions for AI agents

Needs a LuckPanda agent key (Settings › Developers) with the chatbot.manage grant. MCP endpoint: https://luckpanda.app/mcp (Streamable HTTP, bearer key).

chatbot_create_from_website { url }: creates a draft chatbot named after the site and starts reading it.
chatbot_source_list: pages learned, failed or skipped, with a reason for each.
chatbot_test_message: asks the bot a question as the owner. Test chats never email anyone.
Going live (chatbot_update with status live) is a person's action; an agent gets APPROVAL_REQUIRED.

Try it on your website

Paste your address and watch the chatbot learn your pages. No account and no card.

This page in other languages