# Quests

### Overview

A **Quest** is a structured unit designed to group multiple Missions under a common theme, objective, or category. It helps organize user engagement around specific journeys or campaigns.

Each Quest can include several missions that users complete to earn rewards and track progress. 

#### Use cases

| Time-based Campaigns                                                     | Behavior Funnels                                                      | Difficulty Tiers                                                                                  |
| ------------------------------------------------------------------------ | --------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
| Launch seasonal or limited-time quests tied to product updates or promos | Link missions together to drive users through deeper engagement flows | Design journeys like "Starter Pack" for new users or "Power User Trail" for advanced participants |

#### User behaviour impact

* Drives daily logins by giving users a reason to “come back and finish”
* Increases feature exploration by nudging users into underused parts of your app
* Builds momentum by rewarding consistency, not just one-time actions

***

### Creating a Quest

{% stepper %}
{% step %}
Go to the **Missions** section and click **Create Mission.**

<div data-full-width="false"><figure><img src="/files/GFNe67PFjN0NzNqLngOg" alt=""><figcaption><p><em>Quest option in the Create Mission pop-up</em><br></p></figcaption></figure></div>
{% endstep %}

{% step %}
On the **Quest** creation page:

* Configure general parameters (e.g., name, due date, reward, description)
* Select **Missions** to add to the Quest.

  * Only Missions in **Draft** status are shown.
    * Note: You can create a Quest without Missions, but it cannot be activated until at least one Mission is added.

  <figure><img src="/files/rbRhxSAL7dDri9zb3BXI" alt=""><figcaption><p><em>Selecting Missions on the Quest creation page</em></p></figcaption></figure>

{% hint style="info" %}
(Optional) Enable the “Disable missions rewards” checkbox in the Conditions block if you want to reward only the Quest itself, not individual Missions.
{% endhint %}
{% endstep %}

{% step %}
Click **Create**. The Quest will appear in the main table with **Draft** status.
{% endstep %}

{% step %}
*Congratulations!* The Quest has been successfully created and is displayed in the main table with Draft status.

By clicking on the Quest name in the table, the user can view the list of missions that were added to this Quest.

<figure><img src="/files/6BATfp7GueDg61lxkCSW" alt=""><figcaption><p>Exploring Missions added to a Quest</p></figcaption></figure>
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**RESTRICTIONS:**

* ✅ Social Media, Event-Based, and Manual Missions are supported in Quests.
* 🚫 Active Missions cannot be added to Quests.
* 🚫 A Mission already assigned to another Quest cannot be reused.
* 🚫 Missions in a Quest cannot be activated/deactivated individually.
* 🚫 You can only add Missions to Quests that are in Draft status<br>
  {% endhint %}

<details>

<summary>Quest &#x26; Mission Rewards</summary>

* A Quest always has a reward.
* Missions inside a Quest can be:
  * With individual rewards (default)
  * Without rewards (if the Disable mission rewards option is enabled)

</details>

<details>

<summary>Quest Expiration</summary>

* If a Due Date is set, the Quest will change its status to Expired when the deadline passes.
* All Missions in the Quest will then revert to **Draft** status.

</details>

<details>

<summary>Editing or Removing Missions</summary>

To remove a Mission from an existing Quest:

1. Set the Quest status to **Draft**
2. Click **Edit**
3. Deselect the Mission from the Select Missions field

</details>

<details>

<summary>Alternative Way to Add a Mission to a Quest</summary>

You can also assign a Mission to a Quest during Mission creation:

* Use the Select Quest dropdown
* Only Quests in Draft status will appear
* You cannot add a Mission to an Active Quest

<div align="left"><figure><img src="/files/zvKTAn956g4fNFDnWjEd" alt=""><figcaption><p>Selecting a Quest via Mission creation page</p></figcaption></figure></div>

</details>

<details>

<summary>Activation, Deactivation, and Deletion Logic</summary>

| <mark style="color:green;">**Action**</mark> | <mark style="color:green;">**Effect on Missions**</mark> |
| -------------------------------------------- | -------------------------------------------------------- |
| Activate Quest                               | All Missions in the Quest become Active                  |
| Deactivate Quest                             | All Missions revert to Draft                             |
| Delete Quest                                 | Quest is removed; Missions return to Draft               |

</details>

***

### Quests on The Widget

1. After the Quest has been activated, it becomes visible to users on the widget.\
   On the Quest card, the user can see the number of missions included in it, as well as their personal progress.

<figure><img src="/files/QrJjCOu8j0En6YyqTFjj" alt=""><figcaption><p>Quest card</p></figcaption></figure>

2. When the user clicks on the Quest card, the Quest page opens, where they can view more detailed information about the Quest as well as the missions included in it.

<figure><img src="/files/K8OLGLIPjMdHkhLeifM6" alt=""><figcaption><p>Quest page</p></figcaption></figure>

3. Once all missions within the Quest have been successfully completed, the user can claim their reward by clicking the Claim button on the Quest card.<br>


---

# Agent Instructions: 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:

```
GET https://docs.enable3.io/enable3/quests.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.