How Much Support Capacity Will an Ecommerce Peak Need?

Forecast support capacity from your own demand and work data. Do not start with a universal staffing ratio.

Use expected orders, contacts per order, handling time, shrinkage, and coverage hours. Then compare process, automation, and staffing scenarios.

Collect five inputs

1. Expected orders: Forecast orders for the peak period.
2. Contacts per order: Use a recent comparable period.
3. Average handling time: Include active work for the selected contact types.
4. Productive time: Remove meetings, training, breaks, and approved non-queue work.
5. Coverage requirement: State the days, hours, channels, and escalation owner.

Use the same contact definition in every period. Decide whether one conversation or every message counts as one contact.

Use the workload formula

expected orders × contacts per order × average handling minutes = forecast work minutes

Then calculate productive hours:

forecast work minutes ÷ 60 = forecast work hours

Finally, compare forecast work hours with the team's available productive hours.

Worked example

This example is illustrative. It is not a staffing promise.

• Expected orders: 20,000
• Recent contacts per order: 0.14
• Average handling time: 7 minutes
• Forecast contacts: 2,800
• Forecast work: 19,600 minutes
• Forecast work: about 327 hours

Now add the team's actual coverage and non-queue assumptions. Do not divide by a standard hours-per-agent number without this step.

Build three scenarios

Scenario	Demand assumption	Process change	Capacity decision
Base	Expected orders and recent contact rate	Current workflow	Compare with current productive hours
Better information	Same orders, lower preventable contact assumption	Improve tracking and customer updates	Retest the contact-rate assumption
High demand	Higher orders or handling time	Keep escalation coverage	Add approved temporary or permanent capacity

Shopify explains that valid tracking data can appear on the order status page, shipping emails, and the Shop app. This makes tracking setup a useful process variable. See Shopify's tracking guide.

Gorgias recommends finding frequent ticket types before adding automation. It lists order tracking as a common ecommerce workflow. See the Gorgias helpdesk-automation guide.

Add queue and escalation coverage

The total hours do not show when work arrives.

For each channel, record:

• Expected contact volume by hour or shift
• Required response window
• Contact types that can use self-service
• Contact types that need a person
• Escalation owner and coverage hours
• Handoff time between shifts

Do not assume that all work can wait until the next day.

Reforecast during the peak

Compare actual results with the forecast each day.

1. Update the actual order count.
2. Update contacts per order.
3. Update handling time by major contact type.
4. Record backlog at each shift end.
5. Change one assumption when the evidence changes.

Use the WISMO worksheet when order-status contacts drive the variance.

Choose capacity after process fixes

First, correct broken tracking, unclear messages, and avoidable routing. Then calculate the remaining work.

The ecommerce operations service and ecommerce customer-support service are capacity options. They are not inputs to the forecast.

If recurring administrative work remains, outside support can maintain queues and approved updates. The store must own policies, forecasts, and escalation decisions.