Plan requirement
| Subscription | Any plan |
| Also required | Workforce Management or Workforce Engagement Management |
| Access | Admin |
The limits that shape what you can build: teams, schedules, history and forecast horizon. The reports also stop at yesterday, with no future date.
The figures that shape a decision
| History kept | 2 years |
| Scheduling ahead | 90 days, and publishing reaches the same 90 days forward and 30 days back |
| Time off shown | One year ahead, 30 days back |
| Shift length | 5 minutes to 24 hours |
| Roles per person | 1 |
| Workstreams in a combined one | 10, and a forecast shows 10 |
| Dashboards | 10, with 12 widgets each |
| Recurring tasks | Repeat over 12 weeks at most, and the recurrence has to end within 90 days |
| Schedule import and export | A 25 MB CSV in, and 30 days at a time out |
| Notes on a task | 1 |
| Public API | 100 requests a second, 100 items a page |
Granularity narrows as the window widens, in five bands:
- A day or less: 15 or 30 minute intervals.
- Up to 7 days: hourly and daily.
- Up to 31 days: daily and weekly.
- Up to 13 weeks: weekly, monthly and quarterly.
- Up to about 13 months: monthly and quarterly.
The reports also stop at yesterday. Neither the agent activity page nor the agent attendance page lets you pick a future date, and the report date picker will not take today either, so anything about the day in progress has to come from the live pages rather than from a report.
History is the one that bites first
Forecasting works from past volume. A new deployment has none, so early forecasts are poor, and that is expected rather than a fault.
Importing historical volume shortens that period considerably.
Interval granularity matters more than horizon
Half-hourly intervals show the Monday morning peak; daily totals hide it entirely. Since the peak is the reason to forecast at all, granularity is where the value sits.
Teams are a design decision, not a limit
Long before you reach any cap, a structure with twenty teams becomes unmanageable. Build teams around how you schedule people.
Plan the horizon around your rota
If schedules are published a month ahead, the forecast must reach at least that far with confidence. The hard stop is 90 days, so a quarterly rota fits and a half-yearly one does not, whatever anybody has promised.
Ask before committing
If somebody expects year-ahead planning or minute-level tracking, confirm what is possible first. Contact pluscloud support and we will check it against your setup.
Comments
0 comments
Article is closed for comments.