Staffing, RPO & shift work
Fill the shift before the client notices it is empty.
Shift filling is a race conducted by phone. Hundreds of candidates, one vacancy, and whoever gets through first wins - which makes it a throughput problem, not a judgement problem.
An illustrative reference architecture, not a customer
case study. No organisation is named and no deployment is described - this is
what the layers look like for a recruitment & workforce organisation,
so you can map it onto your own estate.
Channelswhere the conversation starts
Inbound numberspublished lines
SIP / contact centreexisting estate
Outboundcampaigns and callbacks
In-appbrowser WebRTC
▼
VoiceKernelthe agentic voice layer
Conversationagent, voice, turn taking
Knowledge groundinganswers with citations
Tool callsreads and writes back
Transferto a human, with context
Tenant isolationownership registry
Audit and erasureper call, per mutation
▼
Integrationyour boundary, your rules
REST + typed SDKscoped API keys
Signed webhooksretried, replayable
Live event streamSSE
▼
Recruitment & Workforceyour systems of record
ATScandidates, roles, pipeline
Rosteringshifts and availability
Compliancetickets, licences, right to work
Payrollrates and timesheets
CRMclient accounts
Only the bottom layer is specific to recruitment & workforce. The
three above it are identical in every deployment, which is the point: the
voice layer does not need to know what industry it is in, only which systems
it is allowed to reach and what it may say.
What it changes
Mechanisms, not projections. Each of these follows from something structural
about the work, so you can check whether it holds for your own queues.
Fill rates improve because contact is parallelA recruiter calls one candidate at a time; the constraint is dialling, and that constraint disappears.
Screening becomes comparableEvery candidate answers the same questions in the same order, which is what makes the shortlist defensible.
Compliance lapses are caught before they biteExpiring credentials are chased on schedule rather than discovered on site.
Recruiters do the part that needs a recruiterAssessment and client relationships, not availability roll-calls.
What the agent actually does
Shift fillingCall the qualified pool in order, confirm availability, and assign the shift to the first who accepts, updating the roster live.
Candidate screeningAsk the qualifying questions consistently, capture the answers as structured data, and book the interview for anyone who passes.
Compliance chasingOutbound for expiring tickets and licences, with the document link sent during the call.
What keeps it deployable
Right-to-work data handled carefullyCaptured into your ATS, not held by the voice layer.
Screening consistency recordedEvery question and answer retained with the call.
Candidate contact preferencesDo-not-call and consent enforced before any outbound run.
An unfilled shift is lost revenue and a client relationship event, and it is lost to dialling speed more often than to candidate supply.
NextRead the source
Everything above is in the open-source Community edition. Nothing on
this page needs a licence.
NextRun it yourself
Point it at your provider account and put one queue through it before
you talk to anybody.
NextThen buy the guarantees
An Enterprise agreement adds the SLA and the
support contract when it carries real volume.