The fortieth InMail of the week still has to sound like the first

A req with forty qualified candidates and one open seat does not get forty identical messages — it gets forty that each mention something specific enough to prove a human actually read the profile. Typing that specificity fresh, over and over, across a full day of sourcing, is where a recruiter's afternoon actually goes slow. The search itself is fast. Writing forty small, true, individual sentences is not.

Sourcing: the line that has to be about this one candidate

A promising profile shows up mid-search — three years at a company whose stack matches the req almost exactly, a side project that answers a question the job description doesn't even ask. The template opening line still works, but the sentence that gets a reply is the one that names the specific thing that made this profile worth stopping for.

Holding the key and saying it lands in the message box through the accessibility API where LinkedIn's composer supports that and a synthetic paste where it does not, clipboard restored either way — the same mechanic whether the field belongs to LinkedIn, an ATS, or a plain email client.

The call ends, and the notes have thirty seconds before the next one starts

A screening call runs its usual twenty-five minutes, and the notes that matter — comp expectations, a start-date constraint, the one skill gap worth flagging to the hiring manager — need to go into the ATS before the next call starts, not reconstructed from memory an hour later. Typing them means composing at a keyboard with the previous conversation still competing for attention. Saying them, in roughly the order they'd be explained out loud, tends to get more of the actual detail down before it fades into the next call's version of the same three questions.

Worth being precise about what this is and is not: it types what a recruiter says about the call, into whatever field is open. It doesn't record or transcribe the call itself — a recruiter who wants the conversation captured word for word, not just their own summary of it, is looking for Coii AudioNotes, a separate product built for that. The rest of a recruiting day, in the recruiter's own words, is what the rest of this page covers.

Updating the hiring manager without waiting for the weekly sync

A hiring manager who asks "how's the search going" mid-week deserves more than "still sourcing" — and a real update, with a candidate count, a note about where the pipeline is thin, and a specific concern about one finalist's availability, is exactly the kind of message that gets typed shorter than intended because a full paragraph feels like it will take ten minutes to compose properly.

Coordinating a five-person loop without it eating the afternoon

Getting five interviewers onto one onsite loop is coordination, not writing, but the messages around it still cost real time: a note flagging that the strongest slot conflicts with someone's standing meeting, a confirmation to the candidate with the finalized agenda, a nudge to an interviewer who hasn't responded forty-eight hours out. None of these messages is long on its own, but a day with six loops to schedule turns into a day with dozens of these small typing tasks stacked between everything else on the calendar.

A candidate who goes quiet, then reappears three months later

A strong candidate who paused a search mid-process — a counteroffer accepted, a personal reason, no explanation given — sometimes reopens the conversation months later, and the message that reopens it well is the one that remembers the specific thing left unresolved rather than restarting from a generic template. Dictating that reply the way the earlier conversation would actually be recalled out loud tends to surface the right detail faster than scrolling back through old threads trying to reconstruct it cold, and it reads to the candidate like someone who actually remembers the conversation rather than someone running a re-engagement campaign.

A rejection that isn't a form letter

Most candidates get a templated pass, and that's fine — most of them applied cold and expect exactly that. The candidate who made it to a final round and lost out on a close call is a different message: specific about what was strong, honest about why someone else got the offer, and worth the extra sentence a form rejection never has room for. Dictating that one paragraph, the way it would actually be said on a call, tends to come out warmer than the typed version most recruiters default to when a template is one click away and the day already has six more things in it.

A day's outreach, kept in order

None of it synced to a shared workspace or visible to anyone else on the team — history stays local to the machine it was dictated on, the same way a laptop's browser history does.

When the connection is a conference Wi-Fi network, or none at all

A recruiting conference, a client site with a locked-down guest network, a flight home after final-round interviews — a recruiter's day is not always spent on a reliable office connection. Because a dictation needs no network once the app is installed, none of the above changes how it behaves. The offline case in full is worth a look for anyone whose actual bottleneck on a travel-heavy week is connectivity rather than typing speed.

A work laptop and a personal machine, kept separate on purpose

Sourcing after hours from a personal laptop is common enough that a licence covers three devices, each installed on its own with no account tying them together. A message drafted on a personal machine on a Sunday evening does not appear on the work laptop Monday morning — there's nothing to reconcile, because there's no shared history to begin with.

A stack of company names that changes with every req

