Customer experience
A Customer Usage Dashboard Should Answer These Four Questions
By the Orvlin team · · 2 min read
Customer usage dashboard design: what to decide
A chart rising steadily looks useful until a buyer asks whether it includes yesterday’s batch or the team’s second workspace. Put definitions and scope near the number so customers do not need support to interpret their own activity.
Distinguish measured consumption from an estimated charge. Explain data freshness, allowance reset and pending adjustments. If the dashboard offers a forecast, keep it visibly separate from charges already incurred. A forecast is not an invoice.
An example with the numbers exposed
An account sees 7,500 of 10,000 included operations used, an estimate of zero overage so far and a reset date of November 5. A separate projection might show likely overage by then. Those numbers answer different questions and should not be combined.
The mistake worth avoiding
A smooth graph can hide a stale pipeline. Show the last successful update, and avoid displaying a confident zero when usage data is unavailable. Customers may make spending decisions based on that zero.
A practical checklist
- Display the account and period being viewed.
- Separate included, paid and pending usage.
- Label estimates and data freshness.
- Make the supporting usage export accessible.
Frequently asked questions
- Should we show usage or money first?
- Choose according to the buyer’s main concern, but offer both. A unit total explains activity; an estimated amount supports budgeting.