SendGrid Reviews

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.

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.

Neutral

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.

Private Cloud

Other

My main use case for SendGrid is sending transactional emails. A quick specific example of a transactional email I send with SendGrid is a welcome email to an application, as well as passwords, login, OTP, and reset passwords. I send emails through the application, mostly around onboarding. I also try to send job alerts with SendGrid, which I would classify as transactional emails. Additionally, I send a bit of marketing emails.

SendGrid offers features that stand out for me, including that it is very easy to use, especially for a developer. The APIs are straightforward, and the documentation is excellent, making it one of the easiest solutions available for sending transactional emails.

The APIs and documentation stand out for me because the Python API is mostly what I have used, and it is quite interesting and easy to work with. The webhook for event tracking has also been something I have used extensively, and it was simple to use because it helped other stakeholders in the company view events regarding emails that we send company-wide.

SendGrid has positively impacted my organization because it is the primary tool I use for sending emails, including transactional emails and some marketing emails. It has been easy to use; I basically set up the SMTP client with SendGrid, which is straightforward. I have functions I recall every time for sending emails, which makes the process simple. The documentation is great, and this has impacted the organization positively because new developers have little to no friction when onboarding—the workflow is straightforward for them. Even developers with very low experience using SendGrid are able to easily get into the code and start working with it. That has been helpful. Other teams have also been able to view email events, which is very important because the company uses emails heavily. Being able to see email events and know what next steps to take has been very impactful to the organization as a whole.

For my use case, SendGrid is very good. The cost could potentially be improved, though I am not very familiar with pricing details. Additionally, some integrations with AI that I am not aware of would be beneficial.

I would rate SendGrid an eight out of ten. I rated it an eight because it could have better integrations with AI. I have seen some email tools use AI, and I believe that would be valuable. I would also appreciate a better workflow between SendGrid and other automation tools.

I have been working in my current field for more than six years.

SendGrid is stable.

SendGrid's scalability is smooth.

The customer support for SendGrid is quite helpful. I would rate the customer support a ten because I have not had any issues with them.

Positive

I previously used Mailgun, and I switched because of the limits and some issues with deliverability. The documentation was not as comprehensive compared to SendGrid. I have also used Brevo before, but I did not directly switch from Brevo to SendGrid.

My experience with pricing, setup cost, and licensing has been smooth. I did not handle that directly, but I believe so far it has been smooth.

I can speak to the time saved, which has been good. I have also experienced faster onboarding where new developers get onboarded quickly with little to no friction, especially for developers unfamiliar with SendGrid.

My experience with pricing, setup cost, and licensing has been smooth. I did not handle that directly, but I believe so far it has been smooth.

Before choosing SendGrid, I evaluated other options, including AWS SES.

My advice for others considering SendGrid is that it is very stable and the documentation is excellent. If you implement SendGrid, you will save developer time. I would recommend that people switch to SendGrid, but also encourage them to read the documentation carefully. The documentation is similar to Twilio documentation, so if you are familiar with Twilio, you would easily be able to set up SendGrid. If not, you should read the documentation thoroughly to understand what you need and what you need to set up. I would rate SendGrid an eight out of ten overall.

Private Cloud

Amazon Web Services (AWS)

I use SendGrid for sending support and other emails from my projects.In my previous project, which was related to AI chatbot systems, I integrated SendGrid with the backend to send onboarding emails, invoices for monthly subscriptions, and new package offers to clients.I covered subscription-based emails, promotion emails, and integrated SendGrid to send password reset emails and account profile update notifications such as name changes to customers using SendGrid's email servicing along with my domain from AWS.

SendGrid's package and ability to handle a large volume of emails at once is one of the key features, as well as the interface and settings to integrate SendGrid with backend systems are quite easy with step-by-step guides provided by SendGrid.The help guide and introduction section on how to integrate SendGrid with backend systems is well elaborated with good examples and setting guides, which makes it quite comfortable and favorable compared to other platforms.SendGrid's analytics help me evaluate how emails are being delivered to users, allowing me to monitor the count without having to maintain specific email records in my backend.

The limit is something I can point out, as I could increase it since AWS services for sending emails provided around 50,000 free emails per day, which is quite high compared to SendGrid.Pricing can be improved for SendGrid, as this is the only area I have seen that needs enhancement.There is always room for improvement in everything, which is why I have deducted one score, and that can be attributed to the pricing factor.Overall, my experience with SendGrid is quite good; I have used it in a couple of my projects and everything is smooth, from integration to sending emails; the only aspect I have mentioned several times during this interaction is the pricing.

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

SendGrid is quite stable.

SendGrid is quite scalable, as the number of emails increases, it scales the rate of sending emails without any delays or failure rate.

I do not currently engage with customer support; I typically obtain information and help from the content already available on SendGrid.

For one of my projects, I used AWS Simple Email Service, as they provided the provision of sending 50,000 emails, and for that client, price was quite a concern, so I decided to switch from SendGrid to Amazon SES since the backend was already hosted on AWS, and it offered a higher percentage of volume per month and lower pricing compared to SendGrid.

