How to personalise direct mail at scale

Written by Autopen Australia · Updated 23 August 2026

The greeting is the worst place for it

“Dear Sarah” proves only that you have a first-name column. Every piece of marketing mail Sarah has received this decade started that way, and it is recognised as automation rather than attention.

A specific detail in the third sentence does the opposite. It is not where the reader is looking for a merge field, and it demonstrates something a database lookup cannot fake: that the letter was sent for a reason connected to them.

Fields worth merging

• Their street or suburb. The strongest field in property and any locally-delivered service.
• A specific transaction. What they bought, when, which branch, which adviser.
• A date that belongs to them. Renewal, expiry, service due, anniversary of joining. It gives the letter a reason to exist today.
• The name of the person who dealt with them. Not the firm — the individual.

Fields not worth merging

• Anything inferred. Estimated income, presumed life stage, probable household composition. Wrong often enough to be memorable, and unsettling when right.
• Anything bought from a broker. The recipient never gave it to you, and referencing it invites exactly the question you do not want.
• Titles. Mr, Mrs, Dr, Ms. High error rate, and getting it wrong is the fastest way to lose a reader in the first line.
• Anything sensitive. Health, finances in detail, family circumstances. Someone else may open the envelope.

Write the sentence so every row works

The usual failure is a sentence built for the median row. Then row 4,182 has “SMITH FAMILY TRUST” in the first-name column and the letter says “Dear SMITH FAMILY TRUST”.

Three rules that prevent most of it:

1. Never place a merge field where its length changes the layout. A three-letter suburb and a twenty-eight-letter suburb both have to sit comfortably.
2. Never require a field to be grammatically specific. “Your [product] is due” breaks the moment the product is plural.
3. Never merge into the first four words. If it is wrong, you have lost the reader before they reach anything else.

Fallback rules, which are not optional

Every merge field needs an answer to “what if this is empty, or garbage?” In order of preference:

1. Drop the sentence. The letter reads fine without it and nobody can tell anything was omitted. Nearly always the right answer.
2. Substitute a general version. “in your area” instead of the street name. Weaker, but valid.
3. Drop the recipient. If the letter only works with the field, and the field is missing, do not write it. You have saved the cost of a piece that was going to underperform anyway.

What is never acceptable is a blank, a bracketed placeholder, or the word “null”. Ask for the fallback rate before production — if 30% of your file is hitting a fallback, the field is not worth merging.

Proof against the extremes

Before writing begins, look at the letters produced by the longest value in each field, the shortest, the empty one, the all-capitals one and the one containing punctuation. Five letters. Ten minutes. It catches nearly everything.

Why handwriting raises the stakes

In printed mail, a merged field is visibly a merged field and readers forgive it. In a handwritten letter there is no visual seam — the merged words are written by the same pen in the same pass — which means the reader has no cue that a machine was involved, and no reason to forgive an error.

That cuts both ways. Done properly it is the most convincing personalisation available. Done carelessly the mistake reads as carelessness by a person, which is worse than carelessness by a system.

How we handle merged fields.