“How are we performing for this client this quarter?”
Autotask PSA Datto RMM Datto Backup Microsoft 365 SmileBack HubSpot IT Glue All reports
AI-GENERATED REPORT
You searched for:

How are we performing for this client this quarter?

A single-client QBR covering ticket volume, SLA compliance, customer satisfaction, device health, and contract spend for Wall PLC in Q1 2026.

Built from: Autotask PSA SmileBack CSAT Datto RMM
How this report was made
1
Autotask PSA
Multiple data sources combined
2
Proxuma Power BI
Pre-built MSP semantic model, 50+ measures
3
AI via MCP
Claude or ChatGPT writes DAX queries, executes them, formats output
4
This Report
KPIs, breakdowns, trends, recommendations
Ready in < 15 min

How are we performing for this client this quarter?

A single-client QBR covering ticket volume, SLA compliance, customer satisfaction, device health, and contract spend for Wall PLC in Q1 2026.

The data covers the full scope of Autotask PSA records relevant to this analysis, broken down by the key dimensions your team needs for day-to-day decisions and client reporting.

Who should use this: Account managers, MSP owners, and service delivery leads

How often: Monthly for client reviews, quarterly for QBRs, on-demand when client signals change

Time saved
Cross-referencing client data from multiple tools manually takes hours. This report brings it together.
Client intelligence
See the full picture of each client across service, satisfaction, and commercial metrics.
Retention data
Early warning signals for at-risk clients, backed by actual data instead of gut feeling.
Report categoryClient Management
Data sourceAutotask PSA · Datto RMM · Datto Backup · Microsoft 365 · SmileBack · HubSpot · IT Glue
RefreshReal-time via Power BI
Generation timeUnder 15 minutes
AI requiredClaude, ChatGPT or Copilot
AudienceAccount managers, MSP owners
Where to find this in Proxuma
Power BI › Client Management › How are we performing for this client...
What you can measure in this report
Key Performance Indicators
Quarterly Performance Overview
SLA Performance Detail
Ticket Volume and Hours Analysis
Device Health Summary
Key Findings
Recommendations
Frequently Asked Questions
Total Tickets
SLA First Response
CSAT Score
Quarterly Revenue
Quarterly Business Review
Client: Wall PLC
Period: Q1 2026 (Jan – Mar)
Sources: BackupAutotask PSASmileBack

How are we performing for this client this quarter?

A single-client QBR covering ticket volume, SLA compliance, customer satisfaction, device health, and contract spend for Wall PLC in Q1 2026.

Demo Report: This report uses synthetic data from Proxuma's demo environment. Connect your own Autotask, Datto RMM, and SmileBack accounts to generate this from real data.
1.0 Key Performance Indicators

Top-level metrics for Wall PLC this quarter, pulled from Autotask PSA, Datto RMM, and SmileBack

Total Tickets
63.5%
Met across all tickets
SLA First Response
18.0 hours
Mean time to resolve
CSAT Score
87.8%
Customer satisfaction rating
Quarterly Revenue
€476,622
23 contracts (13 active)
View DAX Query — Client KPIs
EVALUATE ROW("TotalTickets", COUNTROWS('BI_Autotask_Tickets'), "ResolutionSLA", CALCULATE(COUNTROWS('BI_Autotask_Tickets'), 'BI_Autotask_Tickets'[resolution_met] + 0 = 1), "AvgResolution", AVERAGE('BI_Autotask_Tickets'[resolution_duration_hours]), "CSATAvg", AVERAGE('BI_SmileBack_Reviews'[rating]), "CSATCount", COUNTROWS('BI_SmileBack_Reviews'))
2.0 Quarterly Performance Overview

Wall PLC's Q1 2026 service delivery dashboard: where the account stands across every metric that matters for a QBR

MetricWall PLCPortfolio AvgStatus
Total Tickets 2,376 67,521 total 3.5% share
Hours Worked 1,479 33,271 total 4.4% share
Billable Hours 1,849 125% of worked
SLA First Response Met 73.6% 52.9% +20.7pp
SLA Resolution Met 72.5% 63.5% +9.0pp
CSAT Score 89.4% 87.7% Above avg
Revenue €476,622 23 contracts
Devices Online 114 / 320 64.4% offline
Unresolved RMM Alerts 34 Needs review

Wall PLC is outperforming the portfolio average on both SLA metrics and customer satisfaction. First response compliance sits at 73.6%, which is 20.7 percentage points above the overall portfolio rate of 52.9%. Resolution SLA is also above average at 72.5%. The CSAT score of 89.4% confirms that the service experience matches the SLA numbers.

