Understanding WFM forecasting

<body>
<p id="docs-hc-snippet" style="display: none;">This article helps you understand and interpret the Zendesk Workforce management (WFM) Forecast page.</p>
<div class="article-banners">
<div id="docs-wmp-link">
<a href="https://support.zendesk.com/hc/en-us/articles/5411234991258-plan" rel="noopener" target="_blank">What's my plan?</a>
</div>

<div class="article-banner" id="addon_wfm">
<table>
<tbody>
<tr>
<td>
<strong>Add-on</strong>
</td>
<td>Workforce Management (WFM) or Workforce Engagement Management (WEM)</td>
</tr>
</tbody>
</table>
</div>

</div>
<div id="docs-ai-summary">
<p id="docs-ai-summary-toggle">Verified AI summary <span id="up-triangle">◀</span><span id="down-triangle">▼</span></p>
<p id="docs-ai-summary-content">Understand and interpret the Workforce Management (WFM) Forecast page to predict future contact volumes and staffing needs using historical data. The forecast provides inbound volume estimates and calculates Full-Time Equivalent (FTE) requirements, helping you optimize resources and meet service goals. Use the forecast to visualize expected inbound volume and required staffing across workstreams, adjusting for unique events like marketing campaigns.</p>
</div>

<div class="body">

