“How Do I Set Up a Template?”

When setting up a template within Zapier’s ‘Action’ section, there are only six fields in which the MailLift customer ought to seriously consider. Three of those fields require utilization in order for Zapier’s integration to prove successful. The remaining three fields are optional. Read below to discover what each field can provide to the integration process.

Set Up Template

Required Template Fields

1. To

The To section dictates the destination in which the MailLift customer’s letter request will be received.

To

This field requires the MailLift customer’s unique MailDrop key -an email address that is located within the Integration tab of their MailLift account’s dashboard. Once the MailDrop key has been located, copy and paste it within this field.

2. Subject

This section states the letter request’s title.

Subject - Blank

In the interest of clear, consistent record keeping, MailLift recommends that MailLift customers title their letter campaigns per a three-part format:

Company Name – [Recip. First Name Dynamic Tag] [Recip. Last Name Dynamic Tag ] – Campaign Type

Example:

Subject - Example

Note: Inserting a space between the First and Last Name tags will prevent both sections of text from appearing as if they are running together. For details on how to embed dynamic tags, click here.

3. Body

This section details the letter request’s specifics.

Body - Initial Example

Each letter request that MailLift receives is comprised of four sections: sender, body, recipient, and notes. In order to correctly sync a letter request’s content to MailLift, each section must be formatted with headers and footers comprised of six =’s.

Body - Format Example

Formatting these sections can vary in complexity depending on the level of customization that the MailLift customer has built their letter request form to provide. As the number of variables (ex. ‘Representative Name’, ‘Include Gift Card’) that the MailLift customer’s form can host increases, so is the likelihood that each section within this field will rely on the inclusion of dynamic tags in order to insert that customized content into each unique letter request. Read below to discover how to format each section in accordance with the amount of customization their letter request form contains. For details on how to embed dynamic tags, click here.

Note: Do not include the use of &’s within the body of this field as this character is coded to cause all subsequent content not to sync within MailLift. MailLift recommends using ‘and’ in its place.

A. Sender

Whether this section is likely to contain dynamic tags or not depends on the purpose of the letter request:

i) If Intended for Use by a Single Representative:

This section is unlikely to contain dynamic tags, presuming that the representative’s data will appear unchanged from letter to letter.

Sender - Non-Custom

ii) If Intended for Use by Multiple Representatives:

This section is likely to require dynamic tags as its data will differ from letter to letter. Note: Inserting a space between the First and Last Name tags will prevent both sections of text from appearing as if they are running together.

Sender - Custom

B. Body

Whether this section is likely to contain dynamic tags or not depends on the purpose of the letter request:

i) Non-Customized Content

This section is unlikely to contain many (possibly any) dynamic tags. Insert the intended copy within this section. If interested, add a dynamic tag to personalize aspects of the text.

Body - Non-Custom

ii) Customized Content

This section will require at least one dynamic tag that is synced to a customized field built into the MailLift customer’s submission form where a representative may upload unique letter copy per recipient/circumstance.

Body - Customized

C. Recipient

This section will require multiple dynamic tags as each recipient’s data will differ from the last.

Recipient

Note: Inserting a space between the First and Last Name tags will prevent both sections of text from appearing as if they are running together.

D. Notes

This section lists the MailLift customer’s preferred presentational specifications as previously discussed with a MailLift employee. This data can include stationery, pen color, the addition of business cards, etc. Whether this section is likely to require dynamic tags or not depends on the purpose of the letter request:

i) If Intended for Use by a Single Representative:

This section is unlikely to contain dynamic tags, presuming that the representative’s desired specifications will apply across the entirety of the letter request. Insert any non-customized notes within this section.

Notes - Non-Custom

ii) If Intended for Use by Multiple Representatives:

This section will potentially require dynamic tags as desired specifications might differ from representative to representative.

Notes - Custom

Optional Template Fields

4. Reply To

The Reply To field allows MailLift customers to incorporate MailLift’s Operations Department with every letter request email that the customer issues. As a result, MailLift’s contact information will be inserted within each request email that is sent -making MailLift’s Operations Department more immediately available if ever a question about a specific request email should arise.

Reply To

5. Cc

The Cc field dictates which third party individuals can be alerted via email every time that a new letter request is made. Note: The MailLift customer will receive no alerts upon issuing an email request unless their email address is entered within this field.

Cc

6. Force Linebreaks?

Leave this feature set to ‘No’.

Force Linebreaks

Upon having completed this setting up of the template, proceed to the next step in the Zapier integration process by clicking ‘Continue’.

Continue