Jump to: navigation, search

Genesys CX Insights

Genesys Customer Experience Insights (Genesys CX Insights or sometimes GCXI) provides a presentation layer that extracts data from the Genesys Info Mart database, and presents it in readable historical reports to enable business and contact center managers to make better business decisions for streamlining operations, reducing costs, and providing better services.

For Genesys Cloud customers, depending on the release of Genesys Cloud that you are using, historical reporting is available through either the Genesys Interactive Insights (GI2) interface, or through Genesys CX Insights. See also Genesys Info Mart, Reporting and Analytics Aggregates (RAA), and Genesys Interactive Insights (GI2).



Understanding and using reports

This page helps you understand Genesys Customer Experience Insights (Genesys CX Insights) reports and dashboards. The Genesys CX Insights reports and dashboards for Genesys Info Mart compile historical contact center interaction activity and agent-summarized states for telephony and multimedia DNs.



Genesys CX Insights includes several dozen reports out-of-the-box, which are available in subfolders within the CX Insights folder. The data in the reports represents a snapshot of the database at a given point in time; to view current data, you must run the report to display the latest data. The reports use the hierarchies, metrics, attributes, prompts, details, and filters that are defined in the CX Insights Project.

Reports are designed using MicroStrategy Web. The figure shown here illustrates the organization of some of the reports in the Agents folder and some of the operations that you can perform within MicroStrategy Web. For more information about customizing the reports, see Customizing reports and dashboards



Genesys CX Insights includes several dashboards out-of-the-box. While some dashboards are available in the CX Insights > Dashboards folder, many are found in other folders, where they are grouped with reports based on the type of content they provide -- see the latest list of Dashboards for more information.

The Genesys CX Insights dashboards provide visual summaries of information that would otherwise be displayed across several reports. The data in the dashboards represents a snapshot of the database at a given point in time; to view current data, you must run refresh the dashboard to display the latest data. For optimal viewing of the dashboards, set your screen resolution to a the highest resolution that is practical, and in any case, to a width of at least 1280 pixels.

Dashboards are designed using MicroStrategy Web. For more information about customizing the dashboards, see Customizing reports and dashboards

CX Insights interfaces

Your interaction with CX Insights will usually take place in one of two GUIs:

  • MicroStrategy Web — When you view, run on-demand, or modify a report or dashboard, you do so using MicroStrategy Web, the primary Genesys CX Insights GUI, which you access using the URL (<yourserver>/MicroStrategy/servlet/mstrWeb) provided by your administrator. Administrators can configure permissions that determine which operations each user can perform in MicroStrategy Web. MicroStrategy Web is discussed on this page.
    [+] Supported Browsers
  • MicroStrategy Developer — Reserved for administrator use, MicroStrategy Developer is a standalone application you access on the computer where MicroStrategy software is deployed. Use Developer to create and manage projects, objects and users, and to perform other administrative actions. MicroStrategy Developer is discussed in more detail on the Understanding the Project page.
The Contact Center Dashboard on a mobile device

Mobile support

You can also access Genesys CX Insights dashboards from your Apple iPad. Genesys supports accessing the dashboards in this fashion, but does not recommend using reports from a mobile device, as they are not designed for small screens. See the Genesys CX Insights Deployment Guide for more information, and the MicroStrategy website.

Genesys documentation, including this document, also supports mobile devices. In most cases, it easier to use Genesys CX Insights, and the documentation, in landscape mode.

Video: Generate reports in Genesys CX Insights

This video describes how to generate reports in Genesys CX Insights.

