> 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/leads.md).

# Find a lead and share their portal

A lead is a person taking part in a campaign. Their record brings together appointments, rewards, identity verification, payout details and activity.

## Find the right person

1. Open **Leads** in the sidebar.
2. Search by name, email or phone. Use the status and risk filters to narrow the list.
3. Select the person's row to open their record.
4. Check the campaign and appointment details before taking action.

Project managers work with their project's records. Closers see records connected to their own appointments.

## Read the lead record

Use the record to answer these questions:

| Section                     | What to check                                                                                             |
| --------------------------- | --------------------------------------------------------------------------------------------------------- |
| Lead details                | Contact information, campaign, source and assigned closer.                                                |
| Rewards                     | Each campaign's reward amount, current state and available actions.                                       |
| Identity verification (KYC) | Whether the participant has submitted and verified their identity.                                        |
| Payout details              | The selected method and its verification state. Full payout details are available to authorized managers. |
| Appointments                | Scheduled calls, attendance, duration and outcome.                                                        |
| Fraud signals               | Issues that need investigation before approval.                                                           |
| Activity                    | Recorded actions and when they happened.                                                                  |

A lead may have several campaign rewards. Select the correct reward card instead of assuming the newest record is the one you need.

## Share the participant's link

On the relevant reward card, select **Copy claim link** and share it privately with that participant. This link opens their portal for that campaign, including pre-call tasks and reward progress.

The quick copy button in the Leads list appears when the lead has one reward. If it is missing, open the lead and copy the link from the appropriate reward card.

Copying a link does not make a reward eligible. The participant can submit a claim once the reward reaches **Awaiting lead** and the campaign allows claims.


---

# 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/leads.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.