How to Set Up Form Auto-Reply Emails -- Google Forms, Apps Script, and FORMLOVA

Last updated: May 4, 2026

Setting up a form auto-reply sounds simple until you choose the method.

Sometimes a built-in response receipt is enough. Sometimes you need Apps Script. Sometimes you want the form service to handle the subject, body, reply-to address, preview, and test email without maintaining code.

This guide explains the practical differences between Google Forms response receipts, Google Apps Script, conventional form-service autoresponders, and FORMLOVA's chat-first setup.

If you already know the setup path and only need reusable copy, read the Form Auto-Reply Email Examples guide. This article focuses on setup decisions.

Quick Answer: Separate Response Receipts From Custom Auto-Replies

The first decision is whether you need a receipt or a custom confirmation email.

Method	Best for	Watch out for
Google Forms response receipt	Sending respondents a copy of their answers	Not ideal for custom confirmation copy, response timing, or conditional messaging
Google Apps Script	Keeping Google Forms while sending a custom email	Requires script, trigger, authorization, quota, and error maintenance
Form-service autoresponder	Setting subject, body, variables, and reply-to in a UI	Free and paid boundaries vary by service
FORMLOVA	Creating, adjusting, previewing, and testing the email through chat	Auto-reply customization is available on Standard or higher

These are not the same feature.

If respondents only need a copy of what they submitted, Google Forms may be enough. If you need a confirmation email that says "we received your request," gives a response timeline, includes a resource link, explains an event URL policy, or routes replies to a support address, treat it as a custom auto-reply.

Decide These Details Before Opening the Settings Screen

Before editing any tool settings, define the email.

Decision	Why it matters
Recipient email field	The system needs to know which submitted address receives the reply
Subject line	The respondent should recognize what was received
Body copy	The email should confirm receipt and explain the next step
Reply-to address	Replies should go to a monitored inbox
Submitted fields to include	Only necessary confirmation details should be repeated
Test email	The final email should be checked in a real inbox

Skipping this step creates technically working but operationally weak email.

For example, "Submission completed" is too vague as a subject line. "We will contact you if needed" does not tell the respondent when to expect a reply. A no-reply address conflicts with copy that says "reply to this email."

The job of an auto-reply is not polished language. It is reducing uncertainty after submission.

How Auto-Replies Work in Google Forms

Google Forms can send response receipts when you collect respondent email addresses. That is useful when the respondent needs a copy of their submitted answers.

It is less useful when the message needs to sound like a real operational confirmation:

Thanks for contacting us.
We received your inquiry and usually respond within two business days.
If this is urgent, contact support@example.com.

For that kind of custom email, many teams use Google Apps Script.

A typical Apps Script setup looks like this:

1. Collect respondent email addresses in the form.
2. Open Apps Script from the form or linked spreadsheet.
3. Write a function that runs on form submission.
4. Use MailApp or GmailApp to send the email.
5. Create an installable form-submit trigger.
6. Authorize the script and test a real submission.

This can be a good path for teams comfortable with Google Workspace automation. It keeps the workflow close to Google Forms and allows custom logic.

The tradeoff is maintenance:

Someone must own the script.
Trigger failures need to be monitored.
Authorization and sending quotas matter.
Copy changes may require code edits.

Google Forms is not the wrong choice. If response receipts are enough, it is simple. The question is whether your post-submit communication needs to evolve beyond a copy of the submitted answers.

Set Up an Auto-Reply in FORMLOVA

In FORMLOVA, auto-reply email creation and customization are available on Standard or higher.

The Free plan can still create forms, collect unlimited responses, view responses, search, update status, and export CSV / Excel files. Sending custom auto-reply emails after submission belongs to the paid operational layer.

Start with a plain instruction:

Set up an auto-reply email for this contact form.
Use the subject "We received your inquiry."
Say that we usually reply within two business days.
Add support@example.com for urgent questions.

FORMLOVA can draft a subject and body such as:

Subject: We received your inquiry

Hi {name},

Thanks for contacting us.
We received your inquiry and will review it shortly.

Our team usually replies within two business days.
If this is urgent, please contact support@example.com.

The important part is not that the first draft is final. The important part is that the form, email, preview, and test flow stay in one conversation.

