The AI keyboard for LinkedIn messages and outreach.

LinkedIn is not Slack with a navy header. A sloppy Slack status costs you a clarification ping. A sloppy InMail costs you a role, a candidate, or a relationship you cannot unsay because the other person keeps the transcript in their recruiting CRM. I shipped Work mode’s Professional and Question tones with that asymmetry in mind. This page is for recruiter replies, outbound that does not read like a sequence, and InMail-shaped professionalism on a phone. It does not cover channel status updates. If you wanted those, go to KOPY for Slack.

I also refuse to pretend LinkedIn writing is “content.” Most of the money in the inbox is one-to-one. Recruiter ping. Hiring-manager follow-up. Warm intro you have been sitting on because the first sentence felt either desperate or icy. The recruiter reply examples on the blog are the copy-paste layer: interested, not now, need details, re-engage. This article is the keyboard layer — how I generate a version that matches the actual message I copied, not a universal template that a sourcer has seen 400 times this week.

The cost of getting it wrong is not theoretical. Grammarly and The Harris Poll (2022) put poor communication at about $1.2 trillion for U.S. businesses, with leaders estimating 7.47 hours per week lost and about $12,506 per employee per year. Recruiting is a communication business wearing a jobs-board costume. Every extra loop — “can you send a resume PDF even though it’s on my profile,” “what’s the comp band,” “are you actually hiring for this” — is that 7.47 hours showing up as a candidate who goes dark.

The 2024 Grammarly / Harris work is the part I quote when someone says “just write longer.” Knowledge workers already spend about 19.08 hours per week writing, and 100% of surveyed knowledge workers report weekly miscommunication. Generative AI’s hypothetical $1.6 trillion productivity save is not a license to spray AI sludge into InMail. It is a statement that the writing load is already too high. LinkedIn is where people respond to that load by pasting the same three sentences. Recipients learned to filter that. Work mode only helps if the draft is specific to the message on the pasteboard.

LinkedIn’s Economic Graph research is the labor-market backdrop, not a vanity user count for KOPY. Hiring is lumpy, titles drift, and a recruiter’s first message is often a template because their ATS demands speed. Your job as the recipient — or as the sender on a small team without an ATS crutch — is to answer like a person who read the actual line they wrote. That is a keyboard job. Leaving LinkedIn for a chatbot and pasting back is how the polish gets there and the specifics die.

The five recruiter intents I actually see

Almost every inbound recruiter message is one of five intents. If you generate before you classify, Professional will produce a warm fog that commits you to a call you do not want.

1. Exploratory: “open to a conversation” with no role, or a role that is a mash of three jobs. Question first. Ask for scope, location/remote policy, and what “senior” means in their org.
2. Specific req: a title, a team, sometimes a JD link. Professional + one concrete hook from the message (“the infra migration you mentioned”). Agree only if you will take the call this week.
3. Comp-first fishing: they want your number before they have a role. Question. I do not put a number in a generated first reply on a phone while walking. That number follows you.
4. Network maintenance: they liked a post or a mutual. Continue is for staying in the graph without fake enthusiasm. One sentence of thanks, one sentence of what you actually work on, no fake “would love to pick your brain.”
5. Wrong person: they think you still do a job you left. Professional decline, one line of what you do now, optional referral if you mean it. Do not generate a maybe.

The blog templates map onto this: interested / not interested / not now / need info / re-engage. Work mode’s contribution is filling the brackets from the copied text so you are not sending “especially the [specific detail]” with the brackets still in it.

Outbound that does not smell like a sequence

If you are the sender — founder, hiring manager, or AE who should be on the sales page instead if this is a pipeline SLA — the rule is inverted. Recruiter-style outbound dies when sentence one could apply to anyone with the same title. Copy their note, their post, or the one line from their profile that is not “passionate about synergy.” Generate Professional. Then delete every clause the model added that you cannot point at with a finger on the screen.

