Messages show blanks or the wrong name
How merge fields like {{first_name}} work, why a lead's message may wait, and how to add fallbacks.
Messages use merge fields written in double curly braces, such as {{first_name}} or {{company}}. HeyLeads fills them in from each lead's details when the message goes out.
#Add a fallback
Put a | and the backup text inside the braces. If the value is missing, the backup is used.
| Write | What goes out |
|---|---|
{{first_name}} | The first name. If it's missing, the message is held for that lead. |
{{first_name|there}} | The first name, or there when it's missing: Hi there, |
{{company|}} | The company, or nothing at all. An empty fallback means the field is optional. |
\{{ and \}} | A literal {{ or }}, if you really need the braces. |
When a field ends up empty, HeyLeads also tidies the space and comma around it, so you don't get Hi ,.
#Fix a missing value
Open the lead in Leads
Check whether the name, company or the field you used is actually filled in.
Fill it in, or fix the import
When you import a CSV, map each column to the right field or choose Keep as custom field. Your own columns become custom fields, named in lower case with underscores (a column called Funding Stage becomes
funding_stage).Or change the message
Add a fallback with
{{name|fallback}}, or remove the field from the step.Preview before you launch
Use Preview in the builder to see the message as a lead will get it.
The field shows literally as {{first_name}}.
It was written with different braces or a typo (such as a single brace or a space in the name). Names are letters, numbers and underscores only. The builder flags malformed placeholders before you launch.
AI wrote the message. Do the same rules apply?
Yes. AI-written steps use the same fields, and you can edit them in the builder before launch.
Which fields exist by default?
First name, last name, full name, headline, job title, company, location, email and the LinkedIn link, plus any custom field you imported.