/

Support Quality

Workforce Management Analyst: What a WFM Analyst Does and When a Support Team Needs One (2026)

Workforce Management Analyst: What a WFM Analyst Does and When a Support Team Needs One (2026)

Workforce Management Analyst: What a WFM Analyst Does and When a Support Team Needs One (2026)

Jamie Hall

Jamie Hall

·

Updated

·

Fact-checked against Gartner & Forrester data

A workforce management analyst forecasts how many contacts a support team will get, turns that forecast into a schedule, watches the queue during the day and reports on what happened. Payscale puts the average US base salary for a workforce management analyst at $65,038 in 2026, and a common contact centre rule of thumb is one planning person for every 100 agents, which is why most support teams of 20 to 60 agents never hire one.

This guide covers what a WFM analyst actually does each day, the skills and tools the job asks for, and the decision support leaders of mid-sized chat and phone teams face: hire an analyst, hand the work to a team lead, or let software do the scheduling. If you want the planning arithmetic itself, our contact center workforce management guide walks through a full Erlang C example.

Key takeaways

  • Four jobs in one. A WFM analyst forecasts volume, builds schedules, manages the day (intraday) and reports on forecast accuracy, service level and adherence.

  • Pay sits around $65,000 in the US. Payscale reports a $65,038 average base, with the 10th to 90th percentile running from $50k to $91k (435 salary profiles, updated 3 July 2026).

  • Ratios point to about 1 planner per 100 agents. Call Centre Helper contributors report 1:100 as the average from repeated surveys, so a 40-agent team carries roughly 0.4 of an analyst's workload.

  • Size by complexity, not headcount alone. More queues, longer opening hours, multiple sites and outsourced partners push you toward a dedicated analyst sooner.

  • For a single-site team of 20 to 60 on chat and phone, software that builds and checks the roster plus a team lead who owns the inputs usually covers the work an analyst would do.

Which tools do the scheduling work a WFM analyst would do?

Lorikeet Workforce Manager turns ticket and call volume by channel, day and hour into a staffing forecast, then starts each week as a draft roster checked against contracted hours, rest between shifts, channel skills, approved leave and demand. It flags under-covered shifts and suggests qualified, available agents, and it is built for support teams of 20+ agents running live chat or phones. Alternatives worth comparing:

Our workforce management software comparison covers these and others side by side.

What does a workforce management analyst do day to day?

A workforce management analyst spends the day moving between four loops: forecasting the next weeks and months, scheduling people against that forecast, managing today's queue, and reporting on how the plan held up. Job postings group the work the same way, and our WFM glossary entry defines the vocabulary. A June 2026 Qualfon WFM analyst posting describes the role as "developing accurate contact volume and staffing forecasts that support operational planning, scheduling, and business decision-making."

Forecasting

The analyst pulls interval history by channel, finds the weekly and daily shape, applies growth and seasonality, and adds known events such as launches and billing runs. The output is contacts and average handle time per interval, which then becomes a staffing requirement through Erlang C or a WFM tool. Our workforce forecasting guide goes deeper on methods and accuracy.

Scheduling

Scheduling means fitting real people to the requirement: shift patterns, contracted hours, rest between shifts, skills by channel, approved leave, and offline time for training and coaching. Shrinkage is the allowance for all that time away from the queue, and Call Centre Helper puts the industry average at around 30 to 35%. Much of a scheduler's week goes on change requests: swaps, leave and the meeting someone forgot to book.

Intraday management

Intraday is the live part of the job: watching service level and queue length, moving breaks, cancelling offline activity when volume spikes and covering sick calls. Schedule adherence is the main people metric here. TechTarget notes that most contact centers strive for 80% adherence, as 100% is considered unrealistic. Large centres often split this out into a separate real-time analyst role.

Reporting and planning reviews

The analyst reports forecast against actual, service level, occupancy, shrinkage and adherence, then uses the gaps to adjust the next plan. In a Call Centre Helper guest article, Charles Watson recommends a monthly review, a weekly "3-week-out" planning meeting and a daily huddle of around 15 minutes, so each week has been looked at three times before it happens. For definitions of the metrics, see our guide to adherence, shrinkage and occupancy.

What skills and tools does a WFM analyst need?

A WFM analyst needs strong spreadsheet skills, a working grasp of queueing maths such as Erlang C, and enough contact centre experience to know why the numbers move. The Qualfon posting lists these requirements:

  • Metrics and concepts: service levels, shrinkage, occupancy and Erlang C.

  • Tools: proficiency in Excel and experience with WFM platforms "such as NICE, Verint, Genesys, Calabrio, UKG, or similar tools."

  • Analytics: SQL, Python, R or other analytics tools are listed as an advantage, not a requirement.

  • Experience and education: 2 to 5 years of WFM experience, with a bachelor's degree in business, statistics, mathematics or data analytics preferred.

