Template examples

Google Forms confirmation email template examples

When someone submits a Google Form, the best confirmation email is usually short, specific, and calm. You want the respondent to know the submission was received, what happens next, and whether they need to do anything else. FormNotifier helps you send those messages directly from the Google Forms editor.

What a good confirmation email should do

A strong respondent message does not need to be long. It needs to remove uncertainty fast.

Confirm receipt

Tell the submitter the form response was received successfully.

Echo only useful context

Include the event name, request type, or date if that helps the respondent trust the message.

Set next-step expectations

Explain whether a human follow-up is coming and how long it may take.

Keep it readable

A short, plain-language email performs better than a dump of every answer.

Template example: registration confirmation

Use this when the form is collecting signups for a workshop, event, or session.

Subject: We received your registration for {{Event Name}} Hi {{Name}}, Thanks for registering for {{Event Name}}. We received your submission successfully. Event date: {{Event Date}} Location: {{Location}} If we need anything else, we will contact you at this email address. Otherwise, you are all set for now. Best, {{Team Name}}

Template example: request or intake form

Use this when the form starts a support, service, or internal request workflow.

Subject: Your request has been received Hi {{Name}}, This is a confirmation that we received your request: {{Request Type}}. Reference detail: {{Reference Field}} Our team will review it and follow up within {{Response Window}}. Thank you, {{Team Name}}

Template example: application submission

Use this when the submitter is applying for a program, role, or opportunity and needs reassurance without a promise of acceptance.

Subject: We received your application Hi {{Name}}, Thank you for submitting your application for {{Program Name}}. We received your materials and will review them during the current review cycle. If your application moves forward, we will contact you with the next step. Best regards, {{Team Name}}

Before you use a template in production

  1. Make sure the form collects email or includes a reliable Email question.
  2. Replace placeholders with the actual merge fields available in your form.
  3. Send a test email to yourself so you can inspect formatting and wording.
  4. Review the latest report after testing so you know what a healthy send looks like.
If your message depends on merge values, test with realistic responses. The safest template is the one you have already seen land in a real inbox before launch.

Related FormNotifier guides