> For the complete documentation index, see [llms.txt](https://docs.claimr.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.claimr.io/ux-requirements/quest-ux-requirements.md). # Quest UX requirements ## **What is a claimr Quest?** A quest in claimr is a structured set of tasks designed to engage users and guide them towards specific goals within a campaign.
## **1. Quest header** This section displays the core information about the quest, including its name, the organization offering it (your company), and a brief description. ### **Quest name** Clearly displays the name of the quest. * Use a clear and concise title that reflects the quest's theme or objective. ### **Organization name** Clearly displays the name of the organization or company associated with the campaign. * Ensure consistency with branding guidelines. ### **Quest description** Provides a brief overview of the quest's objectives and actions required. * Use clear and concise language, avoiding jargon. ## **2. Rewards section** This section highlights the rewards users can earn by completing the quest. ### **Rewards:** Displays the rewards associated with the quest. * Use high-quality images or icons to represent rewards. * Clearly communicate the type and value of each reward. ### **Points** Displays the number of points the user can earn by completing the quest. * Use a clear numerical representation and label (e.g., "0/400 Points"). ### **Quest timer** Displays the time remaining for the quest or the time until it becomes available. * Use a clear and easy-to-understand timer format. ## **3. Task section** This section presents the tasks users need to complete within the quest. It includes all tasks within the quest, and each task has a header, body, and a CTA button.

Example: Individual task

Example: The list of tasks

### **Task header** Provides a concise and informative title for the task. * Use action-oriented language. ### **Task body** Provides the main content or details of the task, including any necessary information, instructions, or visuals. * Use headings, subheadings, bullet points, and other formatting elements to organize the content. * Incorporate relevant visuals, such as images, videos, or diagrams. ### **CTA button** Provides a clear action button for users to engage with the task. * Use action-oriented and concise language. For more information, read [Task UX requirements](/ux-requirements/task-ux-requirements.md) ## **4. More quests section** This section shows a preview of other quests available in the campaign. * Presentquest previews in a visually appealing and concise manner. ## 5. Footer This section contains actions or buttons related to the quest. * Use clear labeling (e.g., "Close," "View More"). --- # 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.claimr.io/ux-requirements/quest-ux-requirements.md?ask=&goal= ``` `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.