The Comment Capture Funnel

Hey team — hope you’re ready to smash it this week 👊

One post. 1,155 comments. An agent turned 184 into qualified DMs and 41 booked calls—within a day.

Most teams still hope comments turn into pipeline. This issue shows how to engineer it.

Why this works

• Public reply creates belief. DM creates movement.

• Signals over volume. Prioritise buyers who comment, ask, or reference launches/hiring.

• Small asks win. 5-line DMs and a 9-minute bridge beat walls of text.

First things first, you need the right message:

The 7 Flows (with scripts)

1) Case study post → proof reply → DM handoff → 9-min bridge

• Public reply: “{name}, the lift came from two exact slots + 9-min cap. I’ll DM the bridge checklist now.”

• DM handoff: “Here’s the bridge checklist: {link}. Want a quick 9-minute run-through? Tue 10:15 or Wed 14:00?”

2) Poll → segment by vote → tailored DM

• Public reply (to option A): “Got your vote—DM’ing the opener template you chose.”

• DM handoff: “Your A-variant: {link}. Want me to show timing + ask in 9 minutes? Tue 10:15 or Wed 14:00?”

3) Authority thread → micro-win reply → asset drop → calendar CTA

• Public reply: “Swap ‘when works?’ for two slots—reply jumps. DM’ing the lines.”

• DM handoff: “Lines here: {link}. I can map this to {company} in 9 mins—Tue 10:15 or Wed 14:00?”

4) Launch announcement → priority tag (customers vs prospects) → demo invites

• Public reply: “Congrats on the drop—these two bumps booked 9 demos last launch. DM’ing both.”

• DM handoff: “Bumps inside: {link}. Hold 9 mins to place them in your launch week? Tue 10:15 or Wed 14:00?”

5) Hiring post → vendor sort → “pilot scope” DMs to buyers

• Public reply: “While you hire, this 2-week pilot fills the gap. DM’ing scope.”

• DM handoff: “Pilot scope: {link}. Want a 9-min walkthrough to tailor for the new role? Tue 10:15 / Wed 14:00?”

6) Event recap → attendee replies → 90-sec Loom follow-ups

• Public reply: “Saw you at {event}—comment→DM handoff booked 7 calls for us. DM’ing the lines.”

• DM handoff: “Handoff lines: {link}. Prefer a quick 9-min run-through so you can deploy this week?”

7) Before/after carousel → proof-tile reply → two-slot close

• Public reply: “Proof tile + two-slot close beats links. DM’ing the tile.”

• DM handoff: “Tile + copy: {link}. 9 minutes to show placement? Tue 10:15 or Wed 14:00?”

Live SOP (what to do the first 2 hours)

1. Watch comments in two windows: 0–60 and 60–120 minutes after posting.

2. Reply publicly within 10 minutes; promise an asset.

3. DM immediately with the asset + a small question (or straight to the 9-min bridge if intent is clear).

Five public-reply swaps (rotate):
“Sent the checklist—check DMs.” · “DM’ing the playbook now.” · “I’ll drop the lines in your inbox.” · “Great q—DM’ing answer + template.” · “Thanks {name}! I’ll DM the guide.”

Follow-up cadence (keeps it human)

• D0: Public reply → DM asset

• D2: Nudge with choice: “90-sec overview or 9 mins live? Tue 10:15 / Wed 14:00”

• D4–5: Proof bump: “This booked 9 demos last week. Hold 9 mins?”

• D7–10: Decision: “Lock 9 mins (Tue 10:15 / Wed 14:00) or I’ll park it.”

9-minute bridge line (copy/paste):
“Happy to keep this tight—9-minute run-through so I can show the 3 steps live. Tue 10:15 or Wed 14:00?”

Swipe pack (use verbatim)

• DM handoff (neutral): “Here’s the {RESOURCE}: {link}. Want the quick 9-minute version?”

• Thanks reply → soft push: “Glad that helped 🙌 If useful, I can show how teams use this in 9 mins—keen?”

• Info-only ask: “Short version: we book ~10 calls/week from LinkedIn by pairing public replies with 5-line DMs and a 9-minute bridge. Want the 9-min run-through? Tue 10:15 / Wed 14:00.”

Have a great week — reply and tell me which framework you’ll test first.

— Jack C. @ Team Prosp 👊

P.S Struggling to consistently book calls from LinkedIn?

• Sends AI personalized DMs

• Sends custom voice notes whilst you sleep

• Finds leads from LinkedIn search, sales nav, events, groups and post engagement.

• Turns content → booked calls