I use Question for outbound when I am asking for 15 minutes and I have not earned a pitch. The draft should contain one observed fact and one ask with two time windows or a Calendly you already trust. Agree is the wrong tone for cold outbound; you are not agreeing with anything yet. Continue is for the second touch after they viewed and did not reply: one new fact, not a guilt trip about “just bumping this.”

Tone recipes that stay InMail-shaped

InMail-shaped means: greeting, one proof you read them, one intent, one next step, sign-off that does not say “bestest.” It is shorter than email and more formal than Slack. People who write Slack into LinkedIn sound like they wandered into the wrong building. People who write email into LinkedIn sound like they are serving a subpoena.

• Professional: default for inbound recruiter when you are at least curious. Keep it under 90 words on mobile. If the draft is longer, you are writing a cover letter in a DM.
• Question: default when the JD is missing, the company has three products, or they used “competitive compensation” as a personality. Three questions max. More than three is a screening call they will ignore.
• Agree: you will take the intro or the call. Name two windows or ask them to send a calendar link. Agree without a time is how threads die in “sounds great.”
• Continue: the thread already has a yes and needs a recap: role family, location constraint, who joins the next call. This is the message recruiters wish candidates sent so they can update Greenhouse without decoding vibes.

I do not use Work mode to write thought-leadership comments. That is a different product impulse and it shows. If you comment “Great insights!” with a generated paragraph under a stranger’s post, you have paid me and still looked like a bot. Save generation for messages with a recipient who asked you something, even if the ask was implicit.

KPI table: LinkedIn inbox, not a content calendar

These KPIs are for people who live in messaging, not people optimizing impressions. If your LinkedIn job is posting carousels, this table will feel like the wrong sport. Good.

KPI	Definition on LinkedIn	Failure pattern	Work mode move
Time-to-send	Hours from recruiter or hiring-manager inbound to a classified reply (yes / no / not now / questions)	You wait until you are at a laptop because the first sentence felt high-stakes	Copy the InMail, Professional or Question, send the classification the same commute
Clarification loops	Back-and-forth that exists because you did not state location, timing, or interest level	Three messages to learn the job is on-site five days	Question tone up front; do not Agree into a mystery onsite
Meeting scheduled	Screens or intro calls that actually land on a calendar	“Happy to chat” with no times; both sides wait	Agree + two windows, or ask them to send the link
Deal follow-up lag	Days a warm intro or candidate thread sits after a “let’s reconnect next month”	You meant next month; they assumed you ghosted	Continue on the date you promised, with one new fact, not an apology essay

Deal follow-up lag here is relationship lag, not quota lag. If you are working a commercial pipeline with an SLA, sales follow-ups is the page. Mixing recruiter manners into outbound sales copy is how you get “hope you’re well” on a deal that needed a close plan.

Mobile procedure, including Full Access

LinkedIn’s composer is a normal iOS text field. KOPY sits there like any keyboard. You still have to copy the inbound message first. LinkedIn sometimes copies the whole profile card; trim before you generate. Apple’s custom keyboard rules still apply: Full Access if you want the extension to read the pasteboard and call the model. Setup is the same dance I documented for extensions in general. Do it once. Then the high-stakes inbox is not a laptop-only room.

Edit rules I use on LinkedIn drafts:

• Delete compliments the model invented about their “impactful journey.”
• Replace any company mission restatement with a fact from their message.
• Never let the draft accept a role, salary, or start date you have not decided.
• If you are declining, keep one door: a referral or a month when you might reopen. Only if true.

For longer written offers, comp discussions, or anything that will be forwarded to a lawyer, leave LinkedIn. That is Gmail or Outlook, and I would still generate a first draft — see AI work email on iPhone — but I would not negotiate numbers inside a DM keyboard on the sidewalk.

What this page is not

It is not a growth-hack for connection-request spam. It is not a replacement for reading the JD. It is not Slack tone. Hybrid teammates who bounce from LinkedIn recruiting to Slack staffing should keep the voices separate and use the remote-work pillar for routing. I built one Work mode because the underlying sentences share a spine — owner, date, ask — but the skin is different. LinkedIn skin is slower, named, and on the record in someone else’s ATS. Write like that, even when you only have a thumb.