> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/bettor-sense/bettor-sense-user-interface.md).

# Bettor Sense - User Interface

The Bettor Sense User Interface is designed to give operators a powerful, intuitive, and explainable view into player risk and responsible gaming behavior. It enables data-driven decision-making through a combination of high-level insights and detailed player-level analysis.

## UI structure

{% stepper %}
{% step %}

### Accounts page

* Offers a comprehensive view of the player base.
* Includes both high-level bookmaker insights and a detailed player listing.
* Supports filtering, sorting, and drill-down into individual player profiles.
  {% endstep %}

{% step %}

### Player details view

* Accessed by clicking on a player in the listing.
* Provides a deep dive into the player’s risk score, behavioral patterns, responsible gaming activity, and more.
* Includes explainable AI components such as risk score breakdowns and intervention suggestions.
  {% endstep %}
  {% endstepper %}

## Key use cases

* Monitor player risk trends across the entire customer base.
* Identify high-risk individuals and understand what’s driving their behavior.
* Support responsible gaming teams with explainable insights.
* Track RG tool usage and self-exclusion trends over time.
* Coordinate player reviews across the RG team with Player Status.
* Track borderline-risk players that need recurring review cycles.

The UI supports both operational workflows (e.g., daily monitoring, player reviews) and strategic analysis (e.g., trend reporting, compliance reviews).

{% hint style="info" %}
All data is grouped by day and displayed in **UTC** to ensure consistency across time zones.
{% endhint %}

## Player Status

Player Status is analyst-assigned operational metadata used to support RG review workflows.

Available statuses:

* **(none)** — no status is set.
* **Cleared** — the player was reviewed and no current action is needed.
* **Needs Review** — the player should be reviewed by the RG team.
* **RG Intervention** — the player had a manual RG intervention.

Player Status appears in the **Accounts** listing and in **Basic Info** on the **Account details** page.

It can only be changed in **Basic Info** on the **Account details** page.

Each status includes a timestamp showing when it was last set.

Player Status does not affect the AI model or the player's Risk score.


---

# 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.sportradar.com/bettor-sense/bettor-sense-user-interface.md?ask=<question>&goal=<endgoal>
```

`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.