Agent status code
Definition
Agent status code
An agent status code labels the live state of a contact center agent through a shift: Available, Talking, Wrap, Aux, or Not Ready. Every code carries a timestamp, so adherence, occupancy, and payroll reports all read the log rather than the calls.
In 2024, the main cloud contact center platforms shipped 15 to 25 preset state codes plus a configurable Aux tree. The default set covers a simple queue. The custom codes are what let workforce planners see why the queue is bleeding.
Two agents posting identical handle time can post different code mixes. One sits in wrap for 90 seconds per contact — the other drifts into unscheduled Not Ready. The status log is what the planning tool reads, so it decides who looks productive.
Key takeaways
- Agent status codes label every state an agent enters during a shift, second by second.
- Cloud contact centers shipped 15 to 25 preset codes plus configurable Aux reasons in 2024.
- Timestamped codes, not the calls themselves, are what adherence and payroll reports read.
- Aux is scheduled and reason tagged; Not Ready is unscheduled time with nothing attached.
- Weak code hygiene distorts productivity data further than call volume ever does.
How it works
Contact center software tracks each agent through a finite set of states and timestamps every transition. Workforce management tools read that log to build the adherence reports operations leads open at 9 a.m. on the dot.
Login sets Available. An inbound call flips the state to Talking.
Wrap-up moves the agent into after call work. A break drops the session into a specific auxiliary (AUX) reason.
Transitions fire on every event: call routed, hold pressed, hang-up, logout.
The automatic call distributor (ACD) writes a start time, an end time, and a code for each one, and nothing else in the stack gets a vote.
Two forces shape the code list: what the workforce tool can measure, and what the operations lead needs to see. A code that never lifts into the daily report is dead weight, and it slows agents down at every state change.
A missing code — no distinct Coaching bucket, say — means shrinkage lands in a generic Not Ready bin. Supervisors then coach against a number nobody can break apart, which is how a real training investment gets logged as idle time.
Here is the code family a contact center supervisor watched through 2024, with the typical count each bucket carries:
| Code family | Example labels | Typical count | What it tracks | Reports it feeds |
|---|---|---|---|---|
| Productive | Available, Talking, After-Call Work | 3 to 4 | time handling or waiting for contacts | occupancy, service level |
| Auxiliary | Aux-Break, Aux-Training, Aux-Coaching | 6 to 12 | scheduled off-phone activity | schedule adherence |
| Unproductive | Not Ready, Idle | 2 to 3 | unscheduled or unaccounted time | shrinkage, coaching flags |
| System | Logout, Disconnect | 2 to 4 | session start and session end | payroll, attendance |
Interpretation depends on where the boundaries sit. If wrap bleeds into a personal Not Ready click before the next contact, wrap time inflates and occupancy drops in the very same interval.
Observe.AI’s guide to after-call work (ACW) treats that window as coachable time rather than dead time. The code is what makes it visible enough to coach.
Run the arithmetic once and the stakes get concrete. An agent taking 60 contacts a shift at 90 seconds of wrap spends 90 minutes off the queue, close to a fifth of an eight hour day.
Examples
Every major platform implements the same state model with a different default list. Genesys Cloud, NICE CXone, and Amazon Connect all expose configurable statuses, and the gap between their presets is what makes benchmarking across vendors awkward.
Genesys Cloud exposes agent state through its Presence API. Contact centers define custom presence names such as Working from Home, Focus, or Training, then route them into the same adherence engine that reads the default Available and Not Ready states.
NICE CXone splits state codes into system-defined and user-defined buckets. Supervisors typically map 15 to 25 Aux reasons onto adherence codes in the workforce tool, so shrinkage variance surfaces in both the daily report and the coaching queue.
Amazon Connect ships a smaller default set — Available, Offline, plus custom statuses. Because Connect bills by usage, teams often build lean trees of six or seven codes so the queue and the workforce tool both stay easy to read.
Business Process Outsourcing (BPO) providers in the Philippines running US retail programs sit mostly on Genesys or NICE stacks. Contracts in Metro Manila typically set adherence floors between 85% and 92%, with the bonus tier at the top of that band.
That spread is only three to seven points wide, so a single miscoded break per agent per day can move a site across the line. Clean status discipline is what earns the bonus tier.
It also protects the call handling capabilities a client paid for. When the code log is honest, a capacity argument becomes a data question instead of a standoff.
Related terms
The status code sits at the center of a small cluster of contact center metrics. Each term below either feeds the code log or reads it, and the distinction matters when you are auditing a vendor report line by line.
- Average Handle Time (AHT): total talk plus wrap, read straight from status timestamps.
- First Call Resolution: a downstream result that depends on clean state transitions.
- Workforce Management: the planning discipline that consumes the status code log.
- Occupancy Rate: productive states divided by logged in time.
- Service Level Agreement: the contractual thresholds those code reports get measured against.
FAQ
These are the questions supervisors and vendor managers ask most often about status codes, from how many to run to what payroll actually reads. Each answer stays short enough to act on inside a single shift.
How many agent status codes should a contact center use?
Most teams settle on 15 to 25 codes: three or four productive states, six to twelve Aux reasons, and a handful of system codes. Fewer than ten hides root causes. More than thirty creates coding fatigue on the floor.
What is the difference between Aux and Not Ready?
Aux is scheduled and reason tagged, covering Break, Training, or Coaching. Not Ready is unscheduled time with no reason attached to it. Both pull the agent out of the queue, but only Aux protects the adherence number.
Are agent status codes standardised across platforms?
No. Genesys, NICE CXone, Amazon Connect, and Five9 each shipped different defaults through 2024, so a 92% adherence figure on one stack rarely means the same thing on another. Every ACD uses the same state model, but the labels are yours to define.
How do status codes affect payroll?
Payroll systems read Available, Talking, wrap, and Aux durations straight from the code log. Missing or misused codes mean the export undercounts paid time. That gap is a common dispute in outsourced contracts.
Can agents change their own status?
Yes, within limits. Most platforms let agents flip between Available, Aux with a reason, and wrap. Supervisors control who can enter Training or Offline, and system codes fire only on login and disconnect events.
Why do supervisors care about status-code hygiene?
Clean codes separate a coaching signal from noise, and a call centre tracking adherence without them is chasing ghosts in its own daily report.
Compare vetted BPO partners on OA’s outsourcing hub.
Independent
