Support workforce tools

Workforce management (WFM) tools help a support team turn expected customer demand into staffing decisions. They forecast how much work may arrive, translate that work into capacity needs, schedule people with the relevant skills, and support daily adjustments as demand or availability changes. They connect three decisions: how much work is likely to arrive, how much qualified time is needed, and who is available to provide it. The forecast is an estimate; the roster and the response to a gap are operating decisions.

Connect demand, capacity and schedules

A workable planning cycle links four steps: forecast demand, plan capacity, schedule people and adjust the plan as the day unfolds. Each step answers a different question, so check that a tool's outputs connect rather than treating a forecast as a roster.

Keep these outputs distinct. A weekly workload total can inform hiring but conceal an uncovered live-chat peak. A roster filled for every short interval does not, by itself, settle a longer-term hiring decision.

Define the work before choosing a tool

List the channels the team handles and the response promise for each. Phone and live chat generally need capacity near arrival. Email and other work that can wait need capacity before their response deadline, including work already open. Record the time zone for each service window; Australian teams may cover regions with different local hours.

Define the counting unit: a new customer issue, a contact entering a queue and an item of agent work can produce different totals. Zendesk WFM counts each entry into a workstream, including a later move or reopening. Its initial ticket history can also include spam. Reconcile those counts with the team's reporting definition before using them to plan staffing.

For Australian rosters, check the applicable modern award, enterprise agreement or other registered agreement for the roles being scheduled. These instruments can set hours, overtime, penalty rates, rosters, breaks and leave; the National Employment Standards (NES), within the Fair Work Act 2009, include a 38-hour maximum ordinary week for full-time employees plus reasonable additional hours. Treat a software-generated roster as a plan to check against the relevant rules, not as proof of compliance.

Check the staffing assumptions

Contact volume multiplied by average handling time gives a starting workload estimate. Coverage also depends on when work arrives, how long customers can wait, backlog, chat concurrency where relevant, minimum staffing and agent skills. Account for breaks, leave, meetings and other duties without counting the same unavailable time twice. A person assigned across two channels cannot provide full coverage to both simultaneously.

Ask a provider which history the forecast uses, how unusual days and future events are handled, and whether the displayed requirement includes shrinkage. Compare the requirement with the actual roster after non-customer work is accounted for. Check business-hours settings separately: does the tool's required-staffing view follow the helpdesk's hours automatically?

Use the service promise and the team's actual operating constraints to test whether the planned headcount is plausible. A staffing figure is not enough on its own: check that the right skills are available at the times work arrives, and that breaks, leave and other duties are represented without double-counting unavailable time.

Match the tool to the operation

Check whether a candidate tool forecasts from data your team already maintains, and whether its planning outputs match your channels and planning horizon. Zendesk WFM is a candidate for a team already using Zendesk tickets, and Amazon Connect is a candidate for a contact centre using its Task or Email channels. Confirm subscription and data requirements before relying on either.

Zendesk WFM forecasts inbound volume from ticket data and workstreams, with estimates up to a year ahead and a full-time-equivalent (FTE) staffing calculation. It also supports planning, scheduling, short-term schedule changes and day-to-day monitoring. Access to the planning features described in Zendesk's manager guidance requires admin permission in WFM, so confirm permissions as well as subscription before assigning planning tasks.

Zendesk offers WFM and quality assurance (QA) separately or as a discounted workforce engagement management (WEM) bundle; an add-on is purchased for all agents in the account. Online-assisted or self-service accounts can buy through the Subscription page, while managed accounts need to contact their account representative or Zendesk Sales. No dollar amount is stated, so obtain the current subscription price before comparing costs.

Check how the proposed setup represents service hours and coverage before relying on a coverage view. For asynchronous work, check whether a product can account for response windows and existing backlog, and confirm availability and setup with the provider.

Choose by fit with the work your team actually plans: its systems and data, channels, skills, service windows and planning horizon. Before committing, check that the forecast requirement can be turned into a roster your team can use, and that the roster can be adjusted and reviewed as work changes.

Separate hiring and scheduling horizons

Capacity plans support different planning horizons. A hiring plan estimates longer-term full-time-equivalent needs and can inform work with Human Resources, Finance and Training. A scheduling plan gives interval-level headcount needs for near-term resource use.

Some hiring plans use both long- and short-term forecasts, with enough overlap to identify within-day contact patterns. Some scheduling plans need a published short-term forecast and produce needs in intervals that match the forecast setting. Confirm the exact overlap and interval requirements with the provider.

Amazon Connect capacity planning makes the distinction concrete: Hiring plans estimate long-term FTE needs up to 64 weeks ahead, while Scheduling plans give interval-level headcount needs in 15- or 30-minute intervals. For Hiring plans, the recommended overlap between long- and short-term forecasts is at least four weeks; the minimum is one day. Scheduling plans require a published short-term forecast, with no long-term forecast or overlap needed.

Capacity-plan scenarios can include estimates of future shrinkage and available full-time employees. Treat them as planning inputs to validate, rather than assuming a forecast alone captures future availability.

Capacity Planning Horizons: Hiring vs Scheduling

Keep the plan current

Publish the forecast with its assumptions. Check coverage by interval, channel and skill, then publish the roster and explain how changes reach agents. During the day, compare incoming work and available people with the plan. When a gap appears, decide who can move, which work can wait and who owns the fallback.

Afterwards, compare forecast with actual arrivals and review where coverage failed. Record whether the cause was demand, handling effort, absence, channel mix or a changed definition. Change the relevant assumption before the next planning cycle.

Day-to-day WFM can also include tracking attendance and agent activity in real time, managing short-term schedule changes and reviewing historical reports. Zendesk describes managers, schedulers, analysts and team leads as common roles in this work. Dashboards can be configured to track measures such as handle time and adherence, giving the team a shared view for monitoring and review.