Reports
VH3 AI generates structured operational reports from the intelligence layer so the right briefing lands before the team needs it: daily operations before standup, weekly summaries before planning, account reports before QBRs, and executive health checks before leadership review. Reports read from the same prepared model as discovery, sentinels, and Connie. That means the numbers, cited jobs, customer summaries, and risk signals stay aligned across chat, dashboards, scheduled emails, and custom apps.Report types
Daily operations
A snapshot of yesterday’s work, jobs completed, SLA performance, notable events, and any sentinel triggers. Designed to land in an ops manager’s inbox before the morning standup.Weekly summary
Trends, rankings, and operational highlights across the week. Identifies patterns that aren’t visible in a single day’s data.Account monthly
Per-customer performance report covering job volumes, SLA metrics, response times, and any flagged risks. Suitable for sharing directly with FM clients.Executive health check
A five-dimension health assessment spanning up to three years of operational history. Scored across quality, efficiency, coverage, risk, and growth.Engineer performance
Individual breakdown, completion rates, SLA punctuality, first-time-fix rates, customer feedback, and workload distribution.Site health
Site-level trends, fault frequency, repeat visit rates, equipment failure patterns, and maintenance trajectory.Customer intelligence
Relationship summary, job history, risk signals, communication patterns, commercial activity, and recommended actions.Sentinel digest
Aggregated summary of all sentinel triggers for a given period, useful as a standalone report or as a section within a broader briefing.Report type values
Use the report type that matches the operating rhythm you are automating.Generating reports
Delivery options
Reports can be consumed through the channel that matches the work:- API polling: retrieve the generated report content for custom apps or portals.
- Email delivery: send scheduled reports to named recipients.
- Slack/Teams: route digests and exceptions to channels via automation.
- VH3 Connect: view rendered reports in the application dashboard.
Scheduling
Report generation can be triggered on demand via the API or scheduled via automation. Common patterns:- Daily operations report at 06:30 before the morning standup.
- Weekly summary on Monday morning for operational planning.
- Account monthly report before client review meetings.
- Sentinel digest every morning for the regional channel.
How operators use reports
Reports work best when they become part of a regular operating loop:- Read the daily operations report before standup, then ask Connie to explain one exception.
- Use the weekly summary to decide which sentinel findings need cases.
- Use account monthly for QBR prep, then verify the cited jobs before sharing externally.
- Use engineer performance and site health reports to spot coaching or maintenance actions.
Related
Working with your operation
How reports fit into standups, account reviews, and case follow-through.
Sentinels
Continuous signals that can feed scheduled reports and digests.
Connie
Ask follow-up questions against report findings with citations.
Agent observability
Evidence standards for numbers and cited job references.