Skip to content

Route every form submission to the right person automatically

Use one answer, or a few conditions, to send each submission to the right inbox or channel, with a safe default for the rest.

2 min read

On this page

A single contact form often serves several teams. Sales wants pricing questions, support wants bug reports, and someone in finance wants anything that mentions an invoice. When every submission lands in one inbox, someone has to read and forward each one. Routing does that sorting for you, the moment the submission arrives.

Route on one answer

The simplest route uses a question the visitor already answers, such as What can we help with? with the options Sales, Support and Billing. In a Formpik flow, add a Route by answer step after the trigger and point it at that field. Each option gets its own path, and each path connects to the step for that team: an email to sales, a Slack message to #support, a Teams card for billing.

Every route step also has a default path for answers that match no case. Connect it to a shared inbox, so a submission with an unexpected answer is never dropped.

Route on more than one condition

Sometimes one answer is not enough. A demo request from a company with more than 200 people should go to the enterprise team; the rest go to the regular sales queue. Use an If / else step for that. It checks one or more conditions and sends the submission down the true or the false path. Set it to match all conditions for a strict rule, or any of them for a broad one.

Conditions compare answers in the way the field type suggests: text can be checked for contains or starts with, numbers for greater or less than, dates for before or after, and choice fields for one of a list. For example:

  • Company size is greater than 200 and Country is one of DE, AT, CH.
  • Email ends with .edu, for an education discount team.
  • Message contains urgent or Topic is Outage.

Route on what the message means

Visitors do not always pick the right option, and many forms only have a free-text message. An Ask AI step can read the message and sort it into one of the categories you list, such as Sales, Support or Billing. Its answer becomes a value you can route on with the next step. If the AI cannot answer, the value stays empty and the default path takes over, so the flow never stops.

Keep the routes readable

  • Name each step after what it does: Email billing reads better than Send email 3.
  • Put the most specific condition first. Route cases are checked in order, and the first match wins.
  • Use one route step per decision. Two simple steps are easier to change later than one step with ten cases.

Test every path before going live

Send a test submission from the flow editor for each answer. A test runs the whole flow and highlights the path it took, but nothing is actually delivered, so you can try every route without emailing real people. When the submissions arrive for real, the inbox shows every step each one ran, which makes a wrong route easy to spot and fix.

References

Keep reading

More from the blog