A personalisation field is a placeholder that becomes real text when the email goes out. Write "Hi First Name," once and every recipient reads their own name.
In the editor they show as labelled chips, First Name, Your Signature, not as code. You never type placeholder syntax by hand.
#What is available
| Group | Fills in |
|---|---|
| Contact | Their first name, last name, email, and address details such as city, street, ZIP and state |
| Agent, you | Your name, firm, phone, email, website and signature |
The panel in the composer lists everything available. Click one to insert it.
#Custom tokens
A custom token is a snippet of your own that you reuse, an office address, a standard disclaimer, a booking link. Define it once and drop it into any email.
Custom tokens resolve at send time. Change the snippet and every email and campaign step using it picks up the new value, you do not go and edit each one.
#When a field has no value
A contact with no first name produces "Hi ," if the greeting depends on one. Preview with a sparse record before sending to a big audience, imported lists always contain a few.
#Using them well
- A first name in the greeting is enough. Sprinkling one through every paragraph reads as automated, which is the opposite of the intent.
- Your own details, signature, firm, phone, are the safest, because they are never blank.
- Anything that is the same in every send should be a custom token, so you change it once.