Skip to content

MEETING INTELLIGENCE

Intake calls, interviews, debriefs

Prepares your interviews
and handles what comes after.

Lantern joins the intake call, the interview and the debrief. The brief is sent before you ask, the notes are written while you talk, and the feedback is drafted before you open it.

THE AGENT
moves first
YOU
read, ask, approve
TUE 20 OCT
NEXT · PREPARED
8:30
11:30
16:00
BRIEF SENT · 6:30
Intake call · Head of Engineering
Last quarter's hires, the open reqs and a draft rubric, in Marcus's inbox two hours early.
NOTES · LIVE 11:42
Recruiter screen · Priya Natarajan
03:42 · Built from zero · evidence found. Gap flagged: hiring judgment, question ready.
DRAFT READY · 16:32
Debrief · panel of 4
Four scorecards drafted. Taste change proposed: built from zero required, tenure at scale dropped.
YOU READ IT · 8:12
Marcus Ho, hiring manager
Edits two criteria on the way in.
THE CALL · 11:30
Alex Chen interviews Priya
Asks the flagged question at 09:10.
YOU APPROVE IT · 16:40
Taste change · built from zero
Approve
Dismiss

TRUSTED BY TEAMS AT

Baker McKenzie
Crypto.com
HKSTP
Hyatt
HAECO
Sino Group
Hang Lung
Gammon
PrimeCredit
Nan Fung
InsForge

01 · THREE CONVERSATIONS

Three conversations shape every hire.

Lantern joins all three, so the taste set on the intake call is the taste used in the debrief. Nothing is retyped between them.

01 / INTAKE CALL
Marcus Ho · 45 min
YOUR TASTE · DRAFT V1
Built a function from zero
Payments or ledger infra
Hired the first ten
The hiring manager talks. Lantern writes down the taste.
02 / INTERVIEW
Priya · 30 min
03:42
Built from zero
09:10
Hired the first ten
14:05
Ledger infra · partly
Every answer lands on a criterion, with its timestamp.
03 / DEBRIEF
Panel of 4
YOUR TASTE · V1 → V2
Tenure at scale
Built from zero · required
Proof of building · weighted
The decision rewrites the taste for the next search.
THE AGENT
YOU
BRIEF SENT · 6:30
CV, taste, prior rounds
GAP FLAGGED · 11:38
question ready mid-call
DRAFT READY · 16:32
scorecard written
YOU READ IT · 8:12
edit two criteria
THE CALL · 11:30
ask the flagged question
YOU APPROVE IT · 16:40
one click

02 · BEFORE YOU ASK

The agent moves before you do.

Nothing here waits for a request. The brief, the flagged gap and the drafted feedback each land earlier than the moment you need them. Your part is to read, ask and approve.

03 · DURING THE CALL

Notes written while you talk, in English, Cantonese or Mandarin.

Lantern listens in English, Cantonese and Mandarin, lands every answer on a criterion with its timestamp, and flags the gap while there is still time to ask. The notes reach your ATS when the call ends.

Recruiter screen · Priya Natarajan
Head of Engineering · 11:30 · with Alex Chen
Writing notes · 14:05
03:42
"I wrote the first version of the ledger service myself and ran it for a year."
Built from zero
09:10
GAP FLAGGED
Hiring judgment · not yet covered
Ask next: "Who among the first ten did not work out, and what did you change?"
Partial
12:48
"我哋嘅 ledger 用 Go 寫,後來先加 TypeScript 嘅 service layer。" Spoken in Cantonese, captured as said, summarised in English.
Ledger infra
4 criteria covered · 1 gap · notes sync to your ATS at the end of the call
EN · 粵 · 普
Scorecard · Alex Chen
for Priya Natarajan · drafted 16:32
DRAFT
Built from zero
Strong
Wrote the first ledger service, ran it a year. 03:42
Hired the first ten
Strong
Two known hires after the second outage. 06:15
Hiring judgment
Mixed
One of ten did not work out; owned it. 09:40
Alex edits one line, then submits.
Submit
Edit
Proposed taste change
NEEDS APPROVAL
From the debrief: "We need someone who personally built the function."
Built from zero
Required ↑
Proof of building
Weighted ↑
Tenure at scale
Dropped ↓
Approve
Dismiss
✓
Approved by Marcus Ho · 16:40

