All free tools

Support Ticket Volume Forecast Calculator

Forecast support ticket volume and cost 3, 6 and 12 months out with compound growth. Formula, worked example and annual-to-monthly conversion table.

Inputs

Current monthly ticket volume

500100,000

Directional model only: simple compounding, no seasonality. A 12-month straight-line projection is rarely exactly right, but it's the right order of magnitude to budget against.

Results

Updates live

Month 3

11,576

$11,576/mo

Month 6

13,401

$13,401/mo

Month 12

17,959

$17,959/mo

12-month volume projection

NowMonth 12

How this is calculated

Compounds your current monthly ticket volume by a single growth-rate assumption across a 12-month horizon, then multiplies each month's projected volume by a cost-per-resolution figure to project spend alongside volume.

How to forecast support ticket volume

The simplest forecast that holds up is compound growth from your current volume: volume in month n = current monthly volume × (1 + monthly growth rate)ⁿ. Projected cost is that volume multiplied by your cost per resolution. It is the same arithmetic as compound interest, and it is easy to check against your own history.

Use this for budgets, hiring plans and contract negotiations, where you need a defensible number for 3, 6 and 12 months out. It is not a day-by-day workforce forecast. For interval staffing on phones or chat, feed the expected volume into the Erlang C calculator.

Worked example: 10,000 tickets growing 5% a month

  • Month 3: 10,000 × 1.05³ = 10,000 × 1.1576 = 11,576 tickets
  • Month 6: 10,000 × 1.05⁶ = 10,000 × 1.3401 = 13,401 tickets
  • Month 12: 10,000 × 1.05¹² = 10,000 × 1.7959 = 17,959 tickets
  • At $1.00 per resolution, monthly spend rises from $10,000 to $17,959

5% a month sounds modest, but it compounds to 79.6% a year. That is the most common forecasting mistake: multiplying a monthly rate by 12 (60%) and under-budgeting by almost a fifth.

Converting annual growth to a monthly rate

If your plan is stated per year, convert it before entering it: monthly rate = (1 + annual rate)^(1/12) − 1.

Annual growthMonthly rate to enter
10%0.80%
26.8%2%
30%2.21%
50%3.44%
100% (doubling)5.95%

Picking a growth rate you can defend

  • Tie it to a business driver. Tickets follow customers, orders or active users. Work out your contact rate (for example, tickets per 100 orders), then apply it to the sales forecast your finance team already uses.
  • Check it against your trailing growth. Compare the last three months with the same three months a year earlier. If your assumption is far from that, write down why.
  • Plan for contact rate changes. A new product, a pricing change or a messy migration raises tickets per customer. Better help content and AI self-service lower it. Model those as separate scenarios rather than blending them into one rate.
  • Allow for seasonality separately. This calculator uses a single rate. If November and December run well above average, budget the peak months on top of the trend line.

Using the forecast in an AI vendor negotiation

Per-resolution pricing means your AI bill grows with volume. Before signing, project 12 months of volume, multiply by the vendor's real cost per resolution (contract terms, not the list price), and check whether committed minimums or volume tiers kick in. Then compare the result with what the same volume would cost in headcount using the staffing calculator and the AI customer service ROI calculator. RTCI's comparison of AI support pricing models explains how per-resolution, per-conversation and seat pricing scale differently.

Frequently asked

Why a straight compounding growth rate instead of seasonality?

Simplicity and transparency. A single growth-rate assumption is easy to sanity-check against your own historical data, where a seasonality model would need inputs this tool doesn't ask for.

Where should the growth rate come from?

Tie it to a metric you already track (customer count growth, order volume growth, or your trailing 3-month ticket growth rate) rather than guessing.

Can I use this to budget for an AI vendor contract?

Yes. Set the cost-per-resolution input to a vendor's real figure from RTCI's index to see how your spend would scale with volume.

How do I convert an annual growth rate to a monthly one?

Monthly rate = (1 + annual rate)^(1/12) − 1. 30% a year is 2.21% a month, and doubling in a year is 5.95% a month. Do not divide the annual rate by 12; that overstates growth.

What is a ticket contact rate?

Tickets divided by a business driver, such as tickets per 100 orders or per 1,000 active users. Forecasting the driver and applying the contact rate is usually more accurate than extrapolating tickets directly.