Skip to main content
Sending capacity is reputation, not quota. The deliverability dashboard at /dashboard/marketing/email/deliverability is where you watch your sender reputation in real time and act before it costs you.

​
What you see

The dashboard shows three metric blocks, an AWS SES status panel, and an IP warmup widget if you’re on a dedicated IP.

​
Bounce rate

The percentage of recent sends that came back as a hard bounce (recipient address doesn’t exist) or hard delivery failure.
  • Healthy: under 2%.
  • Watch: 2-5%.
  • Hot: above 5% — Hiveku blocks new sends until you take action.
Soft bounces (mailbox full, server timeout) are tracked separately and rarely cause problems unless they spike.

​
Complaint rate

The percentage of recent sends where the recipient hit “report spam”.
  • Healthy: under 0.05%.
  • Watch: 0.05-0.1%.
  • Hot: above 0.1% — Hiveku blocks new sends.
Complaints are the most punishing signal. One person reporting spam costs you many times more than one bounce.

​
Open rate (engagement signal)

Open rate isn’t a deliverability metric on its own, but mailbox providers use engagement signals to decide whether to inbox or fold-into-spam. Persistently low open rates (under ~10% for a permission-based newsletter) usually mean you’re already landing in spam folders for some recipients. The dashboard charts open rate over the last 30, 60, and 90 days so you can spot trends before bounce or complaint rates move.

​
AWS SES pause thresholds

Hiveku sends through Amazon SES, which enforces bounce and complaint thresholds at the account level. If you cross a threshold, AWS can temporarily pause your sending privileges across the account — this affects every campaign and every sequence. The thresholds:
MetricThresholdWhat AWS does
Bounce rate5%“Under review” — warns you.
Bounce rate10%Pauses sending.
Complaint rate0.1%“Under review”.
Complaint rate0.5%Pauses sending.
The dashboard shows your current AWS SES “reputation health” status: healthy, under review, or paused. If you’re under review, the coach pings you with concrete suggestions before AWS escalates.

​
What to do if you’re paused

1

Stop sending

All scheduled campaigns are paused automatically. Don’t try to bypass.
2

Find the source

The dashboard segments bounces and complaints by recent campaign. Usually one campaign caused the spike — usually because the audience was stale or imported from a third-party list.
3

Clean the list

Remove hard-bounced and complained addresses (Hiveku auto-suppresses, but the source audience may still hold them as members). Re-verify your list with an external tool if it’s been more than 6 months since the last cleanup.
4

File a review with AWS

From the dashboard, click Request reinstatement. The coach drafts a remediation note describing what changed and what you’ll do differently. Reviews typically resolve in 24-48 hours.
5

Resume slowly

Don’t immediately blast your full audience. Send to your most-engaged segment first to rebuild reputation, then expand.

​
Dedicated IP warmup

If you’re on a dedicated IP (see Dedicated Email IP), the warmup widget tracks your daily volume against the recommended ramp:
  • Day 1-3: ~50 emails
  • Day 4-7: ~200 emails
  • Week 2: ~1,000 emails
  • Week 3: ~5,000 emails
  • Week 4+: full volume
Sending too much too fast on a fresh IP burns the reputation before you build it. Hiveku enforces the ramp by default — the coach won’t schedule a send that exceeds the day’s limit. You can override with explicit confirmation if you know what you’re doing, but it’s almost always a bad idea. The widget also shows your IP’s current Sender Score (third-party reputation index, 0-100) and any blocklist hits.

​
Suggested actions

When metrics drift, the dashboard surfaces concrete next steps:
  • “Bounce rate climbed from 1.8% to 3.4% in the last 7 days. The campaign ‘April newsletter’ to audience ‘All leads — created 2023+’ contributed 67% of bounces. Recommended: remove the audience or run an email-verification pass before next send.”
  • “Complaint rate at 0.08%. Most recent complaints came from contacts who hadn’t opened in 180+ days. Recommended: tighten newsletter audience to 90-day openers.”
  • “Open rate down 15% in last 30 days, no bounce/complaint change. Possible inboxing issue — try sending a test campaign and check spam folder placement.”
You can ask the coach to run the same triage on demand: “audit my deliverability for the last 30 days.”

​
Suppressions vs deliverability

Hiveku’s transactional suppression list is the source of truth for “do not send”. The deliverability dashboard reads from the same list — if a hard bounce hits the suppression list, every audience automatically excludes that contact going forward. For raw suppression management (manual add/remove, bulk export), see /email/deliverability and /how-tos/email-suppressions.

​
Troubleshooting

Check engagement signals. AWS-level health is necessary but not sufficient — Gmail and Microsoft also weigh per-recipient signals. Try sending a small campaign and have a few recipients on different providers report whether it reached the inbox.
Almost always a stale list. Pause the offending campaign immediately. Run an external email-verification pass on the audience before re-sending.
Permission isn’t always remembered. Three signals to check:
  • Frequency: are you sending more than 2-3 times a week?
  • Relevance: are you using audience segmentation, or blasting everyone?
  • Footer: is the unsubscribe link obvious?
Click the blocklist hit on the warmup widget for the delisting URL. Most blocklists self-clear if you stop the offending behavior; some require a manual delisting request. The coach can draft the request.

Diagnose deliverability issues

Step-by-step triage when something’s wrong.

Email suppressions

Inspect and manage the do-not-send list.

Dedicated IP

When to upgrade and how warmup works.