Twilio SendGrid is a trusted email delivery platform that lets users create and send emails. The platform ensures emails are engaging and easy to create with tools like drag-and-drop builders. It also features a lot of automation tools and comprehensive analytics all to help improve open rates, engagement, and conversions.
Capabilities |
|
---|---|
Segment |
|
Deployment | Cloud / SaaS / Web-Based |
Support | Email/Help Desk |
Training | Documentation |
Languages | English |
The UI looks great and the way the service/API is set up seems very easy to use.
Horrible, horrible customer service. Sent an email out to support in response to an "Account provisioning failed" email (which, despite what they claim on their support page, has absolutely zero explanation of why it failed and what to do next) to ask about how to proceed with the account verification/provisioning. Days passed and no response. I next opened a ticket directly in their customer support portal asking, specifically, what are the next steps for verification and why was my account not provisioned? Their response? "Hi there, Thanks for your reply. The SaaS that we use for vetting new accounts does not provide us with much granular information in terms of why an account was failed. All I can tell you is that it has something to do with the dedicated shared IP address, but unfortunately I can't see any more detail then that. Best of luck to you in your future endeavors, and I apologize for the inconvenience. Kindly, Erika" So what the hell does that mean? Sure, fine, you don't know why, but you didn't answer my main question: what are the next steps I can take from here? At the end, I had to ask again, before they finally told me that in actuality, "Your account cannot be provisioned at this time" actually translates to "Your account will never and can never be opened/provisioned. Look elsewhere." If we can't use the service that's fine, but why is getting a straight answer from them so hard? Their customer support seems very shifty and evasive. It's probably for the best that we won't be using them.
We were going to use them for transactional email (e.g. order confirmation, order receipts, shipping notifications, etc). No benefits though. We'll be using Amazon SES instead.
They were the worst company to deal with...they over charged and never delivered for three of our clients. They promised a credit never gave it then charged over $2100 for doing nothing.
We disliked everything and warn others to stay away. We provided them with opt in lists they only sent out 25% and charged us for 100% and over charged us by mistake , then promised a credit and claim our customer list wasn't good. We moved the same list to constant contact and no problems. Sendgrid email lies, cheats and fails on all levels.
We were sending an opt in lists for our client to provide client info and credits to accounts. We were attempting to communicate with clients.
The dashboards SendGrid provides are relatively helpful and clear. Their customer support is also decent, though you'll have a very tough time finding the phone number for it.
SendGrid has put no effort into making their interface easy to use. If you forget to fill a field out, you can click a button a thousand times and get no feedback on what you did wrong. Certain sections might be off-limits to you—rather than telling you why or simply greying them out, they will redirect you back to the dashboard page. Their SMTPAPI simply didn't work for us, and there's was no feedback anywhere about why it went wrong, though the API call itself seemed to succeed. Their support telephone number and email is nowhere to be found on their site. As a developer and a marketer, I would never use SendGrid again. All-in-all, it's an extremely poor service with very little effort put into making it seamless for users. They are clearly riding on their long-standing place in the market and are doing nothing new or helpful for users. Go with a newer, friendlier service out there—you'll quickly realize which ones care about their users.
Transactional emails, triggered from our backend.