> 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/daily-operations/validations.md).

# Validate calls and review introduction videos

A closer is the team member who handles a participant's call. **Validations** gives closers a queue of calls and introduction videos to review.

Closers work with their own queue. Project managers and administrators can use **View queue for** to select a team member or **Entire team (global queue)**.

## Tutorial 04

**Validate Calls and Manage Reward Claims**

Record attendance, choose a call outcome and reward decision, and follow the participant claim through review.

{% embed url="<https://assets.cdn.filesafe.space/mYdk8zjDWRfpvpBKfwxH/media/6ac440857d735ea2a14bd6e5.mp4#t=4>" %}

[Open Tutorial 04 video in a new tab](https://assets.cdn.filesafe.space/mYdk8zjDWRfpvpBKfwxH/media/6ac440857d735ea2a14bd6e5.mp4).

**Chapters**

1. Validate an attended call and defer the reward decision.
2. Configure the ShowReward: Validate Call workflow action.
3. Map the exact appointment ID, including the Last Appointment ID example.
4. Resolve a deferred decision and enable the claim.
5. Enter participant claim details and start identity verification.
6. Review a separate verified example until the reward is ready for payment.

The recording starts identity verification, then switches to a different participant with verification already complete. It ends at **Ready for payment** without executing or recording a payout. See [Record a completed payout](/showreward-docs/daily-operations/rewards.md#record-a-completed-payout) for the remaining payment steps.

[All video tutorials](/showreward-docs/getting-started/video-tutorials.md) · [Next: Tutorial 05](/showreward-docs/gohighlevel/workflows.md#tutorial-05)

## Record an attended call

1. Open **Validations → Calls**.
2. Find the appointment and select **Show**.
3. Enter the actual **Approximate duration (min)**. The form may start with the campaign's minimum; update it to reflect the call.
4. Choose the **Call outcome**: **Sold**, **Not sold - Follow-up**, **Move to next call**, or **Not qualified**.
5. Choose a **Reward decision** and add useful notes.
6. Select **Save validation**.

Attendance, the sales outcome and the reward decision are separate choices. Review all three.

| Reward decision         | Result                                                                                  |
| ----------------------- | --------------------------------------------------------------------------------------- |
| **Send reward**         | Enables the participant to claim. Identity, payout and risk checks may still be needed. |
| **Defer decision**      | Leaves the reward decision pending.                                                     |
| **Do not send**         | Does not enable a claim.                                                                |
| **Suspicious — review** | Enables the claim and flags a risk issue that must be reviewed before approval.         |

**Send reward** does not transfer money. Follow the campaign's conditions when choosing a decision. A **Recommended** badge is guidance; you still need to make a choice.

Validation buttons become available from 15 minutes before the scheduled time. Record the result after you know what happened.

To send a validation from HighLevel, follow [Validate a call from a workflow](/showreward-docs/gohighlevel/workflows.md#validate-a-call-from-a-workflow). To react to a manual validation, see [Tutorial 05 and the workflow examples](/showreward-docs/gohighlevel/workflows.md#tutorial-05).

## Record a no-show

Select **No-show**, add notes if useful, and select **Confirm no-show**. This can reject the pending reward associated with the missed call. Check the resulting reward status, especially when the participant has multiple appointments or an earlier reward decision.

## Finish a deferred decision

Open the lead record and find the attended appointment. Where **Resolve decision** is available, choose the updated outcome and a final reward decision, add context, and select **Save final decision**.

Use this for the decision on that same call. A later appointment has its own validation.

## Review a video

The introduction-video submission and review example appears in [Tutorial 03](/showreward-docs/campaigns.md#tutorial-03), after the booking and portal chapters.

Open **Validations → Videos**, select a participant, and watch the introduction video before deciding:

* **Valid**: accept the video.
* **Not qualified**: record that the participant is not suitable. Review the optional **Also cancel the call** checkbox before confirming.
* **Record again**: explain what the participant should fix and request another recording.

**History** lets you inspect earlier call validations. Video items that have already been reviewed or archived are available for inspection when included in the video queue.


---

# 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/daily-operations/validations.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.