Skip to content

Guides

Write a support auto-reply that helps

An auto-reply is the first thing a customer gets from you. Used well, it confirms their message arrived, says when to expect an answer and points to a quick fix. Used badly, it is noise.

Last reviewed

Confirm the message arrived

Start by saying you received the message and that a person will read it. Reference the ticket number if you have one, so customers can quote it later.

Say when they will hear back

Give a real time, such as within one working day. If you are closed, say when you reopen. A specific promise is more useful than a vague thanks.

Keep it short and plain

Four to six lines is plenty. Avoid long legal text and marketing in the same email. The goal is reassurance and a next step.

Handle hours and holidays

Change the wording when the team is away so the promised time is true. A reply that says one working day during a holiday week costs you trust.

Review it quarterly

Check the links, the times and the tone every few months. Out-of-date auto-replies are common and quietly irritating.

Questions

Should an auto-reply count as a first response?

No. It confirms receipt but does not help the customer. Measure first response time from the first reply written by a person.

Do auto-replies reduce tickets?

They can, when the links answer common questions. They work best with a short, specific list rather than a long menu of options.

Should I send one for every channel?

Email benefits most. For chat, a short greeting with the expected wait is enough, and social messages usually need a quick personal reply.

Written by Flatdesk, a help desk for small support teams at one flat price per agent. Try it free for 14 days, no card.