How it works
Agent trace report historically tracks the activities of an agent, state changes, the time when these events occurred, and the duration for agents traced. Agent Trace reporting can help supervisors evaluate how agents are spending their time.
You can obtain an Agent trace report date-wise and for one agent at a time.
To generate trace data, you must enable agent tracing. For this tracing, create a group with the name AgentTraceGroup in ACM and assign agents to this group.
The type of data reported depends on the verbose level configured for the orca-trace-measure-proc service. For more information about how to configure the verbose level, see the section Configuring the verbose level for Trace Processor in Maintaining and Troubleshooting Avaya Analytics™ guide.
The Agent trace report contains the following data:
User state data: Provides information about the agent states and work states an agent transitioned through while traced. It also shows the Not ready by reason codes that an agent sets.
Agent states include Pending Login, Ready and Not Ready, Pending Logged Out, and Logged Out.
Work states include Idle, Available, Busy, and Unavailable.
Call state data: Provides information about the call activities of an agent while being traced. It includes the following information:
Disposition Codes, Workcodes, and Deferred Reason Codes that an agent sets while active on a call.
Rejection Reason Code an agent sets that is responsible for approving emails.
Information on the Engagement ID, Routing Service, Channel, and Direction.
Activity Types, such as Called, Transferred, Consulting, Consulted, Conferenced, Observed, Observing, Coached, Coaching, For Rework, and For Approval.
Email replies and forwards.