01
Used a local connector to reuse the authorised recruiter session and synchronise visible candidate history.
Case study · Delivery evidence
Recruiting automation with context, evidence, and send control
A recruiting workspace that synchronises candidate conversations, refreshes evidence-linked profiles, and separates manual, copilot, and controlled-autopilot authority.
By Onyx Devs Lab · Published · Updated
The operating challenge
Fast reply generation did not solve incomplete conversation context, stale candidate profiles, duplicate sends, or uncertain delivery. Automation needed to coexist with recruiters rather than take over their working interface.
Designed intervention
02
Refreshed structured profiles when context changed, separating facts, inferences, confidence, and missing information.
03
Supported manual, copilot, and controlled-autopilot modes per candidate.
04
Serialised sends, enforced idempotency, and reread the sent message to verify completion.
Validation snapshot
These figures separate delivered scope from pilot validation. Each metric retains its measurement definition so product coverage is not mistaken for business impact.
automation modes
Manual, Copilot, and controlled Autopilot
operating workspaces
Candidate queue, conversation, profile, and operations
conversation-sync coverage
Visible historical messages successfully backfilled
send reread success
Sent text reread from the recruiter side after action
candidate handling time
First review to confirmed next action; 22.4 min before
Evidence boundary
The published validation covers synchronisation, send verification, and workflow time in a controlled pilot. It does not claim improved hiring outcomes without a longer recruiting cohort.