The concern is on the infrastructure side. Only 114 of 320 devices are reporting as online in Datto RMM, and 34 alerts remain unresolved. This does not necessarily mean 206 devices are down. It likely reflects stale agent installations, decommissioned hardware, or devices that have not checked in recently. But it needs cleanup because it obscures real issues.

View DAX Query — Revenue and Contract Summary
EVALUATE
ADDCOLUMNS(
    VALUES('BI_Autotask_Companies'[company_name]),
    "Revenue", CALCULATE(SUM('BI_Autotask_Billing_Items'[total_amount])),
    "Cost", CALCULATE(SUM('BI_Autotask_Billing_Items'[our_cost])),
    "Contracts", CALCULATE(COUNTROWS('BI_Autotask_Contracts'))
)
ORDER BY [Revenue] DESC
3.0 SLA Performance Detail

First response and resolution SLA compliance for Wall PLC vs. the portfolio average, based on 2,376 tickets this quarter

73.6% 1,748 / 2,376 First Response Met
72.5% 1,723 / 2,376 Resolution Met
52.9% Portfolio FR Portfolio Avg (FR)
63.5% Portfolio Res Portfolio Avg (Res)
Reading this chart: Wall PLC beats the portfolio on both SLA dimensions. First response compliance is 20.7 percentage points above average. Resolution compliance is 9.0 percentage points above average. Of 2,376 tickets, 1,748 received a first response within SLA and 1,723 were resolved within SLA.
View DAX Query — SLA Compliance per Client
EVALUATE
ADDCOLUMNS(
    VALUES('BI_Autotask_Companies'[company_name]),
    "Tickets", CALCULATE(COUNTROWS('BI_Autotask_Tickets')),
    "FRMet", CALCULATE(
        COUNTROWS('BI_Autotask_Tickets'),
        'BI_Autotask_Tickets'[first_response_met] + 0 = 1),
    "ResMet", CALCULATE(
        COUNTROWS('BI_Autotask_Tickets'),
        'BI_Autotask_Tickets'[resolution_met] + 0 = 1),
    "FRPct", DIVIDE(
        CALCULATE(COUNTROWS('BI_Autotask_Tickets'),
            'BI_Autotask_Tickets'[first_response_met] + 0 = 1),
        CALCULATE(COUNTROWS('BI_Autotask_Tickets'))),
    "ResPct", DIVIDE(
        CALCULATE(COUNTROWS('BI_Autotask_Tickets'),
            'BI_Autotask_Tickets'[resolution_met] + 0 = 1),
        CALCULATE(COUNTROWS('BI_Autotask_Tickets')))
)
ORDER BY [Tickets] DESC
4.0 Ticket Volume and Hours Analysis

How Wall PLC's 2,376 tickets translate into worked hours and billable hours, with utilization context

Worked Hours
1,479 hrs
Billable Hours
Billable vs. Worked: Billable hours (1,849) exceed worked hours (1,479) by 25%. This typically happens when fixed-price contract hours are billed at a flat rate regardless of actual time spent, or when minimum billing increments round up the total. Either way, the account is profitable on a per-hour basis.
MetricValueContext
Total Tickets 2,376 Q1 2026
Hours Worked 1,479 0.62 hrs / ticket
Billable Hours 1,849 0.78 hrs / ticket
Utilization Ratio 125% Billable > Worked
View DAX Query — Ticket Volume and Hours
EVALUATE
ADDCOLUMNS(
    VALUES('BI_Autotask_Companies'[company_name]),
    "Tickets", CALCULATE(COUNTROWS('BI_Autotask_Tickets')),
    "WorkedHours", CALCULATE(
        SUM('BI_Autotask_Tickets'[worked_hours])),
    "BillableHours", CALCULATE(
        SUM('BI_Autotask_Tickets'[billable_hours]))
)
ORDER BY [Tickets] DESC
5.0 Device Health Summary

Datto RMM device status and unresolved alert count for Wall PLC's 320 managed devices

35.6% Online 114 of 320 devices online
64.4% Offline 206 of 320 devices offline
MetricCountStatus
Total Devices 320 Managed in RMM
Online 114 35.6%
Offline 206 64.4%
Unresolved RMM Alerts 34 Open
Why 64.4% offline? A high offline percentage does not always mean devices are down. Common causes: decommissioned machines still listed in RMM, laptops that only check in on VPN, seasonal equipment, or agents that need reinstallation. The recommended action is to audit the device list and remove or re-onboard stale entries.
View DAX Query — Device Health per Company
EVALUATE
ADDCOLUMNS(
    VALUES('BI_Datto_Rmm_Devices'[company_name]),
    "TotalDevices", CALCULATE(COUNTROWS('BI_Datto_Rmm_Devices')),
    "Online", CALCULATE(
        COUNTROWS('BI_Datto_Rmm_Devices'),
        'BI_Datto_Rmm_Devices'[status] = "online"),
    "Offline", CALCULATE(
        COUNTROWS('BI_Datto_Rmm_Devices'),
        'BI_Datto_Rmm_Devices'[status] = "offline"),
    "UnresolvedAlerts", CALCULATE(
        COUNTROWS('BI_Datto_Rmm_Alerts'),
        'BI_Datto_Rmm_Alerts'[resolved] = FALSE())
)
ORDER BY [TotalDevices] DESC
6.0 Key Findings
!

