Send one contact form to the right lead flow

If you run one contact form across a whole portfolio, every submission landed on whichever lead flow the form was wired to, no matter which property the person asked about. A switchboard can now split them up.

How it works

Build a switchboard with an email intake type and start it from the Form Submission trigger. Pick the form it watches, either a flow form or a custom form. Every submission of that form starts the flow, and the answers arrive as variables you can branch on.

A Switch node reads whichever answer decides the destination, usually the property or community the person picked. Each branch then ends in a Route to Lead Flow node, which names the lead flow that should own the submission and the email intake source on it. A Script node in between is the usual place to tidy an answer up first, so that Sofia Yorkville, sofia and Sofia London all land on the same branch.

What the receiving flow sees

The submission is handed over as the same submission notification the form would have sent anyway, so the lead flow treats it exactly as it treats a form wired straight to it. The person becomes a real lead on the right flow, Casa answers them, that flow's cadences pick them up, and their reply threads back to the same place. Nothing downstream needs to know a switchboard was involved.

Worth knowing

• Route to Lead Flow can also send to an address you type in, for when the destination has to be built out of the submission itself.
• A submission that cannot be routed, because the destination lead flow was archived or its email intake method was switched off, is recorded in the execution history rather than dropped without a trace.
• A switchboard that starts only from a form submission is not given an intake address of its own, because it never reads one.

Switchboard sits under Developer in the menu. As with any flow, it only runs once you toggle it Active.