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

# Escalations

> Give hard calls a second pair of eyes without losing them

## The problem

Some decisions shouldn't be made alone: a permanent ban, a legal threat, a borderline
call a moderator has flip-flopped on twice. Without somewhere to put them, they get
guessed at, or parked in a spreadsheet and forgotten.

You also can't just hand the item to a lead by resolving it — resolving is how the
first moderator says *I'm done*, and in most views that clears the item everywhere.

## The view

<Steps>
  <Step title="Add an escalate action">
    Create an [action](/actions/content-actions) called **Escalate**. Moderators run
    it from the item detail, or with <kbd>Cmd</kbd> + a number key.
  </Step>

  <Step title="Filter on it">
    In the new view, filter **Action taken → Escalate**.
  </Step>

  <Step title="Keep its own list">
    In **Settings**, set **Items leave this view when → Resolved here only**.
  </Step>
</Steps>

## Why the resolve setting matters

*Resolved here only* is what makes this a real handover. The first moderator resolves
the item in their own view and moves on; it stays pending for the lead, who resolves
it again here once they've decided. Two people, two decisions, one item.

Left on *Resolved anywhere*, the first moderator's resolve would clear the item out of
the escalation view before anyone looked at it.

<Tip>
  The same shape works for user reports and appeals — one action, one view, resolved
  independently. Only the name of the action changes.
</Tip>