Twilio SendGrid Email

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.