This is the form your visitors will see
Clean, fast, no CAPTCHA. Try it — this is a real working demo.
What happens next ⚡
- 📥Submission received — stored in your searchable dashboard
- 📧Email notification — delivered to your inbox instantly
- 🛡️Spam filtered — AI classifier + honeypot, no CAPTCHA
- 🔗Webhook fired — optional: forward to Slack, Discord, Sheets
- ↩️User redirected — to your thank-you page
500 submissions/month free · No credit card
Why you need multiple recipients
A contact form submission isn't always for one person. The sales team needs to see inquiries. The support lead needs to see bug reports. The agency founder needs to see new project requests. And the account manager needs to see anything from their clients.
The default for most form backends — including splitforms Free — is a single notification email. That works for solo sites. But the moment you have a team, you need submissions routed to multiple people. Here are the three ways to do it, from simplest to most flexible.
Method 1: Distribution list (simplest, free)
Create an email alias on your domain provider or Google Workspace that forwards to multiple inboxes. Common patterns:
team@yourdomain.com→ forwards to alice@, bob@, charlie@leads@yourdomain.com→ forwards to sales@, founder@, marketing@inbound@yourdomain.com→ forwards to the whole team
Then set your form backend's notification email to team@yourdomain.com. Every submission gets delivered to every member of the distribution list automatically. This works with any form backend, including the free tier of splitforms, because the backend only sees one recipient.
Google Workspace setup: Admin → Directory → Groups → Create group. Add members. Set the group email as your notification recipient. Done.
Cloudflare Email Routing (free): Cloudflare's email routing supports up to 200 destination addresses per alias. Set up team@yourdomain.com as a catch-all that forwards to your whole team. No Google Workspace required.
Method 2: CC and BCC via your form backend
If your form backend supports CC/BCC recipients (splitforms Pro does), you can add multiple email addresses directly in the dashboard — no distribution list needed. The advantage is you can manage recipients per-form without touching DNS or email provider settings.
<!-- Form configuration on splitforms dashboard -->
Primary email: you@yourdomain.com
CC: sales@yourdomain.com
BCC: founder@yourdomain.com, archive@yourdomain.comEach submission triggers one email sent to all three recipients. The To field shows you@yourdomain.com, CC shows sales@, and BCC addresses are hidden from all recipients.
When to use CC vs BCC
- CC — when recipients should see each other (e.g. a sales team where everyone should know who else got the lead). Recipients are visible in the email headers.
- BCC — when recipients should NOT see each other (e.g. when CC-ing an external partner or archiving to a backup address). BCC addresses are stripped from the email before delivery.
- BCC for deliverability — Gmail and Outlook penalize emails with many To/CC recipients. BCC is safer for lists of 3+ additional recipients.
For more on avoiding spam filters, see why contact form emails go to spam.
Method 3: Conditional routing with webhooks
For sophisticated routing — "sales inquiries go to sales@, support tickets to support@, everything else to hello@" — use webhooks. The form backend sends the submission data to your webhook URL as JSON, and your code (or an automation tool) decides who to notify:
// Webhook handler (Node.js / Express)
app.post('/webhook/splitforms', async (req, res) => {
const { name, email, message, subject } = req.body.data;
// Route based on a "department" field in the form
if (subject === 'sales') {
await sendEmail('sales@yourdomain.com', name, email, message);
} else if (subject === 'support') {
await sendEmail('support@yourdomain.com', name, email, message);
} else {
await sendEmail('hello@yourdomain.com', name, email, message);
}
// Always archive
await sendEmail('archive@yourdomain.com', name, email, message);
res.json({ success: true });
});No-code alternatives:
- Zapier — splitforms webhook → "Path" (if/then) → "Send Email" action. Route to different people based on form field values.
- n8n — self-hosted, free for unlimited workflows. Splitforms webhook → Switch node → Email node.
- Make.com — visual workflow builder with conditional routing.
Splitforms webhooks are available on the Starter plan ($1/month). See how to send form data to a webhook for setup details.
Bonus: Route to Slack and Discord instead of email
For teams that live in Slack or Discord, skip email entirely. Splitforms can post every submission to a Slack channel or Discord channel via webhook — no email required, and the whole team sees submissions in real time:
<!-- In your splitforms dashboard, add a webhook URL -->
Slack incoming webhook:
https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXX
Discord webhook:
https://discord.com/api/webhooks/000000000000/XXXXXXXXSee send form submissions to Slack and send to Discord for full setup guides.
Pricing and plans
Splitforms makes multi-recipient notifications affordable:
- Free — 500 submissions/month, one primary email, webhooks to Slack/Discord included.
- Starter ($1/mo) — 1,000 submissions/month, unlimited forms, webhooks for conditional routing.
- Pro ($5/mo) — 5,000 submissions/month, CC/BCC recipients, custom SMTP, priority support.
For most teams, the distribution list approach on the Free plan covers it. Upgrade to Pro when you need per-form CC/BCC without managing aliases.
Ready to get started? Get your free access key. Questions? Email hello@splitforms.com.
FAQ
How do I send a contact form to multiple email addresses?
Three approaches: 1) Use a hosted form backend that supports CC/BCC fields (like splitforms Pro), 2) Set up a distribution list or group alias (e.g. team@yourdomain.com) on your email provider and send form notifications there, 3) Use webhooks to forward submissions to multiple recipients via an automation tool like Zapier or n8n. The distribution list approach is free and works with any form backend.
Should I use CC or BCC for form notifications?
Use BCC when sending the same notification to multiple people. BCC keeps recipient addresses private — each recipient only sees their own address in the To field. CC exposes all recipient addresses to everyone, which is a privacy concern and can trigger spam filters (Gmail penalizes emails with many CC recipients). For team notifications, put the primary recipient in To and additional team members in BCC.
Why are my form emails with multiple recipients going to spam?
Email providers treat messages with many recipients (5+ in To/CC) as more likely to be spam. The fix: send individual emails to each recipient instead of one email to many, or use a distribution list address so there's only one visible recipient. Also ensure SPF, DKIM, and DMARC are properly configured on your sending domain — see our contact form spam guide for the full DNS setup.
Can I send form submissions to different people based on the form content?
Yes. This is called conditional routing. With splitforms webhooks (Starter plan at $1/mo), you can inspect the submission data and route it: sales inquiries go to sales@, support tickets to support@, partnership requests to partners@. Set up a webhook to your own server, a Zapier Zap, or an n8n workflow that reads the submission type field and forwards accordingly.
Does splitforms support CC and BCC recipients?
Yes. On the Pro plan ($5/month), you can configure CC and BCC email addresses in your form settings. Each submission is sent to your primary email, plus any CC and BCC addresses you've added. The Free plan (500 submissions/month) sends to one primary email address. For team-wide notifications, you can also set up a webhook to Slack or Discord on any plan.
More reads: why form emails go to spam, form to webhook guide, all posts.