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.
PeerSpot users discussed what the most important features of a cloud email service were, and the consensus pointed to usability. This includes the service's reliability/availability, support, and migration/integration abilities as well as its compatibility with other applications. On top of the basic user friendliness of the cloud email, members want to see clean a web interface and solid security features in place, along with easy customization that contributes to a strong market perception...
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.