Dynamic Data-Aware Emailing

Functional Summary
My batch email solution involved a thoughtful balance. On the one hand, the goal is to make it as powerful as possible. On the other hand, the idea is for end users - at least what I like to call "user gurus" - to be able to prep and fire a job already set up to be run on a periodic basis. When there are a series of emails flying from an organization, it is preferable that they have a consistent look and feel and even a consistent language tone. Our emails are based on a reusable component library and some flexible assumptions about how things get cobbled together.

Case Studies
A client has been running eBilling 5 times a year now for 4 years. These billing cycles also include multiple reminders to the decreasing population of those who have not yet paid. A monthly eNews is also built and sent. Event reminders are also sent several times a year. Together, all these contact attempts are tracked. If a client calls to claim no notice had been given, staff is able to bring up a log of all emails sent and can then reconfirm current email and addresss.

Advanced Functionalities
The system supports both beautiful html-formatted custom messages that also pull specific content based on data values. Other emails can be static and simply point to a published html web page. Both approaches work. Our engine allows pre-configuration of multiple formats with different layouts and different cascading sytle sheets. Therefore it is possible to use different graphics and logos too across jobs.

Our implementation of this batch engine also includes a companion solution to manage email bounces. Ask me about that solution if you have an interest.