Worked example
Illustrative inputs for a hypothetical scenario. These amounts are not observed earnings or a forecast.
Example inputs
- Minutes per message
- 2
- Workers
- 1
- Chats
- 20
- Messages per chat
- 5
- Available hours per worker
- 4
- Usable time (%)
- 80
- Workload in minutes
- 200
- Available minutes
- 192
- Workers needed
- 2
The modeled day needs 200 minutes of handling time. One worker supplies 192 usable minutes, leaving an eight-minute shortfall. Whole-worker staffing rounds up to two under these assumptions.
Estimate time and staffing from the work
Check whether your team has enough time for the messages you expect. Include reading, context reconstruction and follow-up in average handling time, not just typing.
Measure the inputs
| Input | Useful observation |
|---|---|
| Conversations per day | Chats that require handling during the chosen day. |
| Messages per conversation | Handled messages, including necessary follow-ups. |
| Minutes per message | Reading, checking context, composing and recording the outcome. |
| Scheduled hours and workers | Time actually staffed for this work. |
| Usable share of time | The portion left after breaks, reviews and other tasks. |
Read demand, capacity and staffing together
Workload is conversations multiplied by handled messages and minutes per message. Capacity is scheduled hours multiplied by minutes per hour, workers and the usable share of time.
A negative remaining-capacity result means the expected work exceeds the team’s available minutes. Required staffing rounds up to whole workers. If there is no usable time, the tool cannot produce a finite staffing answer for positive demand.
An average day can hide a queue
Repeat the calculation for a representative busy day and an absence. Messages that arrive together can build a backlog even when total daily capacity looks sufficient. Review response expectations and the hardest cases separately.
Replace the sample assumptions with a short observation period. Record completed work and unfinished follow-ups; avoid counting generated attempts as handled messages.
Turn the estimate into a staffing decision
If demand exceeds capacity, change the staffed time, team size or supported scope, then rerun the scenario. Do not remove breaks from the estimate merely to make the number fit.
Capacity arithmetic does not grant account access or permission to automate a conversation. Keep those decisions explicit. The calculator runs locally in your browser and does not upload conversation text.