Separate coverage from capacity
Coverage is the time when someone or something is responsible for the inbox. Capacity is how much work that coverage can handle. A team may cover every hour and still be overloaded at peak times. Conversely, a quiet overnight period may need a reliable escalation path more than a full additional shift.
The planner estimates hours from your chosen days, daily coverage window and simultaneous seats. It adjusts paid hours for the share of time available for chat work. These are staffing assumptions, not a forecast of messages or revenue.
Make the handover explicit
At the end of a shift, unresolved work needs an owner. Record the current context, the next promised action, any constraint and the time of the last meaningful interaction. Avoid copying more personal information than the next operator needs.
If AI is part of the workflow, define when people take over and whether automation pauses during that handover. Test what happens when two operators open the same conversation or a queued message becomes inappropriate after a reply. Do not rely on everyone remembering to check.
Plan for absence and exceptions
Training, breaks, meetings, illness and incident review reduce available chat time. Include this work in the capacity assumption. A calculation based on every paid hour being productive will underestimate staffing needs.
Start with an observed arrival pattern and review it regularly. Identify a named person for urgent exceptions, even when software handles ordinary work. Keep a written pause and recovery process. A round-the-clock system still needs accountability when something unexpected happens.
Build a roster from observed demand
Start with a simple hourly arrival log using aggregate counts rather than private conversation content. Note unanswered work, escalations and time spent on administrative tasks. Busy hours may need two seats while a quieter period needs only a clear escalation arrangement. A single average for the whole week hides that difference.
The calculator assumes constant seats during the chosen daily window. For variable demand, calculate each distinct block separately and add paid hours before rounding the final staffing requirement. Rounding every small block up to a whole person would overstate the total, while rounding the entire requirement down leaves uncovered work.
Handover time is work. Include time to summarise unresolved threads, acknowledge transfer and review any queued actions. The outgoing operator should know who accepted responsibility. Use named time zones and a date, especially around daylight-saving changes; “the night shift” is not a reliable timestamp.
| Measure | What it answers | What it leaves open |
|---|---|---|
| Coverage hours | When is the inbox staffed? | How many requests arrive in each hour |
| Simultaneous seats | How many operators are needed at once? | Whether the same staff can cover every shift |
| Available chat-time share | How much paid time can serve the inbox? | Absence and seasonal changes unless included |
| Full-time equivalents | What is the total paid-hour requirement? | A feasible roster and local employment rules |
ILLUSTRATIVE WORKED EXAMPLE
One seat, every hour, with 80% available chat time
Illustrative planning inputs: 24 hours per day, seven days a week, one simultaneous seat, 80% available chat time and a 40-hour paid week.
- Coverage is 24 × 7 × 1 = 168 staffed hours.
- Paid hours are 168 ÷ 0.8 = 210 hours, including the entered allowance for non-chat work.
- 210 ÷ 40 = 5.25 full-time equivalents. Rounding to whole people gives six, before checking whether an actual roster works.
Five 40-hour schedules provide only 200 paid hours. At 80% availability, that is 160 staffed hours: eight short of the requirement.
Map shifts and absence cover separately. Increasing seats at peak times increases the requirement.
Put it into practice.
Estimate weekly staffing needs from your actual coverage requirement.
Plan your coverage ↗A chat shift handover template with worked scenarios →
Related questions
Does 168 hours mean one person can cover the week?
No. It is simply 24 × 7. Staffing depends on availability, breaks, workload and the employment rules that apply to the team.
Does the planner account for time zones?
It calculates total coverage hours. Map actual shifts to named time zones separately, including daylight-saving changes.
Can AI replace all uncovered hours?
The arithmetic cannot answer that. Test which conversations the system can handle and ensure a human escalation path for exceptions.
Original practical guidance prepared for Onlytool. Worked cases are illustrative, not measured customer results. This publication does not claim independent vendor testing. Methodology and disclosure.