Schedules
Hotpot's on-call schedules.
Last updated
Hotpot documentation
Hotpot's on-call schedules.
Last updated
A schedule is for a group of people who are on-call for the same thing.
Here's a high-level graphic explaining how Hotpot's schedule settings interact.
Today, a Hotpot team can have a single schedule. If your team has different needs, let us know!
Creating a schedule is an optional part of creating a team. If you haven't already, see the docs for creating a team!
After creating a team, you will automatically be asked about creating a schedule. Yay! Let's talk about the settings you can adjust when building your schedule.
Hey you! Hotpot is built with reasonable, healthy defaults but has a really powerful scheduler backend. Our goal is to keep the UI simple and approachable. Setting up on-call shouldn't be like trying to operate a nuclear reactor or something. Let us know if something is missing here to craft your ideal setup!
Name
The name of the schedule.
Not very useful today, but later can be used to differentiate multiple schedules within the same team.
Description
Some text to help folks know what this schedule is for.
Fill this in with the scope of the schedule. What is this schedule responsible for?
Backstop
This is really important!
Prepare lead time
Stint maintain count
The number of stints into the future that Hotpot will maintain.
Hotpot recommends keeping this at the default. More limits flexibility and less limits predictability.
Stint type
The approach Hotpot should use in allocating segments of a stint.
See Stint type below.
How long do you want each person to default to being on-call?
Stint start weekday
On what day do you switch who is on-call?
Handoff time
At what time do you switch who is on-call?
Auto escalate
Determines if pages for this schedule will automatically escalate.
You probably want this!
Create moments from Pages
Time to escalate
How long Hotpot should wait before escalating to the next stage in the schedule.
Require coverage assignment acknowledgement
Page repeat interval
If we reach the last person in an escalation path, how often should Hotpot bug that person… infinitely? :)
Hotpot does not repeatedly page someone unless it has no other option.
Terminal behavior
What should Hotpot do when it reaches the end of an escalation?
Stint types are currently in beta. Contact us to give them a spin!
Hotpot's default behavior is to treat an on-call stint as 7 days. Some on-call situations require different approaches, however. To support this, Hotpot allows the following types of stint:
One-day, where a new person is assigned every 24 hours.
Two-day, where a new person is assigned every 48 hours. The stint length must be even in this case.
4/3, where a new person is assigned on Friday. This allows for weekday/weekend splits
7 day, the default and fan favorite!
Hotpot supports primaries, secondaries, and more. Learn more about Multistage schedules.
Your next step is choosing which users will be a part of your schedule. Hotpot calls a collection of users a pool, treating them as a source to draw the next person. To add someone, click the plus sign next to their name, which adds the user to the pool.
To ensure users can be contacted, Hotpot verifies that they have all the appropriate settings and attributes to be successful in an on-call rotation. If a user is not present, Hotpot will provide a reason. An example is someone who hasn't entered a phone number when the schedule requires one.
Set the user who will act as the for this schedule.
The lead time before the end of a stint at which an on-call person will be asked to prepare for .
length
Hotpot may choose shorter on-call durations in a given if needed to fulfill the schedule.
Whenever a page is handled Hotpot will create a for you to triage later.
If enabled, Hotpot will require acknowledgement before is considered accepted.
