Buyer searches for "intraday reforecasting contact center" or "shift bidding and adherence software" usually land on the standalone WFM specialists. If you run a modern contact center on Devotel Orbit, the loop those suites sell is already inside your contact center: forecast, schedule, adherence, and the markets and exception workflows that keep the day honest. This post walks that loop the way a supervisor actually works it, names the dashboard routes and docs guides where each step lives, and stays strictly to capability that is shipped today.
1. What the WFM pillar covers
Workforce management in Orbit is twelve shipped processes working one loop, all scoped per tenant and all live on the Scheduling page (Voice → Scheduling in the dashboard):
- Forecast — volume forecasts per channel with a planned-versus-actual accuracy readout.
- Schedule — shift templates applied to agents as assignments, individually or in bulk.
- Daily summary — one screen rolling the day's plan into scheduled headcount per queue against expected volume.
- Real-time adherence — each agent's current activity compared with the scheduled activity, against a default 85% target with a configurable breach threshold.
- Team adherence rollup — adherence percentage per queue per day, with an optional queue filter.
- Exceptions — typed divergence (
system_outage,emergency_meeting,unplanned_coaching,approved_absence,training,other) routed through an approve / deny / cancel lifecycle. - Shift activities and conformance — shifts broken into typed activities (
lunch,break,training,coaching,meeting,off_phone,other) so adherence compares against the right expectation. - Intraday staffing — interval-by-interval required-versus-actual staffing for the current date; the reforecasting surface.
- Open-shift market — publish an open shift, collect agent bids, award one, cancel if the need clears.
- Overtime market — publish an overtime offer, agents submit withdrawable claims, the scheduler awards.
- VTO market — the symmetric surplus workflow: publish voluntary time off, agents claim it, awarded hours come off the plan.
- Timekeeping and skills — per-agent timesheets with a payroll export, and agent skill records that feed both routing and scheduling.
The canonical overview, Workforce Management in Orbit's CCaaS: Forecast, Schedule, Adherence, walks the same twelve surfaces module by module with the honest-parity read against dedicated WFM vendors; this post is the operational companion: how a team gets the loop running in its first week and how it works the day once it is. The product docs go one level deeper: WFM workflows covers the end-to-end setup, the WFM model concept defines forecast, shrinkage, and adherence primitives, forecasts and the staffing optimizer details the planning inputs, and intraday adherence and requests covers the live-day surface.
2. Quickstart: your first forecast-to-schedule cycle
Four steps, each on a shipped route. Nothing here is on a roadmap; every screen named exists in the dashboard today.
- Enable WFM on your tenant. Open Voice → Scheduling in the dashboard. WFM ships inside the contact-center pillar with per-tenant scope; there is no separate module to license and no second system of record to reconcile. Your tenant's queues, channels, and agents are already the inputs.
- Connect skills. On the Scheduling page, open the agent skills panel and record each agent's proficiency per skill. Routing and scheduling read the same skill records, so a schedule built here routes work to agents who can actually take it.
- Run the first forecast. In the forecast view on the Scheduling page, build a volume forecast per channel and check the accuracy readout against actuals as the week lands. The forecasting guide walks the inputs, shrinkage assumptions, and how the optimizer turns a forecast into required headcount.
- Publish the schedule. Apply shift templates as assignments, then open the daily summary to compare coverage against expected volume before the first queue interval. Any interval that starts short goes to the open-shift market the same day. The WFM workflows guide covers template setup and bulk assignment in detail.
3. Intraday reforecast, shift markets, and the exception states a supervisor touches
The morning forecast is a hypothesis. The intraday staffing view on the Scheduling page recomputes required versus actual staffing interval by interval as actuals arrive, so "we are short from 14:00" is a readout, not a discovery at the end-of-day report. When an interval trends short, the response is one of three shipped markets: publish an open shift for tomorrow's gap, publish an overtime offer for today's shortfall, or, when volume falls below forecast, publish a VTO offer and take awarded hours off the plan. Agents bid or claim, can withdraw until awarded, and the scheduler awards; every step is recorded, so extra-hours distribution is transparent and auditable rather than a manager's private negotiation.
Reality also intervenes in the other direction, and the exception workflow is what keeps the adherence report honest when it does. A supervisor files an exception typed system_outage, emergency_meeting, unplanned_coaching, approved_absence, training, or other, and it moves through three states a supervisor actually touches: approve, deny, and cancel. An approved exception stops counting against adherence, which is the difference between measuring plan-versus-reality and punishing agents for a dialer outage they did not cause. The intraday guide walks the live-day queue and the request side of the same surface.
4. Payroll export touchpoints
At the end of the pay period the timekeeping view on the Scheduling page closes the loop: per-agent timesheets aggregate scheduled hours, awarded overtime, and exception-backed absences, and the payroll export downloads them as CSV so approved hours reach payroll as data, not as a spreadsheet someone retyped. That is the whole payroll claim: Orbit exports the hours file, and your payroll system remains the system of record for pay. For the money side of the tenant, usage and spend are documented separately in the billing docs; the WFM payroll export carries hours and approvals, not billing data.
5. Over-adherence alerts
Under-adherence has the breach threshold: real-time adherence flags divergence past a configurable window (1 to 480 minutes, default 5) as a live list a team lead works down. Over-adherence reads from the other shipped views: the team adherence rollup shows queues running persistently hot against plan, and the intraday staffing view shows the surplus interval by interval, which is exactly the condition a VTO offer resolves. The alerting side of the same story is the tenant alerting ladder: usage-anomaly alerting watches the tenant's traffic for the swings that make adherence numbers misleading, and Usage anomaly alerts: the tenant alerting ladder documents how those alerts are scoped and delivered per tenant. Both the breach threshold and the alerting posture are tenant-owned settings; your operations team decides what counts as divergence worth a notification.
Frequently asked questions
What does workforce management cover in Devotel Orbit?
Twelve shipped processes on one loop: per-channel forecasts with an accuracy readout, shift templates and assignments, a daily summary, real-time adherence with a default 85% target, a team adherence rollup, typed exceptions with an approval lifecycle, shift activities and conformance, intraday staffing, open-shift bidding, overtime offers, VTO offers, and timekeeping with a payroll export plus agent skills. Everything lives on the Scheduling page under Voice, scoped per tenant.
Can Orbit reforecast during the day?
Yes. The intraday staffing view recomputes required versus actual staffing interval by interval for the current date, and the shortfall and surplus levers (overtime offers, open shifts, VTO offers) are shipped workflows on the same page.
How do the open-shift, overtime, and VTO markets work?
A scheduler publishes an open shift, an overtime offer, or a VTO offer; agents submit bids or claims that stay withdrawable until awarded; the scheduler awards one and can cancel a published shift if the need clears. Every step is recorded, so distribution is auditable.
Which exception states can a supervisor approve?
Exceptions are typed as system outage, emergency meeting, unplanned coaching, approved absence, training, or other, and each moves through approve, deny, or cancel. Approved exceptions stop counting against adherence.
How do hours reach payroll?
The timekeeping view aggregates per-agent timesheets, and the payroll export downloads approved hours, overtime awards, and exception-backed absences as CSV. Your payroll system stays the system of record for pay; Orbit exports the hours file.
How does over-adherence get surfaced?
The team adherence rollup and the intraday staffing view show queues running over plan, the surplus condition a VTO offer resolves, while usage-anomaly alerting on the tenant alerting ladder watches the traffic swings behind misleading adherence numbers. Breach thresholds and alerting posture are tenant-owned settings.