How to Route Form Submissions to the Right Team
Start with the decision, not the form
Before setting up routing rules, map out who needs to see which type of submission and why. A support request and a sales inquiry usually shouldn't land in the same inbox, even if they came through the same form.
This mapping exercise often reveals that a form is trying to serve two different purposes at once, which is a signal to consider splitting it into two forms rather than adding complex routing logic to compensate.
Setting up rules that hold up over time
Route based on the answer to a specific, unambiguous question, such as a dropdown for 'reason for contact,' rather than trying to infer intent from a free-text field. Free-text routing is fragile and breaks the moment someone phrases something unexpectedly.
Build in a fallback. Every routing setup should have a default destination for submissions that don't cleanly match any rule, so nothing quietly disappears.
Keeping routing maintainable
Document the routing logic somewhere outside the form builder itself, whether that's a shared doc or a comment in the form's internal notes. Rules that only live in one person's memory tend to break when that person is out or moves teams.
Revisit routing rules periodically. Teams change, new categories of requests appear, and a routing setup that made sense a year ago can quietly misdirect submissions if nobody checks in on it.
Want to try this yourself? Explore the product →