A unique identifier representing this row.

The number of ACD related queue interactions that entered this queue during the interval. An interaction is considered ACD related if it has been operated upon by any of the ACD interaction handling tools. nEnteredAcd includes interactions whose end condition is not yet determined. Any interactions that are not answered or abandoned in the current interval might be answered or might abandon in the next interval.

The number of ACD related queue interactions that abandoned this queue during the interval. Interactions that transfer from one distribution queue to another distribution queue, where no agent ever answers the interaction in the first distribution queue, will not show up in nAbandonedACD or nTransferACD. They will only show in nFlowOutAcd.

This value is not currently supported.

Number of ACD queue interactions that were disconnected locally. A local disconnect is defined as a disconnect by a CIC agent/user or the CIC system. A remote disconnect comes from the external party or phone company.

The same as nLocalDisconnectAcd but only for those interactions that were alerting in an agent queue while being locally disconnected.

The same as nLocalDisconnectAcd but only for those interactions that were in an agent queue while being locally disconnected.

Number of ACD related queue interactions that were in an Alerting state while in this queue. Note that interactions which transition to Alerting more than once are only counted once.

Number of ACD related queue interactions that were answered by the agent. Answered interactions are interactions that reached a Client_Connected state with an agent. This number can exceed nEnteredACD for the agent's queue because interactions can enter the queue in the previous interval and then be answered in the current interval. Interactions are only answered once relative to the agent queue assignment.

Number of all interactions—ACD and non-ACD—that were answered by the agent. Answered interactions are interactions that reached a Client_Connected state with an agent. See nAnsweredAcd for more information.

Number of seconds in the first service level. This column does not usually apply for agents. See nAnsweredAcdSvcLvl1 for more info.

The number of ACD interactions answered in the target service level. This column does not usually apply for agents.

The number of ACD interactions answered in the first service level. This column does not usually apply for agents. The value can be applicable, but is important to remember that the value is relative to the agents queue and not the distribution queue. It can be used to track the time to answer an interaction during the ring time. In this case, the service level settings will need to be very short to capture data. For more information, see the description of service levels in the Interval Queue Data summary section.

The number of ACD interactions answered in the second service level. This column does not usually apply for agents. The value can be applicable, but is important to remember that the value is relative to the agents queue and not the distribution queue. It can be used to track the time to answer an interaction during the ring time. In this case, the service level settings will need to be very short to capture data. For more information, see the description of service levels in the Interval Queue Data summary section.

The number of ACD interactions answered in the third service level. This column does not usually apply for agents. The value can be applicable, but is important to remember that the value is relative to the agents queue and not the distribution queue. It can be used to track the time to answer an interaction during the ring time. In this case, the service level settings will need to be very short to capture data. For more information, see the description of service levels in the Interval Queue Data summary section.

The number of ACD interactions answered in the fourth service level. This column does not usually apply for agents. The value can be applicable, but is important to remember that the value is relative to the agents queue and not the distribution queue. It can be used to track the time to answer an interaction during the ring time. In this case, the service level settings will need to be very short to capture data. For more information, see the description of service levels in the Interval Queue Data summary section.

The number of ACD interactions answered in the fifth service level. This column does not usually apply for agents. The value can be applicable, but is important to remember that the value is relative to the agents queue and not the distribution queue. It can be used to track the time to answer an interaction during the ring time. In this case, the service level settings will need to be very short to capture data. For more information, see the description of service levels in the Interval Queue Data summary section.

The number of ACD interactions answered in the sixth service level. This column does not usually apply for agents. The value can be applicable, but is important to remember that the value is relative to the agents queue and not the distribution queue. It can be used to track the time to answer an interaction during the ring time. In this case, the service level settings will need to be very short to capture data. For more information, see the description of service levels in the Interval Queue Data summary section.

The number of ACD interactions abandoned in the target service level. This column does not usually apply for agents.

The number of ACD interactions abandoned in the first service level. This column does not usually apply for agents. See nAnsweredAcdSvcLvl1 for more information.

The number of ACD interactions abandoned in the second service level. This column does not usually apply for agents. See nAnsweredAcdSvcLvl1 for more information.

The number of ACD interactions abandoned in the third service level. This column does not usually apply for agents. See nAnsweredAcdSvcLvl1 for more information.

The number of ACD interactions abandoned in the fourth service level. This column does not usually apply for agents. See nAnsweredAcdSvcLvl1 for more information.

The number of ACD interactions abandoned in the fifth service level. This column does not usually apply for agents. See nAnsweredAcdSvcLvl1 for more information.

The number of ACD interactions abandoned in the sixth service level. This column does not usually apply for agents. See nAnsweredAcdSvcLvl1 for more information.

