---
title: "Support Ticket Response Examples: 60 Free Templates"
description: "Copy 60 support ticket response examples sorted by ticket type: first replies, bugs, billing, access, escalation and closing. Personalize any one free."
canonical: https://luckpanda.app/chatbot/tools/support-ticket-response-templates
updated: 2026-10-14
---

# Support ticket response examples and templates

Canonical URL: https://luckpanda.app/chatbot/tools/support-ticket-response-templates
Language: en
Updated October 14, 2026

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.

Free tool: https://luckpanda.app/chatbot/tools/support-ticket-response-templates (widget, customer-service)

Agents: run it over MCP (https://luckpanda.app/mcp) with chatbot_public_tool_run { "tool": "support-ticket-response-templates", "lang": "en", "inputs": { … } }; chatbot_public_tool_list gives the inputs.

## 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 time

_Any new ticket you cannot solve in the first reply_

```text
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 details

_The ticket is missing what you need to start_

```text
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].
```

### Received during a busy period

_Your queue is longer than usual_

```text
Hi [customer name],

We have your message, ticket [ticket number]. We are answering more requests than usual, so our reply may take until [time and day]. If your question is about [common topic], this article may answer it right away: [help article link].
```

### Received outside business hours

_Tickets that arrive at night, on weekends or on holidays_

```text
Hi [customer name],

Thanks for your message. Our team is offline until [opening time and day], and ticket [ticket number] will be among the first we answer when we are back. If this is urgent, [urgent contact].
```

### Received, known issue

_Many customers report the same problem_

```text
Hi [customer name],

Thanks for letting us know. We are aware that [short description of the issue], and our team is working on a fix. We will update you on ticket [ticket number] when it is resolved, and you can follow progress here: [status page link].
```

### Received and marked urgent

_The customer cannot work or sell_

```text
Hi [customer name],

I can see this is stopping you from [what they cannot do], so I have marked ticket [ticket number] as urgent. I am working on it now and will update you by [time], even if it is only to say what we have found so far.
```

## 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 confirmed

_You reproduced the problem_

```text
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 yet

_Your tests do not show the problem_

```text
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.
```

### Workaround while we fix it

_There is a way around the bug_

```text
Hi [customer name],

While our team fixes this, you can get the same result by [workaround steps]. It is not ideal, and the fix is still a priority. I will let you know on ticket [ticket number] when it is live.
```

### Fix released

_The fix is live_

```text
Hi [customer name],

The fix for [problem] is now live in [version or release]. Please [refresh, update or restart] and try again. If you still see the problem, reply here and I will pick ticket [ticket number] up again straight away.
```

### Working as designed

_The behavior is intended, even if unexpected_

```text
Hi [customer name],

Thanks for flagging this. What you are seeing is how [feature] works today: [short reason]. I know it is not what you expected, so I have shared your feedback with our product team. In the meantime, you can [alternative way to do it].
```

### Bug that changed data

_The customer's records may be wrong or missing_

```text
Hi [customer name],

I am sorry this affected your data. Our engineers are checking which records changed between [start time] and [end time]. Please do not [action that could make it worse] until we confirm. I will update you by [time] with what we found and what we can recover.
```

## 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 answer

_The feature exists and the steps are short_

```text
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 article

_A help article already answers it_

```text
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.
```

### Not possible today

_The product cannot do what they ask_

```text
Hi [customer name],

[Product] does not support [feature] today. The closest option is [alternative], which lets you [what it does]. I have also logged your request so our product team sees it.
```

### Available on another plan

_The feature exists on a different plan_

```text
Hi [customer name],

[Feature] is part of the [plan name] plan. Your account is on [current plan], so it does not appear for you. You can compare plans here: [pricing page link], and I am happy to answer questions before you decide.
```

### Offer a short call

_Written steps are not getting there_

```text
Hi [customer name],

This may be quicker to sort out together. Would a [length]-minute screen share on [day] at [time], or [day] at [time], work for you? If you prefer to keep it in writing, that is fine too.
```

### Question about an integration

_The answer involves another company's tool_

```text
Hi [customer name],

[Product] connects to [other tool] through [integration or method]. To set it up, [first step], then [second step]. Settings inside [other tool] are managed by their team, so for [their part] their help center is the best place: [their help link].
```

## 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 invoice

_The customer needs an invoice for their records_

```text
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 twice

