Nesting

How nesting works

Classroom training teaches systems, products and policy. Nesting is where new agents find out whether they can do all of it at once with a real customer on the line.

A typical setup looks like this:

• The class moves together into a nesting area, a dedicated bay or a separate virtual team for remote agents, often still with their trainer or a dedicated nesting coach.
• Agents take live contacts, usually on simpler call types first. Routing can be set so complex or high-risk calls go to experienced agents.
• Floor support is close by: a coach or a few experienced "buddies" per 8 to 12 new agents, available for quick questions and hand-raises.
• A higher share of calls is monitored and scored, often daily, with short feedback sessions the same day.
• Targets ramp up week by week instead of starting at full production levels.

The purpose is to build speed and confidence before the agent is on their own, and to catch problems while they are still cheap to fix. It is the bridge between new hire training and steady-state work.

How long nesting lasts

Length follows complexity. Common ranges:

• Simple inbound customer service: 1 to 2 weeks.
• Billing, account changes, retail banking: 2 to 3 weeks.
• Technical support, healthcare, insurance claims: 3 to 4 weeks, sometimes longer.
• Licensed or regulated sales: varies with licensing timelines.

The better approach is to define nesting by exit criteria and treat the calendar as a planning estimate. Some agents are ready in 8 days and some need 20. Releasing everyone on the same date because the schedule says so pushes struggling agents onto the floor where they either quit or drag down quality.

Setting nesting targets and exit criteria

Targets should ramp, and exit criteria should be written down before the class starts so agents know what they are aiming for. An example for a utility billing team where tenured agents run a 420-second handle time and a 90% quality score:

• Week 1: quality 80% or higher, no AHT target, all calls reviewed by the coach at the end of each shift.
• Week 2: quality 85%, AHT within 150% of floor target (630 seconds), schedule adherence 90%.
• Week 3: quality 88%, AHT within 125% (525 seconds), adherence 92%, and no critical compliance errors in the last 20 scored calls.
• Release: meets week 3 criteria for 5 consecutive shifts and passes a final process knowledge test.

Agents who miss the criteria get a defined extension with a specific coaching plan, usually one more week. After that, the decision is redeploy to a simpler queue, more uptraining, or exit. A call center nesting checklist helps coaches track each agent against the same criteria.

Why nesting matters for attrition and speed to proficiency

The first few weeks on live calls are where many new agents decide whether to stay. A bad first week, with angry customers, slow systems and nobody to ask, produces quiet resignations and no-shows. A well-run nesting period does the opposite: it gives early wins and makes help easy to get.

Nesting is also where most of the gain in speed to proficiency happens. Agents learn fastest with frequent, specific feedback on real calls. A coach who listens to three calls and gives two concrete changes the same afternoon moves performance faster than a weekly scorecard.

For workforce management, nesting agents are partial capacity. A common planning assumption is that a nesting agent handles 50% to 70% of a tenured agent's volume, rising each week. Plan staffing on that basis, not on headcount, or the center will be understaffed for the month after every class.

Common nesting mistakes

• Skipping nesting when the floor is short. Throwing a class straight into the main queue to cover a volume spike usually costs more in quality issues, repeat calls and early quits than it saves.
• No dedicated coach. Asking busy team leaders to also support a nesting class means hand-raises go unanswered.
• Full targets from day one. Showing a new agent a red handle time score in week one teaches them to rush customers.
• Releasing on the calendar. Struggling agents need a structured extension or a different path, not a release date.
• Changing team leaders at release. Where possible, move nesting agents to a team leader they have already met. A cold handover loses some of the trust built in nesting.
• No data on outcomes. Track 30, 60 and 90 day retention and quality by nesting coach and class so you can see what works.

Running nesting for remote agents

Remote nesting works, but the support has to be designed in rather than assumed. Use a dedicated chat channel or always-open video room where agents can raise a virtual hand and get an answer in under a minute. Schedule short daily huddles at shift start and end. Make sure coaches can silently monitor and whisper or message in real time. And check equipment and connectivity before nesting starts, because a home network problem on day one is a common and avoidable reason a new remote agent never comes back.