I do not remember any specific metrics at this moment, but I think it provides good value for money.

When I selected SendGrid, I evaluated other options, but I cannot recall specific names at the moment.

SendGrid is a good starting point to send emails and to integrate with backend systems easily, so as a start, you may use SendGrid; it is a good option, but as the number of emails grows, its costing is slightly higher compared to competitors, so a user may switch according to their needs.Overall, my experience with SendGrid is fine; as I mentioned, I have compared SendGrid with other facilities and competitors, and the pricing is quite high compared to AWS; the rest of the licensing and all other aspects are smooth. I give this product a rating of nine out of ten.

Private Cloud

Amazon Web Services (AWS)

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.

Negative

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.

Public Cloud

Microsoft Azure

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 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.

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.

Negative

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.

Public Cloud

Other

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.

Positive

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.

Microsoft Azure

John Abelardo Manangan II:

Within the first three years, I only used SendGrid for email sending and for the custom applications I made previously. There are transactional emails and some of the marketing parts in the first three years. Then I got a client that wanted to transition into using SendGrid because they have been using Klaviyo, which is expensive on their budget. I think in 2020, and then I asked them how they wanted to use SendGrid. They told me that they wanted to use the solution for their email marketing. Also, they are an e-commerce store. They have an e-commerce store, so they want all the transactional emails that are related to their customer orders, and order updates, they want to be integrated with SendGrid.

I used the solution with WordPress. It's easy to integrate the solution with WordPress. My supervisor asked me if maybe it's possible to segment the customers from each other because they have several stores. I recommend using a contact list. For each signup form, and each campaign they want, we make a separate contact list, and then they ask me to integrate this with custom coding.

The most valuable feature is the conditions in automation. At each interval, each email can have something like a condition if a certain contact matches the condition, it will proceed to send in the email under the automation.

The contact limit alerts need to be improved. The way that I see the limits and the way they implement the limit alerts in the current month will be billed on the next month and it's just not really accurate if you check on the alerts.

The data field of contacts can use improvement, they are just straight labels and values. It would be better if you have the option to add an object that can be added to the custom field of contact. It will be better to display something on the email templates, and then the conditioning or logic in the automation.

I have been using the solution for seven  years.

The solution is stable. I haven't encountered any downtime. Most of the time, the emails are sent properly, and then I can also see the email deliverability, and I can see the status of each email.

The solution is scalable and we send about 20,000 plus emails.

The solution has excellent technical support and I always contact them whenever I need to implement something that the client wants.

Positive

We switch to SendGrid to lessen the expense of the email solutions because we already tried Klaviyo and Amazon SES previously and they didn't work well. We always use the spam rate and the reports that SendGrid has.

The initial setup is easy. Actually, The deployment takes 10 minutes to one hour. It depends on the domain and the type of the domain. Most of the time, when you add a domain on SendGrid, it seems like it's real-time. I have no problem with it.

The deployment was completed in-house with the help of the SendGrid technical support team.

We are using the Advanced plan,10K. That is about $100 per month but sometimes we do go over the limit of the plan. The license is not based on the number of users.

I give the solution a seven out of ten because it is the most reliable email sending I have been using for the past few years, and seven also because there are some features that are not available in the SendGrid, but it is also seven because other competitors are more advanced or they have more tools to cater. A seven also because of the pricing. SendGrid is the most cost-effective solution that I have been using.

Using the solution in the first two years was okay because my client was using credit from SendGrid. They are a startup and it came from venture capital. They were granted credit and we made use of it. Once the credits were all exhausted, my client told me that we needed to adjust the budget for the plans on SendGrid, and this is where we have something to do with SendGrid. My client's website and stores have colossal traffic every day, so they have trouble with contacts exceeding the plan limit. They asked me to solve the contact issue with the alert level showing on the dashboard on SendGrid which is a little bit of a hassle to do for clients who don't want to upgrade their plan. I think SendGrid is not ready with the email marketing part because, unlike Klaviyo, which has a diagram that you can drag and drop what happens to an email, and then there is also conditioning. SendGrid is all plug-and-play. You can add something like an interval on each email. I think that's the SendGrid automation. You can just set which contact list to use for the automation. I think it's not really that possible with email marketing. I think the easiest way to work with SendGrid is with segmentation and the deeper filtering of the emails when you want to send to some customers that already have this, or already received their orders. Also in the filtering of different emails or contacts that have something like data that might be unique from each other contact. 

We are a startup company and all of our stores use SendGrid which is made up of three users.

If you are thinking of using the solution for the first time you can start with the SMTP if you are just testing. If you want to have a dedicated IP so that your emails can have almost 100% deliverability, you can sign up for their plan, and also buy the dedicated IP. If you want to automate the emails for your customers, I advise you to use the automation feature in SendGrid.

Public Cloud

Other