How to Acknowledge an Email: 15 Reply Templates

Someone sends you a contract, an invoice, a complaint, or a brief. You cannot deal with it today. So you leave it, plan to come back to it, and from the sender's side that looks exactly the same as being ignored. Silence has no tone. The reader fills it in, and under pressure they rarely fill it in kindly.

An acknowledgment fixes that in about fifteen seconds, and most companies still skip it. In its Customer Service Benchmark Report, last updated in March 2023, SuperOffice emailed 1,000 companies with two questions and scored the responses. They found that 90% of companies "do not acknowledge or inform the customer that an email has been received," that 62% never responded at all, and that the average response time was 12 hours and 10 minutes. Worth knowing that SuperOffice sells CRM software and ran the study itself, so read the numbers as vendor research rather than an independent audit. The direction still matches what anyone who has emailed a company recently would guess.

Disclosure: we make InboxPilot, an AI email assistant that drafts replies inside Gmail and Outlook. The format and the templates below work in any email client with no software at all. There is one section near the end where our product is relevant, and it is labeled.

Key takeaways

• What an acknowledgment email actually is: a receipt, not an answer. It names what arrived and what happens next.
• The four-part acknowledgment format: confirm the thing by name, prove you read it, commit to a date, close cleanly.
• 15 acknowledgment email templates: documents, payments, complaints, applications, managers, and the ones you will have to decline.
• Phrases that work, and the ones to retire: "Duly noted" and "Well received" are doing damage you cannot see.
• Why a read receipt is not an acknowledgment: Gmail blocks them on personal accounts, and Outlook lets the recipient decline.
• Why an auto-reply is not one either: Gmail replies once per sender, then goes quiet for four days.
• Five mistakes that make an acknowledgment worse than silence: mostly promises with timestamps on them.
• A reusable prompt for drafting acknowledgments: copy it into any assistant you already use.

What an acknowledgment email actually is

An acknowledgment email is a short reply that confirms a message arrived, names what arrived, and states what happens next. It is not the answer. It is the receipt.

That distinction is the whole skill. An acknowledgment buys time honestly, and it only works if everyone reads it the same way: the sender learns their message landed with a person, learns roughly when the real reply comes, and stops wondering whether to resend. You get the item off your conscience and into a queue with a date on it.

Three things get confused with acknowledgment and none of them do the job:

• A full reply answers the question. If you can write one now, write it. An acknowledgment in front of an answer you already have is just an extra email.
• An auto-reply fires without a person reading anything, which is why it can never reference what you sent.
• A read receipt is a technical notification that a message was opened. It tells the sender nothing about whether a human understood it.

The British and American spellings both appear in the wild. "Acknowledgment" is standard in US usage, "acknowledgement" in UK usage, and no reader has ever thought less of you for either.

The four-part acknowledgment format

Every acknowledgment worth sending does four things, usually in three sentences.

1. Confirm, and name the thing. Not "your email". The actual item. "The signed MSA", "your invoice 4417", "the shortlist for the Tuesday session". Naming it proves a person opened the attachment, and it gives the sender a searchable record they can point back to later.

2. Add the one detail that proves you read it. A single specific reference does more for trust than any amount of warmth. "I can see the delivery date moved to the 14th." "You have flagged the pricing on line 3." This is the part templates usually omit and the part that makes yours not look like a template.

3. Commit to a next step with a date. A next step without a date is a wish. A date you will actually hit beats an impressive one you will miss, because the sender now has a timestamp and will hold you to it. If you genuinely do not know, say what you are waiting on and when you will know.

4. Close without inviting a reply you do not want. "No need to reply" and "I will come back to you" both end the thread. "Let me know your thoughts" reopens it, which is fine when you want thoughts and a small tax on both of you when you do not.

Subject lines rarely need inventing. Reply in the thread so the sender's own subject carries through, since a fresh subject breaks threading in Gmail and Outlook and orphans the acknowledgment from the thing it acknowledges. When you do need a new one:

15 acknowledgment email templates

