# Score a quiz and recommend a page

You'll give answers points, use the highest or lowest score to recommend a page, and decide which recommendation wins a tie.

Available on the Grow, Scale, and Pro plans.

Use quiz answers to recommend the page that fits someone best. Each answer adds or subtracts points, and your flow uses the totals to choose what to show next.

## Start with the pages you want to recommend

Pick real pages on your website, then write down what you'd need to know to recommend each one. Ask the question that separates the biggest groups first. Add a follow-up only where the answer still leaves more than one useful page.

For example, [WorkForge](https://workforge.rightmessage.com) could recommend its [software teams page](https://workforge.rightmessage.com/solutions/software-teams.html) to people planning a product roadmap, or its [agencies page](https://workforge.rightmessage.com/solutions/agencies.html) to teams coordinating client work.

If one answer tells you which page to recommend, route straight to it. Use scores where several answers need to contribute to the choice. You don't need to put every visitor through every question.

Open the flow you want to score. If you still need to build its questions and paths, start with [mapping a visitor journey](https://rightmessage.com/help/mapping-out-visitor-journeys). Use different names for scores and variables, since a stored variable with the same name can override a score.

## Give each answer points

1. Select a choice question on the flow canvas.
2. Beside an answer, choose the chart icon, **Edit answer scores**.
3. In **Scores for answer**, enter a name under **Modify score** and an adjustment after **by**.
4. Choose **Add another score** if that answer changes more than one total.
5. Repeat for the other answers and questions. Include at least two score names in the flow.

WorkForge could use `planning` and `collaboration` as its two scores. An answer about needing a clearer roadmap adds 2 to `planning`. An answer about better handoffs adds 2 to `collaboration`. A relevant follow-up can add 1 to either total. Several questions can contribute to the same score, and one answer can change both scores.

Positive adjustments add points. Negative adjustments subtract them. Each answer-scoring row starts with a blank name and 0 points. Choose an existing name or enter a new one. The plus and minus controls change the adjustment by one.

**Add another score** adds another blank, zero-valued row. You can remove a row with the trash control when more than one exists. To disable the last row, clear its name or set it to zero. The editor's summary includes only named, nonzero rows.

## Give every score a starting value

A missing score isn't the same as zero. Set an initial value for every score you want to compare, including scores that start at zero.

1. Before the scored questions, choose **+** on the path, then **Set Data**. If the canvas is empty, choose **Add the first step** instead.
2. Keep **Update Score** selected under **Action Type**.
3. Under **Modify score**, enter a score name and set the adjustment to `0`.
4. Add a separate **Set Data** node for each remaining score.

A new **Update Score** row starts at 1, so change it to zero for this setup. These actions add or subtract points. They don't replace the total. Only the first score adjustment in a single **Set Data** node is retained, which is why each score needs its own node.

![Set Data with a planning score adjustment and a last\_topic variable that expires after seven days](https://rightmessage.com/help/screens/flows-set-data.light.webp)

The screenshot shows a score adjustment alongside a saved variable. For your starting values, use one score adjustment per node.

## Send each score to its recommendation

1. After the questions and score adjustments, choose **+**, then **High Score**.
2. Keep **Flow Scores** selected if the mode choices appear.
3. Check the score name in each route.
4. Leave **Lowest score wins** off to recommend the highest-scoring option.
5. Drag the rows into the order you'd like to use for ties. The first tied row wins.
6. On each route, choose **+** and add the **Offer** or **Form** that belongs there. Use your real destination page for each offer's link.

If your quiz measures areas that need attention, turn on **Lowest score wins** instead. This changes which path wins, not the scores themselves. The screenshot shows that setting enabled.

![High Score in Flow Scores mode with Lowest score wins enabled and planning first in tie priority](https://rightmessage.com/help/screens/flows-score-routing.light.webp)

Give every route something visitors can see. An empty branch can rejoin the steps below **High Score**, but it won't create a recommendation for you. Put shared content after the branches only when each branch can reach it.

Choose the recommendation before a form. Ordinary steps below a terminal form don't resume after submission. A form uses its separate post-submit path for completion.

The [High Score reference](https://rightmessage.com/help/flow-node-high-score) covers variable comparisons, missing values, the first-route fallback when every score is absent, and what happens when you remove routes or switch modes.

## Check the scores and the page they recommend

Choose **Preview on your site** and use the debugger to inspect the totals and selected path. Test a clear winner for each recommendation, an exact tie, all-zero scores, and unanswered questions. If you subtract points, test negative totals too.

With `planning` at 3 and `collaboration` at 1, highest-score routing should choose `planning`. Lowest-score routing should choose `collaboration`. Equal totals should choose the first tied row. If only `collaboration` has a value, it should win in either mode.

Try both fresh visitors and visitors with remembered answers, since a widget can skip a known question. If a total is missing, check that the question was reached, its answer has points assigned, and an earlier terminal node didn't stop the flow.

When the same answers and route order produce the same recommendation, and every recommendation has reachable content, review and [publish your changes](https://rightmessage.com/help/publishing-your-changes). If a path or total is wrong, use [routing troubleshooting](https://rightmessage.com/help/troubleshoot-flow-routing) to find the cause.