Accessing and running reports and dashboards

  1. Go to the Genesys CX Insights (MicroStrategy Web) link provided by your administrator.
  2. If a page appears where you can select a server, choose the server on which to view reports (you probably have only one, but if more than one appears, and you are not sure which one to select, contact your administrator).
  3. If prompted, enter your user name and password.
  4. The Genesys CX Insights page appears. Click Shared Reports > CX Insights.
    [+] More about report folders
  5. Reports are divided into subfolders based on function; select a sub-folder, for example Business Results.
  6. From the listed reports, either double-click a report, or right-click and choose Run. For example, Business Metrics Executive Report. The prompts for that report appear.
  7. Select a date or date range, and optionally make selections for other prompts.
    To generate meaningful reports, choose dates for which your environment has data. Note that, if you are working in a demo/development environment, data is available for a limited period:
    • For Genesys CX Insights reports, data is available for the period September 2015 to October 2016.
    • For Genesys CX Insights for iWD reports, data is available for the period February 12, 2019 to February 21, 2019.
    When you run reports in such environments, choose dates within that range, or simply remove the default value from the first prompt (Pre-set Date/Day) before you run the report.
    [+] More about prompts
  8. Click Run Report.
    The report appears. You can filter, drill, and otherwise interact with many report values.
As you browse in Genesys CX Insights, clickable breadcrumbs are displayed at the top and bottom of the page:
Shared Reports > CX Insights > Business Results
Click any word in the breadcrumb to return to that folder.

Help finding reports


You can use the search feature to easily find all reports with a given word or phrase in the report name:

  1. Select the top level CX Insights folder (to search the entire folder).
  2. At the top of the page, click the magnifying glass to open the search window.
  3. Select a folder (for example Shared Reports) in which to search, enter a search term (for example Callback), and press Enter (or click the magnifying glass).
  4. For more powerful search options, click Refine. Advanced search options appear, which you can use to refine your search based on various criteria, such as object type, owner, date, or description.

Anatomy of a report


Each report is divided into several sections (except for the main section of the report, each section is called an 'editor'):

  • Report Details Editor — provides information about the data in the report. You can optionally close this editor by clicking x.
  • Prompt Details Editor — provides information about the prompt values used to run the report. You can optionally close this editor by clicking x.
  • The report grid — In most cases, reports consist of a simple grid, illustrating the selected data. Some prompt and metric names shown in reports are self-explanatory, but some may require explanation; see the individual report descriptions (see the list of reports) for more information about specific prompts and metrics.
  • Other editors appear if you open them, such as the View Filter Editor.

What zero signifies in a report

Whenever the underlying query for a Genesys CX Insights report returns no rows, the report displays no data. For example, a query to retrieve activity for a particular agent for a shift that the agent did not work returns no data.

Zero Values in the Speed of Accept Report

For those Genesys CX Insights reports that do return rows, but in which a particular field is not applicable, the reports return a value of 0.

For example, this occurs when all interactions for a particular day are accepted within the first four service time intervals that are defined for a tenant, but none are accepted beyond the fourth interval. As a result, the Speed of Accept (seconds) Report—a portion of which is shown in the figure Zero Values in the Speed of Accept Report—displays 0 values for the each of the fifth through tenth intervals.

The reports also return 0 for measures when the underlying database columns on which measures are based hold 0 values. Additionally, when a report is based on a query that gathers data from more than one aggregation table, empty cells in reports are possible where other cells contain data.

For composite measures, such as percentages and averages, wherever a 0 count or 0 duration ensues, the reports display 0 for such measures. The average duration of calls placed on hold, for instance, is 0 in the circumstances where either no calls were placed on hold during the interval, or where the duration of held calls was 0 seconds (or a fraction of 1 second).

The custom reports that you create might behave differently depending on their design.

The report grid

The main area of a typical report consists of a simple grid, optimized for on-screen viewing, but also easily printed to PDF, XLS or other formats. (For reports with a lot of columns or rows, you may find it easiest to view your reports as PDFs.)

The first few columns of each report represent Attributes (also known as Dimensions). These are values that divide up the data, and their impact is cumulative, from left-to-right. For example, in the Agent Utilization Report (shown here), the first column divides the data by Tenant Name, the second column subdivides the tenant data by Media Type, the third column subdivides the tenant/media data by Agent Name, the fourth column subdivides the individual agent data by Interaction Type, and the fifth further breaks that down by Day.


