The emailer has lightweight mail merging. What do we mean by lightweight? You can drop these fields in...
The ones in bold are the ones we like best because they are the safest to use because they degrade gracefully.
|First Name||-FirstName-||The first name from the contact record|
|Last Name||-LastName-||The last name from the contact record|
|Preferred or First Name||-PreferredFirstName-||
If they have a preferred name it will use that, else it will fall back to using their first name. Some examples...
|Hi P-or-F Name||-HiFirstName-||
This will put in Hi (then either their preferred name or their first name) and then a comma and a <br/>
So it would be like this...
Then here is the text of the email...
The last name of the contact record
|Name||-Name-||The name in the contact record. Use this if sending to an organization type of contact - not a person type of contact.|
|Username||-Username-||The username from the contact record|
|Phone||-Phone-||The office phone (phone 1) from the contact record|
Use the mail merge picker in the toolbar to select the fields.
The last thing you want to do is look bad when you're trying to look good. That's why we put in a mail merge checker button. It checks to see if there are values for each mail merge field in the email.
Use mail merge when emailing subscription lists or contacts in the Brick River central database.
Think about using the -HiFirstName- variable since this is the safest. It will return blank if there is not a value or will return "Hi John," if there is a value.
Watch out/don't do mail merges when importing from a CSV file.
Those emails are NOT contact records in the central database.
Recipients that are added by hand won't get be mail merged.
That's why it's a great idea to use the -HiFirstName- field since this gracefully degrades.
Call 800-924-5220 or