Workforce: staff the busy hours, not the average ones

Staffing by gut feel produces the same two failures every time: quiet hours with too many people, and the 10am rush that burying three agents anyway. The workforce module replaces the gut with arithmetic — your arithmetic, from your real volume.

Forecast, then size

The module reads your actual contact history — tickets by channel, chats, calls with their handled minutes, bookings — and builds a forecast: a recent-weeks baseline weighted by day-of-week patterns, with a band around it so you can see how confident the number is. Then the staffing math does what call centers have done for decades: Erlang C, the standard queueing model, converts forecast volume plus your service-level target into how many people each hour actually needs — with shrinkage and occupancy flagged when the plan asks too much of the humans.

Volume can also arrive from outside: connectors import history from tools like Zendesk and Intercom, bucketed by day and channel, so a team migrating in doesn't start forecasting from zero.

The schedule

Build weeks from templates, copy last week, or let the auto-drafter lay a first pass over the forecast — then adjust by hand where you know better. Publish, and the week is real. The grid shows overlaps as errors and availability conflicts as warnings, because some mistakes deserve a hard stop and others deserve a note.

The self-service half is where the group chat gets quiet. Open shifts — slots without a person — go up for claim, with per-agent concurrency respected. Time-off requests flow to a queue with approvals. Shift swaps run eligibility checks before they reach a manager. And on the day itself, the intraday reforecast looks at what actually happened this morning, re-projects the afternoon, and shows — read-only, honest — where the published plan and reality have diverged.

The people half

Employees carry profiles: availability, notes, documents with proper access control, time off in all its states. Shift data can push to and pull from dedicated scheduling tools like Deputy and When I Work, so a team using one of those keeps its tool while the contact volume and staffing math still live here.

The handoff

This is the module that feeds on the rest of the workspace: chats, calls and tickets are the volume; the forecast turns them into hours; the schedule turns hours into people. When your busiest channel changes — more chat, fewer calls, a new appointment type — the forecast notices before your rota does.

The people records carry the softer half: availability patterns, documents with proper access control, notes, and time off in all its states from request to approval. Swaps run an eligibility check before a manager ever sees them, and the my-week view gives each employee their own schedule without handing them the whole rota. Everyone's answer to "when do I work Thursday" comes from the same source the forecast does.

Related: the forecast reads your real contact volume — chats, calls and tickets — and bookings from appointments count too; the staffing math follows the channels you actually answer, hour by hour.

How this compares

Workforce management splits into two products that rarely meet: schedulers like Deputy and When I Work, which are excellent at publishing shifts, and enterprise forecasting suites like NICE or Verint, which tell big contact centers how many people a Tuesday needs. Small teams usually get the scheduler without the forecast — and staff by gut feel.

This module runs the whole chain in one place. Volume comes from your actual contacts — tickets, conversations, calls, bookings — bucketed by hour and channel, with imports from tools like Zendesk and Intercom if history lives elsewhere. The forecast projects from that history; Erlang C converts projected workload into a headcount per hour; templates and auto-draft turn the requirement into a published schedule; open shifts handle the gaps with claims and swaps. Intraday reforecast even re-projects the rest of today from what actually happened this morning. And if you outgrow it, the Deputy and When I Work connectors pull or push shifts rather than trapping them. Pair the staffing math with the voice and chat queues it's forecasting for, and staffing becomes math instead of vibes.

Try it

Workforce lives under Workforce in your sidebar. Let the forecast build from your last few weeks of real volume, open the staffing view, and look at one specific hour you always struggle to cover. The number it gives you is the one your gut has been negotiating with for years.