This value is not currently supported.

The sum of the time in seconds of all ACD interactions that were in queue before entering a Client_Connected state.

The maximum time in seconds that an interaction was in the queue before entering a Client_Connected state.

The sum of the time in seconds all abandoned ACD interactions were in queue before they abandoned.

The sum of the time, in seconds, all ACD interactions spent from when they first entered a Client_Connected state until the time the ACD interactions went inactive or flowed out of the queue.

It is possible to have talk time appear in an interval without having any new ACD interactions for that interval. The time comes from ACD interactions that connected in that interval.

Interactions might have entered the queue in the previous interval. It is possible to have talk time on a chat. Think of tTalkAcd as the time an interaction is active with an agent.

Note: tTalkACD is the time an interaction is active with an agent, including any Hold time with the agent during the interaction.

Counts the total talk time of a call in the period in which it completed, unlike tTalkAcd which counts the talk time for each period it is counted in.

Number of ACD interactions that were placed on hold while in this queue.

The sum of the time, in seconds, all ACD interactions spent on hold while in this queue.

For future changes.

For future changes.

For future changes.

Counts the number of ACW sessions completed in the given period except manually initiated ACW sessions.

The sum of the time, in seconds, the agent spent in an After Call Work status, also known as wrap up time. The count starts when an interaction goes inactive, usually due to a local or remote disconnect, and ends when the agent leaves the After Call Work status. This value may or may not include non-ACD interactions depending on how the statuses are setup.

Note: tACW is the time in follow-up that is directly associated with an interaction. Follow-up without an ACD interaction (agent selected with no previously disconnected ACD interaction) will not be in tACW. The tACW value will only be recorded in rows of queue statistics directly associated with the interaction. It will not be in any other workgroup, media type, or skill associated rows.

Counts the total ACW Time for the completed ACW sessions. This includes the total time for each session even if it spanned multiple statistic intervals.

Number of interactions, ACD and non-ACD, originating from external locations and connecting to internal extensions. Calls that leave a queue without a connect or disconnect event, also called flowouts, will not be counted in this statistic.

Number of ACD interactions from external locations to internal extensions. Calls that leave a queue without a connect or disconnect event, also called flowouts, will not be counted in this statistic.

Number of all interactions from internal extension to external locations. If a call does not connect to a remote system (for example, Insufficient Dialing Privileges), it will not count toward this statistic.

Number of ACD interactions from internal extension to external locations. If a call does not connect to a remote system (for example, Insufficient Dialing Privileges), it will not count toward this statistic.

Number of all interactions from internal extensions to internal extensions. Internal to internal calls are counted as inbound calls whether the agent placed or received the call because CIC has no way of determining the direction of internal calls.

Number of ACD interactions from internal extensions to internal extensions. This includes ACD Calls transferred between agents in the same distribution queue. Both agents are credited with the ACD call. Calls that leave a queue without a connect or disconnect event, also called flowouts, will not be counted in this statistic.

Sum of seconds for all interactions from external locations to internal extensions.

Sum of seconds for ACD interactions from external locations to internal extensions.

Sum of seconds for all interactions from internal extensions to external locations.

Sum of seconds for ACD interactions from internal extensions to external locations.

Sum of seconds for all interactions from internal extensions to internal extensions.

Sum of seconds for ACD interactions from internal extensions to internal extensions. This includes ACD Interactions transferred between agents in the same distribution queue. Both agents are credited with the ACD interaction.

Number of outbound interactions made by the agent during After Call Work time. If the agent places an interaction after handling an ACD interaction, that interaction, or any other interaction placed during the ACW time, is considered a nACWcall. nACWCall is also accumulated when an agent puts an ACD interaction on hold and places a consult call with another party. CIC assumes that any call placed with an ACD interaction on hold is nACWCall activity.

CIC actually caches the last set of containers associated with the agent's last ACD interaction. This cache is reset any time the agent answers another ACD interaction. When CIC sees an ACD interaction or conditions on the agent queue that would count as an AcwCall, it processes the time and the count against the cached container list. It is done this way because the ACD interaction that made this association might actually be dead and gone from the system by the time the AcwCall event occurs.

Sum of time, in seconds, the agent spent on outbound interactions during After Call Work time. Also see nAcwCalls.

Number of ACD interactions transferred while on this queue. The destination could have been another agent in the same distribution queue, an agent outside of the distribution queue, or a call that was transferred from one workgroup queue to another workgroup queue by a user without beingconnected to a user.

Only set for Callinteraction types.

