LinkedIn Outreach Message Scripts That Actually Get Replies

This complements ` (who to target and how to find and track them) and ` (profile setup and overall strategy). This file is the message wording itself: a repeatable structure for turning a cold connection into a scheduled call, adapted here for an Indian exporter writing to an overseas buyer's procurement or sourcing decision-maker rather than a generic B2B pitch.

These are scripts for a human to send manually

Every template below goes into LinkedIn's own message box, typed or pasted by a person, one conversation at a time. Nothing here should be wired into a bot, browser-automation tool, or scheduled bulk-send script — LinkedIn does not support third-party automation of personal messaging, and accounts caught doing it risk restriction. Sales Navigator's own InMail feature is the one sanctioned way to reach people outside your network at volume; a template can be reused across many prospects by hand (swap the name, product, and specifics), which is different from mechanically automating the sending itself.

The overall shape: connect first, pitch second

The mistake that kills a thread fastest is pitching in the connection request or in the very first message after someone accepts. The sequence that actually books calls:

1. Connection request — short or blank, or a one-line note with real context (their product category, a market they source from). No pitch here.
2. First message after they accept — this is where the pitch goes (see the Pain Formula below), not a long warm-up. Keep it to a handful of short paragraphs.
3. They respond — reference something specific, restate the ask, move toward a call.
4. Scheduling — only after they say a call makes sense.

A four-paragraph pitch with a booking link the moment someone connects reads as a stranger asking for a favour; a short, specific message that names their likely problem reads as someone who's done the homework.

The Pain Formula: the core message structure

This is the one structure nearly every template below is a variant of. Two moves in sequence: turn a buyer's *latent* pain (a problem they have but haven't quantified) into a *realized* one (spelled out, with a cost attached), then position yourself as the party who removes it. Every sentence or pair of sentences gets its own short paragraph — a LinkedIn message renders in a narrow chat box on both desktop and mobile, and a dense block of text does not get read.

Base structure: ``` Hi [Name],

I noticed [specific, plausible problem tied to their business — e.g. their current supplier's lead times, a category they are not yet sourcing from India, a cost pressure in their market].

[One line on what you supply and why it addresses that, framed as help rather than a features list. Optionally: "Some of the buyers we already work with in [region] include X, Y, Z" — only if true; never invent client names.]

So if it makes sense to talk, let me know what your calendar looks like.

But if not, who would you recommend I speak with?

Thanks, [Your name] ```

Adapted for export outreach, the "pain" line is almost always one of: price pressure from their current supplier, a supply reliability or lead-time problem, a category or certification gap, or a market shift (e.g. tariff changes, a competitor entering their supply chain) that makes diversifying sourcing to India timely. Keep any numeric claim ("increases X by Y%") honest and specific to your own track record — do not borrow a rhetorical percentage from a script; a made-up figure is a credibility risk the moment a sourcing manager asks where it comes from.

The closing two-line combination ("let me know what your calendar looks like... but if not, who would you recommend I speak with?") does two jobs at once: it asks for a meeting without naming a specific time (so no one can say "that slot doesn't work" and drop the thread), and it gives a non-buyer an easy way to hand you off to the right person instead of just going silent.

Variants: the same structure, a different opening line

Once the Pain Formula's closing and pitch body are set, only the opening line needs to change depending on how you reached the person — everything else stays the same:

• Cold, no shared context — open directly with the pain observation, as in the base template above.
• "Appropriate person" variant — useful when you are not sure who at a company actually owns sourcing decisions: "I'm writing in hopes of finding the person who handles sourcing for [category] — so if it makes sense to talk, let me know what your calendar looks like," then the same pain/solution body, then "if you're not the right person, who would you recommend I speak with?" This doubles as a referral mechanism inside a single message.
• Second-degree connection ("name dropping") — when you share a mutual connection with the buyer but do not want to ask for a formal introduction: connect directly, then open with "I saw we're both connected to [Name] and thought it might make sense to talk," and go straight into the pain/solution body. No need to explain how well you know the mutual connection — that only comes up if the call happens.
• Shared-group opener — if you messaged someone through a group you are both in rather than a direct connection: "I saw we're both members of [group] and thought it might make sense to talk," then the same body.
• Recent-activity opener — if the buyer posted something relevant (an expansion announcement, a note about a supply issue, industry commentary): thank them for the specific post, then move into the pain/solution body. This only works when someone actually posts content; most buyer-side procurement profiles do not, so treat it as a bonus opener rather than a default.
• Event-based opener — for a genuine trigger (a funding round, an award, a new market entry, a trade-press mention): open with a short, specific congratulations line, then the same pain/solution body. Keep the congratulations genuinely tied to something real; a vague "congrats on your success" reads as filler.