Square brackets mark the parts you replace. Every one of these assumes you are replying in the existing thread.

Everyday acknowledgments

1. The two-line default. For anything where the sender simply needs to know it landed.

Hi [Name],

Got this, thank you. I will come back to you with [the thing] by [day].

[Your name]

2. A request you cannot answer yet. The most common case, and the one people avoid because they feel they need an answer to reply at all.

Hi [Name],

Thanks for this. I have the request for [specific thing] and I can see you need it before [their deadline].

I need to check [the dependency] before I can give you a real answer, so I will have that to you by [day]. If your timing changes before then, tell me and I will move it up.

[Your name]

3. Acknowledging your manager. Short, no hedging, no promises about how you feel about the work.

Thanks [Name], I have it. Starting on [the task] this afternoon and I will have a first version with you [day].

4. Something you have to pass on. Say who has it now, so the sender is not chasing you for someone else's work.

Hi [Name],

Thanks for sending this through. This one sits with [team or person], so I have forwarded it and copied you. [Name of owner] usually replies within [timeframe].

If you have not heard back by [day], come back to me and I will chase it.

[Your name]

Documents, payments, and contracts

5. Receipt of documents. Count what arrived. This is the acknowledgment most likely to be dug up months later.

Hi [Name],

Confirming receipt of the [three] documents: [document 1], [document 2], and [document 3]. All opened correctly on my end.

I will review them and confirm whether anything else is needed by [day].

[Your name]

6. A signed contract. Name the version, because contract threads accumulate versions.

Hi [Name],

Thank you, the signed [agreement name] dated [date] has been received and filed. I will countersign and return a fully executed copy by [day].

[Your name]

7. A payment. Include the amount and the reference. It closes the loop for their finance team as well as yours.

Hi [Name],

Confirming we have received your payment of [amount] against invoice [number]. Your account is now settled in full and no further action is needed.

Thanks for sorting it out so quickly.

[Your name]

8. An invoice you have to route. Never let an invoice sit in silence, because silence is what turns a payment query into a chase.

Hi [Name],

Received, thank you. Invoice [number] has gone to accounts payable today. Our standard terms are [terms], so payment should reach you by [date].

If it has not landed by then, reply here and I will follow it up directly.

[Your name]

Customers and clients

9. A support request. Repeat their problem in your own words. It is the fastest way to prove a person read it.

Hi [Name],

Thanks for getting in touch. To make sure I have this right: [restate the problem in one sentence], and it started [when].

I am looking into it now and will have an update for you by [day]. If anything changes at your end in the meantime, reply here and it will come straight to me.

[Your name]

10. A complaint. Acknowledge the experience without conceding fault you have not established, and give a named owner.

Hi [Name],

Thank you for telling us. I am sorry this has been your experience with [the specific thing], and I would rather hear it than not.

I am looking into what happened with [team or person] and I will come back to you personally by [day], whether or not I have the full picture by then.

[Your name]

11. A quote or RFQ. State what you have and what is missing, in one pass. Every round trip costs you a day, which is why RFQ handling is the one place where acknowledging instead of answering is most expensive.

Hi [Name],

Thanks for the enquiry. I have your requirement for [quantity] of [item], delivery to [location] by [date].

To price it accurately I need [the missing detail]. Send that over and I will have the quote with you within [timeframe].

[Your name]

12. A request you will probably have to decline. Do not use the acknowledgment to soften a no you have already decided on. Acknowledge the request, and say when the answer comes.

Hi [Name],

Thanks for asking, and for the detail. I want to give you a straight answer rather than a fast one, so I am checking [the constraint] with [team] and will come back to you by [day] either way.

[Your name]

Applications, meetings, and feedback

13. A job application. People check these threads obsessively. A date and a rejection policy are worth more than warmth.

Hi [Name],

Thank you for applying for the [role] position. Your application and CV have been received and are with the hiring team.

We are reviewing applications until [date] and will contact candidates moving to a first conversation the week of [date]. We reply to every applicant either way, so you will hear from us regardless of the outcome.

