Lorixen.
EN

Contact forms that reach the right person first time

Short answer: Add a required "What is your enquiry about?" field to your contact form and use it to decide where each submission goes: a separate email notification per option, a routing rule that picks the recipient, or a helpdesk rule that assigns the ticket to a team. Which one fits depends on how many teams you have, how many enquiries arrive, and whether anyone needs to track what happened to each one. Whatever you build, give every route a fallback owner and test each option before you trust it.

Most small business websites have one contact form that emails one inbox, and someone forwards things on. That works until the person doing the forwarding is on leave, or a quote request sits under three support questions for a week. Routing fixes that without asking customers to work out your org chart.

Start with the decision tree

Answer these in order. Stop at the first recipe that fits.

1. How many people or teams need to receive enquiries?

  • One person → you don't need routing. Keep one form, one inbox, and an honest auto-reply. Done.
  • Two to five teams → go to question 2.
  • More than five, or teams in different locations → go to question 3.

2. Does anyone need to see what happened to each enquiry (who replied, when, whether it's closed)?

  • No, email is fine → Recipe A: conditional email notifications.
  • Yes, but only for some types (say, quotes) → Recipe A for most types, Recipe C for the tracked ones.
  • Yes, for everything → Recipe C: helpdesk or CRM routing.

3. Do the teams work from a shared system already (helpdesk, CRM, shared inbox)?

  • Yes → Recipe C, routing inside that system.
  • No → Recipe B: one routing rule with a recipient per option, plus a fallback, until volume justifies a system.

And one more question that cuts across all of them: do some enquiry types need different questions? If a booking enquiry needs dates and a job enquiry needs a CV, separate forms (or conditional fields that appear per type) beat one long form with everything on it.

Recipe A: one notification per enquiry type

Best for: a few teams, modest volume, email as the working tool.

  1. Add a required dropdown or multiple-choice field such as "Reason for contact" with clear options: Sales question, Support request, Accounts, Media, Other.
  2. Create one email notification per option, each sent to the right address.
  3. Attach a condition to each notification, for example "send this notification if Reason for contact is Sales question".
  4. Keep a general notification to a shared address, or make sure "Other" goes somewhere watched.

WPForms documents exactly this pattern in its conditional notifications guide: build the email, toggle on "Enable Conditional Logic", set the rule, then add a new notification for each other team. It recommends basing the logic on a field with set choices such as a dropdown, not free text. Note that some field types for conditions need a paid licence in that plugin.

Watch out for: overlapping rules. If two notifications match the same choice, two teams both think the other one is handling it.

Recipe B: a routing rule inside one notification

Best for: the same email layout for every type, just a different recipient.

Gravity Forms calls this email routing. Inside a single notification, the "Send To" setting can be set to "Configure Routing", and each rule sends to an address when a field matches a value.

Its documentation includes the most useful warning in this whole topic: routing only supplies the recipient address, it can't stop the notification. If none of your rules matches, the notification is processed with an empty recipient. So:

  • Write a rule for every option in the dropdown, including "Other".
  • Add a catch-all rule that sends to a named fallback owner.
  • Re-check the rules whenever someone edits the dropdown options. Renaming "Accounts" to "Billing" quietly breaks a rule that says "is Accounts".

Recipe C: route into a helpdesk or CRM

Best for: anything that needs tracking, handovers or reporting.

Here the form's job is to create a record (a ticket, a lead, a deal) with the enquiry type attached, and the system assigns it. Zendesk, as one example, describes triggers that route tickets based on support addresses, ticket forms or other criteria. One documented workflow assigns tickets to groups by the address they were received at: create the groups, create a trigger per address, then views for each team.

That address-based approach gives a simple bridge from a website form: Recipe A's notifications send sales enquiries to sales@ and support enquiries to support@, and the helpdesk assigns each address to its group. If your form tool can create tickets directly with a field value, route on that field instead.

For leads in a CRM, the same idea applies: map "Reason for contact" into a field on the lead, and use the CRM's assignment rules.

Auto-replies per enquiry type

A single generic auto-reply ("Thanks, we'll be in touch") wastes the one moment the customer is paying attention. With one notification per type, you can send a different confirmation each time:

  • Sales: when to expect a reply, and a link to your pricing or examples.
  • Support: a reference to your help page, and what details speed things up.
  • Accounts: which invoice number or email address to quote.

Set the reply-to on internal notifications to the customer's email address, so the team member can reply straight from their inbox.

Testing the routing

Before you announce the new form:

  1. Submit one test per option, with "TEST" in the message.
  2. Confirm each one arrives where it should, and only there.
  3. Submit with no option chosen, if the field can be skipped (it shouldn't be).
  4. Check the auto-reply for each type.
  5. Repeat after any edit to the form's options or team addresses.

Write the routing table down somewhere the team can see it: option, recipient, backup person, expected reply time.

FAQ

Should I use separate forms instead of a dropdown?

Use separate forms when the enquiry types need different questions or live on different pages, such as a careers form or a booking form. For general contact, one form with a reason field is simpler for visitors.

What happens when the person in a route leaves?

That's why routes should point to role addresses or groups (sales@, accounts@) rather than personal inboxes. Changing who reads sales@ then needs no change to the form.

Can an AI tool classify enquiries instead of a dropdown?

It can, but a dropdown is cheaper, transparent and rarely wrong. Consider automatic classification only when people regularly pick the wrong option, and keep a human-checked "unclear" route.

How many options should the dropdown have?

As few as your teams actually need, usually four or five plus "Other". Long lists make people pick the first plausible match.

When your enquiries arrive in one inbox and get forwarded by hand, we can set up routing that matches how your teams really work.

Sources

WhatsAppLet’s talk