Write messages that get replies (and use merge fields)
How to personalise each message with the lead's name and company, what happens when a detail is missing, and what good length looks like.
A good first message is short, specific and sounds like you. HeyLeads helps by filling in details for every lead and by showing you exactly what each lead will receive before anything goes out.
#Merge fields
A merge field is a placeholder in double curly brackets that turns into something about the lead. Above the text box you will find a row of chips: press one to insert it where your cursor is.
| Field | Becomes | Suggested fallback |
|---|---|---|
{{first_name}} | Their first name | there |
{{last_name}} | Their last name | (nothing) |
{{full_name}} | Their full name | there |
{{company}} | Their company | your company |
{{title}} | Their job title | your role |
{{headline}} | Their LinkedIn headline | (nothing) |
{{location}} | Where they are | your area |
{{email}} | Their email, when you have it | (nothing) |
Columns from your own CSV import (and details collected from a post, such as the post link) can be used by their lowercase name, for example {{post_url}}. Give those a fallback too.
#Always add a fallback
Some leads will not have a company or a title. Write the fallback after a vertical bar, like {{company|your company}}, and HeyLeads uses it when the detail is missing. The chips add a sensible fallback for you.
#Check it for three different leads
Under the text box, the preview shows the message as a real lead would see it. Flip between the sample leads to check that the message still reads well when a name is long or a company is missing.
#How long should it be?
- A message has a meter below it. Under about 600 characters is comfortable: easy to read in one go. Past that it tells you it is getting long, and a very long one is flagged as an essay.
- For a longer story, split it across two messages with a short wait between them. See Send several messages in a row.
- A connection note can be up to 300 characters. Keep it short and human. A request with no note often works just as well, so it is worth an A/B test.
#What makes a message work
- Lead with them, not you. One specific thing about their work or company beats a paragraph about yours.
- One idea, one question. A single easy-to-answer question gets more replies than three offers.
- Do not promise what is not there. If a message says here's my calendar or here's the link, put the real link in it. The checks warn you when a message promises a link and has none.
- Do not pitch in the invitation. Save the ask for after they accept.
- Write the way you talk. Read it aloud. If you would not say it, change it.
- Test one thing at a time. Change only the opener, or only the note, so you know what made the difference.
Can I use AI to rewrite a message?
In a campaign, Describe it drafts the messages for you. In the Inbox, Suggest reply and the rewrite options help with live conversations. See Suggest replies and rewrite with AI.
What does {{first_name|there}} do?
It writes the lead's first name, or the word there if the name is missing, so the message reads Hi there, instead of failing.
Why did my message not send to one lead?
The most common reason is a merge field that was empty for that lead and had no fallback. Add a fallback after a vertical bar and the lead moves on.