Dashboard Overview
The Overview screen is the operating cockpit for delivery and engagement.
What the screen is for
Use Overview to answer:
- How many messages were sent?
- What percentage delivered?
- Are bounces or failures rising?
- Are specific mailbox providers showing risk?
- Is there a delayed queue?
- Do open, click, or bounce trends look unusual?
Filters
Use the domain filter to isolate a sender domain. Use the time range filter to focus on a campaign window, incident window, or daily health check.
Before you investigate
Collect the context for the send you are checking:
- Sender domain and From address.
- Delivery engine used by the task or API template.
- Approximate send time.
- Recipient provider affected, if known.
- Whether this is a new domain, new template, new contact import, or new infrastructure path.
Health score
The health score summarizes delivery health using delivery rate, bounce rate, failed count, and delayed queue behavior.
When the score drops:
- Open failed-send details.
- Check provider-level rows.
- Review recent campaign changes.
- Confirm DNS still verifies.
- Check KumoMTA runtime or local queue health, depending on your delivery engine.
Delivery panel
The delivery panel shows sends, delivered rate, and failed count. Click the failed count to inspect grouped failure details.
Mail providers
Provider rows help you see whether failures concentrate on one destination such as Gmail, Outlook, or another provider.
If one provider is affected, troubleshoot provider-specific reputation, content, or throttling. If every provider is affected, troubleshoot DNS, sender authorization, queue health, or delivery engine configuration.
Trends
Trend charts show open, click, and bounce rate movement over time. Use them to compare campaigns and identify sudden changes after content, list, DNS, or infrastructure changes.
Daily operator workflow
- Filter to the primary sending domain.
- Review delivery rate, failed count, and delayed queue indicators.
- Open provider rows and look for concentration by destination.
- Check recent campaigns or API volume spikes.
- Review operation logs for recent domain, template, queue, or KumoMTA changes.
- If KumoMTA is enabled, confirm webhook and queue age are healthy.
Common mistakes
- Comparing a small test send against a broad historical trend.
- Treating open rate as exact measurement; privacy features can block or prefetch pixels.
- Ignoring suppressed recipients. Suppression is a protection mechanism, not a send failure.
- Troubleshooting content before checking DNS and delivery-engine health.