Email auto response sample templates for support teams

Below is an email auto response sample for every situation a small support team runs into, from the everyday "we got your message" to holiday closures, outages and refund requests. Each one is short enough to read on a phone, tells the customer when a person will reply, and shows them how to add details without opening a second ticket.

Copy them, change the bracketed parts, and read the setup rules near the end before you switch anything on. A good template sent at the wrong moment, or sent five times to the same person, does more harm than no reply at all.

If you only need one, start with this:

Subject: We got your message [#ticket number]

Hi [first name],

Thanks for writing in. Your request is with our support team and a person will reply by [time, e.g. 3pm Eastern today].

If you have screenshots, an order number or anything else that helps, just reply to this email. It will be added to the same request.

[Team name] support

What a good email auto response sample does

An auto response has one job: stop the customer from wondering whether their email landed and when they will hear back. Every extra sentence competes with that job. The templates in this post all follow the same short checklist:

• Confirm the message arrived, in the first line.
• Give a reply time a customer can plan around, such as "by 3pm Eastern" or "within one business day", and make sure your team can actually meet it on a bad day.
• Include a reference number in the subject so the customer can quote it and replies stay in one thread.
• Tell them to reply to the same email with extra details. Customers who are unsure send a fresh email, and now you have two tickets for one problem.
• Offer an urgent route only if one really exists and someone watches it.
• Link to one help article when it is likely to solve the problem. A list of six links reads as "please go away".

Many of the repeat emails a support inbox gets ("did you get this?", "any update?") trace back to an auto reply that skipped one of those points. The table shows what each situation needs most.

General acknowledgement samples

These go out when a new email arrives during working hours. Send them once per new conversation, never on replies inside an open thread.

Standard acknowledgement

Subject: Re: [original subject] [#ticket number]

Hi [first name],

We have your message and a member of the support team will reply within [2 business hours]. Our hours are [Monday to Friday, 9am to 6pm Eastern].

Need to add something? Reply to this email and it joins the same request.

Thanks,
[Team name]

Use this as your default. Keep the original subject in the reply so the customer can find the thread later, and put the ticket number at the end of the subject rather than the start, where it pushes their own words out of view in most inbox lists.

Acknowledgement with a self-help link

Hi [first name],

Thanks for getting in touch. A person from our team will reply by [time].

Many questions about [topic, e.g. password resets] are answered here: [link to one article]. If that solves it, you don't need to do anything else. If not, we'll still be in touch as promised.

[Team name] support

Only use this when you can route by topic, for example a contact form with a "login problem" option, so the link matches what they asked. A generic help center link on every reply teaches customers to ignore the paragraph.

Request that needs more information

Hi [first name],

Your message reached us. To sort this out on the first reply, it helps to have:

- your account email or order number
- what you expected to happen and what happened instead
- a screenshot, if there is an error message

Reply to this email with whatever you have. Someone from the team will pick it up by [time] either way.

[Team name]

Use this on bug reports and technical requests. It saves a full round trip, which on email often means a day. The last line matters: customers should not feel they are blocked until they fill in a form.

After hours and weekend samples

An after hours reply should tell the customer exactly when the wait ends. State the time zone, because "back at 9am" means nothing to a customer six hours away.

Evenings

Hi [first name],

Thanks for your email. Our support team is offline right now. We work [Monday to Friday, 9am to 6pm Eastern] and will reply to you tomorrow morning, usually before [11am Eastern].

If your question is about [common topic], this guide may help in the meantime: [link].

[Team name]

Weekends

Hi [first name],

We got your message. Our team is away for the weekend and back on [Monday] at [9am Eastern]. Requests are answered in the order they arrived, and we expect to reply to yours by [Monday afternoon].

Reply here if you want to add anything before then.

[Team name] support

Monday mornings carry the weekend backlog, so promise the afternoon, not the first hour. You can estimate how big that backlog gets with the after-hours coverage calculator.

After hours with an urgent route

Hi [first name],

Our support team is offline until [time and time zone]. We'll reply to this email then.

If [your store is down / you can't take payments], call or text our on-call line at [number]. That line is for outages only, and someone answers it around the clock.

[Team name]

Define "urgent" in the email itself. "For urgent matters, call us" invites every customer to decide their own problem is urgent, and your on-call person stops trusting the phone.

Holiday and out of office samples

Holiday replies are where teams get burned by dates. Write the exact days, include the year if the closure runs over New Year, and schedule the end date when you turn the reply on.

Company holiday closure

Subject: Closed for [holiday] until [date]

Hi [first name],

Thanks for your message. Our team is closed for [holiday] from [date] to [date] and back on [first working day].

We'll reply to every email in the order it came in. Because of the holiday backlog, please allow until [date] for a reply.

[Team name] support

Reduced holiday hours

Hi [first name],

Over the holidays our support hours are shorter: [dates], [10am to 2pm Eastern]. We are still answering every email, a little more slowly than usual, so expect a reply within [2 business days].

For delivery dates and returns over the holidays, see [link].

[Team name]

One person out of office, on a shared support address

Hi [first name],

[Agent name] is out until [date], so your message has gone to the rest of the support team. [Colleague name] is picking up [agent name]'s requests and will reply by [time].

You don't need to send it again.

[Team name]

Use this when customers write to a named account manager or agent. A personal out of office ("I'm away, contact someone else") pushes the work back onto the customer. This version tells them it has already been handed over.

High volume and delay samples

When the queue is longer than usual, say so plainly and give a new time. Customers are far more patient with "two days" stated up front than with silence that turns into two days.

Volume spike

Hi [first name],

We have your message. We're getting more emails than usual right now, after [a product launch / a sale / a holiday], and replies are taking about [2 business days] instead of our usual [same day].

Your place in the queue is saved. Sending another email moves it to the back, so reply to this one if you need to add details.

[Team name] support

The line about the queue does real work. Many help desks treat a new email as a new ticket, so customers who chase by writing again can push themselves further back without knowing it.

Known outage or incident

Subject: We know about the [service] problem

Hi [first name],

If you're writing about [the problem, e.g. failed logins since 2pm Eastern], we know about it and the team is working on a fix. Updates are posted at [status page link] every [30 minutes].

You don't need to do anything. If your email is about something else, a person will reply by [time].

[Team name]

Turn this on the moment the incident is confirmed and off when it is resolved. For the status updates themselves, the incident message templates cover each stage from "investigating" to "resolved".

Delay on a request you already acknowledged

Hi [first name],

An update on your request [#ticket number]: it needs input from our [billing / engineering] team, so it is taking longer than we said. We now expect to get back to you by [date].

Nothing is needed from you right now. We'll write again if that date changes.

[Agent name]

Strictly speaking this is a manual message, or a canned response, sent when a deadline slips. It belongs here because it heads off the "any update?" email that would otherwise arrive the next day.

Order and billing samples

Money questions make customers anxious, so these replies need to be specific about what happens next and careful about what you ask for.

Where is my order

Hi [first name],

Thanks for your message about your order. You can see live tracking any time at [tracking page link] with your order number and email.

If tracking hasn't moved for [3 business days], or it says delivered and you don't have it, reply with your order number and we'll look into it by [time].

[Store name]

Refund or return request

Hi [first name],

We've received your refund request. A person reviews every request and will reply within [1 business day].

To speed things up, reply with your order number and, for damaged items, a photo. Approved refunds go back to the original payment method and usually show up within [5 to 10 business days], depending on your bank.

[Store name] support

Billing or invoice question

Hi [first name],

Thanks for writing about your bill. Someone from our billing team will reply by [time].

Please don't send card numbers by email. If we need to update a payment method, we'll send you a secure link instead.

Your invoices are also in [Settings, Billing] in your account.

[Team name]

The line about card numbers protects you as much as the customer. If it is in the auto reply, customers stop pasting them into emails.

Cancellation request

Hi [first name],

We've got your cancellation request for [account or plan]. A person will confirm it by [time], along with the date your access ends and whether any refund applies.

If you'd rather pause or switch to a smaller plan, reply and say so. Either way, nothing is charged while we process this.

[Team name]

Only include the last sentence if it is true for your billing setup. A cancellation reply that turns out to be wrong about charges is one of the fastest ways to get a chargeback.

Closed ticket and feature request samples

Ticket closed

Hi [first name],

We've marked your request [#ticket number] as solved: [one line on what was done].

If the problem comes back or something isn't right, just reply to this email and it reopens with the full history, so you won't have to explain it again.

[Team name]

Feature request received

Hi [first name],

Thanks for the suggestion. We've passed it to the product team with your notes. We can't promise when or whether it will be built, but every request is read, and if it ships we'll let you know.

[Team name]

Be honest about the odds. "We love this idea" on every request trains customers to expect features that never come.

How to set them up without annoying customers

The wording is the easy part. Many complaints about auto replies come from when and how often they fire. Before you switch one on:

1. Send one auto reply per conversation. Replies inside an open thread should never trigger a fresh "we got your message".
2. Limit repeats to the same sender. Gmail's own vacation responder replies to a given sender once and then waits four days before replying again, according to Google's help page. Help desks usually let you set your own rule; once per sender per day is a sensible floor for support.
3. Don't reply to machines. The email standard for automatic responses, RFC 3834, says a responder should not answer messages marked as automatically submitted, and recommends a seven day gap for repeated away notices to one sender. In practice: skip no-reply addresses, mailing lists and other auto replies, or two systems will email each other until someone notices.
4. Keep the subject recognisable. RFC 3834 suggests marking automatic replies (an "Auto:" prefix is allowed) and keeping the original subject, which also helps the customer find the thread.
5. Promise a time from your real numbers. Look at how long first replies actually take on your slowest normal day, then promise a little more. The first response time SLA estimator helps you set a number your team can keep.
6. Put an end date on every temporary reply. A holiday or outage message still running a week later is an easy mistake to make and a very visible one.
7. Test from an outside address. Send an email from a personal account, check the subject, the time zone, the links and the ticket number, then reply to it and confirm nothing fires a second time.

Once the auto reply is live, the human reply that follows matters more. Keep your common answers as canned responses so the promised reply arrives on time; there are 70 to adapt in our canned responses examples.

If email is one of several places customers reach you, the promise in the auto reply only holds when everyone works the same queue. Sellio is a shared inbox where email and website chat land in one list for the whole team, priced per workspace rather than per seat (see pricing). If email is your main channel, our page on email ticketing covers how threads, assignment and statuses fit together, and the Freshdesk vs Help Scout comparison looks at two email-first help desks for a five-person team.

FAQ

What should a customer service auto reply email say?

That the message arrived, when a person will reply (a specific time or number of business hours, with a time zone), a reference number, and that replying to the same email adds to the request. Add an urgent contact or one help link only when they are genuinely useful.

How long should an auto response email be?

Short enough to read on a phone without scrolling: two to four short paragraphs, roughly 50 to 100 words. If it needs more, the extra detail probably belongs in a help article you link to.

Should every incoming email get an auto reply?

No. Send one per new conversation, skip replies inside an open thread, and never reply to no-reply addresses, mailing lists or other automatic messages. Limit repeats to the same sender, for example once a day.

Is it better to promise "within 24 hours" or give a specific time?

A specific time or business-hours window works better because customers can plan around it, and "24 hours" sent on a Friday evening is a promise most small teams break. Base the number on your real first response times, not your best day.

What is the difference between an auto response and a canned response?

An auto response is sent by the system the moment an email arrives, with no person involved. A canned response is a saved reply an agent picks and sends by hand, usually after reading the email. Most teams need both: the auto reply sets the expectation and the canned response helps meet it.