Merge tag templates
Personalize Review Requests With Merge Tags
A request that opens with the customer’s first name and names the job you did for them reads like a note from a person, not a blast. Draft that wording below with fill-in slots, then, from Pro, let an automation email it with merge tags so every customer gets their own version.
- Four drafts with slots for name, business and the job
- A fallback line for contacts with no first name saved
- Swap each slot for the matching merge tag in the builder
Draft with slots
Write the request once, with a slot for every detail
Type a sample customer into the fields to see how the email reads with real details. Each word in braces is a slot. In StoryProof, replace it with the merge tag the builder lists for that detail.
- Named job, warm
Sample wording. Works best when the job slot comes from a field you keep up to date.
Subject: [Priya], how did [the boiler swap last Tuesday] go?
Hi [Priya], Thanks again for choosing [Northside Plumbing] for [the boiler swap last Tuesday]. If you were happy with how it went, would you tell other people in a few lines? It takes about two minutes. [review link] Thank you, [Sam]
- Personal sign off, warm
Subject: A quick favour from [Sam] at [Northside Plumbing]
Hi [Priya], I was the one looking after [the boiler swap last Tuesday], and I would love to hear how it has been since. A short note in your own words helps the next customer decide. [review link] Best, [Sam]
What you type stays in this page and is not saved or sent anywhere.
The problem, solved
Where personal requests go wrong, and the fix
- Problem 1
Every customer gets the identical email
A request with no name and no job in it reads like a newsletter, and newsletters get archived unread.
How StoryProof solves it
From Pro, an automation can send emails with merge tags, so one draft becomes a separate version for each contact.
- Problem 2
Some emails would open with "Hi ,"
A slot that has nothing to fill it prints a blank or a stray comma, which looks worse than no name at all.
How StoryProof solves it
An automation can fill in a contact’s name or business name before the email step, and contacts you add by hand can be checked before they are asked.
- Problem 3
Regulars get asked over and over
A personal note loses its charm when the same customer has seen it four times this year.
How StoryProof solves it
Use the review request step for the ask itself: it skips anyone who has already reviewed or was asked recently.
- Problem 4
Not sure which version works better
The warm draft and the brief one both sound fine, and opinions in the team are split.
How StoryProof solves it
An automation can send people down percentage-based paths, so the two drafts run side by side.
- Problem 5
Did the personalised email actually send?
Once it runs on its own, nobody sees the emails go out and problems hide for weeks.
How StoryProof solves it
Automation logs show every enrolment and every step that ran, with the reason a run ended. They are kept for 30 days.
In StoryProof
Turn the draft into a personalised automation
Step 1 of 5
Tidy the contact details first
Look at the contacts the automation will reach. Where a first name or business name is missing, fill it in, or add a step that fills it before any email goes out.
Step 2 of 5
Open an email step in the automation builder
Start from a template or a blank canvas. Work saves as you go and nothing runs until you publish.
Step 3 of 5
Paste the draft and swap each slot
Replace every word in braces with the merge tag the builder offers for that detail. If there is no tag for a slot, such as the job, rewrite the sentence so it reads well without it.
Step 4 of 5
Test on yourself, not a customer
Running a test runs every step for real, emails included. Add yourself as a contact with your own details and run the test on that contact only.
Step 5 of 5
Publish, then read the logs
After the first sends, check the logs for runs that ended early and fix the contact data behind them.
Before you start
What to know before relying on merge tags
Tag names come from the builder
This page does not list StoryProof’s merge tags. Use the ones the builder shows, and do not type a tag you have not seen there.
A tag is only as good as the field
Merge tags print what the contact record holds. A misspelt name in the record is a misspelt name in the email.
Automations need the right plan
Automation emails start on Pro. On other plans, personalise requests by hand.
Email only
Requests go out by email. These drafts are not written for text messages.
Tests send real email
A test is not a preview. Keep test runs to your own address.
FAQ
Questions people ask
Short answers to what usually comes up next.
What is a merge tag in a review request?
A placeholder in the email that is replaced with a detail from each contact’s record, such as their first name, when the email is sent.
What happens if a contact has no first name?
The slot has nothing to print. Fill in the name first, or use wording that does not depend on it, like the no-name draft above.
Can I mention the exact product or job in the email?
Only if a field holds it and the builder offers a tag for it. If not, keep that sentence general rather than guessing.
Should the subject line be personalised too?
A name or job in the subject is often the first thing people see. Test it on your own address to check it reads well in your inbox.
Where can I find more request wording?
The blog has a set of request email templates for different situations. Use them as a starting point and add slots as shown here.
Still have a question? Ask the StoryProof team or book a demo.
Send a request that sounds like you wrote it for them
Draft it once with slots, map the merge tags, and let StoryProof send each customer their own version.
Last updated 2026-11-18.