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

# Dashboard and activity

Use the **Dashboard** to understand appointment outcomes and the reward workload for the selected project. Closers see data within their permitted scope.

## Read the dashboard

1. Check the project name in the sidebar.
2. Open **Dashboard**.
3. Choose a **Period**: 7, 30, 90, 180, or 365 days.
4. Review bookings and attendance first, then rewards and recorded sales.

| Metric          | How to read it                                                                                                                |
| --------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Bookings        | Appointment records from the lookback start onward, including future bookings, rather than unique people.                     |
| Qualified shows | Appointments recorded as attended.                                                                                            |
| No-shows        | Appointments explicitly recorded as no-shows.                                                                                 |
| Show rate       | Attended appointments ÷ (attended appointments + no-shows). Scheduled and cancelled appointments are excluded from this rate. |
| Sales           | Attended appointments with a sold outcome.                                                                                    |
| Close rate      | Sales ÷ attended appointments.                                                                                                |
| Reward spending | The amount of rewards in approved or paid states. This includes approved rewards that have not yet been paid.                 |
| Revenue         | Recorded sale amounts on appointments; it is not a bank balance or a payment-provider reconciliation.                         |

For example, 8 attended calls and 2 no-shows produce an 80% show rate. If 3 of the attended calls resulted in a sale, the close rate is 37.5%. Future bookings do not reduce the show rate while attendance is still unknown.

The period sets the earliest appointment date included; future bookings are included too. Reward totals follow rewards associated with those appointments' leads and campaigns, rather than the date a reward was approved or paid. Do not use these totals as a payment-date statement. The bookings-versus-shows chart covers seven days. If a partial-data warning appears, choose a shorter period before using the figures to make decisions.

## Investigate an unexpected number

1. Check the reporting period and selected project.
2. Check your role: a closer's view can differ from a manager's view.
3. Open **Appointments** and confirm that attendance and sale outcomes were recorded.
4. Open **Rewards** to distinguish approved amounts from paid amounts.
5. Check the displayed time zone when comparing dates with another system.

## Follow an action in Activity

Open **Activity** to review recorded project actions. Search the history or filter by action type, such as attendance validation, reward approval, or payment recording. Each entry shows a time and actor type.

Use this alongside the lead's details when investigating a status change. If you need help, share the relevant project/campaign name, action time and displayed error with your project manager. Keep personal claim links and payment or identity details out of public messages.


---

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