Number of ACD interactions that were not answered when presented to the agent as an Alerting interaction. nNotAnsweredAcd interactions will also count towards nFlowOutAcd

Sum of the time, in seconds, ACD interactions spent in an Alerting state on this user queue. Also referred to as Ring time.

The number of ACD interactions that flowed out during this interval. Flow outs are defined as queue interactions that were removed from a queue without reaching an inactive state. Queue interactions have an inactive state that is used to mark the interaction for deletion by the ACD subsystem after the interaction has either been answered or abandoned. The most common reason for an interaction to not reach an inactive state, and thus flow out, would be a queue interaction that is transferred.

Also, nNotAnsweredAcd. towards nFlowOutAcd.

Another possible reason for a flow out to occur would be from hunt group alerts. A multiple alert for hunt group places the same interaction on multiple user/agent queues. The interaction is considered a flow out in each of the user queues were the users do not answer. This would mean a large number of flow outs could be generated for each member of the hunt group when using this type of interaction routing.

Sum of seconds ACD interactions were in queue before being counted in nFlowOutAcd. See nFlowOutAcd for more information.

Number of ACD interactions that were waiting to be answered or were alerting to be answered at the start of the interval.

Number of ACD interactions that were active with an agent at start of the interval.

Number of ACD interactions that were held at start of the interval.

Number of ACD interactions that are waiting to be answered or were alerting to be answered at the end of the interval.

Number of ACD interactions that are active with an agent at the end of the interval.

Number of ACD interactions that are held at the end of the interval.

Not implemented for this release.

Currently not implemented in this release.

Number of ACD interactions that disconnected while still on the queue, or were transferred to another queue while connected to an agent. Interactions that abandon while in the queue are included, whereas interactions that leave the queue before being connected to an agent (flow outs) are not. The main utility of this value is in validating that all interactions that entered the queue were counted correctly.

Sum of the time, in seconds, the agent was logged in, activated in the queue, and available to take interactions in a status that has the Status allows ACD calls box checked. By default, only the Available status has this box checked. All three conditions must be met to count toward tAgentAcdLoggedIn time. This column does not count the time an agent is actively engaged in ACD interactions, for example, talking on ACD calls. This statistic can be used to track Idle Time.

Same as tAgentAcdLoggedIn but the agent's status has no effect to this statistic.

Not meaningful relative to an agent queue because an agent cannot be a member of more than one agent queue. See IWrkgrpQueueStats.

Custom value for customer use.

Custom value for customer use.

Custom value for customer use.

Custom value for customer use.

Custom value for customer use.

Custom value for customer use.

Not currently implemented.

Not currently implemented.

The time, in seconds, that the agent was logged in to the client. This time is divided between the agent's statuses in tAgentOnAcdCall, tAgentOnOtherAcdCal, tAgentInAcw, tAgentOnNonAcdCall, tAgentAvailable, tAgentDnd, and tAgentNotAvailable.

The values in these status fields are adjusted up or down so their sum equals tAgentLoggedIn. Because rounding differences can cause loss of seconds whenever one time is summed as parts broken down by seconds, rounded values are adjusted to insure there is no difference in the sum.

Sum of time, in seconds, agents were in an available status, whether or not the agent is activated. This column relates specifically to the agent and not the interaction type, meaning it is not limited to ACDavailable statuses or ACD workgroups. Ring time is currently included in the tAgentAvailable time.

Sum of the time, in seconds, the agent was in a Do Not Disturb state. Also, tAgentDND is part of a set of values that must always sum up to tAgentLoggedIn. It is driven by the combination of ACD availability and client status.

Sum of time, in seconds, the agent was on ACD interactions from first Client_Connected until end of ACW for this queue.

Note: tAgentTalk is tTalkACD + tACW, and should be thought of as tHandleTime.

Sum of the time, in seconds, agents were working on interactions (ACD and non-ACD) for queues other this one.

Sum of the time in seconds the agent was working on ACD connected interactions for the workgroup

Sum of the time in seconds the agent was working on ACD connected interactions for other workgroups

Sum of the time, in seconds the agent was in an After Call Work state.

Note: tAgentInAcw is for the Workgroup and User rows of statistics that are associated with tACW, and will include the tACW time. For other rows, tACW will not be included in tAgentInAcw, but instead will be counted as ACD time of another Workgroup and be in tAgentOnOtherAcdCall and tAgentOtherBusy. For non-ACW time, manual follow-up not associated with an ACD interaction, the time in a follow-up status will be included in tAgentInAcw and tAgentStatusACW.

Sum of the time, in seconds the agent was working on non-ACD interactions.

Sum of the time, in seconds, the agent was not available to take ACD interactions, but was logged in to the system.