_A duplicate payment_

```text
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.
```

### Payment failed

_A renewal payment was declined_

```text
Hi [customer name],

Your payment for [plan] on [date] did not go through, so your account is now [status]. You can update your payment method here: [billing page link]. Once the payment goes through, [what is restored].
```

### Refund request: the decision

_The customer asks for their money back_

```text
Hi [customer name],

Thanks for explaining what happened. Under our refund policy ([policy link]), [eligible or not eligible, and the reason in one line]. [What you will do: the refund and how it is paid, or the alternative you can offer]. If anything here is unclear, reply and I will go through it with you.
```

### Refund processed

_You have issued the refund_

```text
Hi [customer name],

Your refund of [amount] for [order or invoice number] was processed today. Banks usually show it within [number] business days. If it has not arrived by [date], reply here and I will trace it with our payment provider.
```

### Plan change or cancellation confirmed

_The customer upgrades, downgrades or cancels_

```text
Hi [customer name],

Done: your account moves to [new plan or canceled] on [date]. [What changes in features, limits or data]. Your next invoice will be [amount] on [date], or there will be none if you canceled. If you change your mind before then, reply here.
```

## 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 reset

_The customer cannot sign in_

```text
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 locked

_Too many failed sign-ins or a security block_

```text
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.
```

### Lost two-factor device

_They lost the phone or app that holds their codes_

```text
Hi [customer name],

I am sorry you lost access to your authentication app. To remove two-factor authentication safely, we need [verification steps], which usually takes [time]. After that, you can sign in with your password and set two-factor authentication up again on your new device.
```

### Change the account email

_The customer wants to sign in with a new address_

```text
Hi [customer name],

To change the email on your account, please confirm the request from your current address, or [other verification step]. Once confirmed, we will move the account to [new email] and send a notice to both addresses.
```

### Suspicious activity reported

_The customer thinks someone else used their account_

```text
Hi [customer name],

Thanks for reporting this quickly. We have [action taken, such as signed out every session] on your account. Please change your password now and turn on two-factor authentication here: [security settings link]. We are reviewing the activity from [date] and will update you by [time].
```

### Admin or owner has left

_Only someone who is gone can grant access_

```text
Hi [customer name],

Only an owner or admin can [add users or change roles] on this account. If none of them can help, for example because they have left [company], reply with [proof the account needs] and we will take it from there.
```

## Feature requests

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

### Request logged

_A new idea you cannot promise_

```text
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 workaround

_Something close is possible today_

```text
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].
```

### Already planned

_It is on the roadmap_

```text
Hi [customer name],

[Feature] is on our roadmap for [quarter or period]. Plans can change, so I cannot give you a firm date, but I have linked your ticket so you hear from us when it ships.
```

### Not planned

_The team has decided not to build it_

```text
Hi [customer name],

Thanks for suggesting [feature]. We have decided not to build it for now, because [honest short reason]. I know that is not the answer you hoped for. If you need it, [alternative or integration] can do it today.
```

### Requested feature is live

_You built what they asked for_

```text
Hi [customer name],

You asked for [feature] in [month]. It is now live: you can find it under [where], and the guide is here: [help article link]. Thanks for suggesting it.
```

### Ask about the use case

_The request is vague_

```text
Hi [customer name],

Thanks for the suggestion. So I can describe it well to our product team, could you tell me what you are trying to get done, how you handle it today, and how often it comes up? Two or three sentences is plenty.
```

## 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 team

_The ticket needs other skills or permissions_

```text
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 engineering

_A bug or outage needs engineers_

```text
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.
```

### Customer asks for a manager

_They ask to speak to someone senior_

```text
Hi [customer name],

Of course. I have asked [manager name or role] to review ticket [ticket number] and shared the full history, so you do not have to start over. They will contact you by [email or phone] by [time and day].
```

### New agent taking over

_A shift change or reassignment_

```text
Hi [customer name],

I am [new agent name], and I am taking over ticket [ticket number] from [previous agent]. I have read the full thread. Where things stand: [one-line status]. Next, I will [next step] and update you by [time].
```

### Internal handover note

_Paste as an internal note, not to the customer_

```text
Handover for [ticket number]. Customer: [name, plan]. Problem: [one line]. Tried so far: [steps and results]. Promised: [what and by when]. Next step: [action]. Customer mood: [calm, frustrated or urgent].
```

### Waiting on a partner

_The cause sits with a carrier, bank or other vendor_

```text
Hi [customer name],

