Support Demand Estimator Calculator

Forecast tickets from orders, returns, delays, and channel mix. Adjust peaks, automation, and staffing instantly. Build smarter support plans using clear timely demand insights.

Calculator inputs

Length of the planning period.
Days your team is actually available.
Average orders before adjustments.
Expected growth during the period.
Use 1.00 for normal months.
Captures sales events and launches.
Inflates average demand for the busiest day.
Questions before the order is placed.
Orders likely to trigger return contacts.
Broken, missing, or wrong-item issues.
Delays, tracking, and carrier exceptions.
Orders that generate cancel requests.
Declines, refunds, and gateway issues.
Miscellaneous demand not covered elsewhere.
Average touches for each issue event.
Customers who contact again about the same case.
Bot or workflow handled demand.
Help-center and portal resolution after automation.
Channel mix can total any value.
The calculator normalizes channel shares.
Useful for high-complexity support teams.
Includes DMs, comments, and messaging apps.
Average handling time by channel.
Longer chats increase workload sharply.
Calls often carry the highest effort.
Fast channels still create hidden load.
Planned daily shift length.
Share of paid time usable for contact work.
Meetings, breaks, coaching, and leave.

Plotly graph

This chart shows the contact drivers shaping your support queue.

Example data table

Scenario Forecast Days Daily Orders Gross Contacts Assisted Contacts Workload Hours Peak FTE
Baseline Month 30 500 2,120 1,527 220.5 4.31
Holiday Push 30 900 4,331 3,118 451.4 8.57
Automation Upgrade 30 900 4,331 2,515 360.1 6.83

Formula used

1) Projected daily orders
Projected Daily Orders = Current Daily Orders × (1 + Growth Rate) × Seasonality Multiplier × Promotion Multiplier
2) Projected orders for the period
Projected Orders = Projected Daily Orders × Forecast Days
3) Base contacts
Base Contacts = Pre-sale Contacts + Return Contacts + Defect Contacts + Shipping Contacts + Cancellation Contacts + Payment Contacts + Other Contacts
4) Repeat contacts
Repeat Contacts = Base Contacts × Repeat Contact Rate
5) Human-assisted contacts
Assisted Contacts = (Base Contacts + Repeat Contacts) × (1 − Automation Deflection) × (1 − Self-service Resolution)
6) Weighted average handle time
Weighted AHT = Σ(Channel Share × Channel AHT)
7) Workload hours
Total Workload Hours = Assisted Contacts × Weighted AHT ÷ 60
8) Staffing requirement
FTE = Total Workload Minutes ÷ [Agent Hours per Day × 60 × Open Days × Occupancy × (1 − Shrinkage)]

How to use this calculator

  1. Enter your planning horizon, support open days, and current daily order volume.
  2. Add growth, seasonality, promotion, and peak-day assumptions to reflect expected ecommerce demand shifts.
  3. Fill in issue rates for returns, defects, shipping, cancellations, payments, and other contacts.
  4. Set contacts per issue and repeat contact rate to model follow-up demand realistically.
  5. Enter automation and self-service assumptions to estimate how much demand avoids human handling.
  6. Provide channel mix and average handle time for email, chat, phone, and social support.
  7. Add staffing conditions such as shift length, occupancy, and shrinkage.
  8. Press Estimate Support Demand to see projected contacts, workload hours, FTE needs, and the Plotly graph.

FAQs

1) What does this calculator estimate?

It estimates ecommerce support demand by combining projected orders, issue rates, repeat contacts, channel mix, automation, and staffing efficiency into workload and FTE outputs.

2) Why include pre-sale inquiries?

Pre-sale questions can become a large share of demand during launches, price changes, and promotions. Ignoring them usually understates staffing needs.

3) What is contacts per issue?

It reflects how many times a single issue creates customer contact. Complex refunds, exchanges, or delayed shipments often require more than one touch.

4) Why does the calculator normalize channel shares?

Teams often enter channel percentages that do not total exactly 100. Normalization preserves their intended mix while keeping calculations mathematically consistent.

5) What is the difference between base FTE and peak FTE?

Base FTE covers average demand across the full forecast period. Peak FTE estimates the staffing needed on your busiest day after applying the peak multiplier.

6) How should I choose occupancy and shrinkage?

Use actual team history when possible. Occupancy often sits below 85%, while shrinkage should include meetings, breaks, coaching, absences, and admin work.

7) Can this model automation improvements?

Yes. Increase automation deflection and self-service resolution to test how bots, portals, macros, and knowledge content reduce human-assisted workload.

8) Is this suitable for weekly and monthly planning?

Yes. Adjust forecast days and open days to match your cycle. The same model works for short campaign planning or broader monthly capacity planning.

Related Calculators

Ticket Volume CalculatorCustomer Ticket VolumeDaily Ticket CountAgent Workload CalculatorTicket Backlog CalculatorPeak Ticket LoadTicket Inflow RateOpen Ticket CountTicket Throughput CalculatorSupport Queue Size

Important Note: All the Calculators listed in this site are for educational purpose only and we do not guarentee the accuracy of results. Please do consult with other sources as well.