A status page only helps customers who remember to check it. Mailing the same uptime, response-time, and SLA numbers as a periodic digest puts the report in front of them directly — with a KPI scorecard or line chart bound to your real metrics instead of hand-typed.
Every status page's real audience is the small fraction of customers who think to visit it during an incident. A mailed digest reaches everyone else.
The headline number
A KPI scorecard shows this period's uptime percentage or average response time, with a trend arrow against the previous period — bindable to a live data source the same way an automated performance digest is.
The trend behind it
A line chart shows response time or incident count over the period, so a customer sees the shape of the trend, not just one snapshot number.
Current standing against a target
A gauge shows standing against an SLA target as a threshold-colored arc, with the value always repeated as real text next to it. Unlike the KPI scorecard and line chart, gauge has no live data-source binding yet — its value gets typed in fresh each send.
One project, every customer's own numbers
A bound chart's filter can reference the recipient's own merge tag — an account ID or name field from your audience source — so a single project sends every customer their own account's numbers rather than your whole platform's.
Getting started
Compose a KPI scorecard, line chart, and gauge into a report layout, bind what you can to your metrics data source, and put it on a recurring schedule.