[Your name]

14. A meeting invite or a reschedule. Confirm the time in a form that survives time zones.

Hi [Name],

Confirmed for [day, date] at [time, time zone]. I have accepted the invite and added [the agenda item] to it.

If you would like to cover anything else, send it over beforehand and I will make room.

[Your name]

15. Feedback you disagree with. Acknowledge that it was received and taken seriously. Argue later, in a different email.

Hi [Name],

Thanks for taking the time to write this up. I have read it properly and I want to sit with the point about [specific point] before I respond, rather than reacting to it today.

I will come back to you by [day] with a considered reply.

[Your name]

Phrases that work, and the ones to retire

Acknowledgment openers are a small vocabulary that carries a lot of unintended tone. A few are safe in almost any context. A few are quietly costing people goodwill.

"Noted" deserves its own note, because it generates more workplace friction than any other two-word reply. It is not rude. It just carries no tone at all, so the reader supplies one, and a reader who is anxious about what they sent supplies the coldest reading available. Between two colleagues who message all day, it is fine. Sent to a customer who has just described a problem, it lands as a shrug. The fix costs four words: say what you noted.

Why a read receipt is not an acknowledgment

Read receipts get proposed as the low-effort alternative to acknowledging anything. They cannot do the job, and the vendor documentation is unusually clear about why.

Google restricts them outright. Gmail Help states that "read receipts are only available to work or school accounts. They don't work with personal Gmail (@gmail.com) accounts." Even inside a Google Workspace organization, an administrator can restrict them, and Google notes that "to receive a read receipt in your inbox, the recipient of your email may need to approve it first." Where approval is required, the recipient chooses "Send receipts" or "Not now".

Microsoft is equally direct about Outlook: "In Outlook, the message recipient can decline to send read receipts." Microsoft also separates the two kinds of confirmation, and the difference matters: "A delivery receipt confirms delivery of your email message to the recipient's mailbox, but not that the recipient has seen it or read it. A read receipt confirms that your message was opened."

Opened is the operative word. A message can be opened in a preview pane by someone clearing notifications on a phone. It can be opened by the wrong person on a shared address. Nothing in a read receipt tells the sender that a human understood the request or intends to do anything about it, which is the entire thing an acknowledgment communicates.

There is a second cost that nobody puts in the documentation. Requesting a receipt on every message tells the recipient you are keeping score, and people notice.

Why an auto-reply is not one either

The other shortcut is a blanket auto-reply, and Gmail's own documented behavior explains why it disappoints people at exactly the wrong moment.

Google's vacation responder runs in whole days: "your automatic reply starts at 12:00 AM on the start date and ends at 11:59 PM on the end date, unless you end it earlier." There is no native way to say "outside working hours". More importantly, it does not fire every time. Google documents that "in most cases, your reply is only sent to people the first time they message you," and that it replies again only if the same person contacts you after four days while the responder is still on. Messages in spam and messages addressed to a mailing list you subscribe to get nothing at all.

Follow the consequence through. A customer emails on Monday and gets a friendly acknowledgment promising a reply soon. They chase on Wednesday because nothing came, and that chase gets silence. The auto-reply made a promise and the mechanism then declined to keep making it, to the exact person most in need of reassurance.

Auto-replies are the right tool for a genuinely unstaffed inbox: holiday closures, planned shutdowns, an address that has moved. They are the wrong tool for a staffed inbox that is simply behind. We covered the mechanics of that in more depth in shared mailbox auto-reply.

Five mistakes that make an acknowledgment worse than silence

Promising a date you will miss. An acknowledgment converts a vague delay into a documented one. If you say Thursday and deliver the following Wednesday, you have not bought goodwill, you have handed the sender evidence. Pick the date you can defend on your worst week.

Acknowledging without naming what you received. "Thanks, got it" against a message with four attachments leaves the sender unsure which parts got through. It also gives you nothing to point to later.

