AWS usually asks short, specific questions in the same case. Answer in that case, the same day, and answer only what was
asked, with evidence. Paste the exact question into case-log.md first.
Replace [...] with real values. Delete any sentence you cannot back with evidence. Never send a template as-is.
T1 — "Who are you / is this a real business?"
Thank you for the follow-up. Vlozi (https://vlozi.app) is operated by Dipanshu Vishwakarma, trading as Vlozi, Devgaon,
Azamgarh, Uttar Pradesh 276201, India. It is a small web platform that offers publishing and growth tools to businesses.
It is early-stage and has a small number of workspaces. The only mail this account would send is system mail from the
platform itself: login and verification codes, password resets, workspace invitations, account messages, billing and
credit notices, and alerts to workspace owners.
Our Terms of Service, Privacy Policy, Acceptable Use Policy, Anti-Spam Policy, Abuse Policy and sub-processor list are
published at https://vlozi.app/terms, /privacy, /acceptable-use, /anti-spam, /abuse and /sub-processors, and the operator
and abuse contact details are on the site. I am happy to provide any further identification you need.Evidence to attach: a screenshot of the site footer; the Terms page naming the operator.
T2 — "How do you get your recipients / do they consent?"
Every recipient is one of three kinds of person. First, someone who signed up with their own address: the one-time code
goes to the address typed at sign-up, and the account stays unverified until the code is entered. Second, someone an
existing workspace owner invited by typing that specific address. Third, for alerts only, the verified account email of
the owner of the workspace the alert concerns. Recipients of this account's mail are never taken from an uploaded,
purchased or rented list, and this account would not be used for marketing or bulk mail.
Sign-up is limited to 5 attempts per IP address per 15 minutes, code resends to 10 per IP address per 15 minutes with a
cooldown per address, and invitations to 5 per recipient per day [only if R7 is verified]. An address that has bounced or
complained is suppressed (see below), and every invitation names the inviter and can simply be ignored.Evidence: screenshots of the sign-up form and its verification step; a sample invitation email; the R7 check results.
T3 — "How do you handle bounces and complaints?"
Amazon SES publishes delivery, bounce and complaint events to an Amazon SNS topic that posts to our webhook. The webhook
verifies the SNS message signature against Amazon's published certificate and accepts only our own topic before trusting
anything. A complaint suppresses the address permanently. A hard bounce suppresses it for 180 days, and permanently if it
bounces again.
I monitor Reputation.BounceRate and Reputation.ComplaintRate in CloudWatch with alarms at [4% / 0.08%] that notify me by
email [only if R9 is green]. I tested the pipeline with the SES mailbox simulator on [date]; screenshots attached.Evidence: simulator results (R5); the CloudWatch alarm screenshot.
T4 — "Show us example content / how did you arrive at the volume?"
These are the complete templates this account would send. Each is triggered by the recipient's own action, or by a
workspace owner inviting that recipient:
1. Verification code: subject "Your Vlozi verification code", a code that expires in [N] minutes [read N from the template].
2. Password reset: a single link, expires in [N] minutes [read N from the template].
3. Invitation: "[Inviter] invited you to the workspace «[Workspace]» on Vlozi", with the inviter and workspace named and one button.
4. Account messages: a welcome after sign-up; a confirmation when an additional workspace is created.
5. Billing and credit notices: past due, trial ending, plan automatically downgraded, a resource paused for credits.
6. Alerts to the workspace owner's verified account email: a chat conversation waiting beyond its response target, credits
running out so that chat replies pause, a scheduled newsletter campaign that was not sent, and a sending-health warning.
No promotional content, no third-party advertising, no newsletters.
The platform has a small number of workspaces, so I expect fewer than 500 messages a day over the next 90 days. I asked for
headroom to 2,000 a day at 5 per second and will accept a smaller quota.Evidence: rendered emails (HTML screenshots) and the headers from a real delivery.
T5 — Denial with generic text: Support-case follow-up
Open a Support case (Technical → SES → Sending limits / production access), not a new production-access request.
Case [CASE_ID] for production access in ap-south-1 was closed on [date] with the message: "[paste AWS's exact words]".
I would like to understand what requirement is not met so I can fix it, rather than resubmit blindly. Specifically:
- Is there a problem with the identity or business information on the account?
- Is the stated use (platform system mail only, transactional, under 500/day expected) outside what you approve?
- Is there anything about the account's history, or the domain, that needs correcting first?
I have published the operator identity, an abuse contact and the acceptable-use and anti-spam policies [and configured
DKIM, a custom MAIL FROM domain and DMARC, and tested bounce and complaint handling: keep only what is true that day].
A short call or chat with someone on the SES team would help if the plan allows it.If the plan includes phone or chat, use it for this case. Record the agent's name and what they said in the case log.
T6 — Request for a quota change after approval
Only after a clean record (two weeks under 2% bounce and 0.05% complaint):
Our account was approved on [date] for platform system mail. Over the last [N] days we sent [X] messages with a bounce
rate of [x]% and a complaint rate of [y]%. We expect [Z] per day and [R] per second after our launch on [date], all of
the same kinds of mail as in the original request. Could you raise the quota to [Z] per day and [R] per second?Rules for every reply
- Same case, same day; never open a duplicate case while one is open.
- Every factual sentence has evidence in
evidence/. If it does not, cut the sentence. - If AWS names something you cannot fix quickly, say what you will do and by when, then do it and tell them.
- Do not mention tenants' newsletters or mailboxes. That is a different request (
phase-b.md).