Docs Make Relia yours
On-call and escalation
Set who is on call, hand over every day or week, escalate to the next person when nobody responds, and page through PagerDuty.
When something needs a fix, on-call makes sure one person on your team is told directly, and that someone else is told if that person doesn't respond.
Before you start
- On-call comes with Growth and Pro. On Free, the card says to upgrade to Growth.
- Escalation (telling the next person) needs Pro. On Growth, only the person on call is paged.
- You need to be an owner or admin to change on-call. Everyone in the rotation must be a member of the project. See Invite your team.
Steps
- Click Settings at the bottom of the sidebar, then the Notifications tab.
- Click More options. Find the card Who is on call.
- Under Rotation (in order), add the people who handle problems, in the order they take turns. Use the arrows to move people up or down.
- Optional: with Slack connected, type each person's Slack member ID (it starts with
UorW). That person is then @mentioned in the alert in your Slack channel, so their phone buzzes. - Under Hand over, choose every week or every day, and the hour. Times are in the timezone shown next to the hour. By default the rotation hands over every week, on Monday, at 09:00.
- Under Tell the next person after, choose how long to wait for someone to press "I'm on it" (5, 10, 15, 30 or 60 minutes; default 15), and how many people in total (1 to 3; default 3). This is the Pro escalation.
- Optional, PagerDuty: paste an Events API v2 integration key and click Connect. PagerDuty then phones and texts the person on call.
- Click Save on-call.
Tip: watch Choose how Relia reaches you: email, Slack, ClickUp and Jira alerts (2 min) to connect Slack first.
Covers (holidays and sick days)
Someone away? Add a cover: pick Who covers… and the dates from and to. During a cover, that person is on call first. Click Save on-call to keep it. Finished covers are removed when you save.
What happens when something needs a fix
- Relia sends its alert to your channels. The person on call is told directly by email, @mentioned in Slack if you added their member ID, and paged through PagerDuty if connected.
- On the incident page, a box shows who is on call. When they click I'm on it (on the incident page or the Slack button), paging stops and PagerDuty marks the incident acknowledged.
- On Pro, if nobody clicks I'm on it in time, Relia tells the next person in the rotation, up to the number you chose.
- When the problem is gone, Relia resolves the PagerDuty incident.
Only problems that need a fix page anyone. Things worth watching never do. A problem already covered by an uptime alert isn't paged twice.
Note: "I'm on it" is for owners, admins and members. Viewers can't acknowledge.
Check it worked
- The card shows On call now: with a name, when the shift ends, and who comes next.
- Click Send a test page. The person on call gets a test by email (and a Slack mention if set). With PagerDuty, Relia opens and closes a test incident, and the card says "PagerDuty test incident opened and closed."
If something's wrong
- "PagerDuty refused the key.": use an Events API v2 integration key from the PagerDuty service, not a REST API key.
- "Slack refused the message.": check Slack is connected on the same tab and the Relia app is in the channel.
- Save on-call is greyed out: a Slack member ID isn't in the right format. It looks like
U012AB3CD. - Nobody is paged: make sure the card's switch is on and at least one person is in the rotation.
Next
Last checked against the product: 1 Nov 2026