IT OPS
Shared Mailbox Weekly Responsiveness Scorecard
Weekly report that pulls reply-time history for every team shared mailbox from Postgres, computes coverage and median first-response metrics per inbox.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly on Monday morning
- ActionQuery prior-week logs from PostgresPostgres
- LogicCompute ack rate and response metrics per mailbox
- LogicRank mailboxes and flag below-target
- OutputPublish scorecard to TeamsMicrosoft Teams
What it does
Once a week it aggregates the per-message coverage and response data your other flows have logged to Postgres, then computes a scorecard for each shared mailbox: volume received, percent acknowledged, median first-response time, and number of SLA breaches. It publishes the ranked scorecard to a Teams channel so managers see which inboxes are well-covered and which need staffing.
When to use it
Use it when you need a recurring management view of how well shared inboxes are being staffed, rather than per-incident alerts. It turns raw logs into a trend you can act on in a weekly ops review.
How it works
- 1A weekly schedule fires Monday morning.
- 2Query Postgres for the prior week's logged messages, acknowledgments, and breach events across all mailboxes.
- 3Group by mailbox and compute volume, ack rate, median first-response time, and breach count.
- 4Rank mailboxes from best to worst coverage and flag any below your target threshold.
- 5Render a compact scorecard table.
- 6Post the scorecard to the leadership Teams channel for the weekly review.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect Microsoft TeamsChannels, chats, files.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More IT Ops workflows
Daily Building Anomaly Digest to MS Teams
Each morning queries BigQuery for the prior day's flagged sensor anomalies, summarizes them by site and system into a ranked briefing.
Indoor Air Quality Breach to Tenant Notice and Work Order
Listens for CO2, VOC, or humidity sensor alerts via webhook, and when a zone exceeds occupant-safety limits it emails affected tenants, opens a Monday remediation task.
Self-Service Reclaim Email for Idle Users
Detects users idle in a SaaS app past the threshold and emails each one a keep-or-release link; unanswered seats after the deadline are auto-flagged for removal.
Outlook Room Conflict Resolver with Approval Gate in Teams
When an Outlook room clashes, proposes a rebooking and asks the bumped meeting's organizer to approve the move in Microsoft Teams before any change is made.
Outlook Room Double-Booking Resolver with Auto-Rebook
Detects when two meetings claim the same Outlook room resource and automatically relocates the lower-priority meeting to a comparable free room.
Monthly Wasted-License Cost Report
Aggregates inactive-seat data across all tracked SaaS apps each month, computes total reclaimable spend, and delivers a ranked cost report to leadership in Notion and Slack.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.

Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.
