Open Shift Offer is an operator job for the moment a shift has no one on it. It reads the open shift from your scheduling system, the employees eligible for it, the hours each has worked and scheduled this week, their availability and approved leave, and the credential the role needs. It then orders the candidates by the rule you set for the site: rotation, seniority, part-time first, overtime last.
The manager sees the ordered list with the reason for each position, the message text, and the wait between rounds, and approves or reorders it. Offers go out round by round through Deputy, Slack, Microsoft Teams, or Twilio SMS. The first acceptance is proposed as the assignment, written once, and the later rounds close.
This is a reference listing. It documents what Fibric would read from Open Shift Offer and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.
Inputs
Open shifts: When I Work OpenShifts, Deputy open shifts, 7shifts shifts with the open filter, Rippling unassigned shifts, Paylocity open shifts, Dayforce unfilled shifts
Who is eligible: When I Work /2/shifts/eligible, 7shifts roles and locations, Deputy employees by area, HRIS job and status from UKG Pro employment-details or Workday
Hours already scheduled and worked this week per candidate: Deputy rosters and timesheets, When I Work /2/times, 7shifts time punches
Availability, approved leave, and gaps between shifts: Dayforce Availability and TimeAwayFromWork, When I Work /2/requests, Deputy Leave
The offer rules you set per site: candidate order, how long each round waits, which channel each person is reached on
Acceptances and declines: When I Work swaps::taken and OpenShift approval requests, Deputy roster updates, Slack button and Microsoft Teams card answers, Twilio replies
Proposed actions
Target capability: propose the ordered candidate list for an open shift, showing why each person sits where they do: rule, hours, credential, availability
Target capability: propose the offer message and the round structure: who is asked first, how long before the next round, and the channel per person
Target capability: propose sending each round through Deputy shifts/offers:notify, Slack, Microsoft Teams, or Twilio SMS once the manager approves the sequence
Target capability: propose assigning the first accepted candidate through When I Work /2/shifts/{id}/assign, a Rippling shift assignment, or a Deputy roster update
Target capability: propose closing later rounds and telling declined candidates the shift is filled
Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.
What you can build
Offer a When I Work OpenShift in rounds
/2/shifts/eligible gives the pool. The operator orders it by your rotation rule and weekly hours from /2/times, the manager approves the sequence in Slack, and the first acceptance is proposed as /2/shifts/{id}/assign.
Employees in the area with an active TrainingRecord for the role are ordered by rostered hours. Each approved round goes out through shifts/offers:notify, and a roster update is proposed for whoever takes it.
Unassigned shifts are matched to workers by department and leave status. Candidates without Slack get the offer as a Twilio SMS with a reply keyword, and the acceptance becomes a proposed shift assignment.
Push overtime candidates to the last round in 7shifts
Users whose punches already pass your overtime threshold move to the final round. The manager sees each candidate's hours beside their position before approving the sequence.
A scheduling connector that exposes open or unassigned shifts and an assignment write: When I Work, Deputy, 7shifts, or Rippling
A source of hours worked this week: the same system's timesheets or punches, or QuickBooks Time
Slack, Microsoft Teams, or Twilio for the offers, and Slack or Microsoft Teams for the manager's approval
Per site and role: the candidate order rule, the round length, and the overtime threshold that moves a candidate to the last round
Authentication
No credentials are stored with the operator. Open shifts, hours, and credentials are read, and offers sent, through the connectors bound to it under the access you granted each one.
Limits
It orders candidates by the rules you give it. It does not decide them, and a union or contract order must be entered per site
Hours counted are what the systems hold; a shift worked but not yet punched is not seen until it is
A round nobody answers ends by time. The next round starts without a new approval only if the manager approved the whole sequence
Deputy shift offers may send SMS billed to your Deputy account, and Twilio messages are billed to yours; each round proposal says which applies
Access and pricing
Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.
The sequence: an ordered list of candidates with the reason for each position, the message text, the wait per round, and the channel per person. The manager can reorder, remove, or add names. Sending starts only after that approval.
What record is left?
The shift id, the candidate order and the rule behind it, each message with its channel and delivery status, every acceptance or decline with its time, the assignment written and the system's response, and the manager's approvals.
Does it assign the shift itself?
No. An acceptance becomes a proposal to assign, which the manager confirms unless they chose up front to assign the first acceptance. Either way the assignment is written once, and the later rounds are closed.
Ask about Open Shift Offer
Ask about the capabilities and requirements in this listing.
This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy