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

# Investigate risk signals

**Risk center** collects possible duplicates and other issues that may affect reward eligibility. A signal is a reason to investigate; examine the record before deciding what it means.

Project managers and administrators can resolve signals. Closers can inspect signals within the records they are allowed to access.

## Review an issue

1. Open **Risk center** and choose **Open**.
2. Read the signal type, severity and description.
3. Open the lead to compare the appointment, reward, identity and payout information relevant to the issue.
4. Choose the appropriate action.

| Action            | Effect                                                                                        |
| ----------------- | --------------------------------------------------------------------------------------------- |
| **Mark reviewed** | Records the signal as reviewed; it no longer counts as an open or confirmed approval blocker. |
| **Ignore**        | Dismisses a signal, for example after establishing it is a false positive.                    |
| **Confirm fraud** | Confirms the issue. Relevant medium/high signals continue to block approval and payment.      |

Resolving a signal recalculates the lead's risk and checks whether a reward can now advance automatically. Make the review decision only after assessing the evidence.

You can also review relevant signals in the reward's **Risk** checklist. This view offers **Ignore** and **Confirm fraud** and allows a note when confirming.

Confirming fraud does not automatically reject the reward. Review the reward decision separately and record a rejection reason where appropriate.

## Common signals

Examples include **Duplicate email**, **Duplicate phone**, **Duplicate payout account**, **Duplicate identity**, **Payout account holder mismatch**, **Previously paid reward**, **Short call duration**, and **Flagged as suspicious**.

For a short call, compare the recorded duration with the campaign's minimum. For a payout mismatch, compare the account holder with the verified participant information. For suspected duplicates, use the signal's description and related records to establish whether the claim belongs to the same person.

If another teammate has already resolved an issue, refresh the record before taking further action.


---

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