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.

My main use case for SendGrid is to inform users about what is happening with their profile or if they are booking something new, slots, or some new information. Basically, I'm using it to inform the team and users about what is happening on the website and what they are interacting with.

I use SendGrid for email notifications. For the team, my main use case for SendGrid is to send reports through automation of SendGrid.

The best feature SendGrid offers is the ability to send multiple emails at the same time.

The ability to send multiple emails at the same time helps my workflow and organization because I do not have to run a loop every time. Once I set all the emails in a comma separator, I can send them to multiple users without creating too much load on my server.

SendGrid has positively impacted my organization by solving the notification problem. By using SendGrid, I can easily send notifications to users, and it is simple to use in my Node.js project.

SendGrid has helped with notifications because when I send an email, the user knows who is sending it and they can revert back to our CRM team. That is positive for our business and organization.

SendGrid fulfills all my cases for what I require to send to the user's emails, so I don't think there is anything for improvement.

For now, the features are enough, and there are no needed improvements at this time.

I have been using SendGrid for the last three years.

SendGrid is stable for my needs.

SendGrid's scalability is good.

The customer support for SendGrid is good. I did not face any issue contacting customer support.

Before SendGrid, I also used Postmark. This is not a switch. This is basically two different projects, and we are using two different email providers.

For my private cloud setup, I'm using SendGrid directly from the JSON that SendGrid provided. I implemented the JSON format into our code and then used that.

I cannot tell if I have seen a return on investment with SendGrid.

As a developer, I did not directly manage the pricing for SendGrid. My senior team discusses all these things and provides me the API to use.

Before choosing SendGrid, I evaluated Postmark as an option as well, which is also good.

SendGrid is recommendable. I would rate this product a 9.

My main use case for SendGrid is to send notifications to customers in my web app as a web developer. I have used SendGrid to send reset password links, invitation emails, and notifications regarding software events, such as when a person joins, leaves, or when anything happens to a specific account that requires customer notification.

Recently, I have been working with a support agent bot for a client where I need to notify staff members whenever a new support message arrives in the web-based support platform. When a customer reaches out and requests human intervention, I generate an email and send it to all available staff members who can address that conversation. SendGrid is used to send all these notifications.

My main use case for SendGrid also includes using webhooks for emails to enable two-way conversations. If I receive anything over email, I wanted to send back a response. I used webhooks from Gmail and Microsoft in that scenario and also utilized SendGrid along with it.

The best features SendGrid offers is the template customization, which really helps in creating templates according to client demand and their UI/UX experience. It is very convenient to create a quick template and use that inside the code.

Template customization in SendGrid has helped me significantly in my projects. Every client comes with their own idea, branding color, and logos. Creating these templates at code level is not very easy and is a painful strategy. Instead of creating all these templates and following all the client's instructions and branding requirements, I go to SendGrid and create that template.

SendGrid has positively impacted my organization by helping in use cases where, since SendGrid is a product of Twilio, it is very convenient to use other products from the same organization, which helps me stay in the same workspace instead of going to another platform. When I needed to reach the support team, SendGrid being a popular product helped me a lot.

Regarding specific outcomes or metrics that show how SendGrid has helped my organization, I have saved a lot of time. Although I do not specifically use SendGrid for campaign purposes, I use it primarily for notifications. The main time I have saved is through the template feature. Using dynamic templates and different template types inside SendGrid saves a lot of time because I do not have to spend time generating those templates in my code.

The issue I have encountered recently is regarding my account. I forgot my password, and when I tried to log in, it indicated that a reset link was sent to my email, but I did not receive it. I also tried to reach out to SendGrid but unfortunately did not hear back properly. Due to this, I have not been able to use my account for around four to six months because I cannot receive the reset link and my account always requires me to verify my email.

Besides the account recovery issue, everything else in SendGrid is pretty good. In terms of email sending notifications, the integration features are awesome because they allow integration using SMTP and using secret keys as well. Both methods help me a lot. SendGrid is doing great in the integration section.

I have been using SendGrid for about two to three years.

I advise others looking into using SendGrid to use it according to their needs and also suggest that if they are going with multiple templates, SendGrid provides dynamic templates in their product, which should be utilized instead of writing custom templates inside code. I would rate SendGrid an eight out of ten.