Daily Ops Brief

A short Telegram briefing that lands in your team's chat every weekday morning: unread operational email, the standing items your team always cares about, and an AI summary of what's urgent, what needs an owner, and what to do next.

Perfect for teams juggling operational email and a handful of standing checks — open incidents, pending approvals, VIP accounts, whatever your team tracks — with no single place that pulls it all together every morning. Instead of everyone independently checking their inbox, one Telegram message gives the whole team the same starting point for the day. Because it's a normal broadcast, your team reviews it and switches it on themselves, so nothing fires before anyone's seen it. If email is really all you need, the simpler Morning Email Digest template does just that — this one is for teams whose morning picture also includes approvals, incidents, and watchlist items.

• What time should the brief land each morning?
• Which Gmail query or label should it pull from?
• Who should receive it — a tagged admin/ops group, a specific team chat, or a hand-picked list of internal contacts?
• What should be on the standing watchlist every day?
• Connect Gmail and confirm which mailbox or label should feed the brief.
• Review the email search query (it ships as something like unread mail from the last day) and adjust it to match what your team actually wants surfaced.
• Fill in the watchlist with your team's standing checks — open incidents, pending approvals, failed jobs, VIP customers, billing exceptions, or anything else worth checking daily.
• Open Broadcasting, choose your internal admin/ops audience, and activate the schedule once a test run looks right. It ships set for weekday mornings at 9:00 UTC — adjust the time to fit your team.

• Early each weekday, the brief kicks off on its schedule
• It checks your connected Gmail inbox for unread or labeled operational messages
• AI combines those emails with your team's standing watchlist notes into one summary — what's urgent, what needs an owner, what to do next
• The finished brief goes out as a Telegram message to whichever internal audience you've chosen for it

Good to know

• It arrives as a reviewable draft, not something that fires on its own the moment it's installed — you pick the audience and switch on the schedule yourself in Broadcasting. It ships pre-set to run weekday mornings at 9:00 UTC, switched off until you activate it.
• The email side reads from Gmail using a search query you control (for example, unread mail from the last day, or anything with a particular label) — change it any time to widen or narrow what feeds the brief.
• The watchlist section is plain text you maintain — the standing things your team wants checked every day (open incidents, pending approvals, failed jobs, VIP customers, billing exceptions, whatever matters to you).
• If you've also installed the incident triage or approval inbox templates, you can reference their open items in the watchlist notes for now — a direct live connection between templates isn't wired up automatically yet, so it's worth adding once you have several of these running together.
• Built for an internal audience only — an admin/ops tag or a specific internal recipient list, never your customer contacts.

Keep in mind

• Don't activate the schedule until you've reviewed a test run — check Broadcasting and pick the right audience first.
• Keep this strictly internal — operational email and watchlist details shouldn't go to a customer-facing audience.
• If the brief seems to be missing recent messages, check the Gmail query first rather than assuming something is broken.