Find the right candidates.
Agents read each requirement, search your ATS and candidate database, and rank matches on skills, rate, location, and availability, with the reason for each match.
From new role
to shortlist, faster.
MausBot agents read each new requirement, search your candidate database, screen candidates by phone or text, and draft the submissions. Your recruiters approve what goes to the client or hiring manager.
See the rollout RecruitingLess searching.
Less searching.
More time with candidates.
Résumés to search. Candidates to reach for a quick call. The same write-up for every submission. Set up MausBot agents to do the groundwork between a new role and a shortlist, so your recruiters can focus on candidates and clients.
Book a call See an example run Your process. Your ATS. Your approval on every submission.
New job requirementFrom a client email or your ATS
MausBot hiring teamAn agent for each step of your process
Sourcing
Screening
Submission
A recruiter approves before anything is sent.
Screen by phone or text.
Agents call or message shortlisted candidates, ask the questions you set, and log every answer in your ATS. Anyone who’d rather talk to a person goes to a recruiter.
Approve with one tap.
Agents draft each submission from the résumé and screen notes. A recruiter approves, edits, or rejects it before it reaches the client or hiring manager.
Example run
A new role comes in.
Here’s what happens next.
A requirement to read. Candidates to screen. Submissions to approve.
See how agents could move one role forward using your ATS and your hiring rules.
Select a step
Sample runIllustrative example
Role logged and five candidates shortlisted in the ATS
A shortlist, ready to screen.
The agent reads the requirement, logs it in your ATS, and searches your candidate database. It shortlists against your criteria and explains each match.
Illustrative run with a sample role and candidates. Actual steps and actions depend on your ATS, connections, and configuration.
Start with the roles you fill most.
Choose one repeatable role type for your first deployment. Agree on the criteria, screening questions, and approval rules, then test them before agents contact candidates.
- 01
Map your hiring steps
Walk through how a role moves from requirement to submission today. Decide which steps agents take on and where a recruiter signs off.
- 02
Connect your tools
Connect your ATS, inbox, and calendar. Give agents your screening questions and submission format, and confirm the phone setup for calls.
- 03
Test before contacting candidates
Run past roles and sample candidates through the workflow. Check the matches, screens, and drafts before agents work on live roles.
We’ll confirm your ATS integration, phone and messaging setup, and costs before deployment.
Before you deploy
Does it work with our ATS?
That depends on your ATS. Many have an API that agents can use to read roles and update candidates; others can be worked through email or the browser. We’ll check yours and confirm the approach before setup.
Do candidates know they’re talking to an AI?
Agents introduce themselves the way you set. We recommend saying at the start that it’s an AI agent and offering a recruiter to anyone who prefers one. Rules on automated calls and AI in hiring vary by location, so check the ones that apply to you.
Who makes the hiring decision?
Your team. Agents gather information, screen against the criteria you set, and draft submissions. A recruiter approves every submission, and hiring decisions stay with people.
What does an AI hiring workflow cost?
The MausBot app is free and open source. A hiring deployment also needs model usage, hosting, phone service for screening calls, and integration work. Pricing depends on your volume and setup; book a call to discuss the initial and ongoing costs.
Which hiring steps would you
hand to an AI agent?
Bring your role types, monthly volume, and current ATS. We’ll help scope a first deployment.