> For the complete documentation index, see [llms.txt](https://showreward.gitbook.io/showreward-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://showreward.gitbook.io/showreward-docs/participant-guide.md).

# Participant guide: prepare, attend and claim

Your personal ShowReward link opens the portal for the campaign that invited you. Keep the link private and use the same link to check your progress. If it does not open, ask the campaign team for a fresh link.

## Before your call

1. Check the call date and time in the portal. It is shown in your local time.
2. Use **Add to Google Calendar** or **Apple/Other (.ics)** if you want a calendar reminder.
3. Select **I confirm I'll attend** to confirm your plans.
4. Complete the preparation tasks shown by the campaign.

Depending on the campaign, tasks may include **Watch the preparation videos** and **Record your intro video**. The portal shows which tasks are optional and any associated bonus. Preparation videos may unlock in sequence.

For an introduction video, follow the campaign's instructions. You can **Record with camera** or **Upload a video**, then send it. If camera access fails, upload a video file instead. Follow the size limit shown in the portal. If you receive a request to record again, read the reason before replacing the video.

Confirming your plans does not validate attendance. The campaign team records the call result after it takes place.

## After your call

**Pending validation** means the team has not yet completed the attendance or reward decision. When your portal shows **Waiting for your claim**, you can complete the claim steps.

1. Read **View terms and conditions**.
2. Complete the identity steps shown. Depending on the campaign, this may be a form or an external identity check that returns you to the portal.
3. Complete **Payout details** if required. Choose an available method and enter your own correct account-holder and destination details.
4. Tick the required confirmations and accept the campaign's current terms.
5. Select **Claim my \[amount]** or **Verify my identity and claim \[amount]**, as shown.

Available payout methods depend on the project. The portal may offer Wise, PayPal or bank transfer. Bank fields change with the selected bank network.

If the portal already has eligible details from an earlier claim, review the summary, accept the current terms and choose **Confirm and claim \[amount]**. Contact the campaign team if saved details need changing.

## Understand your status

| Portal status                          | Meaning and next step                                                                               |
| -------------------------------------- | --------------------------------------------------------------------------------------------------- |
| **Call booked**                        | Attend the call and complete any preparation tasks shown.                                           |
| **Pending validation**                 | Wait for the team's attendance or reward decision.                                                  |
| **Waiting for your claim**             | Open the claim form and submit the required information.                                            |
| **In review**                          | Your claim is being checked. Complete any follow-up the team requests.                              |
| **Action needed**                      | Read the correction request, update the affected details and select **Resubmit corrected details**. |
| **Ready for payout**                   | Your reward is approved and awaiting the team's payment process.                                    |
| **Paid**                               | Check the receipt for the amount, method, date and any payment reference.                           |
| **Campaign paused**                    | Claims are currently unavailable. Contact the campaign team if you need help.                       |
| **Not approved** or **Not applicable** | Read the reason shown and contact the campaign team if you believe it is incorrect.                 |

If an identity check was interrupted, use the resume or **Retry verification** option when it appears. If the portal says the identity result is under review, wait for the team to review it.

Contact the team that invited you for questions about eligibility, a missing appointment, corrections or payment timing. Campaign conditions and the status shown in your portal determine the next step.

For campaign teams supporting participants, [Tutorial 03](/showreward-docs/campaigns.md#tutorial-03) demonstrates the booking and preparation journey, and [Tutorial 04](/showreward-docs/daily-operations/validations.md#tutorial-04) covers claims. These walkthroughs also include team administration screens; participants can follow the instructions on this page directly.

## Related guides

[Troubleshooting](/showreward-docs/troubleshooting.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://showreward.gitbook.io/showreward-docs/participant-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