FORMLOVA shows a preview before saving template changes. That confirmation step is intentional. Auto-reply copy is customer-facing, so the system should not silently change it without review.

Adjust the Copy Through Chat

Auto-reply copy usually needs one or two small revisions.

Use direct instructions:

Make it a little warmer.
Make it more formal for B2B inquiries.
Shorten it for mobile.
Move the response timeframe earlier.
Add the resource link near the top.
Do not include the webinar link; say it will be sent one day before the event.

Separate tone changes from operational changes.

"Make it better" is vague. "Shorten it," "make the first paragraph more formal," "move the reply timing above the submitted details," and "remove the join link" are easier to apply safely.

For reusable subjects and body structures by use case, use the Form Auto-Reply Email Examples guide. It covers contact forms, resource requests, webinar registration, job applications, and survey forms.

Send a Test Email Before Publishing

Always send a test email before publishing or before turning the auto-reply on for a live form.

Preview is not enough. You need to see the message in an actual inbox.

Check these items:

Check	Why
Subject	It should be recognizable and not too long
Sender name	The respondent should know who sent it
Reply-to	Replies should reach the right inbox
Body	Receipt and next step should be clear
Variables	Name, form title, and links should render correctly
URLs	Resource, map, event, and support links should open
Mobile view	Paragraphs and links should be easy to scan

FORMLOVA test emails are not sent to live respondents. They are for checking the template in your own email client. Test subjects are marked as tests, and test emails do not count toward the monthly email quota.

For the broader launch checklist, read Review a Form Before Publishing.

Email Limits and Plan Boundaries

Auto-replies consume email quota when they are sent to respondents.

Current FORMLOVA plan availability is:

Plan	Monthly price	Auto-reply emails	Monthly email limit
Free	0 JPY	Not sent	100 emails
Standard	480 JPY	Available	1,000 emails
Premium	980 JPY	Available	10,000 emails

The Free plan still has an email limit for the email features available on that plan, but custom auto-reply sending is not included. Standard is often enough for contact forms, resource requests, and moderate webinar registration. Premium is a better fit when several forms send auto-replies, reminders, bulk emails, or follow-up sequences.

Do not automate every message just because you can. High-value inquiries, sensitive support cases, hiring communication, and unusual requests should keep a human review step.

What Comes After the First Auto-Reply

Once the first confirmation email is reliable, the next question is timing and targeting.

Goal	Feature area
Send a reminder before a webinar	Reminder emails
Notify different owners by inquiry category	Conditional workflow
Follow up only with low-score survey respondents	Conditional email
Hand hot resource requests to sales	Response search, status, and notification

The broader operating model is covered in the FORMLOVA Form Automation Guide. For contact-form operations, read the Contact Form Operations Guide. For webinar registration email flow, read the Webinar Registration Form Guide.

FAQ

Can Google Forms send auto-reply emails?

Google Forms can send respondents a copy of their responses when respondent emails are collected. For custom confirmation copy, response timing, resource links, or conditional messages, you usually need Apps Script, an add-on, an external integration, or another form service.

Can I set up form auto-replies without Apps Script?

Yes. If a response receipt is enough, Google Forms can handle that without Apps Script. If you need a custom confirmation email without code, use a form service with autoresponder settings or FORMLOVA Standard or higher.

Does FORMLOVA Free include auto-reply emails?

No. FORMLOVA Free includes form creation, response collection, response viewing, search, status management, and CSV / Excel export. Auto-reply email creation and customization are available on Standard or higher.

Should auto-reply emails include all submitted fields?

Usually no. Include only the fields needed for confirmation. Repeating addresses, phone numbers, long free-text answers, and sensitive details increases forwarding and accidental disclosure risk.

Where can I find auto-reply email examples?

Use the Form Auto-Reply Email Examples guide for reusable copy patterns for contact forms, resource requests, webinar registration, job applications, and survey forms.

References

Disclosure and Verification

This guide was written after checking official information from each service as of May 4, 2026. The author builds FORMLOVA. Google Forms response receipts, Apps Script installable form-submit triggers, MailApp, and formrun auto-reply documentation were checked against official sources. Pricing, features, and email limits may change, so check each service's official pages before making a decision.