The review queue
Everyone Elsin flags lands in one queue, where a person on your team decides what happens next.
What lands there
Every candidate whose verdict is Needs review, and anyone checked on device who sent their ID photo for a person to confirm. Candidates with a reason that flags on its own come first, then the heaviest scores, then whoever has waited longest.
Decisions
- Clear flag
- The reasons are explained. The cleared reasons are not counted again for this candidate.
- Keep flagged
- Stays in Needs review, with your note.
- Ask to verify identity
- Sends the ID and face check.
- Interview or day one check
- Sends the continuity check.
- It matches
- Approves an ID photo sent for review.
- It doesn't match
- Declines an ID photo. The candidate is not rejected.
None of these rejects anyone. Rejecting a candidate is a separate pipeline action that a person takes and that records who took it.
Who can decide
Owners, admins and recruiters. Interviewers can open the queue but not decide. An AI agent connected through the API can clear, keep flagged or ask to verify; by default that is only a proposal a person confirms, unless an owner or admin lets agents decide. An agent can never approve an ID.
Keyboard
| Key | Does |
|---|---|
| C | Clear flag |
| K | Keep flagged |
| V | Ask to verify identity |
| J or Down | Next candidate |
| Up | Previous candidate |
| N | Write a note |
| ? | Show the shortcuts |
The record
Each decision stores who made it, the action, the note (up to 2,000 characters), the verdict before and after, and the reasons the reviewer saw. Nobody can edit or delete a decision; it goes only with the candidate.