SendGrid is used to maintain all dynamic templates that are used throughout various channels and modes of campaigns and communication channels for student relations, parent relations, or any brand of education that we want to highlight or push promotions and campaigns. It serves as our email aggregator and email services management system, which we use to build our email reputation and send out communications.

SendGrid is mostly used for email campaigns, and we also use it for mass mailing to students and parents. For example, if we are observing a class that is going to get canceled for a particular holiday on a particular day, we would want to send out an email campaign to those particular classes getting affected so that the students are properly notified, along with the parents.

The best feature that we use right out of the box is the dynamic templates feature and the ability to create a dynamic template from scratch by using HTML code or by using any of the templates from the design library, which makes it very easy to build emails right out of the box with custom parameters that can be passed based on each different user that the same email is going to be sent out to. The second best feature would probably be the activity feed and the email logs that are maintained properly, which shows us when a particular email was sent out, when it got delivered, and when the user opened the email.

SendGrid also provides the option to create unsubscribe groups, which we set to particular communications so that it won't be spamming people who are not in need of that communication. Users can opt themselves into the subscription or un-subscription group, and they would be automatically excluded.

We are now able to handle multiple different emails which still belong to the same SMTP because we would ideally be handling everything in a single inbox, but the emails that get sent out would be specific from different brands. For example, a student that is currently enrolled for education subjects would get an email from education@thedomain.com versus a student which is enrolled for a particular UCAT course would be getting an email from ucat@thedomain.com. In that way, we are able to send out emails to multiple people, and the from address can be the same SMTP but different labels or domain names, which helps create a more professional view for the end user.

Primarily, the best item that has impacted us is the dynamic templates feature, which helps us create a particular template using HTML and CSS along with certain parameters so that we are able to send out the same structured email to multiple different students but with different data points.

The activity log is a little slower at times, but that is probably just nitpicking an issue. Overall, in general, there are not really very difficult pain points. There are certain issues sometimes when we are trying to handle a very big campaign; we might end up having a little bit less reputation in terms of bounces or spam reports that get detected when we send out the emails. Apart from that, there is not anything that would become a significant pain point.

If you don't really have an advanced subscription for SendGrid, it might take a while for you to reach the customer support.

I have been using SendGrid for almost about one and a half to two years or probably more than that.

We definitely have had a very good email delivery rate where we have been handling, for example, in the last week itself, we have had a 98.83% delivery rate of emails, and we have done almost about 121,000 requests by using SendGrid.

With our last to last year's inflow, we were handling around somewhat around 1,000 students, so we were dealing with a minimum of 5,000 or 10,000 emails in a month. To the next year's when we moved into having around 5,000 students, our daily monthly average was almost around 100,000 emails considering all the campaigns and the one-time mass emails that we sent through. Now we are handling close to 7,000 to 8,000 students, and our monthly emails are reaching up to 150,000 to 200,000 emails, considering we have certain projects that need mass communication to both students and parents.

When we are setting up a new account, we have to do all of the DNS setup, the API keys, and all the webhook configurations, which might be a little intimidating for someone who is just starting out and may not have a technical background. Considering our company and the team that uses SendGrid is primarily the tech team, they did not really have an issue with this.

In terms of other communication platforms, such as Mailchimp, SendGrid is probably quite good in terms of being the market leader and also having capabilities of Twilio that recently acquired SendGrid. All of that combined makes it a very good tool for handling marketing campaigns or any emails. SendGrid is a very good, reliable system for handling multiple or high-volume emails.

Considering Twilio acquired SendGrid, it comes as a good package deal, and someone looking to make their entire communication flow streamlined should definitely opt for it.

SendGrid allows us to handle multiple different emails which still belong to the same SMTP because we would ideally be handling everything in a single inbox, but the emails that get sent out would be specific from different brands. For example, a student that is currently enrolled for education subjects would get an email from education@thedomain.com versus a student which is enrolled for a particular UCAT course would be getting an email from ucat@thedomain.com. In that way, we are able to send out emails to multiple people, and the from address can be the same SMTP but different labels or domain names, which helps create a more professional view for the end user.

Primarily, the best item that has impacted us is the dynamic templates feature, which helps us create a particular template using HTML and CSS along with certain parameters so that we are able to send out the same structured email to multiple different students but with different data points.

I would rate SendGrid an 8 out of 10.

Our main use case is integrating SendGrid with Sentinel, and we use the .NET API.

For SendGrid with the .NET API, any use case can work. We can accomplish anything, but for example, contact forms with some Lambda functions. We are using it for more simple sites.

When a user submits a form, it is a perfect use case because when you create an account, there are very well-defined instructions on how to integrate with the API using your specific language that you have a project in. When a user submits the form, it uses the SendGrid client and secret token. It sends a request to SendGrid backend, and there the magic happens.

I do not have anything specific to add about my main use case or anything unique about how my team uses SendGrid.

In my experience, the best features SendGrid offers include the dashboard, which is very nice to review if emails were delivered or if something was wrong. For example, I did not know that they have templates, but we made our own. We used to send full HTML through our API. We just input the user message into the template, and then it looks beautiful when the email arrives.

