Get the next one in your inbox.
One email when we publish something worth reading. No spam — appropriately enough, we'd know.
How to run one contact form with a topic dropdown that routes sales inquiries, support requests, and job applications to three different inboxes.
Get an instant summary, key takeaways, action items, and answers to your questions about this article.
Conditional routing lets a single form send its notification email to different recipients depending on the value of a submitted field — for example, a "topic" dropdown that sends sales inquiries to sales@, support requests to support@, and applications to jobs@, all from one form and one endpoint.
Most sites need at least three inboxes fed by contact forms: sales wants to know about deals, support wants to know about problems, and HR wants to know about applicants. The lazy answer is three separate forms. The better answer is one form with a topic field and routing rules doing the sorting.
Build a single form with a dropdown asking what the visitor needs:
<form action="https://app.formbridge.ai/api/forms/fb_8h2k9p" method="POST">
<select name="topic">
<option value="Sales">Sales inquiry</option>
<option value="Support">Support request</option>
<option value="Careers">Job application</option>
</select>
<input name="full-name" placeholder="Full name" />
<input name="email" type="email" />
<textarea name="message"></textarea>
</form>
That's the entire frontend. One endpoint, one form, one place for your spam protection and inbox to live.
Conditional routing is the piece that takes over from there: instead of a single fixed recipient list, a rule says a submission where topic = Sales gets emailed to sales@yourcompany.com, one where topic = Support goes to support@yourcompany.com, and topic = Careers goes to jobs@yourcompany.com. It's a real, supported feature on FormBridge — the exact screen for building that rule lives in your form's own settings, and is worth checking directly since interfaces evolve.
Sales / Support / Careers. The classic split above. Add a fourth "General" option that falls back to your main inbox for anything that doesn't fit neatly.
By urgency. Instead of a topic dropdown, use a priority field ("Urgent" vs "Standard") to route urgent tickets to an on-call address and everything else to the regular support queue.
By region. For companies with regional teams, route by a "region" field so EU inquiries hit one inbox and US inquiries hit another, without asking visitors to find a different contact page.
A single routed form keeps all of it in one inbox for review, one spam pipeline, one CSV export if you need the full history, and one endpoint to remember when someone asks "which form is this again?" a year from now. Routing changes who's notified — it doesn't fragment where the data lives.
One form means one endpoint to embed on your site, one spam-protection setup, and one place to review submission volume and history. Routing changes who gets notified for a given submission, not how many forms or endpoints you have to maintain.
No. Every submission still lands in the same form's inbox and counts toward the same plan limits, regardless of which recipient the notification email was routed to. Routing only affects who's emailed, not where the record lives.
It's a real, supported feature. Exact setup screens can change as the product evolves, so the precise configuration steps are best confirmed from your own form's settings rather than assumed from a guide.
One email when we publish something worth reading. No spam — appropriately enough, we'd know.