Skip to main content
An escalation policy is the ordered list of who Tallwatch pages when a monitor opens an , and how long it waits before pulling in the next group. Without a policy, the monitor stays silent. With one, you control order and timing.

​
How it works

A policy is ordered notify steps. Step 1 fires when the incident opens. Later steps wait a number of minutes and only run if nobody has acknowledged yet. Acknowledging stops later steps. Each step can hold several alerts. For each alert you pick:
  • Alert via — a
  • to — Channel recipients (everyone on that channel), or an
When to is an on-call schedule, Tallwatch pages whoever is on call through that schedule’s member channels. You cannot pick the same channel+recipients pair, or the same schedule, twice in one step. A typical setup: step 1 pages team chat immediately; step 2 pages the on-call schedule after 15 minutes if the incident is still open. Attach monitors on the policy form when you create or edit it. A monitor with no policy stays silent.
A policy attached to a monitor cannot be deleted until you move those monitors off it.

​
Create a policy

1

Add a policy

Open and name it.
2

Set notify steps

Step 1 should notify as soon as the outage starts (for example team chat). Add another step if you want a later page—common waits are 5, 15, or 30 minutes—and only if nobody has acknowledged yet. Use New alert inside a step to page more than one channel or schedule at that wait.
3

Attach monitors

Pick the monitors that should use this policy. You can change the list later on the same edit form.
4

Save

Save the policy. Attached monitors page through these steps on the next open incident.