Critical Alerts

Claim an open incident so escalation stops, pause its repeat calls, and close it when the problem is fixed.

Set up who an alert reaches and how, from a phone call, text, email or push notification to a person, team, branch or on-call schedule.

Create a source, copy its one-time signal address, point a device or outside system at it, and send a test signal to prove the path works.

Make an alert reach a second and third person when nobody acknowledges it, or when the first phone call fails.

Open one signal to see exactly what the device sent, which rules Nova checked it against and which match field failed, then fix the rule.

Save a starting pattern that prefills the source, destination, template, rule and test signal, so the guided setup builds the same kind of alert every time.

Tie a source to a matcher, severity, template and destinations, and choose how the incident behaves when signals repeat or someone acknowledges it.

Walk the six numbered steps of the guided setup to pick a recipe, source, recipient, template and rule, then fire a test signal.

Say who is on call, on which days and hours, with an optional backup for after-hours, so a destination can reach whoever is covering right now.

Stop a maintenance mute early, switch a window off and on, copy it for next time, or archive it while keeping its history.

Create a suppression window so planned maintenance on a site or system does not call anyone, and preview exactly which rules and incidents it affects.

Open a rule, source, destination, schedule, template, recipe or suppression window by its own link, change it, place a test call, or make an earlier version live.

Understand why a new rule, destination, template or schedule does nothing until you press Publish, and how to make an earlier live version current again.

Find calls, texts, emails and webhooks that failed to deliver, read the provider's error, and send them again.

See who changed which rule, source, destination or window and when, and download the whole history as a spreadsheet file.

See every signal that reached a source, check whether a rule matched it, and run it through the rules again after you fix a rule.

See how many incidents sit in each status and which sources fire most over the last 7 days.

Issue a new signal address for a source, keep the old one alive for a grace period while you switch the outside system over, then revoke it.

Push due escalation steps, retries, heartbeat checks and recoveries through right now instead of waiting for the next scheduled pass.

Understand how sources, rules, destinations and incidents fit together, then build your first alert with the guided setup.

Open one incident to see what the rule will do next, who was called and what they heard, run a response checklist, and acknowledge or resolve it.

Write the exact words a phone call speaks or a text, email or webhook sends, with placeholders for the incident's title and summary.