Staffing CurveSupport
Before you write in
Most issues are one of these five.
| Symptom | Cause |
|---|---|
| Staffing looks far too high | Average handle time is a plain column instead of a weighted measure. Use DIVIDE(SUM(HandleSeconds), SUM(Contacts)). Why this happens. |
| Only one point per day on the chart | The interval field is bound to the Date Hierarchy instead of the plain field. Click the field in the well and pick the column, not the hierarchy. |
| Scheduled staffing doubles when interval length changes | The roster measure sums instead of levelling. Scheduled agents must represent staffing at the interval grain, not a sum of repeated row-level values. |
| "This field takes whole-number percentages" | A what-if parameter was built over 0 to 1 instead of 0 to 100. |
| A gap in the scheduled line | Those intervals have no roster value. A blank is treated as unknown, not as zero agents. |
The full user guide, field mapping reference and calculation guide cover everything else the visual does.
Contact
Email: cap@work4wifi.com
Response time: two business days.
Please include:
- What you expected and what you saw
- The visual version, from the Format pane under About
- Power BI Desktop version, or that you were in the Power BI service
- A screenshot if the problem is visual
Please do not send customer data. A description of the shape of your data is almost always enough. If a sample is genuinely needed we will ask for one with volumes scaled or anonymised.
Licensing questions
Licences are purchased on AppSource and assigned in the Microsoft 365 admin center. Billing, refunds and seat changes go through Microsoft, not us — we cannot see or alter your subscription. If a user holds a licence and the visual still shows Evaluation Mode, that is ours to fix: write in with the tenant and the user, and we will trace it.