04 · AFTER THE CALL

Feedback drafted for you. Your taste updates with it.

The scorecard is written from the transcript before the interviewer opens it, with the timestamp behind each line. When the debrief moves your taste, Lantern proposes the change and a person approves it. Nothing changes on its own.

05 · WHERE YOUR TEAM READS

Briefs and feedback arrive in Slack, before the call.

Briefs, flagged questions and drafted feedback arrive in Slack, by email or inside Lantern. Meetings sync from your calendar and your ATS, notes and scorecards go back to the candidate's record, and the hiring manager sees only the rounds you share.

Slack

Email

Calendar

CLI

MCP

Claude · Codex · Copilot

Your ATS

Lantern
APP
7:02 AM · #hiring-head-of-eng
Your 9:30 with
Priya Natarajan
is in 2 hours. Here is the interview pack, built from the taste you approved on 17 Oct.
Interview pack · Head of Engineering
Open in Lantern
CV
Agenda · 30 min
4 questions on the gaps
Rubric · built from zero
Submit feedback after
What is the status of this search?

06 · AFTER THE MEETING

Approve the debrief once. Every agent updates from it.

The notes, the drafted feedback and the updated criteria go to Application Review, AI Interviews, the next sourcing search and Analytics. Nothing is re-entered.

MEETING INTELLIGENCE
Debrief · 14 Oct · 16:00
"We need someone who personally built the function. Not someone who worked inside a large one."
Marcus Ho · taste change approved 16:40
UPDATED
SOURCING
Searches for the taste, not the title.
18 operators who built from zero added to the search.
UPDATED
APPLICATION REVIEW
Screens against what the manager said.
41 applicants re-read against taste v2 overnight.
UPDATED
AI INTERVIEWS
Asks what the debrief left open.
New first question: who were the first ten hires?
UPDATED
ANALYTICS
Shows where the taste moved.
Pass rate reported against v2 from this week.

The hiring loop

Every decision sharpens the next.

The five agents share one set of criteria. What a debrief decides changes what the next search looks for, what the next screen scores and what the next interview asks.

One hiring taste
V2 · UPDATED 20 OCT
Sourcing
Application Review
updates the taste after every debrief
AI Interviews
Meeting Intelligence
Analytics
Taste updated after the hire
The next search starts sharper.
One loop per role. A person approves every change to the taste.

Hiring is the last moat

Your next conversation
is already prepared.

Bring a real role. We will prepare the intake call, sit in the interview and draft the debrief in front of you.

A worked example · illustrative

Keep a debrief connected to the role

After an interview, the panel discusses whether a candidate built a function or joined one that already existed.

  1. Capture the conversation and the evidence the panel discussed.
  2. Connect the feedback to the role’s hiring criteria.
  3. Have the team review any proposed change before it informs the next search or interview.

The conversation becomes shared context. A person still approves a change to the taste.

This example explains the workflow; it is not a customer result or a live product output.

FAQ

Questions about meeting intelligence

Which hiring conversations does Lantern cover?

Meeting Intelligence covers intake calls, interviews, panels and debriefs. It keeps what the team learns connected across the hiring workflow.

How is it different from a standalone meeting transcript?

The purpose is to connect conversation context to recruiting work. Notes and feedback inform the hiring taste and the other agents rather than staying in an isolated meeting record.

Can one interview change future sourcing?

Interview feedback can inform a proposed change to the hiring criteria. Once a person approves the change, the shared context can guide subsequent sourcing and review.

Where do we check recording and retention controls?

Review the current documentation in the Trust Center and confirm your recording, access and retention requirements before rollout.