> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/organization-and-workflows/recording-triage.md).

# Triage rules

Move new customer recordings into the right folder automatically.

Available on Pro and Enterprise.

Triage rules move each new customer recording into a **Customers** folder, based on where it came from, the customer's email or their country. Admins and editors manage them in **Settings → Triage rules**.

{% embed url="<https://app.screendesk.io/recordings/81361ca9-0da1-4f87-bb00-025913e69c01>" %}

<figure><img src="https://3820804400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfW6XSzJSKsNyZnOkSJPt%2Fuploads%2FypzbHskNCbyaGc6GRctN%2Fdocs-panel-triage.png?alt=media" alt="Settings, Triage rules"><figcaption></figcaption></figure>

## How rules run

When a customer recording arrives, Screendesk checks the rules from the top of the list. The first rule whose conditions all match moves the recording to its folder, and the rest are skipped. A recording that matches nothing stays in **Customers**.

* Rules only check new recordings. Existing recordings aren't re-sorted when you add or change a rule.
* A recording that already arrives in a folder, for example from an integration, stays there.
* Only Customers folders can be targets. Create the folder first, from the folder switcher in **Customers**.

## Add a rule

1. Select **Add rule**.
2. Under **Start from**, pick **Blank** or a template. Templates fill in the conditions for common cases: one helpdesk as the source (shown once that integration is connected), EU, US or APAC customers, missing email, or has an email.
3. Give the rule a **Name**.
4. Under **When a new customer recording**, add conditions. Each is a field (**Source**, **Customer email** or **Country**), an operator and a value. All conditions must match. For "either" logic, make two rules that move to the same folder.
5. Under **Move it to**, pick the folder, then select **Create rule**.

Countries can be written as names (Germany) or two-letter codes (DE).

## Manage rules

* Drag a rule to change its place in the order.
* The **On** switch pauses or resumes a rule.
* **Last match** shows when the rule last moved a recording. Select it to see those recordings in History.
* Archiving or deleting a folder deletes the rules that move recordings into it.

## History

The **History** tab lists the last 30 days of new customer recordings and what happened to each: the rule it matched and the folder it went to, no match, or an error. Filter by **Outcome** or **Rule**, and open a row to see each rule's conditions checked one by one.


---

# 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://docs.screendesk.io/organization-and-workflows/recording-triage.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.