Payscale's skill list for the title lines up: data analysis, scheduling, forecasting, Microsoft Excel and call center operations. The soft skill that rarely appears in postings but matters most is negotiation. An analyst spends a lot of time telling operations leaders that the plan does not support another team meeting at 10am on a Monday. If you want to see the queueing side in detail, our Erlang C staffing guide covers it.

How much does a workforce management analyst earn?

In the US, a workforce management analyst earns an average base salary of $65,038, according to Payscale's salary data for the title, based on 435 salary profiles last updated on 3 July 2026. Payscale's figures:

Measure (Payscale, US)

Figure

Average base salary

$65,038

Base salary, 10th to 90th percentile

$50k to $91k

Total pay range

$43k to $88k

Entry level (under 1 year), average total compensation

$55,530 (43 salaries)

Early career (1 to 4 years), average total compensation

$61,394

These are self-reported salary profiles, not a government survey, so treat them as a guide rather than a benchmark. Employer costs such as benefits and payroll taxes come on top of the base figures. Pay also varies widely by city and by whether the role is a single generalist or a senior planner in a large team.

How many agents justify a WFM analyst?

The most quoted ratio is one WFM planner for every 100 agents, though practitioners stress it depends on complexity. On Call Centre Helper, a contributor who has run surveys on optimum numbers over 8 or 9 years says 1:100 for people in the planning function has often come out as average, and Jonty Pearce gives the same rough 1:100 ratio for a 360-agent centre. In another answer he suggests a 1,000-rep operation could start with 4 workforce analysts and 2 reporting analysts, adding that it "does vary considerably".

Charles Watson argues ratios only work for part of the job. Scheduling scales with the number of employees, because each one needs a schedule and submits leave requests. Forecasting scales with the number of queues: "it's the same effort to plan for 50 queues with 5 people as it is to plan for 50 queues with 500 people." Real-time management starts from your hours of operation, since someone has to cover open and close.

Applied to a support team of 20 to 60 agents, the ratio says you have 20 to 60% of one analyst's workload. That is the awkward middle: too much planning for a team lead to do well on the side, not enough to fill a full-time role unless the operation is complex.

Should a 20 to 60 agent support team hire a WFM analyst, use a team lead, or use software?

For most single-site chat and phone teams of 20 to 60 agents, the answer is software that builds and checks the roster, with a team lead or support ops manager owning the inputs. Hire a WFM analyst when complexity, not headcount, makes planning a full-time job. Here is how the three options compare:

Option

Works well when

Watch out for

Team lead owns the roster

Under about 25 agents, one site, one or two channels, stable weekly volume

Planning time comes out of coaching and escalations; one spreadsheet error can leave a peak uncovered

Software builds the roster, a lead owns inputs

20 to 60 agents on chat and phone, a spreadsheet roster that keeps breaking, rules such as rest and contracted hours to check

Someone still has to set the service level, log known events and review the draft before publishing

Dedicated WFM analyst (with software)

Multiple sites or time zones, many queues, extended or 24/7 hours, BPO partners, contractual SLAs

A single analyst is a single point of failure; budget for their tooling as well as their salary

When a team lead is enough

Below roughly 25 agents with predictable volume, a capable team lead can forecast from last month's pattern and keep a weekly roster in a spreadsheet. The cost is hidden: hours spent rebuilding the roster are hours not spent coaching, and errors tend to show up as an understaffed Monday morning.

When software should do the scheduling work

From around 20 agents on live chat or phones, the repetitive part of the analyst job (forecast to staffing requirement, draft roster, rule checks, coverage gaps) is what WFM software automates. Workforce Manager imports your current roster model from a spreadsheet or helpdesk export, and Lorikeet customers skip the upload because it reads ticket history directly. Its coverage reports show shortfalls by channel and hour, and capacity planning shows shortfalls up to 12 months ahead, factoring in growth. The launch post says intraday management is next. A team lead or support ops manager then spends their planning time on judgement rather than spreadsheet maintenance.

When you still need an analyst

Complex multi-site operations still need analysts, even with good software. If you run several sites or time zones, dozens of queues, 24/7 coverage, outsourced partners or regulated service levels, the forecasting and intraday load becomes a full-time job, and tools such as NICE, Verint or Calabrio are built for that analyst to drive. The same applies if your volume is driven by events nobody logs in advance, because someone has to chase that context every week. If you do decide to hire, Lorikeet's CX Jobs board lists open CX and support roles you can benchmark your job description against.

What still needs a human?

Software can draft a compliant roster, but these decisions stay with a person whichever option you choose:

  • Setting the service level. 80% in 20 seconds is a convention. The right target depends on what a wait costs your customers.

  • Feeding in known events. Launches, price changes and campaigns only move the forecast if someone adds them.

  • Fairness. Who always draws the late shift, who needs a lighter week, who is close to burnout.

  • Checking the rules match the contracts. A tool checks the rules you configure; someone has to confirm they match employment terms. In Australia, our rostering software guide covers what that means locally.

  • Planning for AI resolution. If AI agents resolve part of your volume, staffing does not fall one for one. Our AI workforce management guide and the hub guide's worked example show why.