Depending on your access role and the report you are viewing, you can manipulate a report in several ways:

  • Sort—Right-click in a column, and choose an option from the Sort menu, to sort the table by the order of that column. Or, choose Sort Grid to sort the table by more than one column. Not all columns can be sorted.
  • Drill—Right-click in a column, and choose an option from the Drill menu, to drill up or down on the data in that column. For example, to change from viewing data for the Month, to viewing it for the Day, Hour, or even the Year. See Drilling in report data. Not all columns can be drilled.
  • Filter—Right-click in a column, and choose an option from the Filter on menu, to open the View Filter Editor, where you can select one or more conditions. See Filtering report data.

Agent-based reports do not contain data that summarizes virtual interactions, virtual agent activity, and Interactive Voice Response (IVR) port activity. However, if IVRs are configured as handling resources in your environment, data that pertains to IVR ports is included in the business attribute and interaction detail reports.

Video: Drill or filter in reports

This video describes how to read, drill, and filter historical reports in Genesys CX Insights.

Controlling what data appears in a report


In many cases, you may want to restrict what data is gathered into a report; for example:

  • if your environment contains a large amount of data, some reports can become very long.
  • if you want to see a report about just one aspect of the contact center, such as single agent group.

When you open any report, the report prompts appear, where you can customize the data that is taken into the report. The prompts available are specific to each report—the example shown here pertains to the Agent Conduct Report:

  • For each prompt, enter or select appropriate values. Each prompt provides either a drop-down list or a search field and accompanying button.
  • Use the Index, to the left of the prompts input area, to quickly jump to any section of the prompts.
In many cases, the default values are appropriate; if in doubt about a given prompt's effect, see the descriptions given below, or try running the report with default values to get a better idea of the result. Each report has a unique set of prompts from which you can select values for the attributes used in the report. For example, in the Agents / Agent Conduct Report, you can make the following prompt selections:
[+] Show: Prompts in the Agent Conduct Report

Filtering report data


After running a report, you can further filter the data that appears in the report. These filtering options are powerful, and let you make more selections than those you made on the prompts page when you ran the report. You can add more than one filter on a report.

Use either of the following to methods to filter a report:

Creating a filter using the View Filter Editor

Open the View Filter Editor to manually construct a filter.

  1. Open and run a report. For example, Agents > Agent Utilization Report.
  2. Click Tools > View Filter.
    The View Filter Editor appears.
  3. Click Add Condition.
    The Filter On drop down list appears.
  4. Click Filter On, and select a value on which to filter. For example, Agent Name will allow you to show only specified agent in the report.
    A list of Available agent data appears.
  5. Double-click the name of each Agent to include (you can include one, several, or even all), and click Apply.
    You can add more than one filter on a report.

Filtering on selections

Use Filter On to build a filter more quickly.

  1. Open and run a report. For example, Agents > Agent Utilization Report.
  2. Right-click a value that you'd like to filter on (a value in one of the attribute columns, such as an agent name)
  3. Click Filter on Selections.
    The View Filter Editor appears, where you can modify the filter as needed.

Drilling in report data


You can drill on report data to see more detailed (or more general) information.

  1. To drill on a report, first open and run the report.
  2. Right-click a heading in the report; a context menu opens. If it is possible to drill on the metric on which you have clicked, Drill appears in the menu.
    The choices available vary depending on the type of data on which you click ('Drill down to Agent Name', 'Drill up to Month', 'Drill down to Interaction subtype', and so on). Not all data can be drilled. For example, right clicking the heading Day (in reports where that heading appears, such as Agents > Agent Utilization Report) gives you the option to drill to another time period, such as Month or Year. Arrows in the menu indicate whether a drill option is drilling 'Up' or drilling 'Down'.
  3. Select one of the drill actions that appear. The report automatically updates to account for the change. Open the Drill menu again; the available options have now changed.

