Agency Request is an operator job for the shift nobody picked up. It reads open shifts from your scheduling system, the offers already made to internal staff and their outcomes, and the offer window you set per site and role. When the window closes with the shift still open, it drafts a temp order: site, role, start and end, headcount, and the vendor's rate card.
The site manager sees the order in Slack or Microsoft Teams and approves, edits, or declines it. An approved order goes to the staffing vendor through your vendor management system or a mailbox the vendor accepts orders from, once, with the shift it covers on the record.
This is a reference listing. It documents what Fibric would read from Agency Request 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 and their offer state: Deputy shifts marked open through shifts/offers:notify, When I Work OpenShifts, 7shifts shifts with the open filter, Dayforce unfilled shifts
Offer outcomes: When I Work OpenShift approval requests and assignments, Deputy roster updates, Connecteam shift_updated events when an assignee is set
Who could still take it internally: When I Work /2/shifts/eligible, Deputy employees by area, hours already scheduled this week
The offer window per site and role, and the shift start it must close before
Temp orders already placed for the same site and day, from your vendor management system or the vendor's replies in Microsoft Outlook or Gmail
Approve, edit, and decline answers on the orders it posted in Slack or Microsoft Teams
Proposed actions
Target capability: propose a temp order for an unfilled shift: site, role, times, headcount, rate, for the manager in Slack or Microsoft Teams
Target capability: propose a second internal offer before any vendor order where eligible employees were never asked, through Deputy shifts/offers:notify or When I Work assign
Target capability: propose sending the approved order to the staffing vendor through your vendor management system, or as a message from Microsoft Outlook or Gmail
Target capability: propose cancelling an unconfirmed order when the shift is filled internally after all
Target capability: propose recording the vendor's confirmation against the shift in the scheduling system, so the schedule shows it covered
Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.
What you can build
Order a temp after When I Work offers lapse
An OpenShift with no approval request by the window's end, and no eligible user left unoffered, becomes an order draft. The manager approves in Slack and the order is sent from Microsoft Outlook.
If employees in the area were never notified, the operator proposes shifts/offers:notify to them first, with the SMS fee noted. Only if that round lapses does it propose the vendor order.
Shifts returned by the open filter are checked against the window per location. The order draft goes to the manager in Microsoft Teams and, once approved, to the agency from Gmail.
When the vendor confirms by reply, the operator proposes a shift update in Connecteam naming the agency, so the scheduler sees the cover and the shift_updated event closes the loop.
A scheduling connector that exposes open shifts and offer outcomes: Deputy, When I Work, 7shifts, Connecteam, or Dayforce
A route to the staffing vendor: a vendor management system connector built on request, or a mailbox connector such as Microsoft Outlook or Gmail
Slack or Microsoft Teams for the site manager's answer
Per site and role: the offer window, the roles the vendor may fill, the vendor's contacts and rate card
Authentication
Carries no credentials itself. Schedules are read and orders are sent through the connectors you bind, under the scopes those connectors hold.
Limits
The window closing creates a proposal, never an order. No message reaches a vendor without a manager's approval
A vendor management system connector is not in the catalog; Fibric builds the link to your vendor's system when you ask
It sees a vendor's confirmation only through a channel it reads: the vendor management system or the mailbox the vendor replies to
Deputy shift offers may send SMS and incur SMS fees in your Deputy account; the operator says so on each second-offer proposal
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 order itself: site, role, start and end, headcount, the rate from your vendor's card, and the address it goes to. The manager can edit any line before approving, or decline. Nothing is sent until they answer.
What record does it leave?
The shift id, every internal offer made and to whom, when the window closed, the order as approved, the send and its response, and the vendor's confirmation if it arrives through a channel the operator reads.
Will it ever place an order on its own?
No. It proposes and waits. It does not cancel a vendor order on its own either; a cancellation is a proposal like the order, approved by the same manager.
Ask about Agency Request
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