$ man how-to/heyreach-messaging-templates

MCP Serversintermediate

HeyReach Messaging Templates

Connection request notes, follow-ups, and personalization variables that convert

by Shawn Tenam


PATTERN

Connection Request Note Framework

Under 300 characters. That is the hard limit. Use it as a constraint, not a limitation. Structure: [relevance hook] + [implicit offer]. No introduction. No pitch. No "I would love to connect." Examples that work: "Saw your team just opened a Dubai office. We help companies nail GTM in new markets. Happy to share what is working." "Noticed you are scaling the SDR org. Built a system that handles this. Might be useful." "Your post on outbound metrics was solid. Running similar experiments on our side." Examples that fail: "Hi {first_name}, I am Shawn from Lead Alchemy. Would love to connect!" "Impressed by your background. Let us connect." "I have a solution that could help your team."
PATTERN

Follow-Up Message Templates

Message 1 (after acceptance, day 2-3): Thank them. Deliver value immediately. A relevant resource, insight, or observation. Not a pitch. "Thanks for connecting. I put together a breakdown on [specific topic relevant to their role]. Might be useful given what you are building at {company_name}. Here is the link." Message 2 (no reply, day 5-7): New angle. Reference something specific about their business. Add context, not pressure. "Also noticed {company_name} just [specific signal: hired, launched, expanded]. Seeing similar patterns across [their industry]. Happy to compare notes if useful." Message 3 (final touch, day 10-14): Light, respectful, no guilt trip. "No worries if the timing is off. The offer stands. Happy to reconnect when it makes sense." Three messages after acceptance. Then stop. Respect the inbox.
CODE

Personalization Variable Mapping

HeyReach supports variables from your CSV upload. Standard variables: {first_name}, {last_name}, {company_name}, {title}. Custom variables from enrichment data: {industry}, {employee_count}, {funding_stage}, {tech_stack}, {recent_signal}. Map these from your Clay or Apollo export columns to HeyReach custom fields during CSV upload. The personalization ladder: Level 1 (minimum): {first_name} + {company_name} Level 2 (industry): Reference their industry challenges using {industry} context Level 3 (company): Reference company signals using {recent_signal} or {funding_stage} Level 4 (person): Reference their content directly. Hard to automate. Reserve for top accounts. For scale campaigns, levels 2 and 3 are the sweet spot. Specific enough to feel personal. Automatable enough to run at volume.
PRO TIP

Copy Principles for 2026

Write like you text, not like you email. Short sentences. Casual. No "I hope this message finds you well." One idea per message. First message covers the value. Second covers a new angle. Third is the close. Do not cram all three into one message. Questions outperform statements. "How are you handling [challenge]?" opens conversation. "We solve [challenge]" closes it. Match their energy. Casual LinkedIn profile gets casual messages. Corporate profile gets professional messages. Tone alignment builds trust. No attachments in first two messages. LinkedIn flags automated accounts that send links immediately. Build the conversation first.

related guides
HeyReach LinkedIn AutomationHeyReach Campaign SetupHeyReach Routing LogicHow to Build Cold Email Infrastructure from Scratch
← how-to hubclay wiki →
ShawnOS.ai|theGTMOS.ai|theContentOS.ai