Recruiting pipeline screening
Every application read the day it arrives, scored against the brief you wrote, with the strong ones already moving toward a screen.
The brief
Written like you’d brief a person.
This is the whole setup - a procedure in plain language, with tools and specialist agents referenced inline. When it runs is not written here: that’s the trigger, configured beside it.
Read the candidate with #yekar.ashby.get-candidate, score fit against the job brief, draft the outreach with #yekar.gmail.create-draft, and ask @scheduler to book a screen for anyone above 80.
How it runs
From trigger to logged outcome.
Trigger
Schedule - A frequent sweep of new applications in the ATS
An ATS email notification can start it the moment one arrives.
Read the application
Pulls the candidate's profile and materials.
Score against the brief
Rates fit against the role's stated requirements, with reasoning.
Draft the response
Outreach for strong fits, a considered decline for the rest.
Book the screen
Hands scheduling to the scheduler agent for candidates above the bar.
Where people stay in control
Nothing consequential runs on its own.
- Declines and outreach are drafts until a recruiter approves - candidates never get raw model output.
Tools it uses
Runs on accounts you already have.
Ashby
Gmail
Google Calendar
Google Sheets
Connected once, governed per agent - this use case gets only the tools listed here.
Illustrative savings
$700–$1,900 / month
Assumes 150–500 applications a month at 5–8 minutes of first-pass screening each.
Illustrative monthly savings, estimated from typical handling time at public salary benchmarks, reviewed August 2026. Not a promise or a guarantee - your numbers depend on volume and process.
What makes this dependable
Start with the job
See how Yekar.AI would run one of your real processes.
Bring the job, the systems it touches, and the decisions that need a person.