Send a Form to a Different Email Based on the Answer

You have one contact form and three inboxes. Sales questions should go to sales, support questions to support, invoices to whoever handles billing. Or it’s by branch. Right now everything lands in one inbox and somebody forwards it by hand, or forgets to.

This is one of the oldest questions on the Contact Form 7 support forum, and it keeps coming back. In February 2025 someone helping a friend with their site put it like this:
I’m trying to create a form where the user selects an option on a drop-down (events, contact) and that the form is then sent to a different email ([email protected], [email protected]) depending on that selection.
They’d already tried a conditional fields plugin and got nowhere. The answer turned out to be simpler than they expected. So here are the three common ways to do it, what goes wrong with each, and a short note on doing the same thing for thank-you pages.
Three ways to route a form by answer
1. Contact Form 7: pipes in a select field
Contact Form 7 has a built-in feature for exactly this, which its docs call “selectable recipient with pipes”. In a select (dropdown) field, each option can have two parts separated by a pipe character: the label the visitor sees, and the value CF7 uses behind the scenes.
[select your-dept "Sales|[email protected]" "Support|[email protected]" "Billing|[email protected]"]
Then on the Mail tab, put the field’s tag in the To field:
To: [your-dept]
When someone picks “Support”, CF7 swaps in the part after the pipe and sends the email to [email protected]. We checked this in the CF7 source: the form only ever renders the part before the pipe, so the visitor’s browser sees “Sales”, “Support” and “Billing” and nothing else. The address lookup happens on the server after the form is submitted.
A couple of things trip people up:
- In the email body,
[your-dept]now prints the address, not the department name. If you want the label your team recognises, use[_raw_your-dept]instead. - Every part after a pipe has to be a valid address. People keep reporting an “Invalid mailbox syntax is used” warning on the To field, including in that same 2025 thread. When you see it, go through each option and look for a stray space, a missing
@or a typo in the domain. - It works on select, radio and checkbox fields. It doesn’t help when routing depends on two answers together (say, department and country). For that you’re into add-ons or a few lines of PHP on a CF7 hook.
There are add-ons built for this too, such as “Conditional Email Routing for Contact Form 7”, if you’d rather set rules in a screen than in the field syntax.
2. One notification per department, each with a condition
This is how most of the bigger form builders do it. You don’t make one email with a variable recipient. You make several emails, one per department, and each has a rule like “send this only when Department is Sales”.
In WPForms that’s the “Enable Conditional Logic” switch at the bottom of a notification, which then reads “Send this notification if…”. WPForms lists conditional notifications as a paid-plan feature on its own Lite vs Pro page, so it isn’t in the free WPForms Lite.
The upside is that each email can be different (subject line, CC, which fields it includes). The downside is that you now have three or more notifications to keep in sync. Add a field to the form and you may need to add it to every email.
3. Route to an address picked from the answer
The third way is a single notification whose “send to” address comes from the form itself. Gravity Forms (a paid plugin) calls this “Configure Routing”: you write rules like “send to [email protected] if Department is Sales”, all inside one notification. Gravity Forms’ own docs point out that routing only fills in the recipient. If none of your rules match, the notification goes out with an empty Send To and nobody gets it.
The simplest version of this pattern is also the riskiest: a plain dropdown where the option values are the email addresses. It works, but those addresses now sit in your page’s HTML for every scraper to collect, and depending on how the plugin checks the submitted value, someone could post a different address than the ones you offered. If your plugin can’t hide the address the way CF7 pipes do, use conditions instead.
The pitfalls, whichever way you pick
Exposed addresses
Open your form page, right-click, View Source, and search for @. If your department inboxes show up there, they’ll show up in spam lists too. CF7 pipes and condition-based notifications keep them on the server. A raw email in an option value does not.
Typos you won’t notice
A typo in one department’s address doesn’t throw an error on the front end. The visitor sees “Thanks, we got your message” and the email goes nowhere.
No catch-all
Have a fallback. Every routing setup should either have a default recipient or a notification that always goes to one general inbox, even if it’s only a BCC. Departments get renamed, someone adds an “Other” option and forgets to route it, and those enquiries just disappear.
Not testing every option
Test each choice, not just the first one. Submit the form once per department and confirm each email arrives in the right inbox (and not in spam). It takes five minutes. Do it again whenever you rename or add an option, because the routing usually matches the exact option text, and “Sales” and “Sales team” are not the same.
Same idea, different thank-you page
The same trick works for what the visitor sees after submitting. A big-budget enquiry can land on a “book a call” page while everyone else gets a plain thank-you message. In Contact Form 7 this is usually a few lines of JavaScript listening for the wpcf7mailsent event and checking the field value, or a redirection add-on. Other builders call it conditional confirmations. If you only need one fixed page for everyone, a normal redirect after submission is enough.
Doing it in Trinity Forms
Full disclosure: Trinity Forms is ours.
In the free core, every email notification has a sending rule: “Always send”, “Send only when” or “Don’t send when”, built from conditions on the form’s answers. For department routing you make one notification per department, set each to “Send only when Department is Sales” (Support, Billing and so on), and add one more set to “Always send” to your general inbox, so every message also lands somewhere you check daily. The addresses stay in the notification settings, not in the page.
A notification can also be sent to an address the visitor typed into a field you choose (“Route to a field”). That’s the autoresponder case: a copy goes to the person who filled in the form. It only sends if the value is a valid email address, so a typo in that field means no copy, not an error.
Thank-you pages work the same way. The free core supports several confirmations per form, each with its own condition, and a confirmation can show a message, open a page on your site, or redirect anywhere. So a big-budget enquiry can go to a different page while everyone else gets a thank-you message.
It’s a free download from our site. If you’re already happy on Contact Form 7, pipes will do the simple version of this well. If you’re weighing a switch, our Contact Form 7 alternatives roundup and the WPForms vs Contact Form 7 comparison go through the options.
Frequently asked questions
How do I send a Contact Form 7 form to different emails?
Use pipes in a select field, like [select your-dept “Sales|[email protected]” “Support|[email protected]”], then put [your-dept] in the To field on the Mail tab. Contact Form 7 shows only the part before the pipe on the page and sends to the address after it. Use [_raw_your-dept] in the message body if you want the department name rather than the address.
Can I send a form to different people without showing their email addresses?
Yes. Contact Form 7 pipes keep the address on the server, and conditional notifications (one email per department with a “send only when” rule) keep the addresses in the plugin settings. Avoid a dropdown whose option values are the email addresses themselves, because anyone can read those in the page source.
Can I redirect to a different page based on a form answer?
Yes. In Contact Form 7 you can listen for the wpcf7mailsent event in JavaScript and redirect based on the field value, or use a redirection add-on. Form builders with conditional confirmations let you set a rule per confirmation, so one answer opens a booking page and the rest see a thank-you message.