PrintSF Enterprise Edition > Install & Configure > Advanced Configurations

PrintSF's automated sync process inserts and updates records in our custom object of MAILER HISTORY. This includes inserting a Mailer History record for each piece of requested mail shortly after each order is submitted, and then updating the Mailer History record on subsequent syncs as a variety of events occur, such as:

•A Mailer is Delivered (Delivery status changed to Delivered, and Date Delivered updated)

•A Mailer is Returned (Delivery status changed to Returned)

•A Mailer is Forwarded (NCOA Status changed to Forwarded)

•A Mailer can't be Forwarded (NCOA Status changed to Moved Can't Forward)

Often, customers want to add automated workflows/triggers based on insertion and/or modification of Mailer History records. Some example automations we've helped customers implement include:

•Updating Lead/Contact records as their related Mailer History records show Delivery, Return, or mail forwarding, or to show Last Template sent, and so such data is updated directly on our custom fields on the Lead/Contact and is thereafter synched with matching fields in Pardot, Marketing Cloud or other Marketing Automation platforms, and can thus be leveraged in follow on Journey steps or automations.

•Setting the Mailer History to be related to a Person Account (via a custom Lookup field added to Mailer History), so Mailer History shows as a Related List under the Person Account.

•Setting a Custom Lookup on the Mailer History to make it related to a custom object record on insert, such as "Members", "Applications", "Orders" or other custom object records driving your mailings.

•Closing out Tasks or changing Campaign Member Status on Mailer History creation, usually to remove recipients from a filtered report used in a recurring mail program. An example would be when triggered tasks or Campaign Members are used to queue mailers in a Salesforce report filtered by task status or Campaign Member Status, and run daily or weekly, and when order submission and subsequent syncs should cause the recipients to fall out of the report for the next cycle by changing task status, or changing Campaign Member status, or some other field value.

•Adding a follow up task and/or email alert on Mailer Delivery, to queue up a follow up call for a sales or support person.

•Sending an email alert to a Contact or Account Owner upon delivery of a key mailer, such as a birthday card, annual review request letter, failed payment or past due notice, etc.

•And more!

We strongly recommend working live with a PrintSF engineer to discuss your requirements and learn from best practices we've developed across many automated programs for our customers. That said, there are some common automations from which many customers implement at least a few. These automations are typically implemented using PROCESS BUILDER FLOWS. To help you jump start this process, we provide an *UNMANAGED* package of 5 common process builders. This may be installed to your Sandbox or Production instance, and then the Process Builders may be cloned and modified.

Below is a link to our UNMANAGED package containing 5 start Process Builder Flows. Again, we strongly recommend a session with a PrintSF engineer before going live with any of these, but the package below will help you review the possiblities and methodologies so our call can be most productive.

PRODUCTION INSTALL - Install Unmanaged Process Builder Package to PRODUCTION

SANDBOX INSTALL - Install Unmanaged Process Builder Package to SANDBOX

Lastly, the below video provides an informal demo of the 5 starter process builder flows included in the unmanaged package above.

PrintSF Example Process Builder Flows