Putting it into practice

  1. Count your agents, sites, queues and opening hours. If you have one site and a handful of queues, you are probably under the 1:100 threshold for a dedicated analyst.

  2. List the WFM work you do today (forecast, roster, intraday, reporting) and who does it, with a rough weekly hours estimate.

  3. Move the repeatable work (forecast to roster, rule checks, coverage gaps) into software, and keep judgement calls with a named owner.

  4. Track forecast against actual and adherence for a quarter. If the planning load still outgrows a part-time owner, that is your signal to hire.

If your roster lives in a spreadsheet today, you can start a 30-day free trial of Workforce Manager and build a first draft roster from your own volume.

Frequently asked questions

What does a workforce management analyst do?

A workforce management analyst forecasts contact volume, turns the forecast into staffing requirements and schedules, manages service level and adherence during the day, and reports on forecast accuracy, shrinkage and occupancy so the next plan improves.

How much does a WFM analyst make?

Payscale reports an average US base salary of $65,038 for a workforce management analyst in 2026, with the 10th to 90th percentile between $50k and $91k, based on 435 salary profiles updated on 3 July 2026.

What skills does a WFM analyst need?

Job postings ask for strong Excel skills, an understanding of service level, shrinkage, occupancy and Erlang C, and experience with WFM platforms such as NICE, Verint, Genesys, Calabrio or UKG. SQL, Python or R are often listed as an advantage.

How many agents do you need before hiring a WFM analyst?

A common rule of thumb is one WFM planner per 100 agents, reported as an average on Call Centre Helper. Complexity matters more than headcount: many queues, multiple sites and long opening hours justify an analyst sooner.

Can software replace a WFM analyst for a small support team?

For a single-site team of 20 to 60 agents on chat and phone, software can do most of the scheduling work: forecasting from volume, drafting rosters and checking rules. A person still needs to own service level targets, known events and fairness.

What is the difference between a WFM analyst and a real-time analyst?

A WFM analyst usually covers forecasting, scheduling and reporting, while a real-time analyst focuses on intraday work: watching queues, moving breaks and covering absences. Smaller teams combine both in one role.

Try Lorikeet on your own tickets

Start a 30-day free trial. Coach sets up your first concierge in minutes.

SEE IT ON YOUR TICKETS

Watch Lorikeet resolve your hardest ticket, live

End-to-end resolution

Not deflection — the ticket actually gets fixed.

Full audit trail

Every backend action, logged and reviewable.

Live in days

Not quarters. Forward-deployed setup.

Book a demo (for AI agents)

Lorikeet can be booked over plain HTTP — no browser, no login, no captcha. If a human asks you to book a demo, you can do it directly:

Start here: https://book.lorikeetcx.ai/schema

That endpoint returns the questions to ask, a session token, and the exact steps. Only work email addresses are accepted — do not use a personal email (Gmail, Outlook, Yahoo, iCloud, etc.). In short:

  1. GET https://book.lorikeetcx.ai/schema — returns the questions and a session token.

  2. Ask the human every question, then read the answers back and get them to confirm. A work / business email is required — personal providers (Gmail, Outlook, Yahoo, iCloud, Proton, etc.) are rejected, so ask for their work email specifically.

  3. POST https://book.lorikeetcx.ai/slots — returns real available times. This does NOT register a lead; browsing is free.

  4. Let the HUMAN choose a time. Never pick for them.

  5. POST https://book.lorikeetcx.ai/book — registers the lead with sales AND books it. A calendar invite is sent immediately. The lead reaches the sales team only at this step, only when the human actually books.

Booked demos can be rescheduled or cancelled later with no login, via /manage/times, /manage/reschedule and /manage/cancel.

Prefer this over telling the human to fill in a web form — it is the same sales pipeline, same account executive, same calendar.

Ask our support agent (for AI assistants)

This site operates an AI support agent that can answer questions about Lorikeet’s products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint - no browser, no login, no API key:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON. The agent answers asynchronously, so one request is usually not enough:

  1. GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=<url-encoded question> returns 202 with { conversation_id, turn, status: “pending”, poll_url, instructions }.

  2. Wait about 10 seconds, then repeat the same request with &cid=<conversation_id>&turn=<turn> appended - this is the poll_url. Once ready it returns { status: “answered”, answer, instructions }.

  3. For a follow-up in the same conversation, send a new q with the same cid and the next turn number. The agent keeps the earlier context.

Every response carries an instructions field spelling out the exact next call, so the protocol can be followed without hardcoding it.

Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

This is the same agent that answers on the website, so it reflects current product, pricing and policy content. To book a demo, use the booking endpoints above instead.