AI HR & recruiting agent. Hire without the busywork.
Every applicant scored against the criteria you published, with the reason attached, and every candidate message written and waiting for your send.
On requestBuilt for your company by the Unistaff team. The role that runs in the product today is the AI inbound sales manager.
What it does
Resume screening
Scores applicants against the must-have and nice-to-have criteria in your job description, and writes the reason next to every score.
Scheduling drafts
Writes the invite, the reschedule and the nudge against the availability you give it, ready for your coordinator to send.
Onboarding checklists
Turns your process into a day-by-day list for the new hire, with the owner named on each item.
Reference summaries
Turns the answers you collect into a structured summary, with the quotes it drew from kept alongside.
How it works
Screen
Applications arrive through the form and are scored against your criteria.
Shortlist
Each score carries its reason, so a recruiter can overturn it in seconds.
Draft
Invites, reschedules and rejections are written and wait for a send.
Decide
A person picks who moves forward. The machine never makes that call.
What exists today
- On request
Screening with a reason
Applicants are scored against the criteria you publish, with the reason written next to every score.
- On request
Candidate message drafts
Invites, reschedules and rejections are drafted for your coordinator to send.
- On request
ATS connection
None ships today. A setup can build one against your ATS; until then applications arrive through a careers form on your site.
- Planned
Calendar connection
Interview times are confirmed by a person until a calendar is connected.
How a setup starts
The HR desk is built on request. It starts with a scoping call about your roles and your rules; your criteria are written down and approved, and the careers form on your site is connected. Scope and price are agreed before anything is built.
Then the assistant scores each new batch while a recruiter checks every reason it wrote. Your team decides when the scores are good enough to sort by, and every message to a candidate waits for a person to send it.
Evidence · AI HR
What it is built on
The pieces of the platform this role is built on, each marked with the site's three words: Live works in the product today, On request is built with you during a setup, Planned is on the roadmap.
Live
A careers form on your site posts applications into one record
The intake endpoint runs in production on our own sites today. It caps the request body before parsing it, absorbs bot submissions without writing anything, and stores the application in Postgres. One that fails validation gets a reason back instead of a silent success. For your site, the form is connected during an on-request setup.
On request
Screening produces a score with a reason, and a person decides
The role scores against the criteria you publish and writes why. Every message to a candidate is a draft until your coordinator sends it, and the platform has no send path of its own — which also means it cannot reject anybody by itself.
On request
An ATS connection is built during the setup
Greenhouse, Lever, Workable and the rest are integrations we build against your account during a deployment. We name what we have built and leave the logo wall to someone else.
The gates behind the drafts — approvals, spend caps, the kill switch — are listed on the product page.
Frequently asked questions
No. It screens, schedules, and summarizes. Final decisions stay with humans.
It scores against the criteria you publish, writes the reason next to each score, and holds no decision power. You can read every score, overturn any of them, and see the criteria that produced them.
None out of the box today. Applications come in through a form that posts to our endpoint, and an ATS connection is scoped and built as part of a deployment.
Writing the criteria down is the main work. The build starts after the scoping call, and its timeline is agreed there; once it runs, each batch that arrives through the form is scored on the following run.
Today the assistant drafts the reschedule against the availability you give it and your coordinator sends it. A self-service booking flow needs a calendar connection, which we scope at the start of a deployment.
The assistant writes the rejection in your voice, following the policy you set, and a person sends it. Nothing goes to a candidate without that step.
Volume is where fixed criteria help most: application number three hundred is scored on the same criteria as application number one, and each score carries its reason, so a recruiter can audit any of them.