Support SLA staffing starts with coverage of particular hours, rather than the number of people on your payroll. Two full-time employees do not provide two support seats while they are also running demonstrations, processing orders or taking a break. This guide assumes your deadlines and service hours are already agreed. Use the procedure to find gaps in the duty rota before those gaps become broken promises to customers.
Translate support SLA commitments into coverage
Open the current policy and list its channels, working hours and request types with different response deadlines. Add the latest point when a person needs to begin handling each type, allowing time to read the conversation. Keep the exercise focused on existing commitments: changing the promise while checking the rota would hide the capacity problem you are trying to uncover.
Consider an illustrative team open from 9 to 5 with some requests requiring a response within one working hour. A meeting for everyone between 10 and 11 leaves a gap even if the daily average looks healthy. Move the meeting, keep someone on duty or arrange capable cover; an available status cannot answer a customer when nobody is watching the channel.
The Zendesk workforce metrics documentation distinguishes scheduled time from time actually worked. The coverage sheet and backup procedure here are our proposed method for a small team.
Opening the office and being ready to reply are different moments: starting tools and reviewing overnight work also take time. Check how the policy treats evening messages when the next working day begins. If the underlying timing needs clarification, use the guide to first response time on chat before reviewing the rota.
Count usable minutes rather than headcount
Split the day into intervals appropriate to your commitments, such as half-hour windows. For each person, subtract meetings, breaks, other duties and known absences from their time on support. The result is available working time, rather than a guaranteed number of conversations; case complexity and simultaneous channels still limit what that person can handle.
Review several ordinary days and at least one day with a burst of requests. Separate new arrivals from work on cases already open, because both compete for the same minutes. Someone with an empty calendar window may be preparing a difficult reply to an earlier complaint, so assigning all incoming work to them would overstate your spare capacity.
Avoid adopting an industry occupancy percentage as a ready-made standard for two people. First look at your own switching between chat, calls and administrative work. A fifteen-minute absence by the only person on duty can matter more than a satisfactory total of staff hours across the whole day.
Build a coverage sheet with usable backup
The table below is an illustrative worksheet, rather than a rota recommended for every company. The main agent needs protected time for the queue, and the backup needs basic knowledge plus access to the relevant information. Before agreeing the sheet, check whether the backup has a meeting or break during the very window they are meant to cover.
Agree how cover starts: the duty agent asks, the backup confirms acceptance, and responsibility for current cases is visibly handed over. Saying that sales will help if necessary is not a plan when sales is giving a demonstration at that time. Clarify which questions the backup can resolve and which they should receive and pass to the appropriate owner.
Scroll the table sideways to see all columns.
| Window and risk | Duty agent and cover | Agreed action |
|---|---|---|
| 9–10: overnight messages | Anna receives new work, Mark finishes outstanding cases | Keep team meetings out of the initial review of cases with deadlines. |
| 10–11: Mark gives a demonstration | Anna, with Eva as backup | Eva has inbox access and no simultaneous sales appointment. |
| 12–1: lunch breaks | Mark, then Anna | Stagger breaks and confirm the switch before leaving the queue. |
| 4–5: closing window | Anna, backed up by Mark | Identify deadlines that continue into the next working day. |
Allow a short overlap when a shift change includes cases with a promised update. The incoming person needs facts, the nearest commitment and the next action, rather than a full account of every exchange. Use an internal support note so that the handover does not consume most of the available coverage window.
Choose an overload signal and the first action
Use a signal related to your commitment: the oldest unanswered request is approaching its deadline while the duty agent is finishing a call they cannot interrupt. The number of open cases is useful supporting information, since ten straightforward questions may require less attention than one complex complaint. Your trigger needs to start a specific action, rather than produce an alarm that everybody acknowledges and nobody handles.
The first action might be bringing in the backup, pausing low-priority administration or separating reception of new messages from resolution of older cases. Decide before the peak and name the person who can activate the plan. Raising every case to the highest priority removes the ordering you need to protect deadlines and customer outcomes.
If cover remains insufficient, describe the situation truthfully and give the next realistic update time. A brief acknowledgement does not replace a substantive response where the policy promises one. A recurring coverage gap calls for a change to working arrangements or agreed service hours, rather than a daily request for overtime from the same small team.
Check the rota in the channel and in a rehearsal
Run a controlled test during a planned meeting, break and shift ending. Send a test request, check whether the duty agent sees it and confirm that the backup can actually take responsibility. The test should expose the difference between a declared rota and real channel availability, without using artificial replies to improve statistics for genuine customer cases.
In Meetlead customer support, compare your plan with assignments and waiting cases in the inbox. Agent availability also depends on website settings, the schedule and an active panel session; a shared calendar alone does not prove readiness to answer. Configuration requires an account, a website and the appropriate team permissions.
- The test request reaches the person actually on duty.
- The backup has access and can take ownership without borrowing an account.
- A break does not remove every eligible agent from support.
- The oldest waiting cases are reviewed before the team meeting.
- The handover includes the customer commitment and next update time.
Fix the cause of each observed gap, such as missing department membership, insufficient backup access or conflicting duties. The wider division of work belongs in the guide to customer support in a small business; this exercise checks coverage of commitments already made. Describe your staffing sheet as a manual process when that is what your team actually uses.
Review exceptions rather than the average alone
After a week, inspect cases that approached or crossed their deadline and reconstruct staffing during their coverage window. Compare the rota, actual presence, incoming demand and the work occupying the duty agent. Look for a repeated conflict, such as Monday morning demonstrations, rather than choosing a person to blame from one isolated result.
Choose one adjustment for each conflict and check the next comparable day. Moving a break may improve reception of new messages while delaying replies to earlier cases, so inspect both effects. Keep the adjustment only if it does not simply move outstanding work into the evening or onto the next shift.
Where the problem is missing visibility of case commitments, organize them in a support ticket system. A rota cannot replace knowing who was promised what and by when. Base a request for extra cover on recurring uncovered windows, rather than one exceptionally difficult day with an unusual mix of requests.
Common questions about coverage and SLAs
Are two people enough for a full day? That depends on availability windows, demand and case types, rather than full-time headcount. Build the real rota after subtracting other duties and check the busy windows. If the only duty agent repeatedly has no backup during breaks, the plan does not provide continuous coverage even when traffic is light.
Can we extend the SLA during a peak? Do not quietly alter a promise already made. Separate telling customers about a current delay from agreeing future service conditions. Activate the prepared backup and give appropriate case updates first; publish any lasting change to service hours or deadlines in the appropriate place before making further commitments under those conditions.
Does AI replace a missing duty agent? An AI reply does not establish human availability or count as a human response for the SLA. Assess automated help separately and include cases needing people in your workload. Your cover plan still needs to handle questions automation cannot resolve and customers who want to speak with the team.
