Not ready code
Definition
Not Ready Code: The Status That Runs the Contact Center
A not ready code is the auxiliary status an agent selects when they step off the queue but stay logged in — for a bathroom break, meeting, training block, or post-call wrap-up. It tells the workforce-management system why the agent is off calls, so supervisors can separate paid downtime from shrinkage they need to fix.
Every modern contact center platform ships with a stack of these codes. They sit alongside “available,” “on call,” and “logged out” as the four core states routed through the ACD. In BPO reporting, they’re often the single biggest lever between a healthy site and one bleeding margin.
Key takeaways
- A not ready code labels why an agent is off the queue while still logged in (meeting, break, training, wrap-up, and so on).
- Supervisors use the codes to protect adherence, plan schedules, and separate legitimate off-queue time from unaccounted shrinkage.
- Most contact centers run 8–15 codes, mapped to payroll and reporting categories.
- Overuse of “personal” or unmapped codes is the leading cause of adherence disputes on BPO floors.
How it works
When an agent finishes a call, the ACD moves them into “wrap-up,” then back to “available,” unless they manually select a not ready code. Each code carries a numeric ID, a plain-English label, and a policy flag (paid or unpaid, counted against adherence or excused).
The workforce-management platform reads those codes in near real-time. Supervisors see a live board of who’s on what status. Historical reports roll the codes up by team, shift, and site, so operations can spot patterns — a training queue that’s chewing 6% of headcount, or a break code that quietly stretched from 15 to 22 minutes.
Deloitte’s 2023 Global Contact Center Survey found that 68% of contact-center leaders rank workforce optimization among their top three priorities, and auxiliary-code discipline sits at the heart of that work. When codes are clean, forecasts are clean. When they’re messy, so is everything downstream.
Most platforms (Genesys, NICE, Five9, Avaya, Cisco) let admins define codes in the config, then push them to the agent desktop as a dropdown or keyboard shortcut.
Common not ready code categories
| Code category | Typical label | Paid? | Counts against adherence? |
|---|---|---|---|
| Scheduled break | Break | Yes | No |
| Lunch | Lunch | No | No |
| Team huddle | Meeting | Yes | No |
| Coaching | 1:1 / Coaching | Yes | No |
| Training | Training | Yes | No |
| System issue | Tech / IT | Yes | Excused |
| Wrap-up overflow | ACW | Yes | Monitored |
| Personal | Personal | Varies | Yes |
| Restroom | Bio break | Yes | Monitored |
The exact list varies by client, region, and union agreement — but the shape is remarkably consistent across the industry.
Examples
Concentrix, Manila site (2023). After a floor audit, Concentrix cut its active not ready code list from 22 to 11, merging overlapping labels and dropping codes nobody used. Adherence disputes fell within a quarter because agents and team leads now agreed on what each code meant.
A UK utility’s insourced call center (2024). The workforce team noticed a “personal” code creeping past 4% of logged time — well above the 1.5% target. They split the code into “personal (approved)” and “personal (unapproved)” and tied the second to a coaching trigger. The 4% dropped to 2.1% inside eight weeks.
Teleperformance, healthcare account (2022). A US healthcare client required HIPAA-compliant documentation of every off-queue minute. Teleperformance rebuilt its code stack around client-specific reporting categories, then piped the data straight into the client’s monthly QBR pack. The clean audit trail was a factor in a contract renewal.
A Cebu-based BPO on a fintech program (2024). Leadership traced a stubborn service-level miss to unlogged “coaching” time, with team leads pulling agents off the queue without selecting the coaching code. Once they made the code mandatory before any 1:1, forecast accuracy climbed by nine points.
Related terms
- Workforce management: the discipline that plans, schedules, and tracks contact-center staffing. Not ready codes are its raw input.
- Average handle time (AHT): talk time plus wrap-up. Wrap-up sits inside the not-ready umbrella on most platforms.
- Call center: the voice-first predecessor to the multi-channel contact center. Codes originated here.
- Quality assurance: QA teams often trigger a not-ready code when pulling agents for calibration reviews.
- Agents: the frontline workers whose off-queue minutes the codes describe.
- Business process outsourcing (BPO): the sector where auxiliary-code discipline is most consequential, because it’s often tied to billable hours.
- Outsourcing: the broader practice under which contact-center delegation sits.
FAQ
What’s the difference between “not ready” and “logged out”?
Not ready means the agent is still logged into the ACD but not taking contacts. Logged out means they’ve ended their session entirely. The distinction matters for payroll, since not-ready time is usually paid and logged-out time isn’t.
How many not ready codes should a contact center use?
Most operations run 8–15 codes. Fewer than eight and you can’t diagnose problems; more than fifteen and agents pick the wrong one. ICMI workforce-management benchmarks put the sweet spot at 10–12 for a mid-sized site.
Do not ready codes affect adherence scores?
Some do, some don’t. Scheduled breaks, meetings, and training are usually excused. “Personal” and unmapped codes typically count against adherence. The policy sits in the workforce-management config, not the codes themselves.
Can agents choose their own not ready code?
Yes, from a dropdown or shortcut key. Supervisors can override selections and, in most platforms, force a code before letting an agent leave the queue for coaching or training.
Why do BPO clients care about these codes?
Because the codes feed the invoicing model. If a client pays per productive agent-hour, unaccounted not-ready time is a billing dispute waiting to happen. Clean codes protect both sides of the contract.
Ready to see how outsourcing partners run their floors? Visit our hubs directory to explore BPO providers by location, specialization, and service model. Effective time management starts with knowing where the minutes actually go.
Independent
