Twilio SendGrid vs. WhoisXML Email Verification API

If you're prepared to build out your whole staff UX, audience creation, email production, and analytics on your own using API, this tool may have that flexibility. If you require a sturdy drag and drop production tool, this tool has it but at the expense of a lot of other critical functionality. Out of the box analytics/reporting, is extremely limited. Complex queries, even something like pulling those who haven't engaged in email within a certain time period, is clunky. If you require any support at all, this is not the tool for you. I'm a deliverability consultant and have used many of the top email marketing tools and SendGrid has been extremely difficult for my team. I do not recommend it. Shiny and bright during sales, pretty disappointing thereafter.

We use WhoisXML Email Verification API for the additional value it provides to our corporate email security, and we recommend that most organizations do the same. Disposable email services may help protect the privacy of their users, but in the corporate setting, receiving emails from these domains may not be safe. So, aside from flagging emails from domains categorized as spam, we wanted our spam filtering system to be stricter and include disposable email addresses.

• Managing email lists / audiences is easy with features like groups and segments.
• They provide pre-built email templates that are very easy to modify. It is also super easy to create new email templates with their drag-and-drop email builder.
• Provides clear / easy-to-read analytics of email campaigns.
• I can easily import large email contact lists all at once or add a user manually one-at-a-time, when needed.

Incentivized

• WhoisXML Email Verification API obtains its disposable email detection capabilities from a disposable email domain database that monitors most disposable email providers regularly.
• WhoisXML Email Verification API is compatible with most spam filtering solutions and other email security systems. It is also available as a Splunk application, so compatibility wasn’t an issue for us.

• Not necessarily their Email API but their email in general - they are currently in beta for automated email sequences but are still bare bones. Much more work is needed before it can be used mainstream and be able to convert everything to SendGrid.
• Helping with warming up our dedicated IP for the best-sending score.
• We seem to hit the promotions folder a decent amount (maybe the IP problem above) and even a lot of their emails hit my spam or promotions folder (whether they be transactional or marketing) which isn't a great sign when trusting an ESP.
• Transactional email sequences would be a huge plus.
• Now that Twilio owns SenGrid, having an integrated platform where you could see all our transactional emails together.
• Better reporting and split reporting between transactional and marketing emails.

Incentivized

• We had to avail ourselves of the custom plan because we have a pretty large user base, and each user receives hundreds of emails per day. We were able to come up with a reasonable agreement, in any case.

It is usable but needs improvement in overall user experience and ease of use. A new joinee/anyone new to the tool would need more tarining currently before he can use the platform seamlessly. The set-up to value realization time for Twilio SendGrid customers is generally high because of this concern.

Incentivized

Twilio SendGrid Email API is everything we want it to be, and we have no reason to look for any other solution. Features and pricing match exactly what we need. As developers for SaaS products, Twilio SendGrid Email API provides a great service. I hope that they stay this way and don't inflate the service with too many marketing oriented features, because there are other tools for that and Twilio SendGrid Email API is a API for sending email first and foremost.

Incentivized

Prompt and professional support.

Sendgrid has a lot of features that other providers have and a few more - like the dynamic template builder, which AWS SES doesn't have. We choose the provider based on the scenario of use and the provider we're using. If we're going to be making regular changes to a template, then we'd go with Sendgrid, as the changes will be easier to make and don't necessarily require developer intervention.

Incentivized

• As it was cheaper than the transactional service we previously used, it saved costs.
• The API was relatively easy to work with so it helped us ship the service and test it quickly.
• We still use the transactional email service, even though we recognize its limits as it meets our immediate needs.

Incentivized