Ask returning visitors only for missing answers

Let returning visitors pick up without answering the same questions again. Your widget can skip known answers while your flow keeps a path open to the questions you still need.

You'll need access to edit the flow and each widget that displays it. Use a page with your project's snippet installed. If your rules use email-platform data, identify your test browser too. Collecting an answer and identifying a contact are separate things.

Tell each widget to skip known answers

1. Open Widgets and select the widget that displays your flow.
2. Open Display.
3. Expand Question handling.
4. Select Ask questions we don't know the answer to.
5. Repeat for every widget that runs this flow.

Enlarge

Question handling settings for skipping known questions and showing a back buttonOriginalOriginal

This setting belongs to the widget, not the flow. It asks only missing questions on the path the visitor can reach. It won't move a question ahead of a condition or undo Exit Flow.

If you've enabled Show a back button, include it in your test. It lets visitors return to an earlier question, but it doesn't erase all their remembered data.

Keep a path to the questions you still need

Open your flow in Flows and put the questions before the condition that chooses the final offer. Both visitors with known answers and visitors without them need a path through those questions. Give the no-offer path an ending, such as Exit Flow, after the questions.

For example, WorkForge (opens in a new tab) can ask a returning lead for their team size even when no promotion applies. If the flow exits before that question, it can't collect the missing answer.

If a stored choice decides which follow-up to ask, use a Router. Keep its Default path useful for someone without a matching answer.

Make sure the widget can appear again

Skipping known questions doesn't make an otherwise hidden widget appear. Check that the widget is enabled and placed on the page you're testing. For a floating widget, check When it appears, Targeting rules, and the Desktop, Tablet, and Phone settings.

Test its normal trigger. Opening a widget manually won't tell you whether its scroll or time-on-page trigger works. For an embedded widget, check Where it appears and make sure the embed location exists on the page.

For a floating widget, also check After it's dismissed. Dismissal doesn't delete answers. Once the widget can appear again, it still skips the answers it knows. Choosing Ask every question, every time won't clear a dismissal either.

The widget display reference covers the other question-handling choices, type-specific triggers, and dismissal durations and defaults.

Try a visitor with only some answers

Choose Preview on your site and use the debugger to check what RightMessage knows about your test visitor.

1. Start with fresh browser data and answer part of the flow.
2. Return in the same browser. Check that only the missing questions appear.
3. Answer the remaining questions and check the final offer or exit.
4. Dismiss the widget, then check when it can return under After it's dismissed.

In a WorkForge flow that asks about work type and team size, someone who has answered only work type should reach team size. Someone who has answered both should reach the offer or exit without repeating either question.

A visitor can have missing answers and still be excluded by targeting, a trigger, their device, or a remembered dismissal. If all answers are known and the path has nothing left to display, the widget may have nothing to show.

Once visitors can reach the missing questions and continue to the right ending, review and publish your changes. If your test keeps starting in the wrong place, see returning-visitor troubleshooting.