DEV Community

Rickard Collander
Rickard Collander

Posted on Originally published at supportifier.se

Customer service auto-replies: what should they say?

Almost every customer service team sends an automatic reply when an email or form comes in. It is often the first text the customer gets from you, and often one that was written years ago and never read again. Before Christmas, when you close for a few days and the queue grows, it is time to look at it again.

What is an auto-reply, and what is it not?

An auto-reply confirms that the ticket has arrived; it does not answer the question. The system sends it the moment the email or form comes in, before anyone has read it. The customer is still waiting for what matters: an answer on the substance.

That is why the auto-reply should never count as first response time. If it does, the reports look as if everyone gets an answer in a second, and the real wait disappears from the numbers. How long customers accept waiting in each channel is covered in the article on customer service response time.

That does not make the auto-reply unimportant. A good one does three things: it removes the doubt about whether the email arrived, it sets an expectation for when the answer will come, and it gives the customer a chance to find the answer before anyone has read the message.

What should the auto-reply say?

The auto-reply should say what the customer is wondering at that moment, in the order the questions come up. Six things are enough:

  1. That the ticket has arrived, ideally with a ticket number the customer can refer to.
  2. When the customer will get an answer, in a time you actually keep. "We reply within one working day" beats "we will get back to you as soon as possible", which says nothing.
  3. That the customer does not need to write again. Say that a reply to this email goes into the same ticket. Otherwise the worried customer sends a new email, and you have two tickets about the same thing.
  4. Answers to the most common questions, linking to your help centre: where is my order, how do I return something, how do I change my order. Many find the answer there before anyone has read the email.
  5. What to do if it is urgent, for example a phone number or a chat with opening hours, if you have such a channel.
  6. A sender name and an address that accepts replies. An auto-reply from an address that does not take replies tells the customer nobody is listening.

The customer should be able to read it all on a phone screen without scrolling. Six short points is the ceiling, not the target.

What should the auto-reply not say?

The auto-reply should not repeat the customer's own message. RFC 3834, the standard for automatic replies to email, says the response should be brief, written as plain text and should not include significant content from the original message. The reason is practical: the sender address on an incoming email can be forged. An auto-reply that quotes the customer's text can then send it, order number and address included, to someone else.

Avoid these too:

  • Promises you do not control. "Answer within one hour" in an auto-reply that also goes out on Friday evening.
  • Marketing. The customer has a problem. An offer in the confirmation reads as if you did not understand it.
  • Blame. "Read our FAQ before contacting us" is a reprimand, not help. Write "the answer may already be here" and link.
  • Requests for personal data. Do not ask the customer to send ID numbers or card details in reply to an automated email.

How do you stop the auto-reply from creating a loop?

An auto-reply must not reply to other automated emails. Two auto-replies answering each other can send emails back and forth until someone switches them off, and each one can become a new ticket in the queue. RFC 3834 sets out the rules that prevent it:

  • Do not reply to messages that are automated themselves. A message with an Auto-Submitted header set to anything other than "no" should not get an auto-reply.
  • Mark your own auto-reply. Your reply should carry Auto-Submitted: auto-replied, so other systems know not to answer it.
  • Do not reply to bounces or empty senders, such as MAILER-DAEMON or a message without a return address.
  • Do not reply to the same sender over and over. The standard suggests no more than one identical response per sender within a period of several days, with seven days as a default.

Email programs have their own safeguards. Gmail's auto-reply is not sent to messages in spam or from mailing lists, and the same sender only gets it again after four days. Outlook's out-of-office message is only sent once to each sender until it is switched off and on again.

That works for a person on holiday, but not for a customer service team. A customer who sends two different questions in the same week should get a confirmation for both. So the confirmation should be sent per new ticket from the ticketing system, not by the out-of-office message on a shared mailbox. Replies that land in an existing ticket should not get a new confirmation.

What should the auto-reply say when you close for Christmas?

When you are closed, the auto-reply should say so plainly, with dates. "We are closed 24–26 December and reply from 27 December" gives the customer a point in time to work with. A normal auto-reply promising an answer within one working day is wrong three days in a row.

Customers expect something to work even when you are off. According to Zendesk's CX Trends 2026, 74 per cent of consumers now expect 24/7 service because of AI. That does not mean you have to staff Christmas Eve, but the auto-reply should point to what works without you: the help centre, order status and the returns form.

Three things to put in the Christmas version:

  1. Which days you are closed and when you reply again.
  2. That replies come in the order the tickets arrived, so nobody needs to write again to get to the front.
  3. Answers to the questions that come at that time: deliveries that will not arrive in time, gift cards and exchanges after Christmas.

Put a date in the calendar to switch back. The Christmas greeting still running in February is a common mistake. More on preparing for the peak season is in the article on Christmas trading and customer service.

Can the confirmation give the answer straight away?

Yes, for some questions, but only when the answer is certain. An auto-reply that links to the help article on returns solves the returns question for whoever reads it. It is still the customer who decides whether the answer was enough, and the ticket should stay open until someone has replied or the customer has said it is solved.

Better still is showing the answer before the ticket is sent. In Supportifier, the AI form shows answers from the knowledge base while the customer types their question, and the customer chooses whether to send the ticket anyway. Then the confirmation is only needed for the questions that really need a person.

What to do

  1. Send an email to your own customer service from a private address and read the auto-reply on your phone. Does anything in it no longer hold?
  2. Rewrite it using the six points above. Remove anything that does not help the customer at that moment.
  3. Change the response time to one you keep even on Friday evening, or let it follow your opening hours.
  4. Link to the three most common questions in the help centre. Look at your ticket reports to see which they are; do not guess.
  5. Check that the confirmation goes out per new ticket and not on replies in existing tickets, on bounces or on other auto-replies.
  6. Write the Christmas version now, with dates, and set a reminder for when to switch it back.
  7. Measure first response time from the ticket to the first real answer, not to the auto-reply.

Common questions

Does the auto-reply count as first response?

No. The auto-reply confirms that the ticket arrived but does not answer the question, and the customer counts the wait until someone does. If you include it, first response time drops to almost zero for every ticket, and you can no longer see how long customers actually wait. Measure from ticket creation to the first real answer, from a person or an AI.

Should the auto-reply come from a no-reply address?

No. Customers reply to the auto-reply, often to add something they forgot, and those replies belong in the same ticket. A no-reply address loses them or bounces them, and the customer gets the impression that nobody reads anything. Send the confirmation from the customer service address and make sure replies are linked to the ticket.

How long should an auto-reply be?

Short enough to read on a phone screen without scrolling. Confirmation, ticket number, when the answer comes, two or three links to common answers and what to do if it is urgent. The standard for automatic email responses says they should be brief and written as plain text. Anything beyond that does not get read.

Should we send auto-replies in chat too?

In chat you usually do not need an auto-reply, because the customer can see straight away whether someone is there. What is needed is a message when nobody is: that chat is closed, when it opens and where the answer may be in the meantime. If the customer leaves a question while chat is closed, it should become a ticket with the same confirmation as an email.

Sources


Originally published at www.supportifier.se/en/blog/auto-reply-customer-service.

Top comments (0)