> For the complete documentation index, see [llms.txt](https://docs.expel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expel.io/workbench-reference/dashboards/service-review-dashboard.md).

# Service Review Dashboard

The Service Review dashboard shows a full picture of how your organization and Expel are working together to keep your environment secure. Access it by going to **Dashboards > Service Review**.

<figure><img src="/files/xTd0OlfAve1NMYpAJwq7" alt="Image of the Service Review Dashboard."><figcaption></figcaption></figure>

<details>

<summary>How are we working together?</summary>

On the left, this area shows you the median time from alert arrival in Workbench to the first remediation action completed, for incidents that require verification with your organization. You can see how responsive your organization is when we send you an alert.

On the right, this area shows you the median time from alert arrival in Workbench to the first remediation action completed, for incidents that don't require verification with your organization. You can see how responsive Expel is after an alert happens that we can fix without notifying your organization first.

<figure><img src="/files/RD4P4JLu99e6lVUWvOpb" alt="Image showing the how are we working together section at the top of the page."><figcaption></figcaption></figure>

Under this area, 3 panels show more details.

<figure><img src="/files/htGpq6nlvwI9iggVzd4L" alt="Image showing the three panels, which look like boxes."><figcaption></figcaption></figure>

In the area on the left in our example screen, you can see our actual triage times for alerts.

In the middle area, you see the median time it takes for your organization to verify after Expel assigns a verify action to your organization. In our example, it takes the organization a median of about 4.5 hours to respond. This can be an area the organization wants to improve over time because it reflects how quickly the organization responds to a security question.

In the right area, you see the median time it takes for your organization to complete a remediation action after Expel assigns a remediation action to your organization. In our example, it takes the organization about 2 minutes to remediate. This number varies with each organization and can help you track your internal progress. This can be an area the organization wants to improve over time.

</details>

<details>

<summary>How we think about verify actions</summary>

In the next area, click the text to see information about how your organization can improve these metrics.

<figure><img src="/files/zfXtNOPf3UiD63p2vsx0" alt="Image showing the verify actions information area."><figcaption></figcaption></figure>

</details>

<details>

<summary>Automations and context</summary>

This area shows you how your automations and context are performing over the specified time period.

<div align="left"><figure><img src="/files/TN8kCpqU1H7OCxKzwTxf" alt="Image showing automations and context, with percentages and an explanation for each."><figcaption></figcaption></figure></div>

</details>

<details>

<summary>Alert count by time of day</summary>

This area shows you a heat map of alerts for your organization over the times of the day and days of the week. This information can help your organization staff the times when alerts are more common.

<figure><img src="/files/gpvoVz2jopgatCDQGg6J" alt="Image showing alert count by time of day in a chart format."><figcaption></figcaption></figure>

</details>

<details>

<summary>What has Expel been up to?</summary>

The panel on the left shows you the detections that were added or updated for the specified time period.

<div align="left"><figure><img src="/files/Ju2Wl5TWFIAsLq0cmMal" alt="Image showing the What has Expel been up to box."><figcaption></figcaption></figure></div>

</details>


---

# 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.expel.io/workbench-reference/dashboards/service-review-dashboard.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.
