"Hi ," is one of the fastest ways to show a stranger they are on a list. It happens when a merge tag points at an empty field, and with scraped business leads, empty name fields are normal. Owner names are often not public, and when they are, the match can be wrong.
The fix is not one trick. It is a short routine: find the gaps, decide what each gap should become, and test before sending. You can do all of it today.
Step 1: Find out how many names are actually missing
Before choosing a fallback, look at the data. Open your list (or export it as CSV) and sort by the first name column.
Check for three problems, not one:
- Truly blank fields.
- Junk values such as "Info", "Admin", "Office", "Team", "Sales", single letters or the business name pasted into the name field.
- Formatting issues like ALL CAPS, all lowercase, trailing spaces, or a full name ("Maria Lopez") sitting in a first name field.
Junk values are worse than blanks. "Hi Info," reads as careless, and no fallback rule catches it because the field is technically filled. Clear those cells so they count as blank.
If your source gives a confidence score for owner names, use it. A reasonable rule of thumb: keep names with high confidence, and treat low-confidence names as missing. Calling someone by the wrong name hurts more than not naming them.
Step 2: Choose a fallback that still reads naturally
A fallback is the text that replaces the name when the field is empty. The goal is a greeting that sounds written by a person, not a placeholder.
| Situation | Weak fallback | Better option |
|---|---|---|
| Owner name missing | "Hi there," "Dear Sir/Madam" | "Hi," or start with a line about the business |
| Local service business | "Hello friend," | "Hi {{params.name}} team," |
| Generic inbox (info@) | "Hi Info," | "Hi," plus a request to forward to the owner |
Some practical points:
- "Hi," alone is fine. It is short and normal in business email. "Hi there" is also acceptable, but it is a common mass-mail tell.
- Team greetings work for small businesses. "Hi Bright Spark Electric team," sounds deliberate. Check that the business name is clean first (no "LLC | Best Electrician Near Me" keyword stuffing from listings).
- Avoid cute fallbacks like "Hi friend" or "Hey you". They feel off to someone who has never heard of you.
Step 3: Split the list instead of patching every row
Many sending tools let you set a default inside the merge tag. If yours does not, or you want more control, split the list into two groups and write a slightly different first line for each.
- Group A: names you trust. Greeting uses
{{params.firstname}}. - Group B: no reliable name. Greeting uses "Hi {{params.name}} team," or just "Hi,".
This is the most reliable approach because nothing depends on a fallback firing correctly. It also lets you adjust the body. For Group B, you might add one line: "If you're not the right person for this, could you pass it to whoever handles marketing?"
In GetClient, you can save each group into its own folder in My Leads and run them as two campaigns with the same steps and a different opener. Merge tags must be written exactly as {{params.firstname}}, {{params.name}}, {{params.city}}, {{params.category}} and {{params.website}}, since only that form is filled in when sending. A tag like {{firstName}} or {first_name} will not be replaced.
Step 4: Fix the other merge fields too
Names get the attention, but other fields break the same way. If your email says "I saw {{params.website}}" and the lead has no website, you send a broken sentence.
Go through every tag in every step:
- Website: filter out leads with no site, or use a version of the line that does not mention it. Leads with no website can be a separate offer entirely (see these web design cold email templates).
- City: check for neighbourhoods, postcodes or "United States" in the city field.
- Category: listing categories can be awkward ("Electrical installation service"). Rewrite the sentence so the category sounds natural, or rename it in your CSV with a custom field.
If you are importing a CSV from elsewhere, tidy these columns in a spreadsheet before import. It takes minutes and saves the whole campaign.
Step 5: Preview real rows before you send
Never trust a template preview filled with sample data. Preview the email against actual leads, especially the messy ones:
- A lead with a full, clean name.
- A lead with no name.
- A lead with the longest business name on the list.
- A lead with no website.
Read each one out loud. If any sentence sounds strange, change the copy, not just the data. Check every follow-up step too, since follow-ups often reuse the greeting.
Then send a test to yourself and look at it on your phone. Broken spacing like "Hi ," is easy to miss on a desktop preview.
Step 6: Protect your sending while you test
Missing names often travel with other data problems, like stale or guessed emails. Verify the list before sending, because bad addresses cause bounces that hurt your sender reputation. If bounces are already climbing, work through these high bounce rate fixes.
Start with modest daily volume on any new campaign so you can catch a merge tag mistake before it reaches hundreds of people. This guide on how many cold emails per day covers reasonable starting points. And keep an unsubscribe link in every email, whatever greeting you use.
A quick checklist
- Clear junk names (Info, Admin, Office, the business name).
- Treat low-confidence owner names as missing.
- Split leads into "name" and "no name" groups.
- Write a natural opener for each group.
- Check website, city and category fields for gaps.
- Use the exact tag format your tool fills in.
- Preview real messy rows and send yourself a test.
If you want to build the list and run both versions of the campaign in one place, new GetClient accounts start with free credits. See plans and credits.