CSV
Activity stream · Status grid · Record card
Four real views that ship in the product today. A per-staff timesheet log showing the sync status of each pay period. A sync activity stream with every API request and response. A reminder log showing who got pinged, when, and what they replied. CSV export from every view. All driven by the continuous sync data, all hosted in AU.
The activity stream is the screen you watch when something feels off. Every sync cycle, every approved-entry pull from ConnectWise, every write to a Xero payroll timesheet, every Twilio SMS, every OAuth refresh, every retry after an outage, all logged with a timestamp, a status, the API response code, and a one-line summary. Filter by source (Xero API, ConnectWise API, Twilio, OAuth, Cycle, Replay). Click any row to expand the full request and response payload for debugging.
In a normal week, you do not open this screen. It runs quietly. But when a tech says "my hours did not make it through" or your bookkeeper asks why a timesheet line looks off, the stream is the single source of truth. Filter to that staff member, that pay period, and read the actual sequence of events.
One row per staff member, one column per recent pay period. Each cell carries the real submission status the system holds for that staff member's timesheet: Submitted, Ready to submit, Insufficient time, Mapping error, Submitted (Overridden), Exceeds time. The colour coding mirrors the in-product status. Click any cell to drill into that pay period's record card and read the full history.
The grid is sortable by name, by last-period status, or by recurring-error pattern. Patterns surface immediately: a staff member with a recurring mapping error across three periods is something to act on; a one-off Insufficient time pill on a leave week usually is not. The grid tells you which conversation is worth having.
| Staff | Apr 1–14 | Apr 15–28 | Apr 29–May 12 | May 13–26 | May 27–Jun 9 |
|---|---|---|---|---|---|
| JPJack Patterson | Submitted | Submitted | Submitted | Submitted | Ready |
| LOLiam O'Brien | Submitted | Insufficient | Insufficient | Mapping error | Pending |
| CBCharlotte Bennett | Submitted | Submitted | Submitted | Submitted | Ready |
| MWMia Walker | Submitted | Submitted | Submitted | Submitted | Ready |
| ETEthan Thompson | Submitted | Submitted | Insufficient | Submitted | Pending |
| DHDaniel Henderson | Insufficient | Mapping error | Mapping error | Insufficient | Pending |
Click a staff member from the status grid and the record card opens. Every cycle that touched their timesheet is listed in reverse-chronological order: posts to Xero, replays after mid-week edits, SMS reminders fired, manual overrides applied, pay-period boundary events. Each entry expands to show the full request and response payload, the override note if there was one, and any error detail returned by the Xero API.
The record card also surfaces the actions you can take inline. Re-sync this pay period now. Apply a manual override (because the tech is on leave and the timesheet needs to land as-is). Mark the period as exception (no SMS will fire next cycle). The actions are the same buttons your bookkeeper would have hit in ConnectWise, surfaced here so you do not have to switch tabs.
A weekly digest emailed automatically to the ops manager, the MSP owner, or anyone you add to the recipients list. Sent every Friday close (configurable). Contains a snapshot of the period: cycles run, timesheet lines posted to Xero, SMS reminders fired, errors hit, the top three staff by hours-logged and the bottom three by compliance gap. The summary is generated from the same data the live activity stream draws on, no separate pipeline, no stale numbers.
The email is the lowest-friction reporting surface. Operators who do not log into Connect Zero every day still get the headline numbers every Friday. The owner who only cares about exceptions sees the bottom three staff list and can ask a single follow-up question. Recipients, frequency, and detail level are configured per tenant.
All reports export. CSV for the activity stream, the status grid, and the per-staff record. PDF for the weekly summary email archive. JSON for anyone integrating Connect Zero data into a downstream BI tool. The exports include all visible columns plus the metadata Connect Zero tracks (sync timestamps, entry IDs, audit references). CSV exports are timezone-anchored to the tenant's primary timezone (Adelaide for most AU customers). JSON exports include the timezone offset on every timestamp.
Audit log exports are available on the Scale tier with 365-day retention. Standard tiers retain 30 days (Starter) and 90 days (Team). For compliance audits or year-end reviews, request an audit log export from support and we deliver as encrypted ZIP.
The live demo runs all four reporting views against synthetic data. Click through the activity stream, the status grid, the per-staff record, and a sample weekly summary email. Ungated, no signup.
Summarize your business so the visitor can learn about your offerings from any page on your website.