Routing Conditions: Route Visitors Based on Form Answers

Routing conditions let you define rules that determine where a visitor is sent after completing your form — based on exactly what they answered. This is how meetergo turns a form into a smart decision-maker: different visitors get different outcomes depending on their responses.

How Conditions Work

Each route in your routing form has one or more conditions. A condition checks a specific field against a value using an operator. When all conditions in a route are met, the visitor is sent to that route's destination.

Structure of a condition:

[Field]  [Operator]  [Value]

Example:

Company size  equals  51–200
→ Route to: Enterprise Sales booking page

You can add multiple conditions to a single route. By default, all conditions must be true (AND logic) for the route to trigger.

Supported Operators

Setting Up Routing Conditions

1. Open your routing form and go to the Routing Logic tab.
2. Click Add route.
3. Choose the destination (booking page, external URL, contact form, callback, or custom message).
4. Click Add condition.
5. Select the field you want to evaluate.
6. Choose an operator.
7. Enter the value to compare against.
8. Add more conditions to the same route if needed.
9. Click Save.

Common Routing Patterns

Route by company size

Route by service interest

Route by budget

Route existing vs. new customers

Using New Field Types as Conditions

All field types can be used as routing conditions, including the new Phase 1 types:

• Yes / No — Answer equals Yes to route only confirmed prospects.
• Rating — Rating greater than 3 to route highly satisfied customers to an upsell flow.
• Date — Date is not blank to confirm a user provided a preferred date.
• Time — Use with date for scheduling preference routing.

The Fallback Route

The fallback route has no conditions — it catches all visitors who did not match any other route. Always configure a fallback so no visitor reaches a dead end.

Good fallback destinations:

• A general contact form ("We'll be in touch")
• A self-service resource page
• A thank-you message with next steps

FAQ

Can I use OR logic between conditions (match any one, not all)?

Currently, conditions within a route use AND logic — all must be true. To implement OR logic, create separate routes with one condition each, pointing to the same destination.

What happens if a visitor matches multiple routes?

The first matching route (from top to bottom) is used. Routes below it are ignored. Use the drag handle to reorder routes and control priority.

Can I route based on a field the visitor left blank?

Yes. Use the Blank operator to detect unanswered optional fields and route accordingly (e.g., send to a general queue if no company name was provided).

Can I test my routing conditions before publishing?

Yes. After saving, copy the public form link and fill out the form yourself to verify that conditions route correctly. You can update and re-test as many times as needed.

Can routing conditions reference fields from a previous funnel slide or page break?

Yes. All fields in the form — regardless of which page they are on — are available as condition targets in the Routing Logic tab.