Customizing coverage options by state

Why state-based options exist

Insurance products vary by state — coverage minimums, available endorsements, optional riders, even which carriers will write the business. Showing every option to every consumer leads to confusion and bad data. State-based options keep the Form clean by hiding what doesn’t apply to the consumer’s state.

How it works

Two pieces work together:

1. A State Filter step captures the consumer’s state early in the flow. This makes the answer available for downstream visibility logic.
2. Per-state options on individual questions — for any question that varies by state, you configure which options appear for which states.

If the consumer’s state isn’t explicitly configured for a question, that question falls through to its default options.

Add a State Filter step

1. 1

   Open your Form’s editor.

2. 2

   Add a new step early in the flow (typically right after capturing the prospect’s basic info).

3. 3

   Choose the State Filter step type. Save.

Place the State Filter step before any question whose options should vary by state. Otherwise, the per-state visibility logic has nothing to reference.

Configure per-state options on a question

After the State Filter step is in place, open a question whose options should vary. The question’s options panel will show a per-state configuration:

• For each state, you can override which options appear (or hide options entirely).
• Default options apply to any state you don’t explicitly configure.

Save your changes. New consumer visits to the Form’s Link immediately see the state-aware behavior.

Restricting a Form to specific states

You can also use the State Filter to gate the Form entirely — consumers from non-supported states see a “this isn’t available in your state” message instead of the rest of the questions. The exact configuration is on the State Filter step itself.

This is useful for:

• Carriers or appetites that only write in certain states
• Products that aren’t licensed in some jurisdictions
• Pilots or limited-state rollouts

Common questions

My consumer is in the right state but isn’t seeing the options I configured. Check the order of the State Filter step. If it appears after the question whose options vary, the visibility logic can’t fire — the answer hasn’t been captured yet. Move the State Filter earlier.

Can the same Form serve multiple states with different question sequences? Yes — beyond per-question option overrides, you can use conditional step visibility (where supported) to show or hide whole steps based on state.

What if a consumer changes their state mid-flow? The visibility recalculates. Options not applicable to the new state are hidden; previously hidden options that now apply may appear. Existing answers to other questions are preserved.

Can a Link restrict access by state instead of (or in addition to) the Form? Per-Link state restriction isn’t a separate feature today — state filtering is configured at the Form level via the State Filter step. All Links to the same Form share the same state behavior.