A Telegram digest for people who do not live in #finops

Your CTO is not in the Slack channel where the NAT findings land. They will not open Cost Explorer. They will glance at a phone on Tuesday morning and ask "are we still leaking."

That is what the management report is for. One org-level digest: spend so far, waste rate, a short briefing, a handful of actions, no instance IDs. Email already did this. A lot of leadership teams live in Telegram instead of Slack.

What we post (and what we do not)

On Enterprise you can send that digest to a Telegram Channel you create. You bring the bot. We do not join as some shared unusd user. The message is a short HTML card: numbers, this week's actions, a button to the full web report.

We do not dump every account scan into the channel. Scan detail still goes to email, Slack, Teams, or SNS. Telegram is the rollup, on purpose. A 400-finding firehose trains people to mute the bot.

The digest has org figures only. No volume IDs, no keys, no "please delete i-0abc." If someone needs the resource list, they open the app.

Why not only email

Email is easy to forward and easy to bury. A channel with the CFO, the VP of engineering, and the FinOps lead is a standing meeting that does not need a calendar invite. Public or private channel, your rules. Revoke the bot token and it stops.

Setup is in the dashboard under management reports: bot token, channel id, frequency. The next scheduled digest posts there. You can keep email too.

If you are the person who already lives in #finops, you do not need this. If you are trying to get a number in front of people who will never install Slack, this is the path.

Marketplace and private offers are available when procurement wants the spend on the AWS bill. The digest is the same product either way.