The message that answers instantly — and sets the tone for everything after it.
Auto-reply. An auto-reply is a message sent automatically when a customer contacts a support address, before any person has read the request. Auto-replies confirm the message arrived and usually state when to expect a human answer. Common forms include out-of-office notices, after-hours replies, and acknowledgment emails from a support inbox.
An auto-reply is a trigger and a template: an inbound message arrives, conditions are checked — inside or outside business hours, first message or follow-up — and the matching template goes out within seconds. Sensible implementations add guardrails: no auto-reply to another auto-reply (the classic mail loop), no second acknowledgment when a customer replies on an open thread, and different templates for open hours, closed hours and holidays.
The right way to think about an auto-reply is as expectation design, not deflection. Its job is to make the wait feel chosen rather than suffered. The weakest version is the empty receipt — “we have received your message” — which confirms delivery and promises nothing. The strong version makes one concrete commitment (“a person will reply within four business hours”), offers one or two genuinely useful paths in the meantime, and never pretends to be human.
The silence between sending a message and hearing back is where customer anxiety lives, and anxious customers act: they send a second email, try another channel, or post publicly. Every duplicate they create inflates the queue and slows the real answer — so a good auto-reply is not politeness, it is queue protection. It also quietly reduces pressure on your team: an honest “within four business hours” buys the breathing room that makes a considered first reply possible.
One trap to name directly: an auto-reply is not a first response. Counting it as one makes first response time look instant while the customer is still waiting for a human. Measure from the human reply, always.
Promise only what your worst realistic day can keep, and tie the promise to business hours — “within four business hours” survives weekends; “within four hours” breaks every Friday evening. State your hours and time zone explicitly. Add at most two links, chosen for the address: a status page for a technical inbox, an order-tracking page for a shop, the help center search for everything else. More links read as a wall to keep the customer out.
Then maintain it like the public artifact it is: re-read your own auto-reply quarterly, because it is the single most-sent message your company writes, and it is usually the least recently read. Check it against reality, too — if your promised window and your actual first response time have drifted apart, the auto-reply has become a standing apology you send to everyone.
An auto-reply is the automated edge of a wider reply toolkit — these entries cover the template library, the clock it must not fake, and the hours it depends on.
Give your customers faster answers and your team their evenings back.
Desktop and mobile. Free for solo.