Combining Ticket & Survey Data in Dashboards (CX)
What's on this page
About Combining Ticket and Survey Data in Dashboards (CX)
Many customer experience programs use both survey and ticket data to create a comprehensive “close the loop” program. Surveys provide a means to collect customer feedback, while ticket systems notify your representatives of the most critical feedback, allowing representatives to then reach out to customers and resolve issues as they arise. This process can build trust and close experience gaps, but to keep it running smoothly, it’s important to have the right reports and visualizations in place.
With the data mapper, ticket and dashboard data had to be separated onto different pages. However, now, with the data modeler, this data can be combined into one page, allowing for more dynamic dashboard visualizations.
Qtip: This page focuses on how to make sure you can join survey and ticket data together in a dashboard. For more comprehensive guidance on how to build a tickets program, see Closing the Loop.
Setting Up Tickets in Surveys
In order for tickets and survey results to appear in the same dashboard, your tickets should be connected to a survey. You cannot use tickets created in scheduled workflows or workflows started by non-survey events.
As responses are collected in this survey, tickets will be created and stored in the follow up page.
Creating a Data Model
Creating a Dashboard
After creating a data model, the survey and tickets data is ready to be mapped to a new dashboard.
Qtip: This section describes elements of creating a CX dashboard. For more information on dashboards, see Getting Started with CX Dashboards.
Once the dataset is added to the dashboard, you will see both tickets and survey data fields while building your widgets.
Example Widgets
Below are a few example widgets to help understand how the feature can be used:
- A line chart widget showing the number of survey responses and the number of tickets generated over time.
- A line chart widget showing the average ticket resolution time over time.
Editing the Dashboard’s Data Source
When building your dashboard, it may be necessary to edit your data source in order to enable the kinds of widgets you want to customize your dashboard with. For more information, see Field Types and Widget Compatibility (CX).
Migrating Ticket Reporting Data to the Data Modeler
Warning: When setting up a join, all records will be pulled from the left source (in this case, surveys). Only 1 record from the right source (ticket) per record on the left (survey response) will be joined. If you have multiple tickets per survey response, only a single ticket per response can be joined in this way. If you want to pull in all ticket data separately from your survey responses, use a union instead of a join.
Ticket Reporting Datasets are built using ticket data from all projects combined, whereas the data modeler separates each ticket dataset by project. Ticket reporting datasets cannot be imported into the data modeler, but they can be replicated by combining ticket datasets from different projects in the data modeler.
Attention: Ticket Reporting Datasets can not be imported into the data modeler.
That's great! Thank you for your feedback!
Thank you for your feedback!