Agency Connect keeps internal shift filling and external staffing escalation in one workflow. Try your internal roster first, then automatically contact the staffing partners you choose if the shift is still open.
.png)
Your internal workforce and staffing partners no longer have to live in separate coverage workflows.
One workflow ends. Another one starts from scratch, in a different place, with the same information typed again.
Agency Connect removes that handoff. The escalation happens inside the same callout, against the same shift, with the same record.
Six phases, one continuous process. The internal attempt and the external escalation are the same workflow — not two systems bridged by a phone call.
Fallback is configured per workflow — whether it is enabled at all, how long Frekyl waits, when the request launches, and which partners take part.


These are your existing, approved partners — not a marketplace. Frekyl is the workflow that connects them to a coverage need.
Your organization defines the agency process. Frekyl executes the communication workflow.
These products can work together as one chain — or independently, according to the configuration you choose.

A distribution centre and a remote plant rarely share the same partners, the same timing or the same approvals.
Illustrative. Partners, order, timing, eligible roles and approval steps are configured per site and department by your organization.
Coverage IQ counts upcoming absences against the thresholds you set. When a day crosses the line, the people who can act on it are alerted — so agency escalation is a planned step rather than a scramble on the morning of the shift.

Internal outreach and agency escalation appear in the same history, on the same shift.




Frekyl runs standalone. Where integrated, workforce and absence data can flow between Frekyl and existing HR or workforce systems.
Explore integrations →
See how Agency Connect can keep agency escalation structured, visible, and connected to your existing coverage workflow.