Website Enquiry Workload Calculator: Hours, Handoffs and Peaks

Count coverage and escalation separately

A chatbot can attempt a question and still create work for a person. This model separates enquiries that never enter self-service, attempted enquiries that escalate, and enquiries completed without escalation. It then adds the human minutes each group needs. Use one enquiry definition throughout; counting a message in one input and a whole conversation in another makes the result misleading.

The escalation input is a percentage of attempted enquiries, not of all enquiries. If 30% of 600 enquiries enter self-service, that is 180 attempts. A 20% escalation rate within that group is 36 escalations, not 120. The other 144 attempts are completed self-service enquiries, which can still require review time.

Formulas and units

Attempted and escalated enquiries

Attempted = monthly enquiries × attempted share ÷ 100. Escalated = attempted × escalation share ÷ 100.

Remaining human hours per month

[(Unattempted × current manual minutes) + (escalated × total escalation handling minutes) + (completed self-service × review minutes)] ÷ 60.

Monthly capacity balance

Available team hours per month − remaining human hours. Negative means a shortfall.

Busiest-day capacity shortfall

The greater of zero and: [remaining human hours × busiest-day share ÷ 100 − available team hours that day].

Escalation handling minutes include the entire human task for that enquiry, including reading the transcript and follow-up. They replace the current manual minutes for that group, preventing double counting. Completed self-service review uses its own input. The model does not include a separate fixed maintenance allowance; subtract those duties from available team hours before entering capacity.

Worked example: a monthly surplus and a peak-day gap

For 600 monthly enquiries, eight current handling minutes, 30% attempted coverage and 20% escalation within attempts, the split is 420 unattempted, 36 escalated and 144 completed self-service enquiries. At ten human minutes per escalation and one review minute per completed enquiry, remaining work is (420 × 8 + 36 × 10 + 144 × 1) ÷ 60 = 64.4 hours, compared with an 80-hour manual baseline.

With 80 available team hours, the month has 15.6 spare hours. But if the busiest day carries 15% of the monthly work, it needs about 9.7 human hours. Four staffed hours that day leave a 5.7-hour shortfall. The month looks manageable while the busiest day does not. All figures are illustrative assumptions, not service performance claims.

Use the result to plan a pilot, not promise a wait time

This is a volume-and-hours model. It assumes the busiest day has the same question mix and handling times as the rest of the month. A promotion, outage or policy change can produce a harder mix. It also cannot estimate concurrent arrivals, response-time commitments, backlog carry-over or headcount. A spare-hour result does not guarantee that someone is available at the moment a customer asks.

1. Use enquiry records to estimate actual attempt and escalation shares. Keep quality failures in the workload count.
2. Sample escalation effort, including time spent finding missing context. A handoff that saves the visitor time can still burden the team.
3. Model your busiest observed day and a harder escalation scenario, then agree who handles the overflow.
4. Review the human handoff guide to build a useful team packet and the conversation review rubric to classify outcomes consistently.

Once the workload assumptions are credible, use the break-even calculator to explore time value and costs in USD or CAD. Currency formatting does not change the workload math.