64.4% of devices are reporting as offline in Datto RMM

206 of 320 devices are not checking in. This creates blind spots for patch management, antivirus status, and hardware health monitoring. Even if most of these are stale entries, the noise makes it harder to spot real outages. An RMM device audit should be scheduled before the next QBR.

!

34 unresolved RMM alerts need triage

Open alerts that sit unresolved accumulate over time and lose meaning. Technicians stop paying attention when the alert queue is noisy. Review these 34 alerts, resolve the ones that are no longer relevant, and escalate any that indicate real hardware or software problems.

SLA performance is well above the portfolio average

First response SLA at 73.6% and resolution SLA at 72.5% both exceed the portfolio benchmarks of 52.9% and 63.5%. This client is getting faster responses and faster resolutions than most accounts in the book. The team is delivering well here.

Customer satisfaction is strong at 89.4%

The CSAT score of 89.4% is 1.7 percentage points above the portfolio average. Combined with the strong SLA numbers, this indicates consistent service quality. This is the kind of account where a case study or testimonial request would be well received.

7.0 Recommendations

Actions to take before the next quarterly review, ordered by priority

1

Audit the RMM device list and remove stale entries

With 206 devices showing as offline, the RMM console for Wall PLC is unreliable as a monitoring tool. Schedule a device audit: cross-reference the RMM device list with the client's active asset inventory. Remove decommissioned machines, reinstall agents on devices that have gone silent, and flag any truly missing hardware. Target: get the offline rate below 20% by end of Q2.

2

Triage and close the 34 open RMM alerts

Go through each unresolved alert. Categorize them as actionable (real issue that needs a fix), informational (can be auto-resolved with a policy change), or stale (relates to a device that no longer exists). Clearing the queue will restore trust in the alerting system and make new critical alerts visible immediately.

3

Review the 10 inactive contracts

Wall PLC has 23 contracts on file, but only 13 are active. The remaining 10 may be expired, paused, or superseded. Confirm whether any of these should be renewed, consolidated, or formally closed. Clean contract data improves revenue forecasting accuracy.

4

Request a testimonial from this client

Wall PLC has above-average SLA compliance and a CSAT of 89.4% across a meaningful ticket volume of 2,376. These are the metrics of a satisfied client. Ask their primary contact for a written testimonial or case study. Satisfied clients who generate high volume are the most credible references you can offer prospects.

8.0 Frequently Asked Questions
Where does this data come from?

This report pulls from three sources via Proxuma Power BI: Autotask PSA (tickets, hours, contracts, billing), Datto RMM (device status, alerts), and SmileBack (customer satisfaction ratings). The AI connects to Power BI via MCP, writes DAX queries against the live data model, and generates the report automatically.

What counts as "SLA Met" for first response and resolution?

SLA compliance is tracked in Autotask using the first_response_met and resolution_met fields. A value of 1 means the ticket met the SLA target defined in the contract. A value of 0 means it was breached. The percentages in this report are the count of tickets with met = 1 divided by total tickets for the client.

Why are billable hours higher than worked hours?

Billable hours can exceed worked hours when contracts use minimum billing increments (e.g., 15-minute or 30-minute minimums), when fixed-fee contract hours are billed at a predetermined rate, or when travel time is billed separately. In Wall PLC's case, 1,849 billable vs. 1,479 worked suggests contract billing rules are adding the difference.

How is the CSAT percentage calculated?

SmileBack uses a 3-point scale: happy (5), neutral (3), and unhappy (1). The CSAT percentage shown here (89.4%) represents the average rating normalized to a percentage scale. A score of 89.4% means the weighted average of all responses is strongly positive, with most responses landing on the happy end of the scale.

Can I generate this QBR for a different client?

Yes. Connect Proxuma Power BI to your Autotask, Datto RMM, and SmileBack accounts. Then ask the AI via MCP: "How are we performing for [client name] this quarter?" The AI writes the DAX queries, pulls the numbers, and generates a formatted QBR like this one in under fifteen minutes.

Generate this report from your own data

Connect Proxuma Power BI to your PSA, RMM, and M365 environment, use an MCP-compatible AI to ask questions, and generate custom reports - in minutes, not days.

See more reports Get started