The biggest problems with Nexthink's email practices, up until this point, have centered around a couple of things including the email construction workflow, stylistic uniformity, forward compatibility, and translation.
Workflow
In order to make email accessible to those in marketing that didn't know how to code, simple emails first needed to be built in Mailchimp using the drag-and-drop builder that Autopilot lacked. Then, HTML from Mailchimp's drag and drop tool needed to be exported, imported into Autopilot, and parsed for bits of html that contained tokens. This obviously was not a scalable practice, and was somewhat annoying for anyone building emails.
Translation
Emails generated with Mailchimp and imported into Autopilot were static. No content could be dynamically layered to cater emails to different audiences based on something like language, job level, or any other segmentations. This was limiting.
Stylistic Uniformity Emails construction was previously controlled regionally, and as such, Nexthink emails varied stylistically and structurally.
Forward Compatibility
All emails built for nexthink, around 800 of them, were forward incompatible, meaning that as Nexthink moved forward with differing design paradigms these emails would not be easily modified in bulk. This is a huge issue, that in large part still exists today.
|