Forecast support-ticket volume

A ticket-volume forecast is a planning tool, not a promise about exactly how many customers will write next Tuesday. Its value is in making the likely range of demand visible early enough to adjust coverage, knowledge and escalation. For a small team, a clear weekly estimate with stated assumptions is more useful than an opaque model.

Freshdesk's ticket-volume trends report shows created, resolved, reopened and unresolved work across time buckets. Those are useful inputs, but do not mistake the chart for a forecast. You still need to clean the underlying data, identify business drivers and compare demand with available staffing.

Build a trustworthy history

Export at least several comparable weeks if available, using ticket creation time in one time zone and a stable channel rule. Separate new customer issues from reopens, duplicate threads, spam, internal tests and migrated history. Tag a small reason set. Mark bank holidays, product releases, marketing campaigns, outages and policy changes. If a new chat channel launched halfway through the history, do not interpret the total increase as purely organic growth.

Use weekly counts first, then inspect day-of-week and hour-of-day patterns when you need shift planning. For ecommerce, relate contacts to orders, shipments or active subscribers with an appropriate lag. A customer may contact support days after a shipment or weeks after an order. The ecommerce reporting guide explains why mismatched denominators create false rates.

Make a simple baseline and scenarios

Begin with a recent rolling weekly average or a comparable period from the previous season. Adjust explicitly for known drivers. For example, if a promotion is expected to raise order volume, use the historic contact rate for similar orders and add a range for fulfilment uncertainty. Do not use a fabricated industry average when your own contact reasons and customer base differ.

Show low, central and high scenarios. The range should reflect real uncertainty: campaign response, delivery quality, incident risk and changes in self-service. Reconcile the previous forecast with actual arrivals each week. A miss is information: perhaps demand shifted by channel, a process created extra tickets or the original event estimate was wrong.

The reproducible sample below uses four fictional weeks to derive a 95-ticket baseline and a 105-ticket central campaign case. Its high scenario changes both campaign response and incident demand explicitly. Keep those assumptions beside the range; do not silently convert uncertain order growth into a precise staffing promise.

Convert arrivals into capacity

Estimate time by broad case type, not only ticket count. A hundred quick questions may require less handling than thirty complex disputes. Add follow-up and reopened work, meetings, training, leave and the hours when the team is actually available. Leave headroom for urgent cases and breaks; a plan that allocates every minute to tickets will fail as soon as a supplier escalation appears.

Compare expected arrivals and clearing capacity with the existing backlog. If the high scenario would age the queue beyond the customer promise, prepare actions before it happens: shift cover, a temporary triage owner, updated tracking pages, clearer macros or a specialist escalation agreement. The agent workload guide helps avoid a raw ticket-per-person calculation.

Keep the model accountable

Write down each assumption and who can change it. Review weekly near a peak, and after any launch or outage. Record whether the forecast was too high or low by reason and channel, not just in total. A model can hit the total while missing the urgent cases that determine staffing. Use scenarios as a decision aid, then test actual customer waits with first-response and resolution measures.

Reproduce the forecast from a labelled sample

The complete dataset below is fictional and illustrative. It is not a customer's history, a sector contact rate or evidence of prediction accuracy. Use it to understand the method, then replace it with consistently counted exports from your own operation.

Weekly new-ticket baseline = 380 ÷ 4 = 95. The illustrative contact-per-order ratio is 380 ÷ 7,600 = 0.05, or five contacts per hundred orders in the specified cohort. Calculate a pooled ratio from totals, not an unweighted average of weeks with unequal order volumes. Real tickets often relate to earlier orders, so match the lag and reason before applying this ratio.

Central, low and high cases

Assume a campaign creates additional orders on top of the ordinary baseline. Do not also multiply the whole baseline for that same campaign, or you double-count its effect. In the central scenario, 200 extra orders × 0.05 contacts per order adds ten tickets. In the high scenario, 300 extra orders × a deliberately higher hypothetical 0.06 rate adds eighteen, plus twenty separately assumed incident tickets.

The range is 95–133 new requests, with 105 as the central planning assumption. It has no statistical coverage claim. Reopens stay outside new arrivals: expected handling events become 103, 115 and 147 respectively if each new or reopened item is counted once in this simplified workload model.

For a separate growth-only scenario with no campaign, assume the comparable customer/order base grows 10% and the contact rate stays constant: 95 × 1.10 = 104.5, rounded up to 105 new requests for staffing. Preserve 104.5 in the model so rounding does not accumulate across intermediate steps. Growth does not guarantee the contact rate stays fixed; show the driver explicitly.

Translate the high case without claiming perfect capacity

Assume new requests take eight minutes each and reopened work takes twelve minutes each. The central workload is (105 × 8 + 10 × 12) ÷ 60 = 16 hours; the high case is (133 × 8 + 14 × 12) ÷ 60 = 20.53 hours, rounded. If a fictional schedule supplies eighteen usable handling hours, central headroom is two hours and the high-case gap is 2.53 hours. Those usable hours already exclude meetings, breaks and other work.

Do not interpret that small positive headroom as proof that response targets will be met. Timing, priority mix, ownership and the existing backlog still matter. Ten complex cases arriving together can overwhelm a weekly average. Translate the range into named coverage and escalation choices using the workload guide.

Download and replace the inputs

Download the forecast worksheet and sample dataset. It includes the formulas, exclusions, lag, scenario drivers and an actual-versus-forecast review field. It is a plain-text worksheet that can be printed or copied into your own planning document; it contains no macros or hidden calculations.

The Freshdesk trends report is a documented source of created, resolved, reopened and unresolved counts. For a Zendesk export, reconcile reporting differences before building history. Do not confuse solved events, imported tickets or automated contacts with consistently defined new requests. The forecast is only as comparable as those input definitions.

Sources

• Freshdesk: ticket volume trends report
• Freshdesk: support metrics and SLA definitions
• HubSpot: service analytics and availability

The forecasting method, scenarios and capacity guidance are Support Sorted's editorial judgement.