I find the dashboard useful because it is very extensible. You can slice and dice data. You can have a quick peek at the latest information, so you can use it for quick checks but also for deeper investigations if you want to gain more insights.

SendGrid has positively impacted my organization as we moved to it from our own email servers, though it also gives us less control over everything.

I think SendGrid is great already as it is. If they keep developing it, that would be beneficial. If I were a power user, then I would probably have some ideas, but it is perfect for my use case.

SendGrid can be improved with better user interface design. By default, there is a white, hard-for-the-eyes background. A dark mode by default would be nice. I have not visited the dashboard in quite a while, but I think they do not follow the system color preference. That would be a nice addition. Otherwise, I think they are pretty good, and they are popular for a reason.

I do not have more to add about needed improvements. If there was something significant, I would create a ticket, so my use case appears to be covered.

I have been working in my current field for almost four years.

In my experience, SendGrid is stable. I do not recall any issues with it.

I am sure SendGrid's scalability is good; however, we did not need this feature. Of course, I would imagine any large email service is able to handle that. It should be, of course. SendGrid is designed for both small businesses and large ones, so I cannot provide feedback, but I imagine it is covered.

I never had to contact SendGrid's customer support. There is nice documentation that answers a lot of questions, as well as frequently asked questions and a lot of examples outside of the documentation. Usually, everything is covered.

I used an on-premises solution before SendGrid.

I cannot speak to the return on investment from using SendGrid because I am not involved in that. It is also very hard to see the effect of implementing it. SendGrid gives us some business opportunities sometimes if someone reaches out to us through emails sent through SendGrid. It is really hard to estimate.

I was not the person choosing the tech stack, but at least to me, SendGrid is the option I would choose. There are also others, such as Twilio. In our company, we search for multiple options and spend some days to evaluate which one is better for our team and which covers our needs the most.

My advice to others looking into using SendGrid is to think about whether you actually need to use it or if you can use something different. Spend time researching other options. Then, if you are sure you need SendGrid, spend time designing the code architecture so that it is easy to send emails from anywhere in the code and it is not hard-coded. Consider integrating with templates, as they are available. Make sure that everything is configured correctly. Spend time reading the documentation and learning the tool properly before attempting to do something, because it can cost you money and time later to refactor.

I think SendGrid is also useful for solo developers or people who want to learn web development and need a tool to allow them to send emails without setting up their own server, which can be difficult and also be spam-filtered. There is also a free tier for people like that, so it is great to learn it. I would be happy if another company that I join in the future will be using it. I give this product a rating of nine out of ten.

I use SendGrid for transactional emails and marketing. I have used SendGrid in different projects, mostly to send automated emails like account confirmations, password resets, and notifications.

SendGrid is very reliable and has good email deliverability. It integrates easily with applications and other platforms. The best features SendGrid offers are the deliverability and how it integrates with other systems.

The features I appreciate most include the email API, email templates, and basic analytics to track delivery and open rates.

SendGrid saves a lot of time for my organization. It saves time by automating email sending. Once everything is set up, emails are sent automatically without manual work.

SendGrid could improve pricing flexibility and offer more detailed analytics without extra cost.

I have been using SendGrid for the last year.

SendGrid has proved stable in my use.

For the moment, SendGrid's scalability is perfect for my company.

I have never had to contact SendGrid's customer support except maybe once because there was a problem with the name of the company on the paperwork. Someone else had to contact support, but it was not me, so I cannot really provide details about that experience.

I do not remember evaluating other options. SendGrid was already being used in the company, and I was told about it when I joined.

I would recommend starting with a small setup and testing email deliverability before scaling with SendGrid.

I have seen a return on investment with SendGrid, mainly through improved email deliverability and reduced manual work. Fewer failed emails and less maintenance helped justify the cost.

The pricing experience was reasonable at the beginning, but it increased as my email volume grew.

SendGrid is very useful overall. It saves a lot of time and integrates very well. I would say it is best for developers, startups, and companies that send large volumes of automated emails. I am very happy with SendGrid as a stable and reliable email delivery platform. It saves time by automating transactional emails and integrates easily into applications. Costs are reasonable at first, but they increase with higher volumes. Overall, it provides a good return on investment through reliability, time savings, and improved communication. I would rate this review an 8 out of 10.

My main use case for SendGrid is sending emails using SendGrid. I also design some templates to send to customers, and from time to time, according to the schedule, we send the templates.

My client has taken a paid SendGrid account, and we go into the account section and design some emails. In our code, we use the token key, and based on the token key, we receive the sender information, receiver information, the email body, and subject, and then we send the email.

Regarding my main use case with SendGrid, there are a couple of ways to send the email. One way is that I need to send the certificate details to the students as part of my software. After completing their certification, we send the certificate detail over the email using SendGrid, and the email body is dynamically updated using the code so the student receives the certificate.

The best features that SendGrid offers are email sending and the customization of the UI that you will receive at the recipient's.

This is a great feature in SendGrid because it is easy to customize, it is faster, and we can easily track the delivery report and all the delivery emails.

