We are an integrator, and we have a product in which we use Amazon WorkMail. We send emails on a daily basis in a batch mode to customers. We have about 50,000 emails across various customers.
I use Amazon WorkMail to create email accounts and integrate them with Gmail and Microsoft Outlook. I've launched a website and migrated it to AWS infrastructure, and WorkMail is part of this integration.
We use it to send emails, basically. Plus, whenever you send or receive an email, WorkMail gives you a trigger point. It's very much integrated with other AWS services. For example, one use case we had was with our UAT servers. They were costing us a lot because we had to pay for them every month, even when no one was using them for a few months. So, we set it up so that whenever a client sends us an email saying "please turn on the UAT server," the UAT server automatically turns on using WorkMail. We get a trigger that the client wants the server on, so we turn it on. After four or five days, it automatically turns off, which saves us money. That's one use case we are using it for.
Within our organization, we handle procurement and keep customers updated through email. Most customers use our procurement application, which goes through different stages. When a customer submits a request on our website, we send them a message via Amazon WorkMail to confirm that their request has been received and is under review. We regularly update them on the status of their procurement through email. For instance, if a customer is procuring items from China and shipping them to Africa, we inform them at each stage. From the initial procurement process in China to the transfer of goods to West Africa, such as Nigeria, we keep the customer informed at every step.
We used the product to send email notifications to our customers, end users, or our internal team. If we are hosting any applications, the customer must know it.
Technical Consultant - Email Deliverability at Adobe
Real User
Top 5
Jan 6, 2023
We primarily use the solution for: * Transactional emails. Applications can use SES to send emails related to specific user actions, such as password resets or account confirmations. * Marketing emails. SES can be used to send newsletters, promotional emails, and other marketing communications to large email lists. * Notification emails. SES can be used to send notifications or alerts to users or administrators, such as order confirmation emails or system status updates. * Custom emails. SES can be used to build custom email solutions, such as automated email responses or personalized email campaigns. Overall, SES is designed to make it easy for businesses to send a high volume of emails quickly and reliably, with features like automatic retries and email-sending history tracking.
Amazon WorkMail is a secure, managed business email and calendar service with support for existing desktop and mobile email client applications. Amazon WorkMail gives users the ability to seamlessly access their email, contacts, and calendars using the client application of their choice, including Microsoft Outlook, native iOS and Android email applications, any client application supporting the IMAP protocol, or directly through a web browser. You can integrate Amazon WorkMail with your...
We are an integrator, and we have a product in which we use Amazon WorkMail. We send emails on a daily basis in a batch mode to customers. We have about 50,000 emails across various customers.
I use Amazon WorkMail to create email accounts and integrate them with Gmail and Microsoft Outlook. I've launched a website and migrated it to AWS infrastructure, and WorkMail is part of this integration.
We use it to send emails, basically. Plus, whenever you send or receive an email, WorkMail gives you a trigger point. It's very much integrated with other AWS services. For example, one use case we had was with our UAT servers. They were costing us a lot because we had to pay for them every month, even when no one was using them for a few months. So, we set it up so that whenever a client sends us an email saying "please turn on the UAT server," the UAT server automatically turns on using WorkMail. We get a trigger that the client wants the server on, so we turn it on. After four or five days, it automatically turns off, which saves us money. That's one use case we are using it for.
Within our organization, we handle procurement and keep customers updated through email. Most customers use our procurement application, which goes through different stages. When a customer submits a request on our website, we send them a message via Amazon WorkMail to confirm that their request has been received and is under review. We regularly update them on the status of their procurement through email. For instance, if a customer is procuring items from China and shipping them to Africa, we inform them at each stage. From the initial procurement process in China to the transfer of goods to West Africa, such as Nigeria, we keep the customer informed at every step.
We use the tool for transactional emails and marketing.
Our use case for sending out broadcasts and emails through our CRM.
We used the product to send email notifications to our customers, end users, or our internal team. If we are hosting any applications, the customer must know it.
We primarily use the solution for: * Transactional emails. Applications can use SES to send emails related to specific user actions, such as password resets or account confirmations. * Marketing emails. SES can be used to send newsletters, promotional emails, and other marketing communications to large email lists. * Notification emails. SES can be used to send notifications or alerts to users or administrators, such as order confirmation emails or system status updates. * Custom emails. SES can be used to build custom email solutions, such as automated email responses or personalized email campaigns. Overall, SES is designed to make it easy for businesses to send a high volume of emails quickly and reliably, with features like automatic retries and email-sending history tracking.