Advice flows for guided product advice

An Advice flow turns customer questions into a guided path. Each step should move the visitor closer to a useful recommendation.

When the flow is used as a product finder or choice helper, keep the path focused on one buying decision and connect every important answer to matching or the next useful question. See product finder software and choice helper software for public examples of where this fits in a webshop.

Where to configure this

• Advice flows: create, open and organize flows.
• Builder: questions, answers, branches and result steps.
• Matching: connect answers to product advice.
• Styling: adjust the public look of the Advice flow and product cards.
• Translations: manage languages for flow content and Flow widget labels.
• Preview: walk through the latest saved draft.
• Share & Publish: publish and copy the Flow widget code.

Create or open a flow

1. Open Advice flows.
2. Create a new flow or open an existing one.
3. Choose the source language and, when available, the product dataset.
4. Open Builder to create the question path.

Use a short, recognizable flow name. Add tags when your team groups flows by category, collection or workflow.

Plan the path

Plan this before you start placing steps in Builder.

1. Choose one product group or buying decision.
2. Write down the questions your team already asks customers.
3. Put the most important decision first.
4. Remove questions that do not change the recommendation.
5. End with a result step that clearly leads to the recommendation.

Build questions

Add and edit questions in Builder. Open a question to change its title, description, answer source, images and answer options.

• Use single choice when one answer should steer the next step.
• Use multiple choice when several needs can apply.
• Use a dropdown for long lists such as models, sizes or compatibility values.
• Use a dataset attribute when answers should come from product data.
• Add a short tooltip only when it prevents doubt.
• Use images or swatches when they make choices easier to scan.

Keep answer labels close to how visitors think. Good answers are concrete, short and easy to compare.

Use result steps

Use result steps when a path is finished and visitors should see advice or product recommendations.

Keep result copy short. The recommendation cards should do most of the product work, while the result text explains the next step.

Use branches

Set branches in Builder by connecting answers to the next step.

Branches keep the path relevant. Connect each answer to the next useful question, skip questions that no longer apply and send finished paths to a result step.

For optional multiple-choice questions, also connect the skip path so visitors can continue without choosing an answer.

Preview before publishing

Use Preview to walk through the draft as different visitor types.

Check:

• every important path reaches a result;
• the next question always feels logical;
• optional questions can be skipped;
• answer labels are clear on mobile;
• recommendations match the chosen answers.

Use the assistant

Open the assistant from the builder or matching screen.

When enabled, the assistant can suggest question order, answer options and shorter paths based on the current flow and linked dataset.

It only changes a draft when you click an action such as Add flow or Replace flow. It does not publish for you.

Keep it maintainable

• Use recognizable step names.
• Add internal names when your team needs clearer admin labels.
• Avoid duplicate questions with slightly different wording.
• Keep the first version simple and improve from analytics.
• Test every important path before publishing.

Draft and publish

Builder and Styling save automatically. In the builder you can also save manually with the Save button or Cmd/Ctrl+S.

Changes stay as a draft until you publish. Publishing updates the live link and Flow widget at the same time.

Publish from Share & Publish when the path, matching and styling are ready.