Automated personalized emails are automatic messages that change their content based on what you know about each recipient, so a mortgage client and an agency prospect receive different words from the same workflow. Personalisation beyond the first name is what makes an automated email feel like it was written for the reader. This article answers one question: how to use contact fields, tags and workflow branches on the levelpartner.ai platform to personalise an automated email properly, and where personalisation becomes a liability.
Three levels of personalisation
Most firms stop at level one. The useful work happens at levels two and three.
Level one is merge fields: the first name, company name or account owner inserted into the text. It is expected now, and it is noticed only when it fails.
Level two is field-driven content: a sentence or paragraph that changes based on a custom field, such as the service the contact enquired about, their industry or their region. The email structure is the same; the substance differs.
Level three is branch-driven messaging: the workflow sends a completely different email depending on what the contact did or who they are. A prospect who downloaded a pricing guide gets a different follow up from one who booked a call.
What you need in the data
Personalisation is only as good as the contact record. Before writing a single email, check which fields are reliably filled. A field that is empty on half your contacts will produce half-finished emails.
The fields that matter most for a service firm are usually the service of interest, the industry or type of client, the account owner, the source of the lead and the stage in your pipeline. All of these can be captured by forms and updated by workflows without anyone typing them in.
Before you start
- A list of the custom fields you will personalise with, each checked for how many contacts have it filled.
- Forms that capture those fields at the point of enquiry.
- A fallback value for each merge field, for contacts where it is blank.
- A clear reason for each personalised element. If it does not change what the reader does, leave it out.
How to set it up
- Go to Settings, then Custom Fields, and click Create field.
- Choose a Field type and enter a Field name, such as Industry.
- Click Create custom field, then repeat for service of interest.
- In Sites, open your enquiry form and add both custom fields.
- In Automation, create a workflow with a Form Submitted trigger.
- Add an If / Else action and choose Build My Own.
- Select the Industry field, an operator and a value.
- Click Add Branch for each further industry.
- On each branch, add a Send Email written for that industry.
- Insert custom values for first name and service of interest.
- Use the None branch for a general version.
- Run Test Workflow once per branch, then publish and save.
Personalising for four industries without writing four sets of everything
Write one core email that is true for everyone, then personalise only the paragraph that matters. For agencies, that paragraph might mention client retention. For consultants, utilisation. For mortgage brokers, the volume of applications in progress. For real estate, instructions and valuations.
The rest of the email stays shared. This keeps the number of versions you maintain small, which matters when your service or pricing changes and every version needs updating.
Suppose the firm writes one welcome email with a single industry-specific paragraph, giving four variants. If each variant takes ten minutes once the core email exists, that is forty minutes for all four. Writing four fully separate emails would take roughly four times as long and leave four documents to keep current. The timings are rough guesses used to make the comparison.
What it replaces
It replaces the generic auto-reply that says the same thing to everyone, and the salesperson who rewrites that auto-reply by hand for important leads. With branching, the important context is already in the first email, and the salesperson's time goes on the call.
The time it takes each week
Very little after launch. The ongoing task is data quality: a monthly check that new contacts are arriving with the personalisation fields filled. If a form changes and stops capturing a field, emails quietly fall back to generic content.
The mistake most people make
Over-personalising with data the contact did not knowingly give you. Mentioning that someone visited your pricing page three times reads as surveillance. Personalise with what they told you on a form, what stage they are at with you, and who their contact is. Leave behavioural detail to drive which email they get, not what the email says.
Leaving no fallback. "Hi ," at the top of an email tells the reader exactly how automated it is. Set a fallback such as "Hi there" on every merge field.
When not to use it
Do not build branches for segments with only a handful of contacts. If three people a year enquire from a niche industry, they can receive the general version. Branches cost upkeep, and they only pay off where there is volume.
If you are writing the copy for these variants, our email copywriting examples show how one idea reads in different tones. For the wider strategy of which automated emails to run, read the guide to automated email marketing. The same personalisation logic applies to the yearly automated birthday email.
Troubleshooting
Merge fields show the raw placeholder text. The field name in the email does not match the custom field. Reinsert it from the field picker rather than typing it.
Everyone goes down the same branch. The condition is checking a field the form does not populate, so every contact looks blank. Check the form mapping.
Industry values are inconsistent. Free-text fields produce "real estate", "Real Estate" and "property". Change the form field to a dropdown so values are consistent.
Contacts in the US get British phrasing. Add a branch on country and keep a US version of any paragraph where spelling or terms differ.
Frequently asked questions
Is first-name personalisation still worth doing?
Yes, as a baseline. It is expected, and its absence is noticed. Just do not mistake it for real personalisation.
How many variants of one email is too many?
If you cannot remember what each variant says, you have too many. Four or five is a practical ceiling for most firms.
Can AI personalise each email individually?
AI content can draft variants, but each version should be reviewed before it goes into a workflow. Fully individual AI-written emails sent without review are hard to control and hard to audit.
Does personalisation affect deliverability?
Not directly. It helps indirectly because people open and reply to relevant emails, and engagement supports inbox placement.