Screen inbound job applications from a Gmail jobs inbox

Your jobs inbox fills up with applications nobody has time to read. An Orkeste agent reads each application email, summarises it against the criteria of the role and posts the summaries to your hiring channel, so the hiring manager decides faster. It never rejects a candidate.

The problem

A role gets eighty applications in a week. Reading each one takes days, and good candidates accept other offers while they wait.

How the workflow runs

Runs: Every hour or every day.

  1. Read new applications: The agent reads new emails in the jobs inbox, in Gmail or Outlook.
  2. Match the role: It works out which open role each application is for.
  3. Summarise: It writes a short summary against the criteria in its briefing: experience, location, availability.
  4. Log: It can add each application to an Airtable table.
  5. Share: It posts the summaries to the hiring channel in Slack.
  6. The hiring manager decides: A person decides who to invite. The agent does not shortlist, reject or reply.

The agent summarises; shortlisting, rejecting and contacting candidates stay with people.

Who does what

What this workflow does not do

Works with your stack

Questions about this workflow

Does it read the CV attached to the email?

Not today. Agents read the text of the email, not attached files. The summary is based on what the candidate wrote in the email.

Can it reject candidates automatically?

No. The agent writes summaries and a person decides. Any reply to a candidate is drafted for approval.

How do we keep the screening fair?

Keep the criteria in the briefing to job-related requirements, and ask the agent to leave out name, age, gender and photos from its summaries.

Related workflows

Keep reading