Website builders7 min read

Google Forms notifications: do respondents see your follow-up?

Google Forms confirmations come from forms-receipts-noreply@google.com. Your follow-up from you@yourdomain.com is a completely different delivery story.

Google Forms is the most-used form builder in the world by a large margin, because it is free and comes bundled with Workspace. It also has the most misunderstood deliverability profile. There are two very different mail streams attached to any Google Form, and whether they land in Inbox depends on totally different factors.

Two streams, two outcomes

Stream 1: Google Forms sends confirmation email — from a Google-owned noreply address. Nearly always Inbox; you have zero control. Stream 2: you follow up manually from your own Gmail or Workspace — placement is now about your domain reputation. Most deliverability failures happen in Stream 2.

Stream 1: the auto-confirmation

If you enable "Collect email addresses" and "Send respondents a copy of their response", Google Forms sends a confirmation from forms-receipts-noreply@google.com:

  • Sent from Google's internal infrastructure.
  • Authenticated by Google; universally accepted at Inbox.
  • From header identifies you, but envelope is Google.
  • Not editable — content and styling are fixed.

This stream almost never fails placement. If a respondent says they didn't receive the confirmation, the most likely cause is they typed their email wrong, or they're on an exotic mail provider with aggressive filtering.

Stream 2: your own follow-up

The actual business value usually comes from the follow-up: "Thanks for signing up, here's the next step." That email does not come from Google Forms. It comes from you — sent manually from Gmail, or via a Mail Merge add-on, Google Apps Script, Make/Zapier, or an ESP.

  • Now you're the sender. Your SPF, DKIM, DMARC, reputation.
  • If you're on a fresh domain, you may land in Spam on Outlook and Yahoo.
  • If you're on Workspace, Gmail-to-Gmail is basically always Inbox.
  • If you're sending a templated mass follow-up via Mail Merge, you're now doing bulk mail and need warmup.

Apps Script auto-responder pattern

The classic "send a custom follow-up when a Google Form is submitted" uses Apps Script:

function onFormSubmit(e) {
  const email = e.namedValues['Email'][0];
  const name = e.namedValues['Name'][0];
  GmailApp.sendEmail(email,
    'Thanks for signing up, ' + name,
    'Hi ' + name + ',\n\nYour next step: ' +
    'https://example.com/next\n\nBest, the team',
    { name: 'Acme Team', replyTo: 'support@acme.com' }
  );
}

This sends from your Workspace user's Gmail. Placement is usually excellent because Gmail-to-Gmail is authenticated both ways. The catch: Gmail's daily send limit is low (500 or 2000 depending on your plan), and Apps Script hits rate limits on larger forms.

Do not Apps Script-send to large audiences

Apps Script from Gmail works fine for under 500 responses per day. For a high-volume public form (newsletter signup, course enrolment) route the follow-up through an ESP instead. Gmail will start rate-limiting, and beyond that, suspending your Workspace user.

Seed test your follow-up stream

The test you actually need is on Stream 2, not Stream 1:

  1. Submit the form with seed addresses as the respondent (Gmail, Outlook, Yahoo, Mail.ru, Yandex, Proton, GMX, Fastmail).
  2. Let the Apps Script / ESP / Mail Merge fire.
  3. Record where your follow-up lands, per provider.
  4. Adjust: fix domain authentication, switch to an ESP, or warm up the sender.

Migrate for scale: ESP-driven follow-up

When form volume crosses ~100 submissions/day, move the follow-up to a proper ESP:

Google Forms Submission
  --> Google Apps Script trigger (or Zapier)
  --> POST to ESP API (Resend / Postmark / SendGrid)
        from:     hello@yourdomain.com  (DKIM-signed)
        to:       {{ respondent_email }}
        reply-to: support@yourdomain.com
        subject:  Your next step
  --> Consistent placement at scale

Your Workspace user is no longer the bottleneck, placement is stable per-provider, and you get logs, bounces, and opens.

FAQ

Does Google Forms' auto-confirmation count against my Gmail send limits?

No. Stream 1 (forms-receipts-noreply@google.com) is Google's system mail, not yours. It doesn't touch your Workspace send quota.

Why does my Apps Script follow-up land in Promotions sometimes?

Gmail's Promotions classifier is triggered by content patterns: images, links, unsubscribe footer, marketing phrasing. Plain-text follow-ups tend to hit Primary more reliably than HTML.

Can I set a custom From address on my Apps Script follow-up?

Only within Workspace — you can alias to another user on the same domain if you set up Send As with permissions. You cannot send as a domain Google doesn't authenticate you for.

Is Mail Merge by Quicklution / Yet Another Mail Merge any better?

Both use Gmail under the hood, so placement is similar to direct Apps Script. The value is templating and scheduling. For genuine scale, move to an ESP instead.
Related reading

Check your deliverability across 20+ providers

Gmail, Outlook, Yahoo, Mail.ru, Yandex, GMX, ProtonMail and more. Real inbox screenshots, SPF/DKIM/DMARC, spam engine verdicts. Free, no signup.

Run Free Test →

Unlimited tests · 20+ seed mailboxes · Live results · No account required