> For the complete documentation index, see [llms.txt](https://help.joy.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.joy.so/on-site-content/loyalty-landing-page/loyalty-program-faqs.md).

# Loyalty Program FAQs

{% hint style="info" %}
This feature is available in **all plans.**
{% endhint %}

### What is "Loyalty Program FAQs" feature?

The Loyalty Program FAQs is a powerful tool that lets you create a dedicated section on your loyalty page to answer your customers' most common questions. Think of it like a helpful information booth that's always ready to provide quick answers and clear up any confusion about your loyalty program.

### Why do you need this feature?

Loyalty Program FAQs on the loyalty page to provide customers with quick answers to common questions, enhancing their understanding of the loyalty program. This helps reduce customer confusion, saves time for both the store and customers, and improves overall satisfaction.

Having FAQs also builds trust by addressing concerns proactively, making it easier for customers to engage with and join the program.

### How to set up Loyalty Program FAQs

{% stepper %}
{% step %}
Navigate to **Embedded Content** on your left menu, then click on **Set up** in the Loyalty Program FAQs
{% endstep %}

{% step %}
Select **Set up** in the Loyalty Program FAQs
{% endstep %}

{% step %}
Select **View theme editor** to activate the Loyalty Program FAQs
{% endstep %}

{% step %}
In **Theme settings**, add the **Joy: Loyalty Program** **FAQs** and customize the block’s colors and description to match your store’s theme
{% endstep %}

{% step %}
Click "**save**" to enable your Loyalty Program FAQs in your loyalty page

{% embed url="<https://app.arcade.software/share/Y86Ed6hrGrbOziPUWZpy>" %}
{% endstep %}
{% endstepper %}

### Adding FAQ and arranging their order

{% stepper %}
{% step %}
Navigate to Embedded content, then choose "**Set up**" Loyalty Program FAQs
{% endstep %}

{% step %}
In the **Frequently asked questions**, you can drag and drop FAQs to arrange their display order or click "Add FAQ" for a new question and answer set

{% embed url="<https://app.arcade.software/share/4r57Jq6JgZAVtByEvVCl>" %}
{% endstep %}

{% step %}
If you don't want to manually create the FAQs, you can use the AI Generate FAQs feature. This will automatically generate your FAQs list based on your program setting. You can choose which FAQ items you want to keep, and later on, you can update them to match your brand tone.

<figure><img src="/files/pHrd5pxtClP6y2pUZ1r8" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Each FAQ has its **question** and **answer** fields inline-editable — type directly into either field, press Enter (or click outside), and save.
{% endstep %}

{% step %}
Preview your setting by clicking on View theme editor
{% endstep %}
{% endstepper %}


---

# 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://help.joy.so/on-site-content/loyalty-landing-page/loyalty-program-faqs.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.