Configuring Aspect integration settings in your RingCX account ============================================================== One of the workforce integration options available to you is Aspect Workforce Management. Aspect helps you staff your contact center with enough employees --- with the skills to answer customer questions --- as interaction volumes change throughout the day. Aspect uses the actual workload history to forecast future workload for each fraction of the day and calculates how many staff are needed to handle the work during each of those periods. Using this calculation, Aspect generates detailed agent work schedules. You can configure your account integration with Aspect via the **Integrations** page at the account level. To reach this page, navigate to **Settings \> Accounts** via the left-hand navigation bar, select an account to edit, and click the**Integrations** tab in the configuration panel. The **Integrations** page allows you to select the type of workforce management (WFM) integration you'd like to add to your account. This article will help you configure workforce management integration with Aspect. RingCX data uploaded to Aspect When you integrate with Aspect WFM, RingCX will periodically collect and send real-time and historical data to Aspect for use in Aspect's own reports and analytics capabilities. The component of RingCX that collects and sends the data is referred to as the WFM integration server. The real-time data including agent states are then sent from RingCX to Aspect as a TCP/IP stream. Aspect, in turn, uses this data in its Real Time Adherence analysis feature. Additionally, periodic reports are uploaded from the WFM integration server to an FTP server where the reports are accessed for use by Aspect's reporting features. The data that RingCX will send to Aspect includes the following historical or real-time data in Aspect: * Historical contact reports * A real-time adherence stream Historical contact reports RingCX will periodically send files to Aspect Workforce Management to report inbound and outbound activity. For both inbound queue and outbound campaign activity, there are two reports: a basic report and an average positions staffed (APS) report. APS is an important input in calculating adherence. Adherence, which compares APS to required staff, is the measurement used by Aspect to evaluate performance at each site. The basic report and the APS report are also known in Aspect as the TCSDATA and SGDATA reports, respectively. The basic and APS reports provide similar metrics but use different rules for aggregating data. The basic report aggregates data in a RingCX queue group for reporting as an Aspect contract group. By comparison, an APS report aggregates data in a RingCX agent group for reporting as an Aspect agent group (called a staff group). The following table shows how RingCX metrics map to Aspect metrics in historical contact reports. Note that there is not an exact match between every RingCX metric and Aspect metric. Certain RingCX metrics must be modified or operated on so as to present the data for the corresponding Aspect metric. |----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|-------------------------------| | **Aspect metric** | **Description in Aspect** | **Similar RingCX metric** | **RingCX report** | | Average Handle Time of Right-Party Contacts (RPHT) | (Right-Party Connection Time + Right-Party Wrap-up Time) / (Right-Party Connects) time in seconds for a group | duration agent_wrap_time | Dialer Result Download .. | | Contacts Offered (NCO) | Number of contacts offered in a contact or agent group. This value is calculated as contacts answered + contacts abandoned | Presented | Hourly Inbound Statistics Raw | | Contacts Handled (NCH) | Number of contacts answered in a contact group or agent group | Accepted | Hourly Inbound Statistics Raw | | Average Talk Time (ATT) | Average talk time, in seconds, in a contact group or agent group | Avg Talk | Hourly Inbound Statistics Raw | | Average Delay (ASA) | Average delay of contacts in a contact group. Average Delay means the same as "average speed of answer" (ASA) | Avg Q Time | Hourly Inbound Statistics Raw | | Percent Service Level (%SL) | Percentage of contacts answered within the specified number of seconds in a contact group | Service Level | Hourly Inbound Statistics Raw | | Actual Abandons (ABD) | Actual number of contacts answered by the routing platform but disconnected by the customer before an agent answers | Short Abandon + Long Abandon | Hourly Inbound Statistics Raw | | Average After Contact Work Time (ACWT) | Average after-contact work time, in seconds, in a contact group or agent group | Wrap up time divided by the number of handled contacts | N/A | | Average Positions Staffed (APS) | Total available time in an agent group, divided by number of seconds in the period | NA | N/A | | Number of Right Party Contacts (RPC) | Right-Party Connects by group | Total *Contact* Agent Dispositions | Outbound overview | | Number of Contacts Attempted (NCA) | Number of contacts attempted for a contact data group | Total Dials | Outbound performance | To understand the data that Aspect integrates and reports, contact Aspect for a data integration specifications guide. Real Time Adherence RingCX uses a TCP/IP socket based communication to send a real-time stream showing agent states, which Aspect uses to calculate adherence to a schedule. Agent states are simply status notifiers that allow users to see what an agent is doing. The agent states that can be reported through the real-time stream include the agent-triggered states that are available for selection by an agent in the agent console, as well as system-triggered states that are assigned either automatically or by a supervisor. The WFM integration only uses default RingCX states. If you configure custom states, a reporting entry will only be generated for the default state when a custom state is mapped to a default state. The Real Time Adherence (RTA) feature in Aspect allows you to measure and report agent activity. The following table shows the mapping of RingCX states to Aspect codes and states. For information about the RTA feature, see the Aspect documentation. |----------------------|--------------------------------------------|-----------------|------------------------------| | **UI config option** | **RingCX state** | **Aspect code** | **Aspect state description** | | Agent Login Events | *Login* | 1 | Sign In | | Agent Logout Events | *Logout* | 2 | Sign Out | | Agent State Events | *Available* | 11 | Available | | Agent State Events | *Working* | 22 | Working Off-Line | | Agent State Events | *Engaged ACD* | 13 | Inbound - Line 1 | | Agent State Events | *Engaged VPD* | 15 | Outbound line 1 | | Agent State Events | *Engaged Other* | 16 | Outbound line 2 | | Agent State Events | *On Break* | 12 | Unavailable | | Agent State Events | *Away* | 12 | Unavailable | | Agent State Events | *Lunch* | 12 | Unavailable | | Agent State Events | *Training* | 12 | Unavailable | | Agent State Events | *Aux - Not Available - Disconnect Offhook* | 12 | Unavailable | | Agent State Events | *Aux - Not Available - Allow Offhook* | 12 | Unavailable | | Agent State Events | *Offline* | 2 | Sign Out | | Agent State Events | *Transition* | 23 | Aspect User-Defined state | | Agent State Events | *Suspect* | 12 | Unavailable | | Agent State Events | *RNA State* | 12 | Unavailable | | Agent State Events | *Break After Call* | 13 | Inbound - Line 1 | | Agent State Events | *Monitoring* | 21 | Supervisor | | Agent State Events | *None* | 12 | Unavailable | Configuring Aspect integration To add a new Aspect integration, follow the steps below. * Navigate to **Settings \> Accounts** via the left nav bar. * Select an account. * Select the **Integrations** tab from your account's configuration panel. * Select *Aspect* from the **Type** dropdown menu. * Specify the **UDP Host** and **Port Number** for the WFM integration server. * Specify the **TCP Host** and **Port Number** for the TCP host used for real-time TCP/IP streams. * Specify which of the events you want to report. * Specify the **FTP Host** , **FTP Por** **t Number** , **FTP Username** , **FTP Password** , and **FTP** **Path**. * Select **Send All Agent States** if you want this option. * Don't forget to click **Save** at the bottom of your screen. Aspect integration settings Now that we've reviewed how to add an Aspect workforce management integration, let's review the settings: * **UDP Host**: A string representing the hostname of the WFM integration server. Not currently used. * **Port Number**: A string representing the port number of the WFM integration server. Not currently used. * **TCP Host**: The hostname for the TCP host used for real-time TCP/IP streams to Aspect. * **Port Number**: The port number for the TCP host used for real-time TCP/IP streams to Aspect. * **Agent Login Events**: Specifies reporting an event notification whenever an agent logs in. * **Agent Logout Events**: Specifies reporting an event notification whenever an agent logs out. * **Agent State Events**: Specifies reporting an event notification whenever an agent's state changes. * **End Call Events**: Specifies reporting an event when a call ends. * **Send All Agent States** : Overrides the default behavior by reporting all agent state change events. By default only the state change events for *Login* , *Logout* , *On-break* , *Away* , *Lunch* , *Training* , *En* *gaged* , *Available* , and *Working*are reported. * **FTP Host**: The hostname of the FTP server used for uploading periodic reports for use by Aspect. * **FTP Port Number**: The port number of the FTP server used for uploading periodic reports for use by Aspect. * **FTP Username**: The username used to access the FTP server. * **FTP Password**: The password used to access the FTP server. * **FTP Path**: The path on the FTP to store the files for periodic reports.