Building Talkdesk Explore™ Reports and Dashboards can be one of the best ways to empower your management with a curated view and the ability to explore data. In order to ensure you’re creating a great performance experience, there are some design choices to consider.
Dashboards in Explore are a historical overview of what’s happening in the contact center, which provides you the first level of analysis by filtering and digging a little deeper. The main focus is a visual, quick understanding of what’s happening.
If you have a dashboard running slowly, there are components that are more memory intensive and worth knowing about. Data volume will impact performance the most - the more data returning in an individual element, the more memory resources are consumed. Reports with more than thousands of data points will consume more memory.
Reports, on the other hand, exist to carry the heavy load. They’re designed to provide the basis of exploration, a deeper insight, and understanding of your data, such as the analysis of trends. In this sense, we provide several tools to filter more detail-oriented, without losing the focus of what it’s aimed to be analyzed.
Reports with table calculations consume more memory, therefore, the more table calculations a report has, the more memory is consumed. Also, reports created with dimensions that are pivoted will consume more memory, so, the more dimensions pivoted, the more memory is consumed when the dashboard is loaded.
Tips
Below are some tips to help keep your Reports and Dashboards healthy:
- Reduce the number of widgets on your dashboards. There’s a limitation of 25 tiles (except text tiles) to preserve the dashboard’s performance. If the tiles host heavy queries (several filtering conditions or large timeframes, for instance) you should consider having around 12, 15 tiles in your dashboard, so it triggers the information you need in a timely manner. This will improve the load time of those dashboards and if you’re trying to create a PDF file as well, the process will be quicker.
- Use filters to have a more straight to the point approach to the information you need (instead of receiving a file with a dump of data for the last month). Firstly, use the filters available in the User Interface (UI) before scheduling or sending/downloading your files to guarantee that you’ll receive the information you want to receive.
- Limit the number of days in your reports and dashboards when possible, especially for large reports/dashboards with many records.
- When setting up a schedule or sending a big time frame, consider breaking it into smaller chunks, for example, instead of requesting a whole year of information. Break it down into four distinct deliveries of three months each.
- Schedule your reports and dashboards when possible. You won’t have to wait while the report processes, since it will be ready to consume at the given date/time.
- Diversify the timing of your scheduled reports. Program them to run in the early morning hours, when fewer people will have their reports scheduled.