The monthly client report written from PSA and RMM data — in your brand, with a narrative

How it runs, step by step

1. 1

   A schedule starts one run per client. HTTP steps fetch the month's data from the PSA and RMM APIs: ticket counts by category, SLA attainment, logged hours, open projects, patch compliance, device health, backup status (or the backup table from the backup use case).

2. 2

   The workflow computes the deltas against the previous month and against the client's contract (SLA targets, included hours), flagging anything outside the band.

3. 3

   An agent writes the narrative from the numbers — never inventing one — in the client's language: summary, what improved, what needs a decision, recommendations tied to the data (for example, 23 devices out of patch compliance for a month).

4. 4

   The report is rendered into your template — PDF or a slide deck — with the charts generated from the same data, and placed in the account manager's queue with the editable narrative.

5. 5

   After approval the report is emailed or posted to the client portal and attached to the account ticket; the review edits are kept to tune the prompt.