Notifications are easy to send and easy to ignore. The winning pattern is opinionated routing plus lean storytelling.

The routing rules we ship by default

Before diving in, remind teams how Stack Dyno supports this stage so the bullets feel connected.

• Send anomaly alerts to PagerDuty only when the dollar change crosses the team-specific budget.
• Deliver weekly savings summaries to Slack with three bullets and one screenshot.
• Email PDF/CSV reports to finance once a month with a link back to the live view.

const payload = {
  destination: 'slack',
  channel: '#cloud-spend',
  title: 'GKE namespace variance',
  summary: 'dev-payments is +34% WoW. Rightsize requests by ~2 vCPU to return to baseline.',
  deepLink: '/kubernetes/allocation?namespace=dev-payments',
};

fetch('/api/alerts', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify(payload),
});

Content that earns clicks

Before diving in, give readers a quick narrative so the checklist lands with context.

• Start with the impact in dollars and the recommended action.
• Keep screenshots small and annotated; do not paste a full dashboard.
• Include owner and environment labels directly in the message.
• Link to the view with the filter pre-applied so people can verify quickly.

Measure what lands

Track open rates, click-through, and the number of accepted fixes. If a channel underperforms for two weeks, change the format or the audience before adding more rules.

When alerts are opinionated and scoped, customers will actually open them. Stack Dyno keeps the delivery, formatting, and deep links consistent so you can focus on the message.

---