Co-Founder & CTO at a consultancy with 11-50 employees
Real User
Top 5
Jul 2, 2025
We are satisfied with Amazon WorkMail, as it is able to send emails and provide receipts, including the read and other statuses. Since we are doing more API side integrations, there does not seem to be a need for improvement, except for the opt-out feature that could have enhanced configuration on the APIs.
WorkMail is not available in all AWS regions. It was not available in India, so I had to create a setup in Ireland. That was a limitation because I was trying to get a WorkMail account while being in India. I think it is supported now, but there might still be a few regions where it's not. Integration can always be better. Plus, if more WorkMail agents are available for both India, that would be good. And if we have more WorkMail regions available, they can expect us to use more integrations.
The solution is quite low-level and lacks some advanced features. For example, it doesn't provide tracking capabilities, such as knowing how many users opened an email, which is crucial for email marketing. You would need to integrate these analytics with other tools to get them. I need to know if there has been a bounce and how customers interacted with the email. I would only suggest that Amazon WorkMail relax the rules for using Amazon SES in production. When you create an account, it starts in Sandbox mode, which means you can't use it in production right away. You must go through a process, message Amazon, and request to move it to production. Since Amazon is a big company, I feel customers shouldn't need this permission to use the service in production.
There is room for improvement in the scalability. Currently, you can only send one notification at a time. It would be great if it could send to multiple recipients simultaneously using different email addresses. For example, in one organization, different departments like HR and engineering can use one identity each to send emails. This would make it more scalable and stable. In future releases, I would add the ability to send multiple messages at the same time using different domains within the same company.
We'd like to see the following improvements: * A/B testing. The ability to create and send multiple versions of an email to a small subset of an email list and then use data on which version performed better to inform future email campaigns would be helpful. * Email scheduling. We need the ability to schedule emails to be sent at a specific date and time in the future rather than being sent immediately. * Email personalization. We'd like the ability to insert personalized elements like a recipient's name or location into emails using data from an organization's systems. * Advanced analytics. It would be ideal to have detailed data and reporting on email opens, clicks, bounces, and other metrics, as well as integration with other business intelligence tools. * Advanced spam filtering. We need additional spam filtering options beyond the basic spam filtering already provided by SES, such as blocking specific types of content or customizing the spam filter's thresholds.
Amazon WorkMail provides a fully managed email service, offering scalability, high availability, and seamless AWS integration, ensuring secure and efficient communication.Amazon WorkMail is designed to support a wide range of email communication needs, from transactional and marketing messages to internal notifications. It enhances email reliability through SES integration, utilizes machine learning for better deliverability, and offers robust security through domain protection and...
We are satisfied with Amazon WorkMail, as it is able to send emails and provide receipts, including the read and other statuses. Since we are doing more API side integrations, there does not seem to be a need for improvement, except for the opt-out feature that could have enhanced configuration on the APIs.
Amazon WorkMail's user interface could be more intuitive and user-friendly. Integration with Gmail using both SMTP and POP3 would be beneficial.
WorkMail is not available in all AWS regions. It was not available in India, so I had to create a setup in Ireland. That was a limitation because I was trying to get a WorkMail account while being in India. I think it is supported now, but there might still be a few regions where it's not. Integration can always be better. Plus, if more WorkMail agents are available for both India, that would be good. And if we have more WorkMail regions available, they can expect us to use more integrations.
The solution is quite low-level and lacks some advanced features. For example, it doesn't provide tracking capabilities, such as knowing how many users opened an email, which is crucial for email marketing. You would need to integrate these analytics with other tools to get them. I need to know if there has been a bounce and how customers interacted with the email. I would only suggest that Amazon WorkMail relax the rules for using Amazon SES in production. When you create an account, it starts in Sandbox mode, which means you can't use it in production right away. You must go through a process, message Amazon, and request to move it to production. Since Amazon is a big company, I feel customers shouldn't need this permission to use the service in production.
I would like to see detailed reports on email success and failure rates.
There is room for improvement in the support. It's just that customer support, though good, takes time to resolve issues.
When we first set up an email on Amazon SES, they had to verify it, which was not fast enough.
There is room for improvement in the scalability. Currently, you can only send one notification at a time. It would be great if it could send to multiple recipients simultaneously using different email addresses. For example, in one organization, different departments like HR and engineering can use one identity each to send emails. This would make it more scalable and stable. In future releases, I would add the ability to send multiple messages at the same time using different domains within the same company.
The product should improve technical support.
We'd like to see the following improvements: * A/B testing. The ability to create and send multiple versions of an email to a small subset of an email list and then use data on which version performed better to inform future email campaigns would be helpful. * Email scheduling. We need the ability to schedule emails to be sent at a specific date and time in the future rather than being sent immediately. * Email personalization. We'd like the ability to insert personalized elements like a recipient's name or location into emails using data from an organization's systems. * Advanced analytics. It would be ideal to have detailed data and reporting on email opens, clicks, bounces, and other metrics, as well as integration with other business intelligence tools. * Advanced spam filtering. We need additional spam filtering options beyond the basic spam filtering already provided by SES, such as blocking specific types of content or customizing the spam filter's thresholds.
The only issue is the price, which is far too expensive.