A Bulk Personalization Run You Can Trust

What it is for

Bulk personalization fails silently: a bad URL yields a fluent sentence about the wrong company, and nobody notices until two thousand people have read it. This is the QA discipline — sample first, tag failures by type, approve into a separate column, suppress empty rows — for running an enrichment pass at scale. Use it before pushing generated lines into a sending tool.

The skill Copy

Fix the list before you generate anything: one row per person, a profile or
page URL that resolves today, the company name spelled the way they spell it. A
dead or mismatched URL does not return an error — it returns a confident
sentence about the wrong person.

Run twenty rows first and read all twenty. Count how many you would put your
own name on. Under fifteen, stop — the problem is the source column, not the
wording.

Tag each failure by type, because each has a different fix:
- wrong person or wrong company -> list problem
- true but generic -> weak source material; feed it something else
- outdated (old role, old funding, old product) -> stale source, re-check
- invented detail -> that row had nothing to work with; drop the prospect

Then set the rules for the full run:
- Every row needs a human-approved cell before it can send. Approve into a
  separate column and merge from that column, never from raw output.
- No row sends with an empty personalization field. Suppress it rather than
  falling back to "Hi there, hope you're well" — an empty merge variable in the
  first sentence is the loudest failure in cold email.
- Spot-check five percent of the finished run against the live page, with an
  eye on numbers, headcount, funding and titles.

Release in batches and read the first batch's replies before sending the rest.
Replies tell you what a sample cannot: whether the line felt researched or
harvested.

Keep the rejected rows. They are the cheapest description you will ever get of
what your source data is missing.

How to install it Copy

1. Open the tool and start a new conversation, project or template.
2. Paste the text below wherever the tool keeps standing instructions
   — usually called system prompt, instructions, or persona.
3. Save it so it applies to every run rather than a single message.

Did it work for you?

Where it came from