Last updated: October 15, 2026
When a Google Forms auto-reply is missing, first identify the sender: Google's built-in response receipt, or a custom Apps Script/add-on email. For receipts, inspect email collection and response-copy settings. For Apps Script, inspect the form-submit trigger, authorization, execution log, and recipient mapping. Once you know the sending process ran, check spam and organization quarantine folders.
Keep three checkpoints separate: the response was saved, an email send was attempted, and the intended mailbox received it. Record one test submission against those checkpoints before repeatedly resending. This guide follows that diagnostic order; the broader form auto-reply email setup guide covers initial setup and copy changes.
Quick Answer: "Enabled" Is Not the Same as Delivered
Check the delivery chain in this order.
| Step | Check | Common failure |
|---|---|---|
| 1 | Google Forms response receipt settings | A response copy is being confused with a custom auto-reply |
| 2 | Respondent email address | Email collection is off, or the recipient field is missing |
| 3 | Apps Script or add-on sending process | Trigger, authorization, recipient mapping, or execution log problem |
| 4 | Sending quota and sender identity | MailApp/GmailApp quota, sender, or domain issue |
| 5 | Recipient side | Spam folder, company filter, forwarding, typo |
| 6 | Workflow state | A test worked, but live submissions were never checked |
"Auto-reply is enabled" is not delivery evidence.
You need to know whether the system had a recipient, whether a sending process ran, whether the provider accepted the message, whether the inbox received it, and whether the message still matched the operational promise.
What Google Forms Response Receipts Can Actually Do
Start with the built-in Google Forms response receipt.
That feature is useful when respondents need a copy of the answers they submitted. It is not the same as a fully custom confirmation email.
Check three things.
| Check | Why it matters |
|---|---|
| Email collection is enabled | Google Forms needs a respondent email address |
| Response receipt setting is configured | The form must be set to send respondents a copy |
| The expected message fits the feature | A response copy is not a custom operational confirmation |
If this is enough, avoid adding Apps Script just to add complexity.
If you need a message like the one below, you are outside the basic response receipt use case.
Thanks for contacting us.
We received your inquiry and usually reply within two business days.
For urgent questions, contact support@example.com.
That is a custom auto-reply. Many Google Forms teams build it with Apps Script.
What to Check When Apps Script Does Not Send
Do not debug only the message body.
Apps Script delivery often fails outside the copy.
| Check | Failure example |
|---|---|
| Trigger | The function exists, but no installable form-submit trigger was created |
| Authorization | The script was never authorized after trigger setup |
| Event object | A Forms event and a linked-Sheets event are being mixed up |
| Recipient mapping | The question or column name changed, so the email address is empty |
| Execution logs | The trigger is failing, but nobody checks the log |
| Quota | MailApp or GmailApp has hit a daily sending limit |
The most confusing failures are those where a manual test worked.
Your own Gmail address received the test. A company address did not. Manual execution worked. Form-submit execution did not. One submission delivered. A busy event day only delivered some of them.
Those are not copywriting problems. They are trigger, authorization, sender, quota, or recipient-side problems.
If the same Google Forms stack also carries Sheets, Slack notifications, auto-replies, owner columns, and status fields, use Google Forms + Sheets + Apps Script Operations to decide where each responsibility should live before adding another script.
Separate Spam Filtering from Sender-Side Failure
If the sending process ran, check the recipient side.
Do not check only the inbox.
Spam folder
Promotions or automatic filtering tabs
Company mail gateway
Forwarded mailbox
Typos in the submitted email address
Company, school, government, and enterprise inboxes can block or quarantine messages that personal Gmail receives normally. If the same message reaches Gmail but not a corporate domain, the mailbox administrator may need to inspect filtering or sender rules.
Also check the address itself. If the respondent mistyped it, the form cannot magically recover.
Use an email field rather than plain text, and validate the address at the form level when possible. The broader field-design framework is covered in the Form Field Examples Guide.
Test response capture separately from email on your next inquiry form
Use the settings, execution logs, and inbox checks above to resolve the existing Google Form. Signing up for FORMLOVA does not recover an unsent Google email or its historical logs. If you also want to try creating and reviewing your next intake form through chat, build a separate test draft.
Start with the free form workflow. This prompt is a suggested input, not a report of a completed run:
Create an unpublished test inquiry form. Require name, reply email address, and inquiry details. Set the completion message to “We received your inquiry. Our team usually responds within two business days.” Do not configure an auto-reply email. Show the form and completion-page previews.
Check that the email field uses email formatting, that the response promise matches your team's actual process, and that both mobile and desktop users can read the completion message. Preview submissions are not saved, so plan live response-storage and email tests separately from this screen review.
| Stage | What to verify | Free-plan boundary |
|---|---|---|
| Draft | Fields, required settings, and completion page | Create and preview |
| Published intake | A test response exists in the response list | Collect, search, and manage response status |
| Custom confirmation email | Subject, content, Reply-To, recipient, and sending result | Custom auto-replies require Standard or higher |
The free plan's 100-email monthly allowance does not make custom auto-reply copy a free feature. Your AI client's access conditions and fees also apply.
Check an inquiry form before adding its confirmation email
Draft the name, reply-email, inquiry fields, and completion message on the free plan. Decide separately whether Standard-or-higher custom auto-reply operation is needed.
Sign up free to draft an inquiry form
Register, verify your email, and connect FORMLOVA to a supported AI chat. Use the prompt above and review the form and completion page before publication.
For custom mail on Standard or higher, review the form's current template and recipient configuration, preview the copy, and request a test to your own mailbox. Then check the separate send record for an actual form response. A sent status does not prove the respondent read the message in an inbox or that the team completed the promised follow-up.
| State | What to inspect |
|---|---|
| Setup | Enabled state and saved template |
| Review | Rendered copy, Reply-To, and response promise |
| Recipient | Mapping to the respondent's email field |
| Sending result | Send attempt after a response, including failures or suppression |
| Inbox check | The test message and recipient-side filters |
For a broader use case, see Inquiry Auto-Reply by Category, Gmail Reservation Confirmation, or Event Reminder + Follow-up. Check each workflow's paid features and connected-service requirements, then review recipients and content before sending.
Checklist to Prevent the Same Failure
Once the message arrives once, do not stop there.
Forms change after launch. Copy changes. Response times change. Resource URLs change. Event links change. Owners change. Notification rules change. Email limits matter.
If the team also needs a visible alert when a response arrives, separate the respondent email from the team workflow and use the Google Forms to Slack notification guide for that route.
Before launch and after copy changes, check:
The form collects the respondent email address.
You are not confusing response receipts with custom auto-replies.
Apps Script triggers, authorization, logs, and quotas are checked when script is involved.
Testing uses conditions close to live submissions.
Spam folders and company filters are checked.
Reply-to points to an inbox someone watches.
Respondent auto-reply and team notification are designed separately.
If the issue is not only the email but the whole follow-up process, read response status management and post-submit workflow design. They keep the team from making email carry every operational responsibility.
FAQ
Can Google Forms send an auto-reply email by itself?
Google Forms can send respondents a copy of their responses when the relevant email settings are used. For a custom confirmation email with your own subject, body, response timing, resource links, or conditional copy, you usually need Apps Script, an add-on, another form service, or FORMLOVA.
What should I check first when an Apps Script auto-reply is not sent?
Check the installable form-submit trigger, authorization, execution logs, recipient mapping, and sending quota. Manual execution success does not prove that the form-submit trigger is working.
Why do I receive the test email, but respondents do not?
The test condition may not match production. The recipient may be hardcoded, the respondent email may not be collected, the company mailbox may block it, or the submitted address may contain a typo.
Can I use custom auto-replies on FORMLOVA Free?
Custom auto-reply email is available on Standard or higher. The Free plan can still create forms, collect responses, search responses, manage response status, and export CSV / Excel files.
Official Sources Checked
- Google Docs Editors Help: View and manage form responses
- Google Apps Script: Installable triggers
- Google Apps Script: MailApp
- Google Apps Script: Quotas for Google Services
Read Next
- How to Set Up Form Auto-Reply Emails
- FORMLOVA Form Automation Guide
- Google Forms + Sheets + Apps Script Operations
- Response Status Management
- Post-Submit Workflow Design
For the missing message, record whether response capture, the send attempt, and inbox delivery were each verified, then fix the first unresolved stage. To compare a new intake workflow, follow the FORMLOVA setup guide and start with the draft above.
Disclosure and Verification
This guide is for teams troubleshooting Google Forms response receipts, Apps Script auto-replies, and missing confirmation emails. I work on FORMLOVA, so the workflow examples use FORMLOVA directly. I checked Google Forms response management, Apps Script triggers, MailApp, quota documentation, and FORMLOVA auto-reply operation notes on June 17, 2026. On October 15, 2026, I rechecked Google's response-receipt conditions and installable triggers, plus FORMLOVA's template, preview, and plan definitions for this revision. Google UI, delivery behavior, pricing, and limits can change, so confirm current official documentation before implementing production workflows.
