About us
SetShifts — shift scheduling for businesses that run on shifts
SetShifts runs a team that works in shifts — one location or a chain of twenty. It builds the roster, takes attendance from phones and from a clock at the door, handles leave requests, and produces an hours report ready for payroll at month end.
The problem it started from
Building next week's schedule is work that repeats every week and is never the same twice. Requests arrive by message and in passing, some get forgotten, and whoever builds the schedule holds it all in their head: who asked for what, who can't work with whom, who is short on hours and who is already over their limit.
The result is familiar to anyone who has done it: an evening lost to a spreadsheet, and a phone call on Sunday morning because someone didn't show up.
What we do differently
One principle drives the product: every assignment explains itself.
A system that produces a schedule in one click but can't tell you why it chose the people it chose is a system the manager won't trust — and they'll be back in the spreadsheet by week two. So every shift here can say who is on it, why that person, and what would have happened with someone else. And when a shift can't be filled, it says so plainly, instead of leaving an empty cell for someone to discover later.
Three things follow from that principle:
- Staff enter their own constraints. Not in a chat and not on a note — on their own screen, within a limit the manager sets. What was entered is counted; what wasn't entered can't be claimed after the fact.
- The manager stays in charge. Drag a shift from one person to another, park it aside, override the system by hand. The automation proposes; the decision stays with the person who knows the team.
- Published means published. Once the schedule is out, changing it takes a double confirmation. Someone who has already planned their week around a shift shouldn't find out it vanished without being told.
Who it fits
Any business that puts people on shifts and has more than a handful of staff: cafés and restaurants, retail chains, security firms, clinics and call centres, hotels, factories. Especially a multi-location chain, where one person may work across several sites and nobody holds the whole picture in their head.
Who it fits less well: a business where the same three people work the same hours every week. A note on the fridge does that job well.
What we commit to
- A person answers, within a time we state up front. A failure that blocks work — 4 hours during business hours. A question or a feature request — 48 hours. Not a bot, and not "we'll get back to you soon" with no number attached.
- Everyone sees only their own. Staff see their shifts and their requests — not pay, not notes, and not their colleagues' constraints. That is enforced in the database itself, not in code running in the browser.
- One company never sees another. Not by accident, and not through a direct request to the server that bypasses the screen.
- Your data is yours. Export it whenever you want, cancel whenever you want. No annual contract, no exit fee.
- Hebrew is a first language here, not a translation. The product was built right-to-left from day one, and ships in eight languages — including Arabic and Russian, which many staff read more comfortably.
Where we are today
The product is new and we are early. What that means for you in practice: you talk to us directly, a request you make is actually heard, and a version adapted to your industry is a conversation rather than a ticket in a queue. That is an advantage that only exists at the beginning, and it's worth using.
Talking to us
Through the contact page, or straight to support@setshifts.com
SetShifts is operated by פ.ט אינטק סחר בעמ (company number 516058989), בר כוכבא 14 בני ברק.