Typeform & Tally response emails: stop losing submissions to spam

Typeform and Tally are two of the most loved form tools on the market — Typeform for polished experience and brand feel, Tally for simplicity and pricing. They both share the same quiet deliverability problem. When someone completes a form, the platform emails you a notification from a sender you don't control, on a domain you don't own. Modern spam filters increasingly treat those emails like automated marketing. Notifications drift to Promotions first, then to Spam, then to Not Delivered. And you only find out weeks later from a lead asking why no one got back to them.

What the default notification path looks like

Both tools have a "email me on each response" option. Under the hood:

• Typeform — emails are sent from no-reply@typeform.com or a similar shared domain. Reply-to can be set to the respondent's email if you've mapped that field.
• Tally — notifications come from notifications@tally.so. Tally authenticates its own domain but you inherit its shared reputation.

For low-traffic sites, this is fine. The trouble starts at scale. As more scammy senders appear on the same infrastructure (or as Gmail tightens its heuristics), you can watch your own placement slide from Primary to Promotions over a couple of weeks without changing a thing.

Testing your Typeform / Tally notifications

Don't trust the platform's preview button. Previews are synthesized and don't travel through the real sending pipeline. The only reliable test is submitting the actual form and watching where the notification lands.

1. Grab a set of seed addresses from Inbox Check covering Gmail, Outlook.com, Workspace, M365, Yahoo, Mail.ru, Yandex, ProtonMail.
2. For each seed address, submit the form with that email in the respondent email field (or configure the form's notification to go to that seed).
3. Within 30 seconds you'll see Inbox / Promotions / Spam / Not Delivered for every provider, plus SPF / DKIM / DMARC verdicts on the message.
4. Flag any Promotions or Spam result. That's where a respondent at that provider would hit the same miss.

Route notifications through your own SMTP

The durable solution is to stop relying on the platform sender and route the submission to a mail path you control. Both Typeform and Tally fire webhooks on every response, which makes this easy.

Typeform + Zapier

1. Create a new Zap. Trigger: Typeform → New Entry. Pick your form.
2. Action: Email by Zapier or your own Gmail / custom SMTP. Send from an address on your domain.
3. Body: include all fields. Subject: "New Typeform response — {{name}}". Reply-To: respondent's email.
4. Disable the Typeform built-in email notification so you don't get duplicates.
5. Submit a real response and seed-test the new path.

Tally + Make (or n8n)

1. In Tally, go to Integrations → Webhook and paste a Make webhook URL.
2. In Make, parse the JSON, then use Email / SMTP to send from your domain.
3. Turn off Tally's built-in email notification.
4. Submit a real response; seed-test.

Subject line and body still matter

Even over your own domain, a noisy HTML template reads like marketing. Form notifications should feel like transactional internal email:

• Subject: "New response — [form name] — [respondent name]". Clear, boring, useful at a glance.
• Body: plain text or very minimal HTML. Fields in a simple list. No logo, no banner, no tracking pixel.
• One clean link back to the response in Typeform / Tally. Resist the temptation to add marketing content.
• Reply-To: the respondent. Hitting reply from the team inbox should go straight to them.

Troubleshooting common failures

Notifications going to Promotions

Usually content-driven. Strip the template. Drag one message from Promotions to Primary; Gmail adapts within a day or two for that sender.

Outlook flagging as junk

Check SPF / DKIM alignment on your own sending domain. A missing DKIM selector or an SPF record with 11+ lookups will quietly land you in junk.

Sporadic delivery delays

Zapier free tier polls every 15 minutes; Make runs closer to real time. If timing matters (bookings, auto-routing), use Make, n8n, or a direct webhook into your own server.

FAQ