Weekday Amazon SES deliverability health check in Slack
Every weekday morning, get a Slack recap of new bounces and complaints, domains trending toward Amazon's warning thresholds, and any IP blacklist hits.
Amazon SES
Slack BotOperationsDaily DigestsNotifications & AlertsEvery weekday at 9am, pull an Amazon SES deliverability health snapshot and post a short readable summary to a Slack channel.
For the last 24 hours, use Amazon SES List Suppressed Destinations to fetch the email addresses that were added to my suppression list because of bounces and complaints. Group them by reason so I can see the top bounce/complaint categories at a glance.
Then use Amazon SES List Email Identities to enumerate my verified sending domains, and for each verified domain call Amazon SES Get Domain Statistics Report to pull inbox placement, engagement, spam-complaint rate, and bounce rate. If Get Domain Statistics Report returns empty for a domain, note in the digest that the SES deliverability dashboard is not enabled for it, so I know why the numbers are missing.
If I have any dedicated IP pools (check with Amazon SES List Dedicated IP Pools), call Amazon SES Get Blacklist Reports for those pools and surface any active blacklist hits. If I only send from shared IPs, skip this section entirely.
Write a short, readable summary that includes: how many new suppressions were added in the last 24 hours, the top bounce reasons, per-domain complaint and bounce rate with a plain-English note on whether any domain is trending toward Amazon's warning thresholds (bounce rate above 5% or complaint rate above 0.1%), and any dedicated-IP blacklist hits. Use Amazon's own guardrails as the reference: bounce rate above 5% triggers a review and above 10% causes SES to pause sending; complaint rate above 0.1% triggers review and above 0.5% causes pause.
Post the summary to my ops Slack channel using Slack Bot Send a Message. Format it with Slack mrkdwn so headings and rates are readable at a glance. If any threshold is breached or a blacklist hit is found, prepend the message with @channel and include a one-line "here's what to check next" call to action naming the specific domain, rate, or IP that tripped the alert. If everything is healthy, keep the message short and skip the tag.
Additional information
What does this prompt do?
- Every weekday at 9am, checks the past 24 hours of Amazon SES bounces and complaints and rolls them into a short Slack summary.
- Names the top reasons your emails are failing (mailbox not found, blocked, spam-flagged, and more) so you know what to fix first.
- Watches your bounce and complaint rates against Amazon's own warning thresholds and flags it in Slack if you're getting close.
- If you use a dedicated IP pool, checks those IPs against public blacklists and tags the channel when a threshold is breached or an IP is flagged.
What do I need to use this?
- An Amazon SES account with the deliverability dashboard turned on. That is what powers the per-domain inbox placement and engagement numbers in the digest.
- A Slack workspace and a channel where you want the digest posted.
- Optional: a dedicated IP pool. Without one, the blacklist section is skipped and the rest of the digest runs normally.
How can I customize it?
- Change the schedule (mornings only, midday, once a week, or every day including weekends).
- Send the digest to a different Slack channel, a private channel, or a direct message.
- Adjust the warning thresholds. Amazon's defaults are a bounce rate above 5% and a complaint rate above 0.1%.
Frequently asked questions
What exactly does the digest cover?
Do I need to turn on the Amazon SES deliverability dashboard?
Does this work if I don't use dedicated IPs?
What thresholds trigger the @channel alert?
Will it post on weekends?
Related templates
Every weekday at 8am, your billing team gets a Slack rundown of yesterday's failed Braintree charges, the revenue at risk, and who to chase first.
Every weekday morning, roll up your sprint's work items into a clear per-person standup summary and post it to your team's Slack channel before you meet.
Every three hours we scan Braintree for new disputes and chargebacks, open a tracked ticket with a tailored evidence checklist, and alert your team in Slack before the response deadline slips.
Every weekday morning we check your most important Databricks tables for freshness and data problems, and ping Slack only when something actually looks wrong.
Every Monday, automatically find which employee accounts on your company domain turned up in data breaches and get a plain-English briefing in Slack.
When a pipeline build fails, we post a tight Slack card naming who pushed, the likely cause, and a link to the build so on-call can triage in seconds.
Stop finding out about deliverability problems the hard way.
Get a weekday Slack digest that flags SES bounces, complaints, and blacklist hits before Amazon steps in.