> ## Documentation Index
> Fetch the complete documentation index at: https://support.yena.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Review applicants in the inbound queue

> Every confirmed application waits in one queue with a fit read — accept into your pipeline or send a respectful rejection in one click.

Inbound applications used to mean an inbox full of PDFs and a guilty backlog. In Yena, every confirmed application lands in one place — the job's **Inbound** tab — already parsed, already assessed, waiting for exactly one decision: in or out.

## The queue

<Frame caption="A For Review row: applicant, applied date, a one-line profile summary, and a fit read">
  <img src="https://mintcdn.com/yena/KYoddSHDAKpppHdf/images/screenshots/job-inbound-for-review.png?fit=max&auto=format&n=KYoddSHDAKpppHdf&q=85&s=2e13aa882dd5f5b9b1812951d6cfa151" alt="Inbound tab For Review list showing an applicant with a fit label, an accept-into-stage picker, and a reject control" width="1122" height="110" data-path="images/screenshots/job-inbound-for-review.png" />
</Frame>

Open a job → **Inbound**. The tab appears as soon as the job has applications, split into **For Review**, **Accepted**, and **Rejected**.

Each For Review row shows:

* The applicant and when they applied.
* A one-line summary drawn from their parsed CV.
* A **fit read** — one of four plain labels: *Strong fit*, *Credible fit — clarify*, *Bridgeable*, or *Better aligned elsewhere*. It is computed deterministically from the same matching rules as your board, so it never changes between reloads, and there are no percentages to argue about. A profile or role without enough readable content says *Not yet readable* instead of guessing.
* A quiet **waiting N days** marker once a row has sat unanswered for five days.
* A **Knockout** marker if a [screening question](/en/careers/screening-questions) was answered with the disqualifying answer — a flag for your judgement, never an auto-reject. Expand the row to read all screening answers.

## Accept

Choose a stage in **Accept into…** and the applicant moves onto your pipeline board, activity logged. The default is your applicants stage, so accepting is one click.

## Reject — with the email included

Select the reject control and Yena does the whole thing atomically: the application closes, the rejection is recorded, and the candidate receives a respectful, workspace-branded rejection email.

<Note>
  One click, one email — guaranteed. If you press reject twice, the candidate still gets exactly one email. If the send fails, the same button retries it. The contact record stays in your database as a silver-medalist for future roles unless you remove it.
</Note>

## Why applicants arrive "ready"

By the time someone reaches this queue, they have confirmed their application by email (double-opt-in) and their CV has been parsed into a full candidate profile — experience, education, skills, and searchability included. See [How applying works](/en/careers/cv-first-apply).
