Personalization people can tell

A scraped first line is not relevance. The note has to be about the situation, and every fact has to be one you can open.

Most of what gets called personalization is a first line about the person, pulled from a profile, then pasted onto the same email. Readers recognize it. The reply rate rarely moves. The rest of the note is a template the team has used for a year, with the company name swapped in.

Buyers have now seen that pattern enough times that the compliment works against you. It says a tool wrote the opening, and that the sender did not have a reason to write today. A custom first line on a generic email is still a generic email.

The first line people recognize

“I noticed you posted about X” has become its own template. So has the funding round, the new job title, and the podcast appearance. Each of those used to signal that a person had looked. They now signal that a scraper ran. The reader does not reward the effort. They file the note with the other notes that opened the same way.

A compliment is not a reason

A scraped compliment is about the person. It praises a post, a headline, or a logo, then turns into a pitch that could have gone to anyone in the segment. The reader can feel the hinge. The first sentence is specific. The second sentence is the product. Nothing in the middle connects the two, so the specificity reads as decoration.

That decoration is expensive. Someone paid for the data, the model, and the review, and the reply rate stayed where the plain template was. The team then concludes that personalization does not work. What failed was the kind of personalization. The mail was still about the sender.

Relevance is the situation

Relevance is different. It is about the situation: a role just opened, a public complaint in their market, a change that creates a specific job. The reason belongs in the email because it explains why this note, to this company, this week. If you removed the person’s name and the sentence still only made sense for them, you have a reason. If it would fit the next fifty rows, you have a merge field.

A shorter list with that reason beats a long list with a custom first line. You will send less. The notes you do send will be ones you can defend if the buyer replies and asks where you saw it.

Check the claim before you send

If the model invents the reason, you have a worse problem than spam. You have a false email in a buyer’s inbox. A wrong funding round, a job they left, or a quote they never said is not a small miss. It tells the buyer you did not look, and it is the kind of miss people forward to their team.

Check every concrete claim against a source you can open. The source can be the CRM record a colleague updated, a page on their site, or a job post that is still live. If you cannot open it, do not write it. A plainer true sentence beats a vivid false one.

What to write instead

Start from the job the situation creates, not from the biography. Name the change in one sentence. Say what you do about that change in the next. Ask for one thing. Leave the rest of the product for the reply.

Keep a person on the approval when the draft came from a model. The person’s job is to reject any fact they cannot point at. Sendblox is built for that path: the CRM stays the source of the record, the offer stays inside a structure you approved, and nothing sends until someone has read it.