Alerts only help if you can trust them. A run of false alarms — "domain not authenticated" when your records were fine, "low credit" when you had just been refunded, "delivery stalled" on a campaign that was actively sending — was eroding that trust, and a few alert buttons were sending you to the wrong screen.
What was happening
Several alerts were reading from the wrong source or applying the wrong threshold. The email-authentication advisory checked a saved snapshot of your SPF, DKIM and DMARC records rather than what is actually published in DNS right now — so if you had fixed your records but never re-ran the in-app verify, or never had a saved record at all, it kept warning you that your domain was not configured. That stale-snapshot case was the most common false positive of the bunch, and it is exactly the kind of warning that trains you to ignore the warnings. The low-credit alert looked only at spend, so it could fire even when refunds had outpaced your spending and your balance was flat or rising — telling you to top up at the very moment your balance was actually recovering. A draft backlog sitting behind a campaign that was still delivering normally was treated as a critical "campaign delivery stalled" even though delivery had not stopped; a queue catching up was being reported with the same urgency as a campaign that had genuinely ground to a halt. And the "Review campaign" button in alerts dropped you on the full campaigns list instead of the campaign that triggered the alert, so you had to find it yourself before you could act.
What we fixed
Each alert now reflects reality. The SPF/DKIM/DMARC advisory is decided from a live DNS lookup at the moment it is evaluated, so it clears as soon as your records are genuinely in place — whether or not you ever re-ran the in-app verify, and even if you had no saved record before. The low-credit alert now considers net burn: if your refunds equal or exceed your spend, it stays quiet instead of crying wolf. A draft backlog behind a campaign that is still actively delivering now surfaces as a warning, not a critical delivery-stalled alarm, so you can tell a genuine stoppage from a queue that is simply catching up. And every "Review campaign" link now deep-links straight to the specific campaign that raised it.
Why it matters
When alerts are accurate, you act on them. You stop chasing a domain-authentication warning that was already resolved, you stop seeing low-credit panic right after a refund, and a real delivery stall is no longer buried among false criticals. And when something does need your attention, one click takes you to the exact campaign instead of making you hunt for it.