Shift swaps at a supermarket chain used to die in manager phone tag. We built a WhatsApp flow that checks every swap against skill, hours and cost rules, then hands managers a one-tap approval — settled in seven minutes.
Typical results
350
Swaps handled monthly
0
Roster-payroll mismatches
88%
Fewer uncovered shifts
Figures reflect typical results for this kind of automation.
The challenge
Across 40 branches and 900 employees, swap requests bounced through calls, sticky notes and group chats. Approval took up to two days, so around 25 shifts a month went uncovered when answers came too late. Approved swaps often never reached payroll, producing some 30 roster-payroll mismatches — and disputes — every month.
Before and after
Swap turnaround
−99%Uncovered shifts per month
−88%Roster-payroll mismatches per month
−100%The automation
We built a WhatsApp bot on Make that takes swap requests in a 30-second chat. The scenario validates each request against the live roster — matching skills and certifications, weekly hour limits and overtime cost — and rejects impossible swaps instantly with a reason. Valid ones reach the branch manager as a one-tap approve or decline with full context. On approval, both employees get confirmation and the roster and payroll update themselves.
How it works
- 01
Request in chat
An employee messages the WhatsApp bot with the shift they want to swap and the colleague taking it.
- 02
Rules checked
The scenario validates skills and certifications, weekly hour limits and overtime cost before anything reaches a manager.
- 03
One-tap approval
A valid swap lands with the branch manager as an approve-or-decline button with full context attached.
- 04
Roster updates
Both employees get instant confirmation and the roster changes across every connected system.
- 05
Payroll follows
The swap flows straight to payroll, so each worker is paid for the shift actually worked.
Starts from
- WhatsApp swap requests
- Live roster
Delivers
- One-tap manager approval
- Roster update
- Payroll sync
The impact
Median swap turnaround fell from two days to seven minutes, and the chain now settles about 350 swaps a month without a single phone call. Uncovered shifts dropped from 25 a month to 3, and roster-payroll mismatches disappeared completely — taking the pay disputes with them.
Questions about this automation
How does an employee request a shift swap?
The employee messages the WhatsApp bot with the shift they want to give up and the colleague taking it. The bot asks only for missing details, so a request usually takes about 30 seconds. Both employees get a confirmation, or a clear reason when the swap cannot go ahead.
What rules are checked before a manager sees the request?
The automation checks the live roster for matching skills and certifications, weekly hour limits and any overtime cost the swap would create. Requests that break a rule are declined instantly with the reason. Only valid swaps reach the branch manager, as an approve or decline button with the details attached.
How do approved swaps reach the roster and payroll?
On approval, the roster updates in every connected system and the change is sent to payroll, so each employee is paid for the shift they actually worked. Declined requests leave the roster untouched. A multi-step build like this is usually rolled out in stages, starting with the WhatsApp request flow.