AgentWorks for Recruitment

The recruiter decides. The agents do the admin around it.

Applications come in by email, CVs need reading, interviews need a time that suits three diaries. A team of agents does that groundwork, and nothing reaches a candidate before a recruiter has said yes.

Recruitment agencies and in-house talent teams of roughly 10 to 250 people.

The work that comes back every week.

Reading every CV

Dozens per vacancy, most of them a clear no. Someone still opens each one.

Finding an interview slot

The candidate, the hiring manager and a room. Four emails before anything is in a diary.

Keeping candidates informed

Everyone wants to know where they stand. Status emails slip when the week gets busy.

Writing vacancies

Each one from a rough brief, in the right tone, without the usual clichés.

Preparing interviews

A question set per role and level, so two interviewers judge the same things.

Your team

A team of agents, each with one job.

Each agent does one thing well, in your own apps, and asks before it sends or changes anything. You give them their rules. They share the board with your people.

Candidate screener

Called by the workflow

Reads each CV against the vacancy brief and writes a short shortlist note: must-haves met, gaps, questions to ask.

Reads and summarises on its own. It never rejects or contacts a candidate; that is the recruiter’s call.

OutlookSharePoint

Interview scheduler

Called by the workflow

Finds free times in the hiring manager’s calendar and drafts the invitation with a booking link.

Checks calendars on its own. Asks before it sends an invitation or books an event.

Outlook CalendarCalendlyOutlook

Vacancy writer

You ask in chat

Turns a role brief into a clear, inclusive vacancy text in your house style.

Writes drafts only. A person publishes the vacancy.

Google DriveSharePointReady-made

Interview kit builder

You ask in chat

Builds a structured question set per role and level, with what a good answer sounds like.

Writes drafts only. Nothing leaves the workspace.

Google DriveSharePointReady-made

Working together

From application email to booked interview

Starts when A new email arrives in your applications mailbox, for example jobs@ as an Outlook shared mailbox.. One workflow hands the work from agent to agent, and stops where a person needs to decide.

  • The recruiter decides who is invited, held or declined. The screener only writes a note.
  • Every email to a candidate and every calendar booking asks first. You can allow one action from then on, and take that back later.
  • Vacancy texts and interview kits stay drafts until a person uses them.

The apps it works in

OutlookGmailOutlook CalendarCalendlySharePointGoogle DriveMicrosoft Teams

Applicant tracking systems such as Bullhorn, Recruitee, Carerix or Homerun have no ready connector. Connect them through a webhook (a new application starts the workflow), the HTTP request step if the system has an API, or an MCP server.

All 40 apps

What you need

On Free you can try this with up to 3 agents, 2 workflows and one email trigger that checks every 10 minutes. The full team on a shared mailbox needs Business: unlimited agents and workflows, 10 app triggers checked every 2 minutes, and team boards.

Pricing

CVs are personal data under GDPR, so connect only the mailbox you need. The EU AI Act lists AI used to screen or filter job applications as high-risk. Here the agent summarises and a recruiter decides on every candidate. On Business, each workflow gets an AI Act risk classification in the Security tab.

Questions

AgentWorks for Recruitment

Runs in the EU. Every action that changes something asks first.

No. The screener writes a note per CV and puts it on the recruiter’s board. Inviting, holding and declining is a step a person approves.