At a contact center, alarm bells clanged when it was suddenly observed that the wait times shot up by 2x, and resolution time by 4x. This raised several red flags in the reports and dashboards. However, beyond that observation, the traditional reports could not provide intelligence as to why was this happening and what action should be taken to mitigate it. Which capability do they need to be best geared for such eventualities?
Unique challenges of managing data-driven contact centers
The challenges of managing a customer contact center are like no other business. There is little control over demand forecast, and if it goes haywire, resources must be deployed in tandem to meet SLAs. Customers can choose any day, time or channel—voice, chat, e-mail or even switch between them–and expect continuity and consistence of service. Service quality is highly people dependent. Overworked agents result in burnouts and high-resolution times. CXOs need to continuously monitor and optimize to balance between resource slackness and stress. Moreover, multi-location centers develop data silos, sometimes fragmenting a single customer account. To plan for every cycle, data is often collected in multiple spreadsheets which need to be manually collated. This results in delays and errors, ensuing in a lack of trust. Analytics derived from this data are limited in scope and not reliable enough to help on-ground decision support.Addressing challenges with Workforce Management solutions

Introducing static reports
WFM software integrates a business analytics and intelligence module that supports executive decision making. These modules have built-in static reports and dashboards which track key parameters that monitor business health. Often hard coded by analysts and developers and automated to be distributed periodically to the management team, these built-in reports are a great tool that provides a snapshot of the business and trendlines from the aggregated data.However, static reports have limitations in terms of their applicability, and CXOs of data driven contact centers rely on ad hoc repots to optimize their operational agility. When data analysts build reports, their focus tends to be on the data and not the visualization and hence, the report formats tend to be unintuitive numbers on a spreadsheet. This can be compounded by static reports being hard coded instead of reporting tools, making alterations by the business user nearly impossible.Static reports are great for management reviews and to make strategic decisions on the business direction.
Ad hoc reports supplement static reports
Operations are ever dynamic and unpredictable and functional managers need information and decision support to deal with the current and emerging situations. Line managers need to make operative decisions on a day-to-day basis. They need reports of what happened yesterday, last summer or during the last holiday season, and intelligence from analysis of this data to take immediate decisions to optimize the next shift, day or week. They need to drill down from the aggregated data into root cause and take corrective actions or adjust maximize efficiency. They also need real time answers to their queries to understand the insights hidden within the data.
Static and ad hoc report comparatives
The infographic compares Static and Ad hoc reports and their usage:Static / Canned Reports | Ad hoc Reports | |
---|---|---|
Periodicity | Pre-decided, Weekly, Monthly or Quarterly or Annual | Any time, on need basis |
Usage |
|
|
Audience | Pre-decided as per distribution list | Created by/shared with audience and stakeholders on a case-to-case basis |
Generation | Automated | Manually, in self-service mode |
Frequency | Repeats as per schedule | One-time |
Format | Often text-based, with tables of aggregated data to show trends | Highly Visual and user friendly to support agile decision making |
Developer dependency | Yes | No |
Ability to code | Required | Not required |
Customizable by users | No | Yes |
Ad hoc reporting for WFM
The true power of WFM solution is unleashed when managers use ad hoc reporting to get real-time insights from real-time data, that can be immediately acted upon. Ad hoc reports and analytics pulled out from WFM software must be real-time to be a useful decision support tool for users. For example, canned reports generated at the end of day or shift are of no use in managing intra-day workload variations. Also, these reports must integrate data in real-time from all sources may they be at different geographical locations, or multiple contact channels like e-mail, chat or calls. Ad hoc analysis is a business intelligence process that lets users dig deeper into the objective data to find answers to specific business questions that would help in decision making. WFM solutions integrate a BI module that uses advanced analytics, preferably with AI and ML capabilities. They have inbuilt analytics and drill-down capabilities that help in understanding the root cause of unplanned events and deviations, and to take decisions about corrective actions.What makes a good ad hoc reporting tool?
Ad hoc reporting tools also have self-service analytics capability and integrate data from various sources using built-in data management tools. Additionally, ad hoc reports present information visually which makes it easy to quickly grasp and act. This is an important to minimize time lag in understanding the real story hidden in the data. WFM users should be able to create these reports on-the-fly as needed to support agile decision making. Despite the challenges of using disparate data types or sources, running ad hoc queries, and ad hoc analytics and reports should be generated with no time lag. To summarize, an ad hoc reporting and analysis tools for WFM should have:Use-cases of ad hoc reporting and analysis
Consider these ad hoc report examples that illustrate where it scores as an important decision-making tool in managing operations.- A monthly or quarterly sales report for a company presents aggregated trends and shows that sales revenues are consistent. However, an ad hoc report pulled by the sales head shows that the western region sales is declining, though it’s balanced by a corresponding increase in eastern region. A further drill down into western region data using self-service analytics provide more insights on this drop attributing it to declining orders from large volume customers, or salespersons who previously contributed higher revenues. Armed with this knowledge, the sales head can pull the right levers to turn around the situation, acting immediately.
- A contact center supports customers of multiple products of a company. The average call volume is 15,000 calls/day, with an average resolution time of 2.5 mins. The team is well trained on the products, and the resource plan is optimized to meet an average wait time of less than a minute. The key SLA metrics are captured by the periodic static reports and monitored by the VPs and stakeholders. Suddenly, it was observed that the wait times shot up by 2x, and resolution time by 4x. This raised an immediate red flag in the reports and dashboards. However, beyond that observation, the traditional reports could not provide intelligence as to why was this happening and what action should be taken to mitigate it.To understand the root cause, the WFM managers used ad hoc reports, breaking down call reports by shifts, agents, products, time of the day and centers. These reports made it clear that there was exponential increase in the call volumes for one of products, along with a high-resolution time which effected the overall performance. Ad hoc reporting was used to trace the root cause to a feature change in a newly launched model, which was not user-friendly and resulted in an increased the number of support calls.To resolve, calls pertaining to the new model were routed to a dedicated resource team culled out from the existing team. The rest of the team maintained the SLAs for the other products, while the new product team were monitored using a different matrix agreed with the customer.
Ad hoc reports within WFM software empowers decision making in call centers
