The Email Inbox That Runs Your Recruitment Desk

On a normal Tuesday morning in a recruitment agency, the inbox is a to-do list. Overnight and over the weekend, emails have arrived. Interview requests from clients. Availability confirmations from candidates. A placement confirmation. A candidate withdrawal. A new client brief. Each one requires a CRM update. Each one is sitting there, unprocessed.

By the time you have cleared the inbox — opened the CRM, found the relevant records, made the updates, sent the required responses — an hour of your morning has gone. It happens every day.

What autopilot mode does

Autopilot mode connects to your email inbox (Outlook or Gmail) and monitors incoming messages. When an email arrives that contains a recruitment action, the system identifies what needs to happen in the CRM and either executes it immediately or presents it for your approval.

You did not open the CRM. The update happened.

Five real scenarios

1. Interview request

Email from a client: "We'd like to interview Calen on Monday at 2pm. Can you confirm availability?"

Autopilot contacts Calen to confirm Monday availability, books the interview in the ATS once confirmed, sends confirmations to the client and Calen with the relevant details, and logs the interaction against both records.

You did not touch the CRM.

2. Placement confirmation

Email from a client: "We're delighted to offer the position to Marcus, starting 1st April at the salary discussed."

Autopilot creates the placement record, generates the invoice (if invoicing is connected), triggers the Right to Work and compliance checks if applicable, and updates Marcus's record to placed status.

You did not touch the CRM.

3. Candidate withdrawal

Email from a candidate's representative: "Jordan has decided to accept a counter-offer and won't be proceeding."

Autopilot updates Jordan's record, adjusts the pipeline stage, notifies the relevant client contact, surfaces alternative candidates from the database for the consultant's review, and logs the withdrawal with full context.

You did not touch the CRM.

4. New client brief

Email from a new contact: "We have an urgent requirement for a Head of Finance. Are you able to help?"

Autopilot creates a new job record, classifies the role type, runs an initial candidate search, and drafts a response to the client for your approval before sending. The first step of the recruitment process is already done by the time you open your inbox.

5. Counter-offer situation

Email from a placed candidate: "I've been made a counter-offer by my current employer and I'm considering it."

Autopilot logs the counter-offer event against the placement record, alerts the relevant consultant with full context, flags the pipeline as at-risk, and drafts a suggested response. You see the situation with the context already captured.

How the approval mechanism works

Two modes, user-configurable:

Review mode: Every identified action is presented for your approval before execution. You see the email, the proposed action, and confirm or dismiss. Nothing executes without your confirmation. This is the default mode for new users.

Automated mode: You configure which action types run automatically. Unambiguous actions — a clear interview request with a named candidate and a specific time — can be set to execute without intervention. Ambiguous emails are always flagged regardless of settings.

Most agencies start in review mode to build confidence. Once you have seen the system classify and propose correctly over a few weeks, you can start automating the high-volume, low-risk actions — interview bookings, confirmation sends, record updates.

What happens to emails it cannot classify

Emails that do not contain identifiable recruitment actions are untouched. Autopilot only acts on emails it can confidently classify as containing a recruitment action. Newsletters, marketing emails, ambiguous personal messages — all pass through to your inbox normally.

For emails it can partially classify (it can see there is an action but cannot determine the right CRM record to update), it flags for your review rather than guessing.

The "what if it goes wrong" question

It is the right question to ask, and it deserves a direct answer.

The system can misclassify. An email with ambiguous language or an unusual format might generate an incorrect action suggestion. This is why the confirmation mechanism exists — in review mode, every action is approved before execution. Even in automated mode, the system logs every action it takes with the source email attached. If something is wrong, you can see exactly what happened and reverse it.

The audit trail is complete. You have full visibility into everything autopilot has done.

In practice, the classification accuracy is high for the common email patterns that make up the majority of recruitment inbox volume. Interview requests, placement confirmations, withdrawals — these are structurally similar enough that the AI classifies them reliably. Edge cases exist, and they get flagged.

The time value

The average recruitment consultant receives 20–40 CRM-relevant emails per day. At 2–5 minutes of CRM work per email (finding the record, making the update, sending the response), that is 40 minutes to over 3 hours of CRM admin per day that autopilot handles.

Even at conservative assumptions, autopilot converts hours of admin time to billable time every week. At £50/user/month, the economics are not complicated.