Acknowledging and then going quiet. The acknowledgment is a promise to close a loop. Leaving it open is worse than never having opened it, because you have now demonstrated that a person read the message and chose not to act.

Reply-all acknowledgments. Fifteen people did not need to know you personally received the deck. Acknowledge to the sender.

Acknowledging when you could have answered. This is the most common one and the most expensive. If the question is "what is your lead time on the 40mm valves", and the lead time is written in a document you own, the acknowledgment is pure overhead. You have sent two emails to accomplish what one would have done, and the customer still does not know the lead time.

That last one is worth dwelling on, because a lot of inboxes are full of acknowledgments standing in for answers that already exist somewhere in the business.

A reusable prompt for drafting acknowledgments

If you already use an AI assistant, this prompt produces acknowledgments that read like a person wrote them, mostly because it forbids the things that make them read otherwise. Paste it, then paste the email underneath.

You are drafting a short acknowledgment reply to the email below.

Rules:
- Two to four sentences. No preamble, no restating the whole message.
- Sentence 1: confirm what arrived, by name. Not "your email", the
  actual document, invoice, request, or application.
- Sentence 2: reference one specific detail from the message that
  proves a person read it.
- Sentence 3: the next step and the date it happens by. If I have not
  given you a date, write [DATE] rather than inventing one.
- Match the sender's formality. Do not add enthusiasm they did not use.
- Never promise an outcome, only a next action.
- If the email can be fully answered with the information provided,
  say so instead of drafting an acknowledgment.

My relationship to the sender: [customer / manager / vendor / applicant]
My realistic turnaround: [e.g. two business days]

Email:
[paste the email here]

Two things to check before sending whatever comes back. Any date it produces is invented unless you supplied it, and any claim about your process, your terms, or your pricing is a guess unless it came from you.

When acknowledgment should stop being a human job

This section is about our product, so treat it accordingly.

Acknowledging email is cheap once and expensive four hundred times. The teams that feel this hardest are the ones running a shared address where the same handful of requests arrive on rotation: order status, quote requests, document chases, availability questions. Every one gets acknowledged, and the acknowledgment is not the work. The answer is.

InboxPilot sits in the Gmail or Outlook inbox the team already uses, reads incoming mail, and drafts a reply grounded in your own documents and price lists rather than a generic template. A person approves each send. For the messages that genuinely need acknowledging, the draft is already written with the specifics filled in. For the ones that only needed an answer, you skip the acknowledgment entirely and send the answer, which is the outcome the sender wanted in the first place.

Three honest caveats. A draft is only as good as the documents behind it, so if your lead times and terms live in someone's head, that is the thing to fix first. Keep a person on the approve button well past the point where it feels necessary, particularly for anything with a number in it. And if your inbox gets a handful of messages a day, the four-part format above and a bit of discipline will do everything software would, for free.

Related reading

• Shared mailbox auto-reply: the documented limits of canned responses in Gmail and Microsoft 365.
• How to automate your Gmail inbox: filters, templates, and the vacation responder, step by step.
• What an AI email agent does: the category explainer, including what it is not.
• Generate emails from your own documents: how a draft gets grounded in your price list instead of guesswork.
• Best RFQ email management software: where quote requests go wrong between acknowledgment and price.
• Best shared inbox software: the tools teams shortlist when acknowledgment volume becomes a staffing problem.
• InboxPilot pricing: plans and draft limits.

Gmail read receipt and vacation responder behavior is quoted from Google's Gmail Help articles "Request or return a read receipt" and "Send an automatic reply when you're out of office", both checked August 2026. Outlook read receipt behavior is quoted from Microsoft Support, "Add and request read receipts and delivery notifications in Outlook", checked August 2026. Response and acknowledgment rates are from SuperOffice's Customer Service Benchmark Report, a study of 1,000 companies conducted and published by SuperOffice, a CRM vendor, and last updated March 2023. Vendor documentation changes; check the current pages before relying on a specific limit. Names, invoice numbers, and dates in the templates are illustrative. InboxPilot is the publisher of this article.