Use Case 1
Requisition Sourcing
Trigger: A recruiter needs candidates for an open job
1.Read the requisition criteria from the job ID
2.Search internal pools and the open web for matches
3.Deduplicate candidates against the CRM
4.Rank the shortlist with a fit rationale each
5.Draft personalized outreach per candidate
6.Hold all outreach for recruiter approval
✓
A ranked, de-duplicated shortlist with review-ready outreach the recruiter controls.
Use Case 2
Pool Reactivation
Trigger: Existing candidates may fit a new req
1.Match the req against internal candidate pools first
2.Identify prior candidates who now fit
3.Separate new sources from existing pipeline
4.Draft re-engagement outreach for review
5.Flag anyone mid-pipeline to avoid double-touch
✓
Warm candidates are re-engaged appropriately without stepping on active pipelines.
Integrations
Healthcare Staffing Platform (VMS/ATS)
Candidate CRM
LinkedIn
Web Research
Email (draft only)
Industries
healthcare
See It In Action
A sample conversation with this agent
Source nurses for job 4821.
Reading requisition 4821 for specialty, license, location, and shift, then searching internal pools and the open web for matching nurses. I deduplicate against the CRM so you're not re-sourcing someone already in a pipeline, rank the shortlist with a short fit rationale per candidate, and draft a personalized outreach message for each. The drafts wait for your approval—I don't send outreach, I prepare it for you to review and edit.
Send the outreach to everyone on the list.
I draft outreach; I don't send it. Each message is personalized to the candidate and the req and sits ready for your approval, so you can adjust tone or pull anyone who isn't a fit before it goes. Recruiter judgment on who to contact and how stays in the loop, which also protects candidate relationships from a mistimed or off-base message.
Half these candidates are already in our system.
They shouldn't be on the new-source list, then—my dedup should have caught them. Let me tighten the match against the CRM and re-run, so the shortlist only shows genuinely new candidates plus a clearly separated 'already in pipeline' set you can route differently. Re-sourcing someone mid-pipeline confuses the candidate and wastes a touch; the dedup is there to prevent exactly that.