The cause is on [partner, such as the carrier or payment provider]'s side, and we have opened a case with them, reference [partner case number]. We do not control their timeline, but I will check with them on [day] and update you then, whatever the news.
```

## 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-up

_No reply after your first request_

```text
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-up

_Still no reply_

```text
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.
```

### Closing soon without a reply

_The last follow-up before you close_

```text
Hi [customer name],

We have not heard from you since [date], so we will close ticket [ticket number] on [date]. If you still need help after that, reply to this email and we will pick it up again with the full history.
```

### Please test the change

_You need the customer to confirm a fix_

```text
Hi [customer name],

We have made a change that should fix [problem]. Could you try [action] and tell me whether it works? If it does not, a screenshot of what you see will help us take the next step.
```

### Closed after no reply

_Send when you close a silent ticket_

```text
Hi [customer name],

We have closed ticket [ticket number] because we did not hear back. Nothing is lost: if [issue] comes up again, reply here and we will continue from where we left off.
```

### Waiting for a time to talk

_You agreed on a call but have no time yet_

```text
Hi [customer name],

To book the call we discussed, pick a time that suits you here: [booking link], or reply with two times that work and your time zone. The call takes about [length] minutes.
```

## 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 summary

_The problem is fixed_

```text
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 closing

_You think it is fixed and want them to confirm_

```text
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.
```

### Close with a survey

_You collect satisfaction feedback_

```text
Hi [customer name],

I am glad we got [issue] sorted out. If you have a moment, this one-question survey tells us how we did: [survey link]. Thanks for your patience while we worked on it.
```

### Partly resolved

_One part is fixed and another is still open_

```text
Hi [customer name],

We have fixed [part that is fixed]. [Part still open] needs [what it needs], so I have opened ticket [new ticket number] to track it. That way this one can close, and you get updates on the rest separately.
```

### No fix possible

_You cannot give them what they need_

```text
Hi [customer name],

I am sorry we could not get [goal] working. [Product] cannot [limitation] because [reason]. What we can offer is [alternative]. I am closing this ticket, but reply any time if you want to try the alternative together.
```

### Thanks for reporting

_Their report helped fix something for everyone_

```text
Hi [customer name],

The issue you reported is now fixed for everyone, and your clear report made it easier to track down. [Optional: what changed]. Thank you for taking the time to write in.
```

## 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 response

_The ticket waited longer than your target_

```text
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 update

_You said you would write and did not_

```text
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.
```

### Taking longer than expected

_Your first estimate was wrong_

```text
Hi [customer name],

This is taking longer than we told you. The cause turned out to be [short reason], which needs [what it needs]. Our new estimate is [date], and I will update you on [day] either way.
```

### An outage affected you

_After a service incident_

```text
Hi [customer name],

Our service was down from [start time] to [end time] on [date], and you could not [what they could not do]. I am sorry for the disruption. The cause was [short cause], and we are [what you are changing]. The full report is here: [incident report link].
```

### Service credit under your agreement

_A missed target entitles the customer to a credit_

```text
Hi [customer name],

We missed the [response or uptime] target in your agreement on [date], so you are entitled to a service credit of [amount or percent]. We have applied it to your next invoice, [invoice number]. I am sorry we fell short.
```

### Second miss on the same ticket

_You have let them down twice_

```text
Hi [customer name],

This is the second time we have let you down on ticket [ticket number], and I understand if your patience is running out. I have asked [manager name or role] to oversee it until it is resolved. You will hear from [them or me] by [time].
```

## 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.

1. **Find the ticket type.** Use the situation chips above the library, or search for a word such as "refund", "locked" or "bug".
2. **Copy it, or personalize it.** Copy 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.
3. **Check every fact before you send.** Amounts, dates, links and ticket numbers come from your own systems. Search your reply for "[" so no slot goes out unfilled.
4. **Or improve a reply you already wrote.** Open 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**

```text
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**

```text
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**

```text
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**

```text
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*

Visitor: How do I add a teammate to my account?

Chatbot: 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)_

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

Chatbot: 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](https://luckpanda.app/chatbot/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.

Try it on your website: https://luckpanda.app/chatbot/try