How to write an auto-acknowledgment email that sets expectations

Subject: Re: [original subject]

Thanks for writing in. This is an automatic confirmation that your
message reached our support team.

A person will reply within one business day. If you think of
anything to add, just reply to this email and it will join the
same conversation.

While you wait, these cover the most common questions:
- Getting started: [link]
- Billing and invoices: [link]

If your account is down or you think it's been compromised, reply
with URGENT in the subject line and we'll prioritize it.

— The [Company] support team

Template 2: After hours or weekends#

Subject: Re: [original subject]

Thanks for your message. Our team is offline until [day] at
[time and time zone], and we'll reply then.

If this is about a service outage, our status page has live
updates: [link]

For anything else urgent, such as a security concern, reply with
URGENT in the subject and the on-call person will see it.

— [Company] support

Only use this version during the hours it describes, and only promise an urgent route if someone is actually watching for it.

Template 3: Sales or general inquiries#

Subject: Re: [original subject]

Thanks for getting in touch. Someone from our team will reply
within one business day.

If you're evaluating us, our pricing and plans are here: [link],
and the docs show exactly how setup works: [link].

If you're an existing customer with a support question, writing
to [support address] gets you to the right people faster.

This one gently redirects misrouted support requests without bouncing them.

Adjusting the acknowledgment when things change#

An auto-ack is not a set-and-forget message. The timing line in particular should change when your reality changes, and the moments it matters most are exactly the moments teams forget to update it.

During an outage or incident. When dozens of people write in about the same problem, swap in a temporary version that names the issue, links to your status page, and says you'll send an update to everyone who wrote in once it's resolved. That single change can prevent a wave of "any update?" follow-ups, and it tells customers you already know what's happening.

During a launch or a price change. If you expect a spike, lengthen the timing promise for a few days rather than missing the usual one. Customers forgive "two business days this week while we handle a launch" far more readily than a silent three-day wait.

During holidays. Put the return date in the message, in the customer's terms: a weekday and a date, not "after the break."

Whoever changes the message should also own changing it back. A holiday acknowledgment still running in February is a small thing that makes a company look unattended.

Personalization: a little goes a long way#

Most tools let you insert the customer's name or their original subject line. Using the subject line is almost always helpful, because it confirms which message you received. Using the first name is fine if your data is clean; if names are often missing or mangled, a greeting like "Hi there" beats "Hi {first_name}" or "Hi JOHN.SMITH84."

Preventing auto-reply loops#

Two automated responders can email each other indefinitely: your acknowledgment hits their out-of-office, which hits your acknowledgment, and so on. Mail systems have standard ways to avoid this, and any decent tool should support them.

Mark your auto-replies as automatic. RFC 3834 defines the Auto-Submitted header. Your acknowledgment should carry:

Auto-Submitted: auto-replied

Don't reply to automated messages. Before sending an acknowledgment, skip messages that carry:

• Auto-Submitted with any value other than no
• Precedence: bulk, list or junk
• List-Id or List-Unsubscribe headers (mailing lists and newsletters)
• An empty or MAILER-DAEMON return path (bounces)

Rate-limit per sender. Even with headers checked, send at most one acknowledgment per sender per day or so. Someone who sends five follow-ups in an hour doesn't need five confirmations.

If you're using a hosted inbox or helpdesk, check its settings for these behaviors rather than assuming them.

Testing before you turn it on#

• Send a test from an outside account and read the acknowledgment on mobile
• Reply to the acknowledgment and confirm the reply lands in the same conversation
• Send from an address with an out-of-office on and confirm there's no loop
• Check that every link works and the timing line matches reality
• Confirm the urgent route actually reaches a person

Bottom line#

A good auto-acknowledgment is short, honest and useful. Confirm the message arrived, say when a human will reply in terms you can keep, offer one or two shortcuts and a real urgent path, and send it from an address that accepts replies. Then make sure it can't get stuck talking to another robot.