Systems involved
| System | Role |
|---|---|
| Zabbix / LibreNMS | Uptime and SLA percentages per site and device class. |
| ConnectWise PSA / Halo | Ticket open, close, and SLA breach counts. |
| Datto / Veeam | Backup job status, RPO and RTO posture. |
| Microsoft Defender / Sentinel | Security incidents and posture changes. |
| Cloudflare / status checks | Customer public site availability. |
| Studio Procedures | The Customer weekly report runbook. |
| Gmail / Outlook | Delivery to the customer’s CTO and account owner. |
| Microsoft Teams | Customer-shared channel and internal #weekly-reports. |
| Google Drive / SharePoint | Archive of every report sent. |
Walkthrough
Run the weekly report procedure per customer
The
Customer weekly report procedure takes a customer code as the only argument. It runs in parallel for the twelve customers on Monday at 06:00.Pull the source data
For each customer, Copilot calls Zabbix for uptime, the PSA for ticket counts and SLA, Datto for backup health, Defender for security signals, and the public-site checker for customer-facing availability.
Reconcile against last week
The procedure compares against the prior week and flags meaningful deltas — a 3 percent SLA drop, a backup that hasn’t run in 48 hours, an open incident, a ticket trend going the wrong way.
Generate the report artifact
Copilot writes a Markdown report with the uptime table, ticket breakdown, change list, backup matrix, security summary, recommendations, and an executive summary at the top. The report renders as a clean PDF.
Hold for review
The procedure pauses for a human review before delivery. The account engineer scans the twelve reports, edits commentary where the data needs context, and approves.
Deliver the report
Each PDF goes through Gmail to the customer CTO and account owner with a short cover note. The same report is posted in the customer-shared Teams channel as a pinned message for the week.
Internal post
A condensed roll-up — twelve customers, key risks, actions required this week — is posted in the internal
#weekly-reports channel so the team starts the week with the same picture.Where Studio earns its keep
- One procedure produces twelve consistent customer reports without an analyst opening five dashboards twelve times.
- The numbers come from the source systems, not a stale CRM field someone forgot to update.
- The deltas surface what’s worth talking about — the report leads with the things the customer should care about.
- The same artifact reaches the customer email, the shared Teams channel, and the QBR archive in one delivery.
Related
Procedures
Author
Customer weekly report once and run it per customer code.Files and artifacts
How generated reports flow back into the workspace and out to customers.