WFM guideScheduling

Contact centre break optimisation

Q: How should contact centres stagger breaks to protect service level?

Contact centres should stagger breaks so that at any given moment, the number of agents on break does not exceed the expected 'break floor' — the number of agents that can be off the phones simultaneously while still meeting the SL target for that interval. For most operations, this means no more than 10–15% of the available agent pool on break at any time. In practical terms, for a team of 20 agents: break slots should be spread across at least 5–6 distinct time windows, with no more than 3–4 agents in any single slot. The exact number depends on the SL target, forecast volume, and AHT for that interval — lower volume periods can accommodate more simultaneous breaks than peak periods. Most WFM systems can calculate the optimal break schedule automatically given the staffing requirement by interval; operations without WFM software should distribute breaks manually using the staffing requirement chart from their scheduling spreadsheet.

In a contact centre, the timing of breaks matters as much as the total break time. Twenty agents taking breaks simultaneously loses 20 agents. The same team on staggered breaks loses an average of 4–5 agents at any moment. Total break entitlement is identical; SL impact is completely different.

Simultaneous vs. staggered breaks: the SL impact

Worked example: 20 agents, 2 hours of breaks per agent per 8-hour shift

Simultaneous breaks (worst case)

— All 20 agents take lunch 12:00–12:30 simultaneously
— For 30 minutes: 0 agents available
— SL during this window: 0% (all contacts abandoned or held)
— Contacts queued at 12:30: approximately 125–150 (assuming 250 contacts/hr)
— Time to clear the backlog after 12:30: 15–20 additional minutes
— Total SL damage window: 45–50 minutes from a 30-minute lunch

Staggered breaks (optimised)

— 20 agents spread across 6 break slots: 11:30, 11:45, 12:00, 12:15, 12:30, 12:45
— 3–4 agents per slot (30 minutes each)
— Peak simultaneous off-phone: 4 agents (20% of pool)
— Minimum agents available during 11:30–13:15 window: 16–17
— SL during peak break window: approximately 85–88% (minor degradation)
— No backlog generated: contacts clear within the interval

Both scenarios deliver the same total break entitlement per agent. The SL difference is entirely attributable to break timing, not break duration.

Break placement rules

Place the largest break (lunch/main break) across the shoulder of the midday peak, not at its centre

The midday volume peak typically runs from approximately 11:30 to 13:00. Stagger the main break across this window, starting the earliest slot at 11:15 and the latest at 13:15. Avoid placing all main breaks between 12:00 and 12:30 — this is the instinct, but it concentrates simultaneous breaks at the exact peak of the peak.

Place short breaks in the troughs between volume peaks

If forecast volume shows a trough between the morning peak (09:00–11:00) and the lunchtime peak (12:00–13:30), the 10:45–11:30 window is the optimal short break slot for the morning shift. The break lands where the staffing requirement is lowest relative to scheduled agents.

Calculate the break floor before publishing breaks

The break floor is the maximum number of agents that can be simultaneously on break while still meeting the SL target for that interval. Calculate it for each 30-minute window: staffed agents − agents required for SL = break floor. Ensure no break slot puts more agents off the phone than the break floor allows.

Do not schedule breaks in the first or last 30 minutes of a shift

A break in the first 30 minutes of a shift means the agent arrives, takes a break, and then starts handling contacts. This wastes ramp time and disrupts the operational readiness of the team at shift handover. A break in the last 30 minutes is similarly disruptive and generates adherence issues — agents leave slightly early for a break that overlaps with their shift end.

Synchronise break schedules with shift handover patterns

In operations with rolling shift handovers (e.g. new shift starting every 30 minutes), break schedules should account for the net availability change at each handover. An agent going on break at the same moment a new shift starts and an existing shift ends can cancel out the handover uplift.

Managing break overruns

A break overrun — an agent returning late from a break — reduces available agents below the planned break floor and can damage SL if it coincides with a volume surge. However, managing break overruns requires care: treating them as disciplinary issues before understanding root causes creates the surveillance culture dynamic that damages engagement.

Occasional overruns (<5 minutes, isolated)

No management action required. Single short overruns are noise in the system — tracking them individually creates disproportionate administrative burden and signals distrust. Monitor trend, not individual incidents.

Consistent overruns (same agent, repeated pattern)

Investigate root cause before escalating. Common causes: break slot too short for travel to rest area; break timing coincides with phone call to family; agent with wellbeing issue using break for decompression. Address root cause — adjust break slot or break length where practical.

System-wide overruns (multiple agents consistently late back)

This is an operational design problem, not an agent behaviour problem. Common causes: rest area is too far from workstations; break slots are genuinely too short; break timing is inflexible and does not account for call handover. Redesign the break schedule — do not manage agents for a problem the system created.

Overruns driven by deliberately extended breaks

Address as an adherence conversation after establishing the pattern is deliberate and not system-driven. Apply the management response band (equivalent to adherence band 78–82% in the adherence management framework) — coaching and review, not immediate formal action.

Break optimisation questions

How should contact centres stagger breaks to protect service level?

Spread breaks so that at any given moment, agents on break do not exceed the break floor — the maximum number off-phone while still meeting the SL target. For most operations, this is 10–15% of available agents. For a team of 20: spread across 5–6 distinct slots with no more than 3–4 agents per slot. WFM systems calculate this automatically from the staffing requirement by interval. Without WFM software, distribute breaks manually using the staffing requirement chart from the scheduling spreadsheet, checking each slot against the break floor.