Advanced tip: For more comprehensive drill options, click the Data menu, and select Drill. The Drill Editor appears, where you can drill on multiple columns, and access advanced options.

Printing or exporting report data


You can easily export your reports to a variety of formats, including PDF (useful for printing) or Excel/CSV (useful if you want to take the data into other applications or manually edit the output).

  1. Click Report Home > Export > PDF.
    The PDF options page appears in a new browser tab.
  2. Optionally, select options to control how the report will be exported, such as page size, orientation, or other aspects of formatting. For many reports, it is a good idea to select Fit to 1 Pages Wide and Landscape.
  3. Click Export. The PDF opens automatically in the browser tab. If you are happy with the output, you can click Download (to save the file) or Print.

Some users find it useful to export data to a spreadsheet format, as it is then possible to more easily sort and view the data, particularly if there is a lot of data in your report, due to the larger screen area available in a spreadsheet application, such as Microsoft Excel. This is particularly true if you have a great deal of data in your report, or in the case of reports that just can't easily fit in a browser window because they contain many columns or rows.

Scheduling the delivery of reports


You may find that it is helpful to run the same report regularly; every day, or every week, for example, and deliver it automatically to one or more users in your contact center, whether to email, printer, or a mobile device. This procedure describes how to schedule the delivery of a report by email by first defining an email address, and then subscribing to the report using that address.

You must be an administrator (or a member of the group “CX Insights report developers” or “CX Insights report editors”) to configure an email address. Otherwise, contact your administrator to complete steps 2 and 3 for you (steps are provided by MicroStrategy, in the article KB30581).

  1. Log in to CX Insights.
  2. Click your user name, select Preferences, and click E-mail Addresses.
  3. In the Email Addresses list, click Add a New Address. Enter the Address Name (a short name to identify the account), the Physical Address (the email address), and choose the Device (the type of email, such as Microsoft Outlook). Click Save.
  4. In the breadcrumbs, click CX Insights to return to the Home page.
  5. Open the Shared Reports folder, and navigate to the report you want to schedule.
  6. Hover over the report name/description, and several options appear below the description. Click Subscriptions.
  7. On the My Subscriptions page, scroll down and click Add email subscription. The E-mail Subscription options appear, as shown in the adjoining figure.
  8. Choose an option from the Schedule, and To lists. You can add more than one recipient in the To list.
  9. Optionally, test the subscription by selecting Send a preview now (if you do, an email typically arrives within a few minutes). Click OK.

If you create a subscription for a user who is, or later becomes, disabled, MicroStrategy does not send the report to that user, though it continues to send it to other subscribers.

In release 9.0.010 or later, if you have created subscriptions for a user, use the following steps to transfer those subscriptions to another user (without having to recreate them from scratch):

  1. Open MicroStrategy Products > Command Manager. A log-in dialog appears.
  2. Log in as user who is a member of both the General Developers group and the General Users Administrators group.
  3. Enter the following command into a script:
    ALTER EMAILSUBSCRIPTION "<subscription_name>" OWNER "<user_name>" IN PROJECT "<project_name>";
    For example:
    ALTER EMAILSUBSCRIPTION "Agent Conduct Report 3/21/19 2:30:15 PM" OWNER "Administrator" IN PROJECT "CX Insights";
  4. On the menu, click Connection > Execute.

For information about user groups (including General Developers group and the General Users Administrator) see the Genesys CX Insights Deployment Guide. If you have difficulty, contact Genesys Customer Care for assistance.

Enabling Languages on the server

Several languages are supported by Genesys CX Insights, and the files to support them are included in the IP. However, before users can select a language, an administrator must enable it on the server.

