Skip to content

Daily Cost Digest: Proactive Daily Briefing

Every day at 09:00 UTC, Xplorr posts a cost summary to Slack. No one needs to ask: the bot pushes what changed, what’s at risk, and what to look at.

The digest is Slack only. Microsoft Teams delivery is being built with the Teams bot.

  • Spend on the last complete day against the average of up to 7 complete days before it, with the change in percent. Today’s partial figure is shown separately and labelled as partial.
  • Top services on that day (up to 10).
  • Top resources by cost.
  • Charts: a service breakdown and a daily trend over complete days.
  • Anomalies: how many open cost spikes were detected from that day on, with the highest severity, plus any forecast alerts, listed separately.
  • Open recommendations: how many are waiting, with their total estimated monthly savings. Recommendations with no savings estimate are counted separately, not summed as zero.
  • Budgets: current spend against each budget.
  • Forecast: projected month end spend, compared with your budget when you have exactly one organization wide budget.

Buttons at the bottom open the console: View Dashboard, Cost Analysis and Recommendations.

The digest runs as a scheduled job inside the Xplorr agents service:

  1. At 09:00 UTC the scheduler lists every connected Slack workspace
  2. For each organization it fetches the data above from the Xplorr API
  3. It builds a Block Kit message
  4. It posts it to each routed channel with the digest switch on, or to the workspace’s default channel when there are no routes

Every channel receives the same organization wide digest. Scoping a channel’s digest to specific accounts, services or tags is being built; see Channel Routing.

The time is a deployment setting (DIGEST_CRON), the same for every organization. It cannot be set per channel.

  1. Connect Slack. The Xplorr Slack app is set up with the Xplorr team; see Slack Bot Overview.
  2. Pick the channel. By default the digest goes to the workspace’s default channel. To post it to more channels, see Channel Routing.

There are no per section toggles: every digest carries the sections above, and sections with no data are left out.

If your organization has only a Slack webhook configured (Settings in the console), Xplorr posts a webhook version of the daily digest to that webhook’s channel at 09:00 UTC. It is skipped on days with zero spend.

The layout of a digest in Slack (figures are illustrative):

📊 Daily Cost Digest: Example Org
2026-03-21 | Powered by Xplorr
─────────────────────────────────
Spend (2026-03-20) 7-day avg
$1,847.23 $1,620.50 (+14.0%)
─────────────────────────────────
Top Services
1. EC2 $842.10
2. RDS $312.45
3. S3 $198.70
─────────────────────────────────
2 anomalies detected, highest severity: medium
─────────────────────────────────
Open Recommendations Estimated Savings
8 $1,240.00/mo
─────────────────────────────────
[View Dashboard] [Cost Analysis] [Recommendations]

Can I get the digest in Microsoft Teams? Not yet. The Teams bot is being built.

What if no cost data is available yet? The digest reports the last day with complete data. Once your first sync completes, the next digest includes your data.

Can I trigger a digest on demand? No. Ask the bot a question such as “What did we spend yesterday?” for an answer on demand.