Agent Desktop / Console
Workbench
Disposition
7 min
overview call disposition is a mandatory feature that ensures agents classify the outcome of every customer interaction (call, chat, or email) it operates on a two level hierarchy ( disposition class and disposition code ) to provide structured data for operational reporting, process analysis, and quality assurance the administrator defines the structure and assigns it to specific campaigns how it works the system requires an administrator to define the logical groupings (classes) and the specific outcomes (codes), which are then made available to the agents via a disposition plan the two level hierarchy disposition class (level 1) definition a broad, logical category for grouping similar call outcomes (e g , "sales outcomes," "technical support," "not connected") purpose to organize codes into manageable buckets for the agent interface and high level reporting creation created by the admin under system configuration > dispositions tab, and marked as "user defined " disposition code (level 2) definition the specific reason or final result of the interaction it is nested within a disposition class purpose to capture the precise, reportable outcome (e g , "sale closed," "follow up scheduled," "busy number") this is the key data point creation created by the admin by selecting a disposition class and adding the new code to it assignment to campaign the admin must create a disposition plan that bundles the necessary codes and classes, and then assign that plan to a specific voice campaign (e g , inbound, outbound) this action populates the agent's telephony panel with the correct disposition options post call use cases performance reporting used to calculate conversion rates (e g , how many calls result in "sale closed") or failed attempts (e g , "line busy") agent process compliance ensures agents adhere to the required post call wrap up process by selecting an outcome before moving to the next call automated action triggers certain codes can be configured to trigger subsequent actions, such as removing a number from an outbound dialer list ("do not call") or scheduling a follow up benefits standardized data ensures all agents use a consistent, defined set of codes to classify outcomes, eliminating ambiguity in reporting actionable reporting provides the structured data necessary for supervisors and analysts to drill down into operational efficiency and business results agent accountability forces a necessary step at the end of every interaction to complete the customer record limitations two level default the default configuration is a two level disposition (class then code) changing this to a single level disposition requires back end configuration by support team