> ## Documentation Index
> Fetch the complete documentation index at: https://docs.recepai.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Request Settings

> Your request types, who handles them, how fast, and who gets told.

**Request Settings** is what makes [Active Requests](/front-desk/requests/active) work like your hotel rather than a generic board. It decides what a guest can ask for, who it goes to, how long it should take, and who hears about it.

***

## What is on the screen

Four sections.

### Request types

One per kind of request your hotel handles. Each carries:

* **Color on the board**
* **Handled by** — the department or person it belongs to
* **Pick up within** and **Complete within** — your targets
* **If missed, alert** — who hears when a target passes
* **Notify** and **Notified by** — who is told about a new one, over which channel, and **Set hours** or **Any time**

A type can also carry a **briefing** — instructions your AI staff read when a guest asks for that thing.

### Team members

Who is on your team, what they **handle**, and how they are reached.

### Preferences

Hotel-wide switches, including **Auto-archive completed requests**, the **Desk bell**, **Phone verification before requests**, and the **team language for guest requests**.

### Live Board

The read-only board for a back-office screen.

***

## What you do here

<Steps>
  <Step title="Create your request types first">
    The team assignments, the alerts and the targets all hang off a type, so those parts wait for it. The Live Board and the hotel-wide preferences do not — they work on their own.
  </Step>

  <Step title="Write the briefing for the types that need one">
    This is what your AI staff read when a guest asks. "Towels are on the housekeeping trolley, we do not deliver after 23:00" is the difference between a useful answer and a generic one.
  </Step>

  <Step title="Set targets you would defend">
    **Pick up within** and **Complete within** are what [Analytics](/front-desk/requests/analytics) measures against. A type with no target is reported as not measured, which is honest but tells you nothing.
  </Step>

  <Step title="Name a person for the missed-target alert">
    Without one, a target that passes is recorded and nobody is told.
  </Step>

  <Step title="Set alert hours if your team is not on all night">
    **Any time** means exactly that.
  </Step>
</Steps>

<Warning>
  **A channel needs a way to reach the person.** An email alert with no email address on the team member does not arrive — the screen says so where it can, but the setting and the contact details are two separate things to fill in.
</Warning>

***

## What happens next

A new type is available immediately: your team can file a request under it, and the type shows on the board with the colour you gave it. Targets start being measured from the next request filed under it. **Phone verification before requests** changes what a guest must do before your AI staff will file one for them — the screen explains what it changes before you turn it on.