"Can I send an auto-reply email from Google Forms?" — extremely common question. And the honest answer is: Google Forms doesn't ship with a real auto-reply feature.
What it does ship with is "the respondent can optionally email a copy to themselves." This guide compares three real implementation patterns and lays out how to design the compromise, because "free and perfect" isn't on the menu.
First, kill the misunderstanding — "Send respondents a copy" is not auto-reply
Google Forms has a setting: Settings → Responses → "Collect email addresses" → "Send respondents a copy." A lot of people mistake this for auto-reply. It isn't:
- It only sends if the respondent manually checks the box themselves
- The email content is a mechanical copy of their answers
- You can't customize the wording
- No attachments, no custom message
So it's completely useless for "Thanks for signing up — we'll get back to you within three business days" branded confirmations.
If you want to reliably send thank-you, confirmation, perk, or follow-up emails from your side, you need a different approach.
The three implementation patterns
Pattern A: Use an add-on
Easiest. From Google Workspace Marketplace, install one of:
- Email Notifications for Google Forms
- Form Notifications
- Form Approvals
Pros
- No-code setup
- Custom message body and sender
- Conditional sending (only when certain answers are given)
Cons
- Free tiers cap monthly sends hard (often 20–50 per month)
- Paid plans run a few dollars to tens of dollars per month
- Sends route through the add-on vendor's servers — long-term continuity risk
- Personal data flows to the add-on vendor
Good for
Surveys with tens of responses per month when you don't have engineering capacity.
Pattern B: Roll your own with Google Apps Script
Free and flexible. Bind a script to the form:
function onFormSubmit(e) {
const responses = e.response.getItemResponses();
let email = '';
let name = '';
responses.forEach(r => {
const title = r.getItem().getTitle();
if (title === 'Email address') email = r.getResponse();
if (title === 'Name') name = r.getResponse();
});
if (!email) return;
const subject = '[Acme Inc.] Your submission';
const body = `Hi ${name},
Thanks for getting in touch. We've received your submission and will follow up within three business days.
Acme Inc.`;
GmailApp.sendEmail(email, subject, body);
}
Open "Extensions" → "Apps Script," paste the code, and configure a trigger on "On form submit."
Pros
- Free, within send limits
- Body, conditions, attachments — all under your control
- No external dependency
Cons
- Gmail send limits: free Google accounts 100/day, Workspace 1,500/day
- Scripts need maintenance — Google API changes can break them
- You design the error notification flow yourself
- Complex conditional logic gets hairy fast
Good for
Internal engineering capacity, hundreds to low thousands per month, and a strict cost ceiling.
Pattern C: Move to a dedicated tool
Dedicated survey / form platforms treat auto-reply email as a core feature:
- Confirmation email to respondents
- Notification email to admins
- Conditional send rules
- Attachments and template variables
Pros
- No-code, immediate
- High send ceilings (tens of thousands per month)
- Full control of copy and design
- No maintenance burden
Cons
- Monthly subscription (typically $10–$100/month)
- Switching cost up front
Good for
100+ responses per month, multiple forms, or when brand experience matters.
Comparison table
| Pattern | Monthly cost | Send limit | Body flexibility | Maintenance |
|---|---|---|---|---|
| Send-copy only | Free | None | None | None |
| Add-on (free) | Free | 20–50/mo | Low | None |
| Add-on (paid) | $5–30 | Thousands | Good | None |
| Apps Script | Free | 100–1,500/day | Full | Required |
| Dedicated tool | $10–100 | 10k+/mo | Full | None |
The deeper view — three things people miss about auto-reply
Point 1: Sender address is part of brand experience
Apps Script and add-ons typically send from the Google account you configured. When a company auto-reply comes from yourname@gmail.com, recipients read it as a personal email, not a business email — and trust drops accordingly.
Mitigations:
- Use a Workspace account on your custom domain
- Dedicated tools let you set a sender like
noreply@your-company.com - DMARC / SPF / DKIM to defend against spoofing
Point 2: Spam filter warfare
Sending in volume from Apps Script means sending from Gmail, which increases the odds of being flagged as spam on the receiving end. Common triggers:
- Subject lines stuffed with "free," "confirmation," "limited offer"
- The same body sent at scale
- Heavily linked HTML email
Dedicated tools maintain proper sender-domain authentication (DMARC/SPF/DKIM), and deliverability rates differ materially.
Point 3: Send logs, retries, and error handling
If a respondent enters a typo'd email, Apps Script can silently fail with no notification.
A dedicated tool offers:
- Send logs viewable in the admin UI
- Automatic bounce detection
- Resend capability
- Alerts on delivery failure
These become critically important the day you get the complaint "the auto-reply was supposed to fire but I never got anything."
A decision flow
Q1: How many responses per month?
- <20 → free add-on or compromise on "send copy"
- 20–100 → paid add-on or Apps Script
- 100+ → evaluate a dedicated tool
Q2: Do you need custom email copy?
- No → "send copy" is fine
- Yes → add-on / Apps Script / dedicated tool
Q3: Do you need to send from your own domain?
- Yes → Workspace + Apps Script, or a dedicated tool
- No → add-on is sufficient
Q4: Do you need to track delivery errors?
- Yes → dedicated tool is the only real answer
- No → Apps Script works
How Repoan handles auto-reply
Repoan treats auto-reply email as a first-class feature.
- Respondent auto-reply — body, subject, sender all customizable
- Admin notification email — response summary plus direct link to the admin dashboard
- Conditional send rules — e.g., send a follow-up only to CSAT ≤ 4 responses
- Send logs — full history and error logs in the admin UI
- Custom domain sending — emails go out from your own domain
- Template variables — dynamic substitution like
{{name}},{{answer_1}}
Wrap-up
For Google Forms auto-reply:
- The built-in "send copy" feature is not auto-reply in any meaningful sense
- Add-ons are convenient but free tiers throttle hard
- Apps Script is powerful but has real ops cost and risk
- Past a certain scale, a dedicated tool is dramatically easier
The moment you search "how do I auto-reply" is the moment your form starts becoming part of a real business process. Once you've crossed that line, Google Forms' scope often stops matching what you need.
Related reading: