On-call rotation and text alerts: the basics for small teams
An on-call rotation decides who handles alarms outside normal hours, usually one person per week. Text alerts make the rotation real: the night alarm reaches the phone of whoever is on duty. Welco does this with time windows, so each shift's alerts go to the right phone.
7-day free trial, 15 message creditsCard required for verificationNo charge for 7 daysEmail reminder before billing
Published:
The problem
Nobody is sure who is on call
- Night alarms go to the whole team
- Everyone assumes someone else has it
- The handoff lives in someone's head
The fix
One owner for every hour
- A written rotation for the month
- Night alerts reach the night phone
- A test text at every handoff
- A rotation is a written list of who is on call, for which hours.
- Weekly turns are the easiest pattern for teams of three to eight people.
- Welco sends alerts by time of day and weekday. Your rotation itself lives on paper or in a calendar.
- Send a test alert at every handoff so the new person knows it works.
What an on-call rotation is
Being on call means you are the person who responds if something breaks outside normal hours. A rotation shares that duty fairly, so one person doesn't carry it every night.
The rotation is just a list: names, dates and hours. It answers one question at 2 AM: whose phone should ring? The other SMS alert guides cover what that phone should receive.
Common rotation patterns
- Weekly: one person covers nights and the weekend for a full week, then hands off. Simple and the most common.
- Weeknights and weekends split: one person takes Monday to Thursday nights, another takes Friday to Sunday.
- Primary and backup: two people each week. The backup steps in if the primary can't respond.
What makes a rotation feel fair
- Turns are the same length for everyone, and the list is posted where the whole team can see it.
- Swaps are allowed, but they are written down before the shift starts.
- Holidays rotate too, so the same person doesn't cover every long weekend.
- The person coming off duty gets a quiet day after a rough night, when the work allows it.
Why small teams struggle with it
Large IT teams buy on-call software to manage this. Small plant, facility and IT teams often have a shared cell phone that gets passed around, or nothing written down at all. Alarms then go to everyone, or to someone who is on vacation.
How Welco fits an on-call rotation
Welco has no rotation or schedule screen, and it doesn't page a second person if the first one stays silent. It sends each alert to the phones you set for that time of day and day of week.
So your rotation lives where it already does, on a sheet or a calendar. Welco's on-call and after-hours routing carries it out: daytime alerts to the day team, night and weekend alerts to the person on duty.
That makes a weekly handover one small change. You update who is on the night route, then send a test alarm.
Two ways to handle the weekly handoff
- A shared on-call phone. The number in Welco never changes. Whoever is on duty carries the phone that week.
- Personal phones. At each handoff, point the after-hours window at the new person, who has already joined with their own phone.
Set up on-call text alerts in 6 steps
Plan it on paper first. The settings take minutes once the plan is clear.
Choose your shift windows
Most teams use three: weekdays during work hours, weeknights, and weekends. Write the exact start and end times, such as 5 PM to 7 AM.
Write the rotation down
Put names against weeks for the next two months. The on-call contact sheet template gives you a ready layout.
Decide shared phone or personal phones
A shared phone means fewer changes in Welco. Personal phones mean nothing to pass around, but someone updates the setting each week.
Invite everyone on the rotation
Email an invite to each person on the rotation, or to whoever holds the shared phone. They join with that phone and reply YES before any alert reaches them. Use a mobile, because a landline can't receive alert texts.
Set the time windows in Welco
Send the daytime window to the day team and the night and weekend windows to the on-call phone. Put a backup person on the same window if you want two people to see each alarm.
Test at every handoff
When the duty changes, trigger one test alarm from the real system. The incoming person sees it arrive and knows the path works.
Send night alarms to the night phone
Set your shift windows once. Welco follows them every day.
7-day free trial, 15 message creditsCard required for verificationNo charge for 7 daysEmail reminder before billing
An after-hours alert on the duty phone
A server room UPS loses mains power late on a weeknight. Only the on-call phone gets the text. The day team sees it in email next morning.
Alert email from powerchute@it.example.com, subject “PowerChute: UPS On Battery”. Welco trims it to one text of 87 characters: “Welco: [Server Rm UPS] On battery, 22 min runtime at 10:48 PM. Reply STOP to opt out.”
Text received: Welco: [Server Rm UPS] On battery, 22 min runtime at 10:48 PM. Reply STOP to opt out.
Characters219871 credit
The rule here is simple: weeknights from 5 PM to 7 AM, power alarms go to the on-call phone only. Our best practices for alert texts explain how to pick which alarms qualify.
How long should an on-call shift be?
For a small team that gets a few night alarms a week, one week per person is the usual turn. If the phone rings most nights, shorter turns are kinder and safer.
Google's workbook chapter on on-call (read October 6, 2026) recommends shifts of 12 hours or less when a rotation gets pages every day. It also suggests shorter turns, such as 3 days on and 4 days off.
The same chapter describes a split week, for example Monday to Thursday and Friday to Sunday. That pattern suits teams of two or three, where a full week alone is too much.
How many alarms can one on-call person handle?
Fewer than most teams send. Google's Site Reliability Engineering chapter on being on call (read October 6, 2026) sets a ceiling of two incidents per 12-hour shift. Its reason is that each incident takes about six hours to fix and follow up.
Google counts an incident as every alert from one root cause. So a storm should reach the phone as one clear story, not 40 texts. Our guide on how to prevent alarm floods shows how.
The chapter also notes that a team running a primary and a secondary around the clock at one site needs at least eight people. Most small teams have far fewer, so keep night texts for alarms that truly need a person.
Can the on-call person reply to or acknowledge an alert?
They can reply, but the reply isn't an acknowledgement. A reply to a Welco text goes back as an email to the sender that last texted that phone. Nothing is marked as handled in your alarm system.
Welco also has no escalation chain. If the on-call person doesn't respond, the text isn't passed to the next person after a delay.
If timed escalation and acknowledgements are a must, a full on-call tool fits better. Our PagerDuty alternative page explains where those tools win, and the Opsgenie comparison helps teams moving off Opsgenie.
How to run a clean weekly handover
A good handover takes ten minutes and ends with a test. The same workbook chapter has the outgoing engineer email a short handoff note at the end of each shift. Small teams can copy the habit.
- Write three lines for the incoming person: open problems, alarms that flapped, and planned work.
- Update the night and weekend route to the incoming person's phone, or hand over the shared phone.
- Trigger one test alarm from the real system and check that it reached the new phone.
- Mark the swap on your shared on-call contact sheet, so the whole team knows who has it.
On-call mistakes to avoid
Small teams make the same few slips. Each one shows up at the worst possible hour.
- Keeping the rotation in one person's head. When they are sick, nobody knows who has the phone.
- Changing the night route without a test. A wrong time window only shows itself at 2 AM.
- Leaving someone who changed jobs on the night route. Take them off the day they leave.
- Sending every daytime alarm to the duty phone too. It becomes noise before the night even starts.
- Treating a reply as proof the alarm is handled. Check the alarm system itself before you stand down.
On-call readiness checklist
Check these before each new rotation starts.
0 of 7 done
Frequently asked questions
Does Welco build the on-call rotation for me?
What if the on-call person doesn't respond to a text?
Should the on-call person also get daytime alarms?
Is a shared on-call cell phone a good idea?
Who makes a good backup on call?
Do people on the rotation need to install an app?
How should an on-call rotation cover public holidays?
Reviewed by Rakesh Patel, Founder, Welco
Make your next handoff a non-event
Set your shift windows and test one alarm today.
7-day free trial, 15 message creditsCard required for verificationNo charge for 7 daysEmail reminder before billing