In my experience, ESP features tend to follow a version of the 80\/20 rule: They all do the same 80% (although the various ESPs accomplish it using varying technology). While you want to make sure they do it well, the 20% differentiation is where you look to pick the platform that will grow with you.<\/p>\n\n\n
![\"80-20-espselection\"](\"https:\/\/www.emailvendorselection.com\/wp-content\/uploads\/80-20-espselection.png\")
<\/figure><\/div>\n\n\nBefore you get caught up in any bells and whistles of extra features, be crystal clear on those advanced esp features you\u2019ll actually use<\/a>, those of medium importance, and those that you would like to have but can live without. Then stick to that list. Time and time again I see clients asking for a feature they never end up using. You want to avoid getting sucked in by the shiny object syndrome, with \u201ccool\u201d features that you don\u2019t need now or won\u2019t realistically use in the next 18 months. To be sure, try the Shiny Things test here<\/a>.<\/p>\n\n\n\n Once you\u2019ve done that homework, it\u2019s time to look at the differentiators touted by the ESP you\u2019re considering. In all honesty, ESPs vary only a little in the main functionality offered. That\u2019s the 80% they all do the same. However, how<\/i> they function can differ, so really pay attention to the interface. How<\/i> something gets done is as important as what<\/i> is getting done, because if it\u2019s difficult to do, it probably won\u2019t get done.<\/p>\n\n\n\n Now you can look at the 20% that\u2019s different but look at it through the lens of, \u201cWhat do we realistically need?\u201d like we talked about above. Also look at the features offered by the ESP you\u2019re leaving. Were there any you thought you needed but never did use (or figure out)? Which features did you actually use? Which ones did you wish for? Let this insight inform how you view your next ESP choice.<\/p>\n\n\n\n We could talk about delivering on promises here, and that is a concern! But I am specifically talking about deliverability<\/a>. In truth, deliverability is not the ESP\u2019s job. It\u2019s yours.<\/b> However, the ESP should be bolstering your results by doing everything they can to ensure the highest possible deliverability rates for their platform.<\/p>\n\n\n\n So what does that look like? Don\u2019t simply ask them for a number. They could come back and tell you their clients average a 96.2% deliverability rate, and that is meaningless. For one thing, that could mean someone is down at 80% if you\u2019re averaging. More importantly, you need to know the deliverability rate you can expect for your<\/i> emails, not someone else\u2019s emails. (image source 250OK<\/a>)<\/p>\n\n\n\n The ESP needs to be on your team to make sure they are only enhancing your efforts. To dig deep into their deliverability capabilities, ask:<\/p>\n\n\n\n When your ESP\u2019s platform is down, you lose the ability to send not only manual but automated emails too. That means downtime is a really big deal.<\/p>\n\n\n\n No ESP can guarantee you 100% uptime. (If one does, turn and run the other way.) When an ESP tells you a downtime, dig deeper than the number they give you. If the ESP tells you their downtime is X, verify it, and do the math, keeping in mind that even a tiny percentage of downtime can mean a huge issue for you. You might think 99% uptime sounds great, but what\u2019s 99% of 365? The answer is 361.35 days\u2026leaving 3.65 days of downtime.<\/p>\n\n\n\n Talk to customers of that ESP about their experiences with downtime. What is the reality? How often does it happen? How is it handled? Is the ESP proactive when it happens? OK, it\u2019s a miserable job, but someone has to read the Service Level Agreement <\/a>\u2014 maybe not you, but someone. It\u2019s not a perfect world (and remember there are no perfect ESPs) and something could go wrong, as much as we hope it won\u2019t. What recourse is provided should the Service Level Agreement (SLA) not be met? Know that going into the relationship with a new ESP, so you won\u2019t get any ugly surprises later.<\/p>\n\n\n\n While reading through the SLA (or having someone give you the highlights of it), you will probably realize it says nothing about compensation should things go wrong<\/b>.<\/p>\n\n\n\n Remember my earlier point about downtime? If you lose money due to an outage or some other glitch that prevents you from using the ESP\u2019s platform, you probably won\u2019t get reimbursed. So really pay attention to that ESP\u2019s performance record and ask a lot of questions. Dig deep.<\/p>\n\n\n\n Your customers and subscribers trust you with their personal information\u2014not the ESP, but you. Protecting that data is your job, but there is a vulnerability you can\u2019t avoid because you have to use that data in order to use that ESP. That means your ESP must guard the data as diligently as you do.<\/p>\n\n\n (Source: Gemalto Breach Level Index<\/a>)<\/p>\n\n\n\n Security should extend beyond the platform to cover access to the network as well as local access from the platform facility. Before evaluating the security capabilities of any ESP, be clear on the requirements of your organization and industry, and the level of security wanted or mandated.<\/p>\n\n\n\n Ask the ESP about audit trails and security tools<\/b>. Do they provide monitoring and alerts? What about data breaches? Has the ESP had a data breach? If so, when and what steps were taken to prevent a recurrence?<\/p>\n\n\n\n Then get granular: Does the vendor offer encrypted fields for email? Does the vendor offer tokenized sending?<\/p>\n\n\n\n While these might seem like almost confrontational questions, it’s worth the time (and discomfort) to seek out the answers. You don’t want to be switching ESPs any time soon, right? And investing more time now can help you make a better choice. Besides, the ESPs might also be vetting you. You present a potential risk to the ESP and they need to make sure having you as a client won’t damage their sending reputation (or make their lives miserable). This is such a serious matter that Andrew Bonar<\/a> compiled a list of resources for ESPs for the OnlyInfluencers blog<\/a>.<\/p>\n\n\n\n Switching ESPs is always a hassle, so make sure you\u2019re switching to an ESP that\u2019s going to work for you for a long time. Be willing to dig deep and ask a lot of questions, about even seemingly minor issues. You might just uncover some dirt that will save you from bigger issues later.<\/p>\n","protected":false},"excerpt":{"rendered":" When you\u2019re looking for a new ESP, you\u2019re going to have to ask some hard questions in order to find the best fit, even if you don\u2019t want to. However, if you don\u2019t do the due diligence now, your reluctance to do so could come back to haunt you when something goes wrong. So dig […]<\/p>\n","protected":false},"author":30,"featured_media":13598,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_editorskit_title_hidden":false,"_editorskit_reading_time":0,"_editorskit_is_block_options_detached":false,"_editorskit_block_options_position":"{}","footnotes":""},"categories":[2],"tags":[],"dealstore":[],"coauthors":[538],"acf":[],"_links":{"self":[{"href":"https:\/\/www.emailvendorselection.com\/wp-json\/wp\/v2\/posts\/13589"}],"collection":[{"href":"https:\/\/www.emailvendorselection.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.emailvendorselection.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.emailvendorselection.com\/wp-json\/wp\/v2\/users\/30"}],"replies":[{"embeddable":true,"href":"https:\/\/www.emailvendorselection.com\/wp-json\/wp\/v2\/comments?post=13589"}],"version-history":[{"count":1,"href":"https:\/\/www.emailvendorselection.com\/wp-json\/wp\/v2\/posts\/13589\/revisions"}],"predecessor-version":[{"id":93293,"href":"https:\/\/www.emailvendorselection.com\/wp-json\/wp\/v2\/posts\/13589\/revisions\/93293"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.emailvendorselection.com\/wp-json\/wp\/v2\/media\/13598"}],"wp:attachment":[{"href":"https:\/\/www.emailvendorselection.com\/wp-json\/wp\/v2\/media?parent=13589"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.emailvendorselection.com\/wp-json\/wp\/v2\/categories?post=13589"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.emailvendorselection.com\/wp-json\/wp\/v2\/tags?post=13589"},{"taxonomy":"dealstore","embeddable":true,"href":"https:\/\/www.emailvendorselection.com\/wp-json\/wp\/v2\/dealstore?post=13589"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.emailvendorselection.com\/wp-json\/wp\/v2\/coauthors?post=13589"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}<\/span>Second, Does That ESP Deliver?<\/span><\/h2>\n\n\n\n
You, ultimately, are the one who determines your deliverability rate for your organization, by adhering to email deliverability best practices<\/a>.<\/p>\n\n\n![\"delivery-versus-inbox-placement\"](\"https:\/\/www.emailvendorselection.com\/wp-content\/uploads\/delivery-versus-inbox-placement.jpg\")
<\/figure><\/div>\n\n\n\n
<\/span>Third, What Does Downtime Really Look Like?<\/span><\/h2>\n\n\n\n
Also ask the ESP some questions to learn more, like how often do they release updates that require a temporary service suspension? How much unplanned downtime have they experienced in the last 24 months? What caused it and what did they do about it?<\/p>\n\n\n\n<\/span>Fourth, the SLA, a.k.a. When Things Go Wrong\u2026<\/span><\/h2>\n\n\n\n
<\/span>Lastly, Is Your Data Safe?<\/span><\/h2>\n\n\n\n
![\"data-breaches\"](\"https:\/\/www.emailvendorselection.com\/wp-content\/uploads\/data-breaches.jpg\")
<\/figure><\/div>\n\n\n