A recruiter working three reqs in three different stacks says a rotating set of company names, product names, and technical terms that a general dictionary was never going to have. Typing each one into the app's dictionary once, by hand, means it comes out the same way every time after that — used as a hint before the audio is processed and checked again over the transcript afterward, on word boundaries, never a fuzzy guess. It doesn't pick anything up on its own: a company name mentioned for the first time on a new req still comes out however the engine happens to hear it, until it's added.

That's a real cost on a busy sourcing week — dozens of unfamiliar names across a handful of open reqs, each needing a manual entry before it types cleanly. A recruiter who wants a tool that infers those names automatically as it goes is asking for something this app does not do, and it's worth saying so plainly rather than discovering it three reqs in.

A message read back before it's sent to someone who's watching for a reply

A message dictated quickly between two calls deserves the same glance a typed one would get before it goes out — a misheard company name or a garbled job title reads exactly as confident in the transcript as a correct one, and only a second look catches the difference on a message a candidate is going to read closely, looking for the sign that they weren't just added to a mail merge. That check costs a few seconds against a message that took five to say, and on the messages that actually get a reply, it's worth treating as part of the habit rather than an optional extra step.

The raw version of what was said stays on the history row next to whatever got cleaned up afterward, so a name that turns out wrong is a quick fix from history, not a redictation from scratch.

What a held key does not fix for a recruiter on the road

There's no vocabulary that learns a candidate's name or a recurring client's terminology automatically — the dictionary exists, but every entry is typed in by hand, once. Wispr Flow builds that kind of vocabulary on its own and runs on Mac, Windows, iOS and Android at $15 a user a month ($12 annually), checked against its own pricing page today — a real advantage for a recruiter who sources as often from a phone between meetings as from a laptop at a desk, and one this app does not close.

Apple's own Dictation is already free on every Mac and types into the same LinkedIn or ATS fields. The case for a dedicated app is less about whether the words get typed at all and more about what happens to them once they're said — filler left in or out on purpose, the raw version kept alongside the cleaned one, and a key that starts the instant it's held rather than after a short pause.

A sourcing-heavy week and an interview-heavy one ask for different things

Some weeks are almost entirely outreach — dozens of short, personalized opening lines, said and sent fast, moving on to the next profile. Others are almost entirely screens and debriefs — longer notes, fuller updates, the occasional hard rejection conversation. The same held key covers both, but a sourcing week rewards speed above all else, while an interview-heavy week has room for the longer, more considered version of a note. Treating every message like a sourcing blast on a week that actually needs careful debrief notes is the wrong instinct, and the reverse costs time on a week where volume is what matters.

A recruiter juggling three open reqs at once usually lives somewhere between the two extremes on any given day, and the switch between modes is not something the app enforces — it just makes either one faster than typing would have. What stays constant is the check before sending: a rushed sourcing line and a carefully considered debrief note both deserve the same few-second read-through, because a wrong candidate name reads exactly as confident in either one, and a template that hasn't been personalized in the rush of a sourcing sprint is worth catching before it goes to someone who is going to notice.

What still needs a human decision, not a faster typist

None of this changes who a recruiter decides to move forward, what an offer looks like, or how a compensation conversation gets negotiated — those are judgment calls a held key has no part in. What it changes is the mechanical cost of writing everything around those decisions: the outreach line, the screen note, the update, the rejection. A recruiter who spends less of the day on typing spends more of it on the sourcing search itself, the actual screen, or the negotiation that a templated message was never going to help with anyway.

What it costs for one recruiter or a small team

$19 once, three devices per licence, macOS 13 Ventura or later, Apple Silicon or Intel. The thirty-day trial runs the full app, no card and no account — long enough to carry a real sourcing push and a round of screens through it and see whether saying the outreach line changes how many actually sound specific by the fortieth one. Try it for thirty days against a live req rather than a demo profile.

What a week of this actually adds up to

No single message in this workflow reads as dramatically better than a typed one would have — a personalized opener, a fuller screen note, an honest rejection. What changes across a full week is how many candidates get a message that proves someone actually read their profile, and how many hiring-manager updates carry the actual pipeline detail instead of a vaguer one typed short to save time. The broader case for recruiter dictation covers the same ground without one week's reqs attached to it, and a look at what stays private on a machine that never uploads anything is worth reading for anyone who has ever hesitated to paste a candidate's comp expectations into a cloud tool. The same held key applied to a support queue instead of a pipeline and to client correspondence in a law practice cover adjacent versions of the same habit, for anyone whose day mixes recruiting with either.