Calculate on-call pay

We believe everyone should be paid for being on-call, and that the fairest way is to pay for the inconvenience. Practically speaking, that means paying an hourly rate for the time someone spends on call.

That's what we do at incident.io and we know that the calculations can get pretty complex. So we figured: what if a product could 'just do it', and you could shelve that dodgy spreadsheet or CLI script once and for all.

Introducing: the on-call calculator

You can use the calculator to generate reports based on your on-call pay configuration, using the schedule data from inside PagerDuty. The calculator supports weekly rules (e.g. extra pay outside working hours, or on the weekends) as well as holiday rules (think double-pay for Christmas).

Even better, your responders can also see a breakdown of what they’re being paid for each shift, making it super transparent for everyone.

If you're interested, you can try it out here.

n.b. If you're interested in on-call pay in general, we've just published the results of our on-call survey.

New workflow triggers

We've create three new workflow triggers, to help you build more flexible automations:

1. When an incident's severity changes
2. When an incident's status changes
3. When a custom field value for an incident changes

This lets workflows handle cases like "every time the severity becomes critical", or "every time the list of impacted products changes".

For example, this workflow would text me every time the incident severity increases to a value of Major or Critical. It would not text me if the severity decreased (e.g. from Critical to Major).

What else we shipped

• 🆕 You can now clone a workflow so you don't have to start from scratch every time
• 💅 You can now use variables in the subject-line of emails (not just the body)
• 🐛 You can now select labels when exporting follow-ups to GitHub
• 🐛 We removed some erroneous full stops in our PagerDuty messages
• 🐛 We now support organizations whose Zoom integrations require numeric-only passwords
• 🐛 We fixed a bug where users without Slack display names wouldn't show up on announcement posts
• 👷 We've done some work to make our API faster (and the web UI along with it)