> ## Documentation Index
> Fetch the complete documentation index at: https://altostrat.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Weekly executive report for managed customers

> Pull the week's uptime, ticket backlog, change activity, backup health, and security posture from the systems they live in, then deliver a customer-ready PDF and a Teams summary every Monday at 09:00.

Every customer with a managed services contract gets a Monday report covering the prior week. The MSP needs to produce twelve customer reports — uptime, ticket throughput, changes executed, backup posture, security incidents — without an analyst spending their morning copying numbers into PowerPoint.

## 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

<Steps>
  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Archive">
    Each report is filed in the customer's SharePoint folder with a date-stamped filename for the next QBR pack.
  </Step>
</Steps>

## 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

<CardGroup cols={2}>
  <Card title="Procedures" icon="workflow" href="../../procedures" arrow="true" cta="Build the runbook">
    Author `Customer weekly report` once and run it per customer code.
  </Card>

  <Card title="Files and artifacts" icon="file" href="../../files-and-artifacts" arrow="true" cta="Manage reports">
    How generated reports flow back into the workspace and out to customers.
  </Card>
</CardGroup>