What to Put in a Cold Message So It Gets Answered

Why does a template read as a mass send before the first line ends?

A recruiter who has seen the same opening line a dozen times this week recognizes it instantly, and the recognition happens before your actual point arrives. A model returns the median instance of whatever genre you ask it for, and the entire value of a cold message was always in being non-median. Ask it for a generic outreach message and it hands you the same generic outreach message everyone else is also sending.

• The tell isn't AI. It's the shape: no name, no specific project, an ask that could go to anyone in the industry.
• What survives. One line that could only be about this team or this person, because you actually looked.

The volume behind this is real, and employers are told nearly the same thing from their side of it: why applications per opening tripled this year, and how many of them are real walks through the arithmetic a candidate is competing inside. Candidates submitted 356 million applications on Workday's recruiting platform in 2024, up 26 percent, while the jobs its customers posted grew 7 percent ¹. Reaching out was supposed to be the escape hatch from that math, and in a Greenhouse survey of 2,900 job seekers, nearly half said they were sending more applications than a year earlier ².

That is the exact pressure that turns a genuinely good idea, writing a real person a real message, into another mass-produced format. The idea still works. It just stopped working as a shortcut you could run at scale, because scale is what broke the resume pile in the first place, and a recruiter's inbox is downstream of the same math.

What does a message actually need to say?

Three sentences: who you are in one line, the specific thing about this team or role that made you write, and what you're asking for. Nothing in that structure requires length, and length is usually where a template hides its own emptiness. A recruiter reading a hundred of these a week rewards the one that gets to the specific line fastest.

• Line one: who you are, in a phrase, not a paragraph.
• Line two: the specific thing you noticed, named precisely enough that it couldn't be about a different team.
• Line three: the ask, small enough to say yes to in one reply.

The most common uses of a model in a job search are already this shape. In a Greenhouse survey of more than 2,200 workers and job seekers, interview prep and analyzing a posting for skills to highlight were the two most common, ahead of having an agent apply on a candidate's behalf ³. The honest use of a tool here matches that pattern: sharpen a draft you already wrote, don't outsource the noticing that made it worth writing.

A useful check before sending: read the message once as if you were the recipient, and ask whether it tells you anything you couldn't have guessed about the sender. If the answer is no, the specific line hasn't landed yet, no matter how polished the sentence around it has become.

Ask for something small enough to answer in a line

The size of the ask decides whether answering costs the recipient anything. "Can you tell me one thing about how the team actually uses AI day to day" can be answered in one line from a phone. "Can we hop on a call this week" asks a stranger for a block of their calendar on a first message. Match the ask to the relationship you actually have, which for a cold message is none yet.

• Too big. A call, a coffee chat, a referral, on message one.
• Right-sized. One specific question a person can answer in two sentences from their phone.

A referral and a cold message are not doing the same job, and it helps to be honest with yourself about which one you're sending. A referral moves you out of the queue entirely; a well-written cold message, at best, moves you up within it. Neither replaces the application itself, and neither one is owed a reply just because you sent it.

Knowing which one you're actually attempting changes what a good outcome looks like. A cold message that gets a two-line answer and nothing more has still done its job: it put a name to a face before an application landed in the same queue as everyone else's. Treat that as a win, not a stall, and you'll send fewer messages out of disappointment and more out of an actual reason.

When should you not send a message at all?

Skip it when you don't have a real, specific reason for writing to this person, because a message built entirely on hope reads exactly like the templates it's trying not to sound like. Skip it too when the role is closed, when you've already messaged this same person about a different role in the last month, or when your only reason for writing is that you found their email address.

• No specific reason. Don't send it. Apply through the normal path instead.
• Recently messaged the same person. Wait. Don't repeat the ask.
• Nothing to ask for. A compliment with no question isn't a message. It's noise.

The same test that catches a generic cover letter catches a generic cold message: would this line survive being sent to someone else at a different company? Why an AI-written resume ends up sounding like everyone else's is the same convergence problem wearing a different format. Fix it the same way, with one fact only this message could contain.

Send a true message, to someone you have an actual reason to write to, asking for something they can answer without much cost to their day.

See a sample report >