Asking a first-degree connection for a warm introduction

When a mutual connection is close enough to make a proper introduction (rather than just being name-dropped), ask them directly rather than assuming they will offer: ``` Hi [Connection],

[One line of context: how you know them, or what you discussed.]

[Name who you would like to be introduced to, and why — e.g. "You mentioned it might make sense for me to connect with [Buyer] at [Company] to explore whether we could supply [category] for them."]

I know you're busy, so I've drafted a short note below you could forward as-is if that's easier — but no worries at all if it's not a good time to make the introduction.

Thanks, [Your name] ``` Making the ask easy to decline, and pre-drafting the forwardable note, both raise the odds of a yes — a mutual connection who feels cornered into an introduction is less likely to make it, and less likely to make it warmly.

Send timing

Based on the observed pattern in this material (not a universal law, but a reasonable starting default): weekday mornings outperform weekends, since most procurement staff check LinkedIn messages as part of a work routine rather than on personal time. Sending in the early part of the buyer's workday, in their local time zone, gives the message a better chance of being near the top of their inbox rather than buried under a day's accumulated messages. Sunday evening (their time) is a secondary window some outbound senders use for reaching more senior people who check email/LinkedIn ahead of the week. None of this is precise — adjust to when a specific buyer market is actually active, and do not over-index on an exact hour.

Follow-up cadence

Most people who do not respond are not rejecting the message — the message got buried, they meant to reply and forgot, or it landed at a bad moment. A working default:

• Wait 3 to 7 days before the first follow-up.
• Send a maximum of three follow-ups per prospect (so four messages total, including the original). Beyond that, more messages rarely convert and start to read as pressure.
• Space each follow-up 3-7 days apart, choosing the shorter end if you are running high volume and want faster signal, the longer end if you are pursuing a smaller number of higher-value target accounts and want to respect their time.
• If there is still no response after the third follow-up, stop for at least a month or two before considering a fresh, differently-angled outreach to the same person — do not restart the same sequence sooner than that.

Follow-up templates stay short and do not repeat the full pitch: ``` Hi [Name],

I hadn't heard back and wanted to check in — if it still makes sense to talk, let me know what your calendar looks like. If not, who would you recommend I speak with?

Thanks, [Your name] `` or, referencing the original value proposition briefly: `` Hi [Name],

Following up on helping you [specific value — e.g. "diversify sourcing for X ahead of your next buying cycle"]. If it still makes sense to talk, let me know what your calendar looks like.

Thanks, [Your name] ```

Converting a "yes" into a booked call

Once someone agrees a call makes sense, close the loop quickly rather than leaving scheduling open-ended, which is where threads quietly die:

• If they already gave a day/time: confirm it and send a calendar invite with a dial-in or video link, and ask for their email and phone number if you do not have them yet (this also raises the odds they actually show up, since a calendar reminder does real work).
• If they said yes without a specific time: offer two or three concrete slots across the coming days (with your time zone and, if crossing time zones with the buyer, a conversion note), and ask for the best number to reach them.
• If you use a scheduling tool (Calendly or similar): share the link directly, and add a fallback line ("if none of these times work, let me know what does") so a buyer with an unusual schedule is not lost.

Common failure modes to watch for

• Pitching too early — selling features or price in the first message instead of naming a problem and asking for a conversation. This is the single most common reason a thread dies immediately.
• Overlong messages — LinkedIn's chat window is narrow on both desktop and mobile; a wall of text does not get read to the end. Keep every paragraph to one or two sentences.
• Fabricated social proof — inventing client names or exaggerated statistics to sound more credible. Buyers doing real diligence check; a caught exaggeration ends the relationship before it starts. If you have no clients yet, either drop the social-proof line entirely, or (only if literally true) reference companies you are actively in conversation with rather than claiming them as clients.
• Following up too aggressively — messaging daily, or past the three-follow-up cap, reads as pressure rather than persistence and increases the odds of being blocked or reported.
• Treating a template as one-size-fits-all across unrelated buyer segments — the same message can be reused across many buyers within one tightly defined ICP (see ``) because they share the same underlying pain, but reusing a spice-buyer message verbatim on a machinery buyer will read as generic and untargeted. At minimum, tailor to industry plus the specific pain.

The through-line

The mechanics above are simple by design — a short pain-and-solution message, an easy-to-answer close, a disciplined follow-up cadence — because the actual work is upstream, in defining the right buyer and finding the real pain worth naming (see ` and `). A well-targeted message using this structure will outperform a cleverer-sounding message sent to the wrong person every time.