When setting up your transactional email flows, you did everything possible to make them look as good as possible. You've thought about your content, formatting, and delivery of the necessary data. You tested everything extensively before you "went live" with your transactional email flows. Everything is now live and running entirely automatically. Your source system sends triggers and data to Flowmailer, and you no longer have to worry about your transactional email flows. This all sounds nice, but the reality is often a little less ideal.
For example, almost no source system is always available. Furthermore, it is quite possible that essential data for broadcasting your transactional e-mail is missing and it is not inconceivable that one of your users has accidentally "broken" a template. As a result, one or more transactional e-mail flows will stagnate, and your customers will not receive transactional e-mails.
Since almost all transactional emails involve the recipient expecting to receive them, stagnation will result in customer reactions. Of course, you don't want to wait for that. As soon as problems arise in processing your transactional flows, please let me know immediately. Flowmailer offers two functionalities that fulfill this need: notifications and checks.
Notifications
In a previous release, it was already made possible for a user with admin rights to set one or more email addresses to receive notification emails. Flowmailer sends notification emails to the specified email addresses the moment Flowmailer issues so-called 'alerts.' Reasons for Flowmailer to issue alerts include the creation of a new user within a Flowmailer account or the occurrence of errors in source systems or Flowmailer templates. Each issued alert deserves attention, so receiving these notifications in your mailbox is definitely good.
Checks
Recently, "checks" have been introduced. A check ensures that an alert is sent to a specifiable email address when processing for a specific source or Flow within a defined period does not meet expectations.
Example: check whether between 8 a.m. and 10 p.m. on weekdays and between 8 a.m. and 0 a.m. on weekends at least one order confirmation is successfully processed (sent out) within Flowmailer every hour and send a warning e-mail if this is not the case.
Checks allow you to monitor both the processing of messages within Flowmailer and the delivery from your source systems. If stagnation occurs, Flowmailer will let you know immediately.
Conclusion
When sending transactional email flows, visibility and control of these flows are of great importance. As soon as there are disruptions in the data delivery process from your source systems or the processing of email messages within Flowmailer, you want to know as soon as possible.
Notifications and checks allow you to get even closer to your sending process and intervene immediately when things happen.