# Recruiting: every applicant read · One by Lughlabs

> Dara checks every application against your must-haves, with quotes. Otto’s phone screen says it’s an AI. Nia keeps everyone posted.

URL: https://lughlabs.ai/use-cases/recruiting/

One for Recruiting

## Every applicant read. Every decision yours.

Your bots: Dara checks every application against your must-haves, with quotes. Otto’s phone screen says it’s an AI. Nia keeps everyone posted.

[Talk about your hiring](https://lughlabs.ai/talk?plan=business)

In practice

### One open role, handled.

#### 312 applications, each with a reason.

Dara reads every application against your must-haves and quotes the line that shows it.

#### A disclosed AI screen, same for everyone.

Otto’s screen asks every candidate the same four questions and keeps their answers in their words.

#### No candidate left waiting for news.

Nia drafts an update for every candidate in process, and sends rejections only after you approve.

#### Monday’s hiring update, before anyone asks.

Nia sums up the pipeline and names what is stuck, and who it’s waiting on.

[Skip the demo](https://lughlabs.ai/use-cases/recruiting/#ucx-after-stage)

Fictional company · Sped up

Your crew

### Three bots, one hiring desk.

Where people decide

### Fair by design. Decided by people.

A person decides at every gate.

1. Read Your must-haves only Only the job-related must-haves you set, and the résumé line that shows each Wiki › Must-haves.md
2. Shortlist You decide Dara recommends with reasons and rejects no one Records › Candidates
3. Screen Says it’s an AI Start with a disclosure, then the same four questions for everyone Voice › Configure › Recording and disclosure
4. Advance You decide Notes and quotes come back; the stage moves on your answer Records › Candidates
5. Interview Your team People interview and score; Nia keeps each candidate posted Your ATS
6. Offer or not Allow once, each Nia drafts the note; with Ask before sending external email on, every send waits Settings › Action confirmations

On record Each change: who and when A record’s history: written by a bot or a call, stage changes, reviews Records › a record’s history

Check local rules before using AI in hiring, such as [NYC Local Law 144](https://www.nyc.gov/site/dca/about/automated-employment-decision-tools.page) and the [EU AI Act](https://eur-lex.europa.eu/eli/reg/2024/1689/oj). Live calls need calling turned on. Not legal advice.

Works with

### Keep your ATS. Add a crew.

Search apps

- Reads applications, résumés and stages **One-click connect**
- Reads applications and interview schedules **Connect with your key**
- Works with hiring and people records **Needs a one-time setup**
- Works with hiring and people records **Needs a one-time setup**
- Works with hiring and people records **Needs a one-time setup**
- Works with hiring and people records **Connect with your key**
- Works with hiring and people records **Connect with your key**
- Reads candidate threads; sends replies you approve **One-click connect**
- Reads mail and drafts replies **One-click connect**
- Reads free times for interviews **One-click connect**
- Reads bookings and availability **One-click connect**
- Reads schedules and meeting details **One-click connect**
- Works with meetings and recordings **One-click connect**
- Reads schedules and meeting details **One-click connect**
- Finds messages and posts updates **One-click connect**
- Reads schedules and meeting details **One-click connect**
- Works with forms and signed documents **One-click connect**
- Works with forms and signed documents **Connect with your key**
- Reads and updates spreadsheet rows **One-click connect**
- Finds and works with workspace records **One-click connect**
- Finds pages and updates databases **One-click connect**
- Reads résumés and job descriptions you share **One-click connect**
- [Any MCP server or OpenAPI tool](https://lughlabs.ai/docs/connectors)

Trademarks belong to their owners. Availability varies by deployment.