> For the complete documentation index, see [llms.txt](https://docs.rhym.io/rhym-help-guide-and-faqs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rhym.io/rhym-help-guide-and-faqs/how-to-create-campaign/how-to-create-product-recommendation-quiz/product-recommendation-result-screen-logic.md).

# Product Recommendation: Result Screen Logic

### Add Product Recommendations <a href="#add-product-recommendations" id="add-product-recommendations"></a>

After framing your questions, navigate downward to the "Product Recommendation Screen" section. Here, you can establish the logic dictating which products get recommended based on quiz answers.

<figure><img src="/files/sSNZy1tPJtsK46856jjB" alt=""><figcaption></figcaption></figure>

In the above example of Product Recommendation Quiz, we have two questions added -

1. "What's your monthly income?"
   1. Less than 4k
   2. 4k to 8k
   3. More than 8k\\
2. "What's your credit score?"
   1. Less than 500
   2. 500-700
   3. More than 700

**Also we can see we have added a product card of "ABCD" Credit card.**

We have to check the answer type for which we want a user to be recommended the **"ABCD Credit card"**

For exampl&#x65;**- According to the question and answer, let's say the "ABCD" credit card is suitable best for people who will have their-**

1. **Income- More than 8k**
2. **Credit Score- between 500-700**

**Accordingly, we need to fix this logic shown in the right hand side panel.**\
Please refer to the screenshot below

<figure><img src="/files/vqiVorufaxLY4kmIKQbG" alt=""><figcaption></figcaption></figure>

**Please Note:** <mark style="background-color:yellow;">If the person taking the above quiz selects</mark> <mark style="background-color:yellow;">**"More than 8k**</mark><mark style="background-color:yellow;">" in the first question and selects</mark> <mark style="background-color:yellow;">**"Less than 500"**</mark> <mark style="background-color:yellow;">or</mark> <mark style="background-color:yellow;">**"More than 700"**</mark><mark style="background-color:yellow;">- the ABCD Card will not be shown.</mark>\
\ <mark style="background-color:yellow;">As the logic is "and" and not "or". In simple words the product outcome works with exact match. User would have to fulfil both the logic to get the recommendation of "</mark><mark style="background-color:yellow;">**ABCD Credit Card"**</mark>

Also, if a user selects certain options to which there is no assigned product card, he will see a blank screen. Therefore, its advisable to set the logics perfectly and avoid any misses to provide a good campaign experience

Let's now discuss on how you can add new product recommendations card, delete, clone etc. You just need to hover over the card, to get all the 3 options available to you-

1. **Add card**- Let's you add a blank new card
2. **Delete card**- Let's you delete that product card
3. **Clone card**- Let's you duplicate the product card added, helps in cases where you want to use some specific font, color, border style of the CTA button

<figure><img src="/files/YEaSezBs82rhGaOE4kj1" alt=""><figcaption></figcaption></figure>


---

# 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.rhym.io/rhym-help-guide-and-faqs/how-to-create-campaign/how-to-create-product-recommendation-quiz/product-recommendation-result-screen-logic.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.