AWS SES keeps being rejected for NO REASON!

Hi everyone,

We have already registered within AWS services dozens of customers (probably already more than 100 actually). Basically, for nearly all our customers, we recommend they register with AWS because it just works and it's cheap for transactional emails.

This being said, we never had much problems with approvals for production. We had times where we had to wait almost a month for the approval, which was weird back then (not long ago though) but this time is different and VERY weird what's going on!

Here's the first request for production:

Bounces and complaints will be dealt with directly using an email for that purpose and since we will be setting up this using the plugin Newsletter for WordPress, it will be automatically managed. Our recipient list of users is maintained only for those that reached out to us and users have ALWAYS the possibility to reject receiving emails by deleting their account (because it will be transactional emails). Eventually we might start building a mailing list for newsletters, but that will not be right now and it will be something that will take a little bit of time, using some campain to attract subscribers or something similar and in order to have everything according to GDPR.

First response came in less than 24h and, for the first time, it was a rejection, only claiming that the request was against the AWS terms.

When I've read it, I couldn't believe it because this case was pretty much the same as many others recently approved to us so I sent a new explanation step by step, which was this one:

1. This is a company that has multiple stores in Portugal, most of them represented by franchises
2. The headquarters send daily emails to all of them and they purchase online on the "internal ecommerce" (it's not even open to public)
3. Since the total email accounts that receive the communications are around 200, if there are two times in one day that the headquarters need to communicate with their franchises, that's 400 emails sent to them (all franchises sign a contract where those email communications are accepted by them, making this valid for GDPR)
4. For now this is what they want to use the system for: both for transactional emails for their internal ecommerce and to send mass communication to their franchises
5. Later in the future, they want to create a campaign where they have a landing page offering a discount to users that want to subscribe to their newsletters (this way users are agreeing in receiving the emails and that's according to GDPR)
6. When they have at least 500 contacts, they want to start communicating once a month with their mailing list

After this, the answer was also fairly quick and it was, again, only claiming this:

We made this decision because we believe that your use case would impact the deliverability of our service and would affect your reputation as a sender. We also want to ensure that other Amazon SES users can continue to use the service without experiencing service interruptions.

I again sent a response asking for more details on WHY this would be the case and what was causing that decision so we can fix that and have the approval. It just makes no sense at all that the decision is made this way without even identifying the real WHY behind the decision making process. Makes absolutely no sense and it sounds very random.

How can I escalate this to have it approved or have more information on the WHY this was rejected so it can be fixed and then approved?