Setting Up a Contact Form Autoresponder

Someone fills in your contact form, hits Send, and sees "Thanks, we'll be in touch." Then nothing arrives in their inbox.

Did it go through? Did they typo their own email address? Should they try again or wait? That small uncertainty does more damage than it looks like it should — people submit twice, or they decide you're not responsive and email a competitor instead. An autoresponder closes the gap, and it costs you four sentences written once.

The Setting That Actually Breaks

An autoresponder needs to know three things: that it's on, what to say, and which submitted field holds the person's email address.

That third one is where these go wrong. Your form's email field might be email, or contact_email, or your-email, or reply_to. The autoresponder has to be told which, so it replies to the human rather than to nothing at all. Point it at a field name that doesn't exist and the email silently goes nowhere — no error, no bounce, just an autoresponder that appears not to work. It defaults to email, so if your field is called something else, that's the setting to check first.

What to Write

The temptation is marketing copy. Don't. This email has one job — confirm receipt and set expectations — and everything else dilutes it.

Subject: We got your message

Hi,

Thanks for getting in touch — your message has landed and a
real person will read it.

We usually reply within one business day. If it's urgent,
just reply to this email and it'll come straight to us.

— The team at Example

Four things make that work. It confirms specifically, because "your message has landed" is the actual question they have. It gives a timeframe, which is the difference between waiting patiently and resubmitting on Thursday. It invites a reply, which turns a dead-end notification into an open thread — and the useful context usually arrives in that reply. And it's short, because nobody reads a receipt twice.

Equally, some things to leave out. "Do not reply to this email" tells someone who wants to talk to you not to talk to you; if reply-to is set properly, replies reach you. A sales pitch reads as automated and cheapens an interaction where somebody just voluntarily contacted you. And don't promise a response time you can't hit — "we reply within an hour" on a form you check twice a day manufactures disappointment on a schedule.

Deliverability

This is transactional email in the purest sense: triggered by the recipient's own action, sent once, expected. That's the easiest category to get delivered, but a few things still matter.

Only send on real submissions. If spam-flagged submissions trigger a reply, bots figure out they can use your form to send mail to arbitrary addresses, and your sending reputation becomes their problem to exploit. This is a deliverability argument for keeping the spam ladder on, not just an inbox-tidiness one.

Keep the email plain. Text or light HTML delivers better than a heavy template and reads better on a phone. Send exactly one — an autoresponder that starts a drip sequence is unsolicited email, and it will get you marked as spam by people who were, moments ago, interested in your product.

The Other Half: What You Receive

The autoresponder emails the submitter. What lands in your inbox is a separate decision, and worth making deliberately.

Per-submission notifications are right for low-volume, high-value forms — sales enquiries, job applications, support requests — where you want to know now. On a newsletter signup, that same setting turns your inbox into a firehose and you start ignoring it, which defeats the point.

That's what the daily or weekly digest is for: one summary instead of one email per submission. Notifications, digests, and the autoresponder are independent, so a very common setup is an autoresponder to the submitter, a digest to you, and no per-submission noise at all. Instant form notifications covers the other side of that trade-off.

Two Common Questions

Will it reply to spam? Not when spam protection is on, and that's the point. A form that emails anyone whose address gets typed into it is an open relay with extra steps.

Should I personalize with their name? Usually not worth it. A generic greeting that always works beats a personalized one that renders "Hi ," whenever someone leaves the name field empty.

---

Confirm every submission automatically. Try Bluejay Forms free.