At any moment, every agent in a call centre is in some state: ready for a call, talking, wrapping up, on a break or logged out. Call centre agent status codes, also called aux codes or break codes, record those states. Set up well, they tell supervisors who can take the next call and show managers where the shift’s time went. Set up badly, they become a source of arguments. This guide explains the common agent states, how break reasons work in Voxdial Contact Center, and how to report on them fairly.
The common agent states
Different systems use different names, but most contact centres track the same basic states:
| State | What it means | Can take calls? |
|---|---|---|
| Available (Ready, Idle) | Logged in and waiting for a call | Yes |
| Ringing | A call is being offered to the agent | Answering |
| On call | Talking on an inbound or outbound call | No |
| Wrap-up (Closure, ACW) | Finishing notes and the disposition after a call | No |
| Break | Meal, rest or other approved break | No |
| Paused | Temporarily not taking calls, for example for a meeting or task | No |
| Offline (Logged out) | Not signed in | No |
In Voxdial, the agents list and the supervisor dashboard show each agent’s current status with colour codes, and the wallboard shows how many agents are available, on call, paused, on break and ringing.
Wrap-up time and auto closure
After each call, a Voxdial agent moves into Closure, the wrap-up state, to pick a disposition and add notes. Agents then set themselves back to available from the agent console.
Forgetting to come out of wrap-up is one of the most common reasons agents look busy when they are not. Voxdial’s auto closure setting, turned on per agent, ends wrap-up automatically after a configurable time (30 seconds by default) and puts the agent back in the queue. Use it on high-volume queues with simple calls, and leave it off where agents need more time for detailed records. Our guide to after call work covers how to measure and reduce wrap-up time.
Call Center Settings also decides what happens when an agent’s phone rings but they do not answer. You can put that agent into Closure (the default), Available, Break or Paused. Closure stops the same unanswered phone from being offered call after call until the agent sets themselves back.
Break codes: why reasons matter
A plain “Break” status tells you an agent is away. A break reason tells you why. That difference matters when you plan staffing and when you talk to an agent about their time.
In Voxdial, supervisors manage the list of Break Purposes without a developer. The list comes with Meal, Restroom, Meeting, Training and Other, and you can rename, reorder, add or retire purposes. When the Break Reason Prompt is on in Call Center Settings, an agent who goes on break picks a purpose and types a short reason. Both are saved to the break-reason report.
Tips for a good break code list:
- Keep it short. Five to eight reasons are enough for most teams.
- Separate planned from unplanned. Scheduled meal and tea breaks are different from a system problem or a supervisor meeting.
- Add work-related codes. Training, team huddles and quality reviews are work, and should not look like idle time.
- Retire, do not delete. Turning a purpose off hides it from agents but keeps past reports intact.
Paused versus break
Paused and break both take an agent out of the queue, but they mean different things. Use Break for personal time such as meals and rest. Use Paused for short work tasks away from calls, such as a callback list, an email or a supervisor request. Keeping them separate stops useful work from being counted as time off.
Reporting on agent states fairly
The Voxdial Agent Performance report shows, for each agent, time spent idle, paused, dialling, on break, ringing, on incoming calls, on outgoing calls and in closure, with call counts, login duration and utilisation. The Detailed Report shows one agent’s day as a timeline of status periods, with start times and durations.
These reports are powerful, so use them carefully:
- Look at patterns, not single days. One long break on a day with a family issue is not a trend.
- Compare like with like. Agents on a complex queue will spend more time in wrap-up than those on simple calls.
- Check the system first. High ringing time can mean a headset or network problem, not a slow agent. See VoIP call quality for remote agents.
- Share the rules in advance. Agents should know which code to use for what, and what the team expects.
- Talk before you judge. Use the timeline as the start of a conversation, not a verdict.
Using states to keep callers moving
Agent states also drive routing. A caller only reaches agents who are available, so a team with many agents stuck in wrap-up or paused will see longer waits and more abandoned calls. Watch the wallboard’s available count during peak hours, and set breaks so that not everyone leaves at once.
When every agent is busy, Voxdial can still help callers. Queues can play announcements and offer other steps over time, missed callers land on a callback worklist, and a BitVoice AI voice agent can answer as a backup and hand the caller to the next free agent with a summary. Agents still answer first. See call queue management for queue design tips.
Want to set up agent states, break codes and reports for your team? Talk to BitVoice.
FAQs
What are call centre agent status codes?
They are the states an agent can be in, such as available, on call, wrap-up, break, paused and offline. They control whether the agent gets calls and show how their time was spent.
What are aux codes or break codes?
Aux codes, or break codes, are reasons an agent picks when they are not available for calls, such as meal, meeting or training. They make break time easier to plan and report.
What is auto closure in Voxdial?
Auto closure is a per-agent setting that ends the wrap-up state automatically after a configurable time, 30 seconds by default, and returns the agent to the queue.
Can I change the break reasons in Voxdial?
Yes. Supervisors can add, rename, reorder and retire break purposes from Settings, and turn on the break reason prompt so agents choose a purpose when going on break.
