Skip to main content

Acknowledgement email templates for customer service: confirming you have their message, and what happens next

Seven emails for the first reply, when you have read the message but do not have the answer yet. Each one confirms it arrived, shows a person read it, and gives a time you can keep.

The templates

Each one copies with its subject line. The parts in brackets are the parts to change; everything else can go out as written.

Bug report: got it, and here is what I need

Subject: Re: [their subject line]

Hi [Name], Thanks for reporting this. I have read it and I am looking into it. To track it down, could you send me: 1. The version of [Product] you are on ([where to find it, for example: Product menu, About Product]) 2. Your [macOS / iOS / browser] version 3. [A screenshot of the error / a short screen recording / the log file from location] If you can tell me the steps that make it happen, even roughly, that helps most of all. I will get back to you once I have had a proper look, [by day / within a couple of days]. [Your name]
Acknowledging a complaint

Subject: Re: [their subject line]

Hi [Name], Thank you for telling me, and I am sorry [Product] let you down. So I am sure I have understood: [their complaint, in one sentence, in your own words]. I want to look into what happened before I answer, rather than guess. You will hear from me by [day or date] with what I found and what I am going to do about it. [Optional, if you can act now:] In the meantime, I have [what you have already done, for example: paused your renewal]. [Your name]
A feature request

Subject: Re: [their subject line]

Hi [Name], Thanks for the suggestion. It is now on my list of requests, [with a note of how you would use it / alongside a couple of similar asks]. I will be honest about timing: I cannot promise when, or whether, it will be built. One question that would help me decide: what would you do with it that you cannot do now? If it ships, I will write to tell you. [Your name]
An honest auto-reply for a one-person business

Subject: Got your message: [Product] support

Hi, Thanks for writing. This is an automatic reply, just to confirm your email arrived. [Product] is made and supported by one person, me, so the reply will come from me. I usually answer within [one working day], and I work [Monday to Friday, your time zone]. If your email is about [billing / your licence], it helps to include [the email address you bought with / your order number]. [Your name]
When the answer will take a few days

Subject: Re: [their subject line]

Hi [Name], A quick note so you are not left wondering: I have your email, and [your question] needs more than a quick answer. [One sentence on why, for example: I need to reproduce it on an older version of macOS.] You will have a proper reply by [day or date]. If I find the answer sooner, you will have it sooner. [Your name]
Urgent: an outage or data at risk

Subject: On it now: [short description of the problem]

Hi [Name], I have your message and I am working on it now. [One sentence on what you know so far, for example: I can see the sync server is failing, and it is affecting other customers too.] [Only if data is involved, and only if it is true:] Your data is [safe / backed up as of time]. Please do not [reinstall / delete the app / sign out] until you hear from me, because [reason]. I will update you by [time], even if the only news is that I am still on it. [Your name]
The short version

Subject: Re: [their subject line]

Hi [Name], Got it, thanks. I will look into this and reply properly by [day]. [Your name]

Subject lines for an acknowledgement

A personal acknowledgement belongs in the customer’s thread, under their own subject. Only an auto-reply needs one of its own, and it should say plainly what it is, so nobody mistakes it for the answer.

  • Re: [their original subject line] (keeps it in the same thread)
  • Got your message: [Product] support (for an auto-reply)
  • Looking into [short description of the problem]
  • Your email about [topic]: what happens next
  • On it now: [short description of the problem]

What makes an acknowledgement worth sending

  • It names a time. “We will get back to you shortly” tells them nothing. “By Thursday” gives them something to plan around, and you something to keep.
  • It shows a person read it. One sentence restating the problem is the difference between an acknowledgement and a receipt.
  • It asks for everything at once. A bug acknowledgement that asks for the version today, the OS tomorrow and a log on Friday costs the customer three round trips.
  • It does not invent a ticket number. For one person, “Ticket #48213” pretends to be a department and gives the customer nothing to use. Their email address and the thread are the reference.
  • It says what to do in the meantime, when there is something. A workaround, or a warning not to reinstall, is worth more in the first email than in the second.
  • It is short. Everything that belongs in the real answer should wait for the real answer.

The second email is the one that goes missing

The acknowledgement is easy to send. The trouble starts right after: the last message in the thread is now yours, and in a mail client “I replied” and “I answered” look identical. The thread gets archived with the rest, Thursday comes and goes, and the customer who was told to expect a reply is still expecting it.

Moorline treats those as two different things. A conversation stays on your list until the work is handled and the customer has been told, however many holding replies sit in the thread. The acknowledgements you send every week can live as snippets, one ⌘; away in the composer, with {name} filled in as the customer’s first name. Moorline does not send anything on its own, auto-replies included; if you want one, your mail host’s auto-responder is the place for it. And when the fix does land, the issue resolved email templates are the second email.

Questions people ask

What is an acknowledgement email in customer service?

A short reply that confirms a customer’s message arrived, that a person has read it, and when they will get a full answer. It is not the answer itself. It buys time honestly when the real reply will take longer than the customer would expect to wait.

How do you acknowledge a customer complaint by email?

Thank them for telling you, apologise for the experience without arguing the facts yet, restate the complaint in one sentence so they know it was understood, and give a date for your full reply. Leave the investigation and any defence out until you actually have the facts.

How quickly should I acknowledge a customer email?

As soon as you know the full answer will take longer than they would expect to wait. If you can answer properly within the day, skip the acknowledgement and send the answer: an acknowledgement followed an hour later by the reply is one email too many.

Should a one-person business use an auto-reply?

Only an honest one: it says the email arrived, who reads it and roughly when they will hear back. An auto-reply promising "a member of our team" when there is one of you, or a ticket number nobody will ever quote, sets expectations you cannot meet. If you usually reply within a few hours, you may not need one at all.

What should I write instead of "we have received your message"?

Say what happens next. "I have your message and will reply by Thursday" carries the same fact plus a promise. "Your request has been received" carries only the fact, and leaves the customer wondering whether anyone will ever read it.