SendGrid's impact is very good because previously I was using SMTP email that is server-based, which was not a successful way, as the email was getting failed with no delivery report. Using SendGrid, the emails deliver faster, and they do not go to spam but are directly received in the recipient's inbox.

Since switching to SendGrid, I have seen that time is saved. The trust of the portals like Gmail and Outlook ensures the emails are received quickly with minimum failure, which increases the business.

SendGrid is already nice, but it could be improved by providing the company ID when sending the email. I was sending emails to my customers in a tenant-based project, where I need to maintain the company ID for each email to determine which emails belong to which company. When checking the delivery report, I need to filter with the company ID, which currently cannot be done.

I have been working in my current field for the last fourteen years.

SendGrid is stable.

The scalability of SendGrid is great.

Customer support is also nice.

Previously, I have used SMTP, which was very slow and resulted in frequent failures, which is why I switched to SendGrid.

I do not have any challenges with deploying SendGrid on Azure compared to my previous setup.

I have not evaluated any other option before choosing SendGrid. I directly started with it.

Since using SendGrid, I save money, and it is a good investment. The time is also saved, as it is really hard to send emails one by one to multiple people. Using SendGrid makes it easy.

The pricing is good, the cost is good, and I have no issues with licensing.

I definitely recommend others to look into using SendGrid. I would rate this product a ten out of ten.

My main use case for SendGrid is to send emails to my clients.

A specific example of the kind of emails I send to my clients using SendGrid is that we ask them about what their software license entitlement is, and we ask them to respond back to us. The email categories are notifications; we send them notifications, and we also ask them to follow up. We have defined email templates that we use to reach out to them.

The best features SendGrid offers include the ability to send emails with no lag in email sending and enabling the API component so I can use Microsoft Outlook from my organization. I can use SendGrid APIs to send out emails.

The API component has definitely made my workflow easier, and it has also helped us remain within our compliance reviews. Additionally, it has helped us to integrate it with other third parties, such as AWS services and AWS SES. We are also looking at opportunities to integrate it with some of the IBM components.

SendGrid has positively impacted my organization by being a trusted partner for sending emails.

SendGrid can be improved by making it more versatile and facilitating easier connections with third parties.

I believe SendGrid should connect with the IBM Watsonx platform more easily.

I have been working in my current field for over nineteen years.

SendGrid is stable so far.

We have not tested SendGrid's scalability yet as we are still in the preliminary development stages, and we have not scaled out SendGrid capability to one thousand, five thousand, or ten thousand customers. We are still developing with a handful of test cases.

As of now, I have not interacted with customer support as there has not been a need.

We did not previously use a different solution before SendGrid, as this is a brand new requirement around agentic AI use case that we have not done before.

SendGrid is deployed in my organization in a hybrid cloud setup.

My company does not have a business relationship with this vendor other than being a customer, and we do not have a technical relationship with this company since we are just trying to do a concept.

Unfortunately, we have not collected metrics for return on investment with SendGrid yet as we are still in the preliminary stages of starting.

I have no details about pricing, setup cost, and licensing as that is managed by our Alliance and Ecosystem team.

Before choosing SendGrid, we did not evaluate other options because this is an agentic AI use case that we just started choosing.

My advice to others looking into using SendGrid is to explore your use cases, and then reach out for help if needed. Additionally, cost plays a factor, and there are other players in the market also offering the same services. I gave a rating of nine out of ten because there is some scope for improvements.

My main use case for SendGrid is working on email notifications and push notifications, with most usage being emails through SendGrid.

A specific example of how I use SendGrid in my workflow is that I have approximately two to five year reports annually, weekly, or monthly, transferred via email to the client. The client reviews the email, which looks like a ledger and other accepted reports, sent through SendGrid.

Through a cron job, we are sending emails step-by-step to the client. First, we select the email scheduler, then the email is sent to the client by scheduling jobs.

The best feature in SendGrid is that it shows if the email is delivered or readable; its status is a big feature of SendGrid.

The tracking status helps me in my day-to-day work.

SendGrid has positively impacted my organization because it is best for email purposes. All of the projects include SendGrid, and the company uses it because SendGrid is the most reliable resource and provides the services.

I think SendGrid is providing much better services and could also provide webhooks for the developer to retrieve data from it, as webhooks are needed and important for us.

The documentation is not fine, so I believe the documentation needs to be improved.

I have been working in my current field for approximately eight years.

SendGrid is stable.

The customer support for SendGrid is better.

Before choosing SendGrid, I evaluated other options, including Twilio, which is the best alternative to SendGrid.

My experience with pricing, setup cost, and licensing for SendGrid is that it is easy to purchase the accounts.

There is both price reduction and time savings. It is easy to implement, and the developer saves much more time on implementation as it also has a cheaper rate, which is a big thing that the requirement is better for us.

We are not switching; we are currently working through SendGrid, as it is actually the best solution for our organization.

SendGrid is a most powerful third-party tool to use for email sending, and it improves the delivery rates compared to other services.

I would advise others looking into using SendGrid that it is the most reliable resource and provides the best services through email, with no emails bouncing except for some due to a lack of an email address, it being invalid, or the network not being fine; SendGrid is the best solution.