> For the complete documentation index, see [llms.txt](https://docs.trysavvy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trysavvy.com/other-useful-docs/work-in-progress/pending/work-in-progress-how-to-create-an-option-selector-results-page.md).

# Work in Progress: How to create an Option Selector Results Page

{% hint style="info" %}
This layout is useful to have a dynamic recommendation page at the end of a Flow depending on the analysis of the user's answer.
{% endhint %}

![](/files/-MhVSt64RbIsCGrLe0Df)

### How to create this integrated component?

* Create an Option Selector with one Button for each recommendation or option that we may need.
* Duplicate this Option Selector and use the same key to name it
* Create a Computed Field which returns the Primary recommendation (in this case it would be Action 1)
* Add conditions to buttons: for the first Option Selector Create a condition for each Button, where the Computed Field includes the equivalent for each Button.

![](/files/-MhVWViZE2Y5JjZzDeaq)

* For the second Option selector it would be exactly the opposite, the Computed Field should **not** include the equivalent for that Button.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.trysavvy.com/other-useful-docs/work-in-progress/pending/work-in-progress-how-to-create-an-option-selector-results-page.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.