<p class="p">This article helps you understand and interpret the Zendesk Workforce management (WFM)
Forecast page. </p>
<p class="p">The forecast takes your historical data based on <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/9940824842394" target="_blank">workstream scenarios</a> you've specified and creates inbound volume
estimates for up to a year in the future. Full-Time Equivalent (FTE) calculations are also
included, which show how many staff members are required to handle the estimated workload.</p>
<p class="p">This article contains the following topics:</p>
<ul class="ul" id="topic-1__ul_ylv_hyl_dgc">
<li class="li"><a class="xref" href="#topic_ynn_bct_tfc">About WFM forecasting</a></li>
<li class="li"><a class="xref" href="#topic_qq1_cts_tfc">Understanding inbound volume</a></li>
<li class="li"><a class="xref" href="#topic_qrb_mgf_bhc">Understanding required staffing</a></li>
</ul>
<p class="p">Related articles:</p>
<ul class="ul" id="topic-1__ul_snp_tfq_c3c">
<li class="li" dir="ltr"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/9940824842394" target="_blank">Viewing and managing forecast scenarios</a></li>
<li class="li" dir="ltr"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/9940054229402" target="_blank">Viewing your active forecasts</a></li>
<li class="li" dir="ltr"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/9858048119194" target="_blank">Understanding WFM forecasting</a></li>
</ul>
</div>
<div aria-labelledby="ariaid-title2" class="topic nested1" id="topic_ynn_bct_tfc">
<h2 class="title topictitle2" id="ariaid-title2">About WFM forecasting</h2>
<div class="body">
<p class="p">Forecasting is the process of predicting future contact volumes and staffing needs using
historical data and advanced algorithms to ensure that the right number of agents are
scheduled at the right times. This helps you optimize resources and consistently meet
service goals.</p>
<p class="p">When you first activate Zendesk WFM, six months of your historical ticket data is migrated
from Zendesk to the WFM system. This means that your initial forecast is based on the six
month dataset. While the forecasting engine can use up to two years of data if it's
available within WFM, longer historical data requires a manual data import <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408843597850" target="_blank">request to Zendesk support</a>.</p>
<p class="p">Keep in mind that Zendesk WFM also includes spam tickets, which may be different from how
you capture ticket volume in Zendesk Explore. See <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408889141146" target="_blank">Understanding suspended tickets and spam</a>.</p>
<p class="p">You also have the option to import your own data into your workstream forecast. See <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/6443365713946" target="_blank">Importing historical volume</a>.</p>
<p class="p">A minimum of one month of data is required for forecasting in Zendesk Workforce management
(WFM). If you enter a date with less than one month of data, the forecast will not be
generated. Additionally, the system limits the use of historical data to a maximum of two
years. Any data exceeding this two-year threshold will not be factored into the
forecast.</p>
<p class="p" dir="ltr">When you select a <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/9940824842394" target="_blank">workstream scenario</a>, Zendesk WFM begins calculating the future
contact volumes and staffing needs.</p>
<p class="p">Depending on the amount of historical ticket data available, it may take a moment to see
the forecast for the selected workstream.</p>
<p class="p" dir="ltr">In some cases, there may not be enough collected data to display a complete
forecast. In such instances, the forecast is repeated. For example, if only three months of
data are available, Zendesk WFM replicates this pattern for the remainder of the year.</p>
<p class="p">Use the information on the Forecast page to visualize, analyze, and manage <a class="xref" href="#topic_qq1_cts_tfc">expected inbound volume</a> and <a class="xref" href="#topic_qrb_mgf_bhc">required staffing</a> across workstreams. </p>
</div>
</div>
<div aria-labelledby="ariaid-title3" class="topic nested1" id="topic_qq1_cts_tfc">
<h2 class="title topictitle2" id="ariaid-title3">Understanding inbound volume</h2>
<div class="body">
<p class="p" dir="ltr">When your forecast is available, it's displayed on the Inbound volume chart. The
inbound volume forecast is based on the <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/6443365725210#h_01HAQ998BYDGKY6DZQD4BGSX8B" target="_blank">Prophet Forecasting Algorithm</a>.</p>
<p class="p">The Inbound volume chart indicates where the historical data ends and the forecast begins.
Each time you recalculate the forecast, the mark shifts accordingly. Each value on the line
marked as a historical value represents the amount recorded until the last recalculation. If
Zendesk WFM does not have the complete value for that time period (whether that is for a
full day or a full week), the chart displays the values tracked to that point. This may
appear as a sudden drop because the displayed values only reflect partial volumes.</p>
<p class="p"><img class="image" id="topic_qq1_cts_tfc__image_ejt_yfq_c3c" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/wfm_active_forecast.png" width="800"></p>
<p class="p" dir="ltr">Each workstream is represented by a color. You can view forecasts for up to 10
workstreams at a time. </p>
<p class="p"> Zendesk WFM calculates the inbound volume every time the ticket changes workstreams.</p>
<p class="p" dir="ltr">Use the date picker to select daily, weekly, monthly, or yearly views of the
incoming workload. </p>
<p class="p">Hovering over the chart intervals shows you the values of expected volumes for the selected
workstreams.</p>
<img class="image" id="topic_qq1_cts_tfc__image_klk_3gf_bhc" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/ts_forecast_inbound_volume_hover.png" width="600">
<p class="p">You can also expand the chart to a table view, which can be exported. The table allows you
to view the estimated incoming volumes and the values for each workstream based on the
selected interval option. See <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/9940054229402" target="_blank">Viewing your active forecasts</a>.</p>
<img class="image" id="topic_qq1_cts_tfc__image_llk_3gf_bhc" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/ts_forecast_inboundvolume_expand_table.png" width="600">
<p class="p" dir="ltr">Forecast allows you to adjust your expected volumes based on unique events, such
as marketing campaigns or feature sunsets. See <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/9940824842394" target="_blank">Viewing and managing forecast scenarios</a>.</p>
</div>
</div>
<div aria-labelledby="ariaid-title4" class="topic nested1" id="topic_qrb_mgf_bhc">
<h2 class="title topictitle2" id="ariaid-title4">Understanding required staffing</h2>
<div class="body">
<p class="p" dir="ltr">Based on the forecast scenario, Zendesk WFM calculates the staff count needed to
handle the expected workload in the Required staffing chart. Colors represent the selected
workstreams and you'll see the required staffing values when you hover over the chart.</p>
<p class="p" dir="ltr">The chart shows the projected required staffing count for upcoming dates.
Historical required staffing calculations aren't stored.</p>
<img class="image" id="topic_qrb_mgf_bhc__image_msj_smf_bhc" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/ts_forecast_required_staffing_chart.png" width="600">
<p class="p">Full-Time Equivalent (FTE) represents a standardized unit of measurement that reflects the
number of hours worked by a typical full-time employee.</p>
<p class="p">The baseline to qualify as 1.0 unit of FTE is defined by the amount of weekly working
hours. Typically, this is set at 40 hours, so a part-time employee who works 20 hours is
considered a 0.5 FTE.</p>
<p class="p">The Required staffing table displays the calculated FTEs needed for each 15-minute interval
based on a modified version of <a class="xref" href="https://www.callcentrehelper.com/erlang-c-formula-example-121281.htm" target="_blank">Erlang C</a>. This is a mathematical model used in WFM to estimate the
number of agents (FTEs) required to handle a given workload while maintaining a specific
SLA. It's widely used in call centers and contact centers for staffing calculations. </p>
<p class="p">Required staffing takes into account the following parameters:</p>
<ul class="ul" id="topic_qrb_mgf_bhc__ul_rrb_mgf_bhc">
<li class="li">
<strong class="ph b"><a class="xref" href="#topic_zrb_mgf_bhc">Channel</a></strong>: The volume of
calls, emails, or chats.</li>
<li class="li">
<strong class="ph b"><a class="xref" href="#topic_bsb_mgf_bhc">Occupancy</a></strong>: The time spent on
work-related activities in seconds.</li>
<li class="li">
<strong class="ph b"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/8203054518298#topic_ur1_w3b_ldc" target="_blank">Duration</a></strong>: The average duration of your
chats.</li>
<li class="li">
<strong class="ph b"><a class="xref" href="#topic_fsb_mgf_bhc">Concurrency</a></strong>: Max number of
simultaneous active chats. </li>
<li class="li">
<strong class="ph b"><a class="xref" href="#topic_dsb_mgf_bhc">Average Handling Time (AHT)</a></strong>:
The average handle time for your tickets in seconds.</li>
<li class="li">
<strong class="ph b"><a class="xref" href="#topic_hsb_mgf_bhc">First Response Time</a></strong>: How
long it takes for your agents to give a first reply (SLA %).</li>
<li class="li">
<strong class="ph b"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/8203054518298#topic_kvb_w3b_ldc" target="_blank">Wait time</a></strong>: The average waiting time for your
chats</li>
<li class="li">
<strong class="ph b"><a class="xref" href="#topic_jsb_mgf_bhc">Shrinkage</a></strong>: Time spent on
non-work related activities.</li>
<li class="li">
<strong class="ph b"><a class="xref" href="#topic_msb_mgf_bhc">Minimum staffing</a></strong>: Minimum
number of people scheduled to work.</li>
<li class="li">
<strong class="ph b"><a class="xref" href="#topic_nsb_mgf_bhc">Availability</a></strong>: Defines when
your agents need to work on this workstream. It usually matches the operational hours of
your locations. </li>
</ul>
<p class="p">Consider the following example:</p>
<ul class="ul" id="topic_qrb_mgf_bhc__ul_srb_mgf_bhc">
<li class="li">Volume = 38 emails/day</li>
<li class="li">In a period of minutes = 24h period = 24*60s= 1440s</li>
<li class="li">Average Handling Time = 210s (3:30min)</li>
<li class="li">Required Service Level % = Target = 50%</li>
<li class="li">Target Answer Time = FRT = 5h30 = 19600s</li>
<li class="li">Maximum Occupancy = 90%</li>
<li class="li">Shrinkage = 30%</li>
</ul>
<div class="p">This leads to a value of 1.5 agents per day, considering an FTE
is:<pre class="pre codeblock"><code>8h/day &gt;&gt; 1,5*8 = 12h of work</code></pre>
</div>
<p class="p">In general it can be defined as: </p>
<div class="p">
<pre class="pre codeblock"><code>Total Hours Worked by Part-Time and Full-Time Employees ÷ Number of Available Full-Time Hours in Year</code></pre>
</div>
<p class="p"><img class="image" id="topic_qrb_mgf_bhc__image_trb_mgf_bhc" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/WFM_FTE.png" width="600"></p>
<p class="p">You can also expand the chart to a table view which can be exported.</p>
<p class="p"><img class="image" id="topic_qrb_mgf_bhc__image_vrb_mgf_bhc" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/ts_forecast_requiredstaffing_table.png" width="600"></p>
<p class="p" dir="ltr">When Zendesk WFM calculates required staffing, Zendesk business hours aren't
taken into account. Instead, the staffing requirements based on the historical times of
incoming volumes are displayed so you can consider business hours adjustments if needed. For
the day and week view, the staffing requirements value reflects the maximum FTE value
attained on that time interval. For the month and year view, it's the sum of the required
hours. </p>
<p class="p">Values are calculated as follows:</p>
<ul class="ul" id="topic_qrb_mgf_bhc__ul_wrb_mgf_bhc">
<li class="li">
<strong class="ph b">Day View:</strong> 15-minutes intervals. </li>
<li class="li">
<strong class="ph b">Week View:</strong> 1-hour intervals. The maximum number of people required in the four
15-minute intervals that fit into the hour in question. <p class="p">For example:</p>
<ul class="ul" id="topic_qrb_mgf_bhc__ul_xrb_mgf_bhc">
<li class="li">3:00-3:15&gt; 2 FTE</li>
<li class="li">3:15-3:30&gt; 5 FTE</li>
<li class="li">3:30-3:45&gt; 3 FTE</li>
<li class="li">3:45-4:00&gt; 2 FTE</li>
<li class="li">&gt;&gt; Total = 5 FTE between 3:00-4:00.</li>
</ul>
</li>
<li class="li">
<strong class="ph b">Month view:</strong> 24-hours (1day). Hours of work instead of FTEs. This number is the
result of a direct relation between the number of people set as available and hours in the
day.<p class="p">For example:</p>
<ul class="ul" id="topic_qrb_mgf_bhc__ul_yrb_mgf_bhc">
<li class="li">From 3:00-4:00 &gt;&gt; 5 FTEs (working 1h each) &gt;&gt; 5h of work</li>
<li class="li">Same calculation for all hours in the day</li>
<li class="li">The sum of all 24 intervals provides the number displayed in the <strong class="ph b">Totals</strong> row
for each day.</li>
</ul>
</li>
<li class="li">
<strong class="ph b">Year view:</strong> It’s the sum of the 7 days in the week, also expressed as “hours of
work”. It's calculated in the same way as the total for 1 day.</li>
</ul>
<p class="p" dir="ltr">You can modify your required staffing parameters. See <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/6443407875354" target="_blank">Setting up WFM forecasting</a>.</p>
</div>
<div aria-labelledby="ariaid-title5" class="topic nested2" id="topic_zrb_mgf_bhc">
<h3 class="title topictitle3" id="ariaid-title5">Channel types</h3>
<div class="body">
<p class="p">Zendesk WFM offers three channel types: Voice, Email and Chat. </p>
<p class="p">The major difference between them relates to the redistribution of the inbound volume
captured outside of business hours:</p>
<ul class="ul" id="topic_zrb_mgf_bhc__ul_asb_mgf_bhc">
<li class="li">
<strong class="ph b">Voice and Chat</strong>: Tickets outside of opening hours are not distributed in the
first hours of availability since these are synchronous channels. </li>
<li class="li">
<strong class="ph b">Email</strong>: Tickets outside of opening hours are re-distributed in the first
15-minute interval, since this is an asynchronous channel. To avoid high requirements
for just the first 15 minutes, we redistribute those values over the period of First
Response Time. For example, if the First Response Time (FRT) is 4 hours, we redistribute
the requirements over those 4 hours.</li>
</ul>
</div>
</div>
<div aria-labelledby="ariaid-title6" class="topic nested2" id="topic_bsb_mgf_bhc">
<h3 class="title topictitle3" id="ariaid-title6">Occupancy</h3>
<div class="body">
<p class="p">Occupancy directly impacts how efficiently agents are utilized:</p>
<ul class="ul" id="topic_bsb_mgf_bhc__ul_csb_mgf_bhc">
<li class="li">
<strong class="ph b">Higher Occupancy → Fewer FTEs</strong>: This indicates that agents spend more time
handling calls, emails, and chats, and less time idle. As a result, fewer FTEs are
needed to manage the estimated inbound volume.</li>
<li class="li">
<strong class="ph b">Lower Occupancy → More FTEs</strong>: This indicates that agents have more idle time,
necessitating a larger workforce to handle the same workload. </li>
</ul>
</div>
</div>
<div aria-labelledby="ariaid-title7" class="topic nested2" id="topic_dsb_mgf_bhc">
<h3 class="title topictitle3" id="ariaid-title7">Average Handling Time (AHT)</h3>
<div class="body">
<p class="p">Determines how much time an agent spends per interaction:</p>
<ul class="ul" id="topic_dsb_mgf_bhc__ul_esb_mgf_bhc">
<li class="li">
<strong class="ph b">Higher AHT → More FTEs</strong>: Each agent handles fewer interactions per hour,
resulting in a need for more FTEs.</li>
<li class="li">
<strong class="ph b">Lower AHT → Fewer FTEs</strong>: Each agent can handle more interactions per hour,
leading to a requirement for fewer FTEs.</li>
</ul>
<div class="p"> It's represented as follows:<pre class="pre codeblock"><code>hh:mm:ss</code></pre>The value is then translated
to total seconds to be used in the formula.</div>
<div class="p">
<pre class="pre codeblock"><code><strong class="ph b">Total H.T </strong>will be equal to: Call Volume × AHT</code></pre>
</div>
</div>
</div>
<div aria-labelledby="ariaid-title8" class="topic nested2" id="topic_fsb_mgf_bhc">
<h3 class="title topictitle3" id="ariaid-title8">Concurrency</h3>
<div class="body">
<p class="p">This parameter applies only to chat tickets and indicates how many simultaneous chats
agents can handle. It directly impacts FTE calculation, as it increases agent productivity
and reduces staffing needs:</p>
<ul class="ul" id="topic_fsb_mgf_bhc__ul_gsb_mgf_bhc">
<li class="li">
<strong class="ph b">Higher Concurrency → Fewer FTEs:</strong> Agents handle multiple interactions
simultaneously, which increases productivity and decreases the number of FTEs
required.</li>
<li class="li">
<strong class="ph b">Lower Concurrency → More FTEs: </strong>Agents handle only one interaction at a time (as
in voice calls). With the total workload unchanged, this leads to a requirement for more
FTEs.</li>
</ul>
</div>
</div>
<div aria-labelledby="ariaid-title9" class="topic nested2" id="topic_hsb_mgf_bhc">
<h3 class="title topictitle3" id="ariaid-title9">Service Level Agreement (SLA)</h3>
<div class="body">
<p class="p"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/5600997516058" target="_blank">SLA</a> is a key performance metric in contact centers that defines
the percentage of tickets answered within a specific time threshold. It directly impacts
FTE estimation because it determines how quickly tickets must be handled, which influences
staffing needs:</p>
<ul class="ul" id="topic_hsb_mgf_bhc__ul_isb_mgf_bhc">
<li class="li">
<strong class="ph b">Stricter SLA (Higher Target) → More FTEs: </strong>When the SLA target increases (for
example, from 70% in 30 seconds to 90% in 20 seconds), more agents are needed to ensure
a higher percentage of calls are answered quickly. A stricter SLA reduces the allowable
wait time, increasing the need for available agents at all times.</li>
<li class="li">
<strong class="ph b">Relaxed SLA (Lower Target) → Fewer FTEs:</strong> A relaxed SLA allows for better agent
utilization (higher occupancy) and reduces staffing costs (for example, from 90% in 20
seconds to 70% in 30 seconds).<p class="p">In Zendesk WFM this is set by the following
parameters:</p>
<div class="p">
<pre class="pre codeblock"><code>Speed of answer / First Response Time / Wait time</code></pre>
</div>
<div class="p">Represented in: <pre class="pre codeblock"><code>hh:mm:ss</code></pre>
</div>
</li>
</ul>
</div>
</div>
<div aria-labelledby="ariaid-title10" class="topic nested2" id="topic_jsb_mgf_bhc">
<h3 class="title topictitle3" id="ariaid-title10">Shrinkage</h3>
<div class="body">
<p class="p">Shrinkage accounts for the paid agent time that is not spent handling customer
interactions. This parameter is included in the FTE calculation as the difference between
Net and Gross FTE, where:</p>
<div class="p">
<ul class="ul" id="topic_jsb_mgf_bhc__ul_ksb_mgf_bhc">
<li class="li">
<strong class="ph b">Net FTE</strong>: The number of agents needed to handle interactions (Available
Hours).</li>
<li class="li">
<strong class="ph b">Gross FTE</strong>: The number of agents scheduled after accounting for In and Out of
Office Shrinkage.</li>
</ul>
</div>
<p class="p">Impact of Shrinkage on FTEs:</p>
<ul class="ul" id="topic_jsb_mgf_bhc__ul_lsb_mgf_bhc">
<li class="li">
<strong class="ph b">Lower Shrinkage → Fewer FTEs</strong>: A higher percentage of scheduled agents actively
handle interactions, reducing overall staffing needs.</li>
<li class="li">
<strong class="ph b">Higher Shrinkage → More FTEs</strong>: Fewer agents are available at any given time,
necessitating more total agents to meet demand.</li>
</ul>
<p class="p">For example, if you need 100 productive agents and the shrinkage is 40%, you actually
need 167 agents to account for the time lost due to auxiliary time and out-of-office
shrinkage.</p>
</div>
</div>
<div aria-labelledby="ariaid-title11" class="topic nested2" id="topic_msb_mgf_bhc">
<h3 class="title topictitle3" id="ariaid-title11">Minimum Staffing</h3>
<div class="body">
<p class="p">Minimum Staffing can be defined as the minimum number of people scheduled to work. The
default value for Zendesk WFM is 1 FTE.</p>
<p class="p">This parameter does not influence the formula for FTEs but affects their distribution
throughout the available hours. This indicates to the system that you want to schedule at
least one FTE for every hour of work.</p>
<p class="p" dir="ltr">Your minimum staffing number is respected whenever possible during automatic
scheduling. However, there are cases where high forecasted demand takes priority over
minimum staffing. If a workstream is part of a <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/6443314489242#topic_qbx_1tz_11c" target="_blank">combined workstream</a>, the minimum staffing number
to respect is the highest across all workstreams involved.</p>
<p class="p" dir="ltr">When you set a minimum staffing level for a workstream, the scheduling
algorithm treats this requirement as a top priority to satisfy. The algorithm still
respects non-negotiable constraints such as <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/6443345205402" target="_blank">fixed shifts, automatic shift rules, intraday configured tasks, start
times</a>, as well as <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/6443314489242#topic_qbx_1tz_11c__activate_schedule_combined" target="_blank">combined workstream settings</a>. After honoring these
constraints, it actively schedules people to meet the minimum staffing levels throughout
the day.</p>
<p class="p" dir="ltr">If constraints make meeting every minimum staffing target impossible, the
algorithm applies a best-effort approach. For example, it ensures at least one person is
assigned to each applicable workstream where feasible, then fills higher minimum staffing
needs next.</p>
</div>
</div>
<div aria-labelledby="ariaid-title12" class="topic nested2" id="topic_nsb_mgf_bhc">
<h3 class="title topictitle3" id="ariaid-title12">Availability</h3>
<div class="body">
<p class="p">This parameter allows you to define the time period during which agents can work on the
workstream. Tickets will be distributed according to the defined time periods. It's not
the same as the working hours of the location but rather the time frame in which WFM
projects agents will be scheduled to work on this workstream. </p>
<p class="p">For example, if the location working hours are set to Monday through Friday, from 8:00 AM
to 6:00 PM, where agents handle calls from region A from 8:00 AM to 1:00 PM and from
region B from 1:00 PM to 6:00 PM.:</p>
<ul class="ul" id="topic_nsb_mgf_bhc__ul_osb_mgf_bhc">
<li class="li">Workstream A availability will be Monday through Friday, from 8:00 AM to 1:00 PM.</li>
<li class="li">Workstream B availability will be Monday through Friday, from 1:00 PM to 6:00 PM.</li>
</ul>
<p class="p">The timezone you select adjusts the hourly blocks based on your timezone. For example, if
you are in GMT+1 and set availability for Monday to Friday from 8:00 AM to 6:00 PM in
GMT+2, you'll see FTEs calculated from 7:00 AM to 5:00 PM. This is because when it's 8:00
AM in GMT+2, it's still 7:00 AM for you (one hour behind the set availability).</p>
<p class="p">Availability is switched off by default in Zendesk WFM, which means that the distribution
of tickets occurs over 24 hours, 7 days a week, based on the periods when tickets are
received.</p>
</div>
</div>
</div>
<script id="docs-schema-markup" type="application/ld+json">{
"@context": "https://schema.org",
"@type": "TechArticle",
"@id": "https://support.zendesk.com/hc/en-us/articles/9858048119194-Understanding-WFM-forecasting",
"url": "https://support.zendesk.com/hc/en-us/articles/9858048119194-Understanding-WFM-forecasting",
"headline": "Understanding WFM forecasting",
"description": "You can use workforce management forecasting to predict future contact volumes and staffing needs based on historical data and configurable parameters to optimize resource allocation.",
"articleSection": "Scheduling your workforce (WFM add-on)",
"datePublished": "2025-10-22T15:30:08+00:00",
"dateModified": "2026-04-23T09:54:58.200926+00:00",
"inLanguage": "en-US",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://support.zendesk.com/hc/en-us/articles/9858048119194-Understanding-WFM-forecasting"
},
"author": {
"@type": "Organization",
"name": "Zendesk",
"url": "https://www.zendesk.com"
},
"publisher": {
"@type": "Organization",
"name": "Zendesk"
},
"isPartOf": {
"@type": "WebSite",
"name": "Zendesk Help",
"url": "https://support.zendesk.com/hc/en-us"
},
"about": {
"@type": "SoftwareApplication",
"name": "Zendesk"
}
}</script><script id="ai-summary-script">
//<![CDATA[
const ai_summary_style = document.createElement('style');
ai_summary_style.innerHTML = `#styled-article-body{padding:0 0 0}#article-body #docs-ai-summary{background-color:#f3f3f3;border:1px solid #d3d3d3;padding:10px 10px 6px;margin-bottom:16px}#article-body #docs-ai-summary #docs-ai-summary-toggle{font-size:.9em;font-weight:700;margin-bottom:4px;cursor:pointer;display:flex;justify-content:space-between;align-items:center}#article-body #docs-ai-summary #docs-ai-summary-toggle #up-triangle{margin-left:auto;padding-right:10px;display:none}#article-body #docs-ai-summary #docs-ai-summary-toggle #down-triangle{margin-left:auto;padding-right:10px}#article-body #docs-ai-summary #docs-ai-summary-content{font-size:.9em;padding-left:25px;padding-right:25px;margin-bottom:12px}`;
document.head.appendChild(ai_summary_style);

const toggleAISummary = () => {
const summary = document.getElementById("docs-ai-summary-content");
const upTriangle = document.getElementById("up-triangle");
const downTriangle = document.getElementById("down-triangle");
if (summary.style.display === "none") {
summary.style.display = "block";
upTriangle.style.display = "none";
downTriangle.style.display = "inline";
} else {
summary.style.display = "none";
upTriangle.style.display = "inline";
downTriangle.style.display = "none";
}
};

document.getElementById("docs-ai-summary-toggle").addEventListener("click", toggleAISummary);
//]]>
</script>
</body>