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

# Sensitivity and routing

> Decide which Slack channel each alert goes to and how much each channel should hear.

## Routing

Ordyn posts alerts only to channels you turn on. For each channel, write a plain-language description of what belongs there, for example "customer-facing payment failures" or "background job health". Ordyn routes each alert to the channel whose description fits best.

Manage channels on the **Triage** page. You can create a new Slack channel from there, which is the easiest way to run [shadow mode](/shadow-mode).

## Sensitivity

Each channel has one sensitivity level. It sets what posts on a problem's first occurrence.

| Level | Never posts | Ordyn decides | Always posts |
| - | - | - | - |
| **Everything** | Nothing | Ungraded alerts | Every grade |
| **Chatty** | Nothing | Low | Medium and above |
| **Balanced** (default) | Low | Ungraded alerts | Medium and above |
| **Quiet** | Low | Medium | High and Critical |
| **Critical only** | Low and Medium | High | Critical |

Critical always posts, at every level. Repeats of a known problem follow a stricter rule than first occurrences: they re-post only when the problem is materially different, has gotten worse, or a recorded fix did not hold.

## Try before you commit

The sensitivity tuner replays the last 30 days of alerts routed to a channel at any level, so you can see how the channel would have looked before you change it. Open it from the channel's settings on the **Triage** page.

## Duplicates

Turn on **Suppress replies to duplicates** to have Ordyn skip replying when a new alert is a repeat of one it already answered in the same channel.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.