Use the following steps to enable a language on the server.

  1. Execute the following command to back up the GCXI meta db:
    kubectl -f apply k8s/gcxi-backup.yaml
  2. Execute the following command to stop currently running containers
    kubectl scale deploy/gcxi-slave --replicas=0
    kubectl scale deploy/gcxi-master --replicas=0
  3. Edit the gcxi.properties file, and add the LANGS variable:
    where each <lang_code> is a value from the table in Supported languages. The first value added (<lang_code_1>) becomes the default language. For example, to make Chinese (simplified) the default language, and enable both German (Germany) and Japanese:
    Note the following:
    • The format of the <lang_code> variables changed beginning in release 9.0.010.
    • In release 9.0.009, only one language code can be enabled at any time. Further, once you enable a language other than US English, switching to a different language can cause only partial translation. If, after enabling a language, you wish to switch to a different language, talk to your Genesys representative, or upgrade to a later release.
  4. Execute the following command to load gcxi.properties into Kubernetes:
    kubectl delete configmap gcxi-config
    kubectl create configmap gcxi-config --from-env-file=k8s/gcxi.properties --namespace genesys
  5. Execute the following commands to start the master container:
    kubectl scale deploy/gcxi-master --replicas=1
    Wait until master node is done (wait until Tomcat is up, and MicroStrategyWeb page is available).
  6. Execute the following command to start the slave container:
    kubectl scale deploy/gcxi-slave --replicas=1
    Users can now change the language. (See Changing the language used in the reports.)

Note the following:

  • When you enable a language on the server, the reports and GUI are automatically switched to that language.
  • When non-administrative users change language preferences, they will see a list of language choices that includes languages you have not enabled; to avoid confusion, if users will need to switch languages, you should notify them about what language you have enabled for them to use.
  • As an administrator, you can optionally change language default settings for all users; log in as an administrator, and click Preferences -> Project Defaults -> General.

Supported languages

Beginning with release 9.0.009, Genesys CX Insights provides support to translate (localize) the GUI and Genesys CX Insights reports into the the languages listed in the following table. The format of the language variables changed in Genesys CX Insights release 9.0.010, and additional languages were added; see the appropriate column in the table to match your installed release.

Language LANGS variable value in release 9.0.009 LANGS variable value in release 9.0.010 and later
Arabic ar-SA
Chinese (simplified) CHS zh-CN
French (Canada) FRC fr-CA
French (France) FRA fr-FR
German (Germany) DEU de-DE
Italian ITA it-IT
Japanese JPN ja-JP
Korean ko-KR
Portuguese (Brazilian) PTB pt-BR
Russian RUS ru-RU
Spanish (Latin American) ESLA es-419
Turkish TRK tr-TR

You cannot change the language used in Gensys CX Insights for iWD reports.

Changing the language used in the reports


Before you can select a language, an administrator must enable it on the server. Only one language, in addition to US English, is enabled at any time. Talk to your administrator to find out what language is available for your use (or see Enabling Languages on the server). Changes described in this procedure apply only to your own sessions, not to other users.

Use the following steps to change the language used in the GUI and reports.

  1. Log in to Genesys CX Insights.
  2. Click on the drop-down menu next to your user name, and select Preferences.
  3. On the User Preferences > General page:
    1. Change the language used in the GUI: In the Language section, select a language from the list.
    2. Change the language used in the reports: Click Show advanced options, from the Metadata list, select a language.
  4. Scroll to the bottom of the page, and click Apply.
  5. Use the browser's back arrow, or click in the breadcrumbs, to continue.
Not all languages listed in the GUI are enabled for your use. Check with your administrator.

Where can I learn more?


In addition to the Genesys CX Insights documentation, extensive MicroStrategy Product Documentation is available. (MicroStrategy is the engine that drives Genesys CX Insights.) See links to specific MicroStrategy wiki pages on the Additional Resources page in this document.

  • For context-sensitive help to explain the options you see on the Genesys CX Insights GUI, click the ? next to the editor for which you want more information.
  • For advanced users seeking detailed information, click the menu next to your user name, and click Help to access the latest online MicroStrategy user guides and manuals.
This page was last modified on April 15, 2019, at 12:08.


Comment on this article:

blog comments powered by Disqus