Weekly Shift Planning for Call Centers — How to Build a Schedule That Works
A weekly shift schedule is the bridge between your staffing plan and your service level target. The staffing plan tells you how many agents you need per interval. The schedule turns that into specific shift assignments — who works when, which days off they get, and when their breaks fall.
Getting this right has a direct impact on three things: whether you hit service level (enough agents at the right times), whether you control overtime costs (not paying premium hours to cover scheduling gaps), and whether agents stay (predictable, fair schedules are one of the strongest retention levers in hourly workforces).
We have free downloadable templates for both basic weekly shift planning and shift scheduling with break times. This post explains how to use them effectively.
Before you schedule: the inputs
A shift schedule is only as good as the inputs that inform it. Building schedules without these inputs leads to chronic overstaffing in some intervals and understaffing in others.
Call volume by interval
You need to know how many calls arrive during each 30-minute or 60-minute interval, by day of week. Pull this from your ACD for the past 4–8 weeks and look for patterns.
Example: a customer service queue
| Time | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| 7:00–8:00 | 35 | 32 | 30 | 33 | 38 | 20 |
| 8:00–9:00 | 65 | 60 | 58 | 62 | 70 | 35 |
| 9:00–10:00 | 85 | 80 | 78 | 82 | 88 | 50 |
| 10:00–11:00 | 90 | 88 | 85 | 87 | 92 | 55 |
| 11:00–12:00 | 80 | 78 | 75 | 77 | 82 | 48 |
| 12:00–1:00 | 70 | 68 | 65 | 67 | 72 | 40 |
| 1:00–2:00 | 75 | 73 | 70 | 72 | 78 | 42 |
| 2:00–3:00 | 82 | 80 | 78 | 80 | 85 | 45 |
| 3:00–4:00 | 78 | 75 | 73 | 76 | 80 | 38 |
| 4:00–5:00 | 65 | 62 | 60 | 63 | 68 | 30 |
| 5:00–6:00 | 45 | 42 | 40 | 43 | 48 | 22 |
| 6:00–7:00 | 30 | 28 | 25 | 27 | 32 | 15 |
This pattern — ramp up in the morning, peak mid-morning, dip at lunch, secondary peak in the afternoon, taper in the evening — is typical. Saturday volume is roughly 55–60% of weekday volume. Your pattern will be different, but you will have one, and the schedule must match it.
Agents required per interval
Convert call volume to agents needed using your average handle time and service level target. The formula (Erlang C) accounts for the fact that call arrivals are random, so you need more agents than the simple math suggests.
Rough calculation: (Calls per hour × AHT in minutes) ÷ 60 = agent hours needed. Then add 15–20% to account for service level buffering and random call arrival patterns.
For the 9:00–10:00 Monday interval above (85 calls, 6-minute AHT): (85 × 6) ÷ 60 = 8.5 agent hours. With buffer: 10–11 agents needed on the phones during that interval.
Shrinkage
Not all scheduled hours are productive. Shrinkage — the percentage of paid time when agents are not handling calls — includes breaks, lunch, training, coaching sessions, meetings, bathroom time, and unplanned absences. Typical shrinkage in a call center is 25–35%.
If you need 10 agents on the phones during an interval and your shrinkage is 30%, you need to schedule 10 ÷ 0.70 = 14–15 agents for that interval.
Shrinkage breakdown example:
| Category | Percentage |
|---|---|
| Paid breaks (2 × 15 min) | 6.25% |
| Lunch (30 min unpaid — still absent from phones) | 6.25% |
| Coaching / meetings | 3% |
| Training | 2% |
| Bathroom / personal | 2% |
| Unplanned absence (sick, no-show) | 5% |
| System issues / transition time | 2% |
| Total shrinkage | ~27% |
If you are using a single shrinkage number that was set years ago and never validated, your schedules are probably wrong. Measure actual shrinkage quarterly and adjust.
Building the schedule
Step 1: Define shift patterns
Choose shift lengths and start times that cover your operating hours while matching volume patterns. Common patterns for a call center operating 7 AM–10 PM:
| Shift | Hours | Covers peak? | Notes |
|---|---|---|---|
| Early | 7:00 AM – 3:30 PM | Morning peak (9–11 AM) | Desirable for agents with school-age children |
| Mid | 9:00 AM – 5:30 PM | Both peaks | Most common; covers the busiest window |
| Late | 1:30 PM – 10:00 PM | Afternoon peak + evening | Less desirable; may need shift differential |
| Split coverage | 11:00 AM – 7:30 PM | Lunch gap + afternoon | Useful for bridging the lunch dip in coverage |
The number of agents assigned to each shift should be proportional to the call volume during that shift's hours. If 60% of daily volume arrives between 8 AM and 4 PM, roughly 60% of your agents should be on shifts that cover those hours.
Step 2: Assign days off
For a 5-day workweek in a 6- or 7-day operation, agents need 1–2 days off per week. The constraint: you need minimum coverage every day, including weekends.
Fixed days off (same days off every week) are more popular with agents and better for retention. Rotating days off (different days off each week) provide more even coverage but are harder on agents' personal lives.
For a 6-day operation (Monday–Saturday) with 30 agents needing 1 day off each:
| Day off | Agents off | Agents available |
|---|---|---|
| Monday | 5 | 25 |
| Tuesday | 5 | 25 |
| Wednesday | 5 | 25 |
| Thursday | 5 | 25 |
| Friday | 5 | 25 |
| Saturday | 5 | 25 |
This gives even distribution. In practice, you may want fewer agents off on your highest-volume days (Monday and Friday in many operations) and more off on lower-volume days (Saturday if weekend volume is lower).
Step 3: Place breaks to protect service level
Break placement is where many schedules fail. If half your agents take their morning break at 10:00 AM — your peak hour — service level collapses during that interval.
Rules for break placement:
- Stagger breaks so that no more than 10–15% of on-duty agents are on break during any single interval
- Avoid breaks during the first and last 30 minutes of a shift — agents need ramp-up time and wrap-up time
- Lunch breaks should be staggered over a 2-hour window (11:00–1:00) rather than concentrated at noon
- Track actual break timing — if agents are taking breaks 15 minutes late or extending breaks by 5 minutes, the schedule's assumptions are wrong
Example break schedule for a mid shift (9:00 AM – 5:30 PM):
| Break | Agents assigned at 9:00 AM | Agents assigned at 9:15 AM | Agents assigned at 9:30 AM |
|---|---|---|---|
| Morning break (15 min) | 10:30 AM | 10:45 AM | 11:00 AM |
| Lunch (30 min) | 12:00 PM | 12:30 PM | 1:00 PM |
| Afternoon break (15 min) | 2:30 PM | 2:45 PM | 3:00 PM |
Step 4: Account for known absences
Before publishing the schedule, subtract known absences: approved time off, scheduled training days, and planned coaching sessions. If subtracting these brings coverage below the required agent count for any interval, you need to adjust — offer overtime, move a training session, or accept a temporary service level dip.
Managing the schedule week-to-week
Publishing and communication
Post the schedule at least 2 weeks in advance. This is both an operational best practice and, in some jurisdictions, a legal requirement (predictive scheduling laws in Oregon, San Francisco, New York City, Chicago, Seattle, and others require advance notice with penalties for late changes).
Make the schedule accessible — posted in a shared system, not just emailed or taped to a wall. Agents who have to ask their supervisor what shift they work next week have a scheduling system problem.
Handling shift swaps
Agents will need to swap shifts for personal reasons. A good swap process:
- Agent finds a qualified replacement (same skill set, same account if applicable)
- Both agents agree to the swap
- Supervisor approves (verifying coverage is maintained)
- Schedule is updated in the system
The key word is "qualified." An agent trained only on Account A cannot swap with an agent trained on Account B if the shift requires Account B coverage. Cross-training more agents on multiple accounts gives more swap flexibility.
Handling same-day absences
Unplanned absences (sick calls, no-call no-shows) happen every day. Your schedule needs a plan for this:
| Response | When to use |
|---|---|
| Absorb it | If remaining agents can handle volume without exceeding 85% occupancy |
| Offer voluntary overtime | If coverage gap is 1–2 agents and you have agents willing to extend |
| Call in off-duty agents | If coverage gap is significant and service level will miss target |
| Accept reduced service level | If the cost of overtime exceeds the cost of a temporary SL miss |
Track the frequency and cost of each response. If you are offering overtime to cover absences more than twice per week, your base staffing is too thin — hire to cover the actual absence rate, not the theoretical zero-absence scenario.
Common scheduling mistakes
Scheduling to headcount rather than volume. Dividing agents evenly across shifts produces flat coverage for a demand curve that is not flat. The 9 AM–12 PM peak needs more agents than the 5 PM–7 PM taper. Match coverage to volume, not to shift count.
Ignoring break impact on service level. A schedule that shows 12 agents on duty at 10:00 AM but has 3 of them on break only has 9 agents available. If you need 11 to hit service level, the schedule looks fine on paper but fails in practice. Always calculate net available agents (on duty minus on break) per interval.
Using a single schedule for all weeks. Call volume varies by week — month-end, holidays, promotional periods, seasonal trends. A static weekly template works as a baseline, but it needs adjustment for known volume changes. Pull forward-looking volume data and adjust the schedule before publishing, not after service level has already dropped.
No buffer for unplanned absences. If your schedule has exactly the number of agents needed with zero absences, any sick call creates an immediate coverage gap. Build a 5–8% absence buffer into your scheduled headcount — it costs less than the overtime you will pay to cover the gaps.
Concentrating days off on weekends. If every agent wants Saturday and Sunday off but your operation runs 7 days, you either understaff weekends (service level drops) or deny all weekend requests (agents leave). Assign weekend days off fairly — rotating weekend coverage or offering weekend differential pay — and set expectations during hiring.
Publishing schedules late. Posting next week's schedule on Friday afternoon for a Monday start gives agents no time to arrange childcare, transportation, or personal commitments. Late schedules directly increase no-shows and attrition. Post schedules 2 weeks ahead and treat the deadline as non-negotiable.
