{"id":47305,"date":"2023-10-17T09:49:45","date_gmt":"2023-10-17T07:49:45","guid":{"rendered":"https:\/\/www.imagicle.com\/?p=47305"},"modified":"2025-04-15T18:49:16","modified_gmt":"2025-04-15T16:49:16","slug":"customer-service-analytics-webex-calling-mt","status":"publish","type":"post","link":"https:\/\/www.imagicle.com\/en\/blog\/webex-calling\/webex-integrations\/customer-service-analytics-webex-calling-mt\/","title":{"rendered":"New Customer Service Analytics for Webex Calling Multi-Tenant."},"content":{"rendered":"\n

Hey there, Imagicle friends! Summer is over, and we are all back at work. Wouldn’t it be amazing if we could have a second summer? Imagine all the exciting news we could share about reporting for Webex Calling Multi-Tenant! <\/p>\n\n\n\n

Well, guess what? I’m Luca, part of Imagicle’s awesome R&D team, and I can’t wait to show you some fascinating insights into analyzing Webex Calling calls through our new Call Analytics reports<\/strong>. Let’s dive in!<\/p>\n\n\n\n

Enhance the functionality of the Control Hub’s built-in reporting tool.<\/h3>\n\n\n\n

I know what you’re thinking. Control Hub already has a built-in reporting tool. So, why should you care about a dedicated Imagicle app to do the job? <\/em><\/p>\n\n\n\n

Well, the reasons are many.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n


Let’s start with the number of reports<\/strong>. Control Hub offers only 7 reports, while Imagicle Call Analytics provides 50+ reports that group and monitor data, costs, and now even customer service KPIs<\/strong><\/a>. You can choose from templates or customize them, extract them in real time, and schedule them via email.<\/p>\n\n\n\n

Secondly, Control Hub reports provide raw data that require interpretation and prior knowledge of Webex Calling CDRs and data analysis. Imagicle has simplified this complex matter in Call Analytics, offering rich reports<\/strong> with simple and easy-to-read data easily accessible from the Imagicle UCX Suite portal.<\/strong><\/p>\n\n\n\n

All this was made available a few months ago, when Imagicle announced\u00a0the native integration of Call Analytics with Webex Calling Multi-Tenant<\/strong><\/a>. And now, we’ve further enhanced the solution, and we now have these awesome new reports that give us a chance to really dive into how\u00a0automatic call management services implemented through Webex Calling Native Call Queues, Auto Attendant, and Hunt Groups are performing<\/strong>. So buckle up and let’s take a look at them together!<\/p>\n\n\n\n

\n\n\n\n
Want to see Call Analytics in action?<\/h5>\n\n\n\n

Watch a free, customizable demo right now.<\/p>\n\n\n\n

\n
WATCH THE DEMO<\/a><\/div>\n<\/div>\n\n\n\n
\n\n\n\n


Webex Calling Auto Attendants. Understand IVR effectiveness.<\/h3>\n\n\n\n

Native Webex Calling Auto Attendants, also known as IVRs, play a crucial role in Customer Service as they are our customers’ first point of contact. It’s important for us to track various metrics to understand how effective they are.<\/p>\n\n\n\n

The Auto Attendant Summary report<\/strong> gives us valuable insights into the number of calls handled by the IVR<\/strong>, including those transferred or abandoned by callers. It also tracks the average, maximum, and total time users spend interacting with the IVR<\/strong>.<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n


Just like queues, it’s beneficial for an IVR system to capture call routing information<\/strong>. This includes details like the destination number, call type (user, queue, Hunt Group, or another IVR), and the duration of the interaction with the IVR before transfer. Moreover, monitoring the IVR’s activity over time is crucial to understand if a certain destination is not performing well, if there are any technical errors, etc.<\/p>\n\n\n\n

By running the Auto Attendant calls distribution<\/strong> and Auto Attendant calls over time reports<\/strong>, we can have a comprehensive understanding of IVR performance and make informed decisions.<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n


Webex Calling Call Queues Reports. Are queues actually facilitating call management?<\/h3>\n\n\n\n

In the specified time interval, how many calls were processed by the queue? Of those, how many were handled correctly? How many were abandoned by the callers, and what percentage does that represent compared to the total? The\u00a0Call Queues Summary<\/strong>\u00a0report provides a comprehensive overview, presenting the number of calls handled based on their outcome: served, abandoned, overflowed, or transferred by each Webex Calling queue.<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n


Call Analytics then calculates the average, maximum, and total waiting times for the queues<\/strong>, and additionally allows set a waiting threshold<\/strong> (ranging from 10 seconds to 1 minute), setting a benchmark to analyze the quality of service<\/strong>.<\/p>\n\n\n\n

So, what happens after the call leaves the queue? Let’s talk about where outgoing calls are routed from. Ever wondered how many calls each destination handles<\/strong>? And what about the average wait time and talk time of a particular agent <\/strong>on incoming calls from a specific queue? Well, the Call Queues Calls Distribution<\/strong> report has got all the answers for us. <\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n


Speaking about agents: how are queue agents performing? Are they losing any calls compared to the ones they handle correctly? And how much time do they usually spend on calls? You can find the answers in the Call Queues Agent Analysis<\/strong> report.<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n


Also, how do queues’ activity change over time? And how does the number of calls handled by a specific queue evolve? Check out the Call Queues calls over time<\/strong> report for that.<\/p>\n\n\n\n

Each report is designed to provide valuable insights into a specific point in the call journey through the queue<\/strong>, giving a holistic analysis of how your company is leveraging this tool<\/strong>. With these reports, you’ll find out if queues are actually making call management faster, or if you need to make some tweaks and reinvestments to help your agents and tools perform better.<\/p>\n\n\n\n

Webex Calling Hunt Groups. The best and only way to analyze them.<\/h3>\n\n\n\n

One of the pillars that make Call Analytics a pivotal tool for your Webex Calling is\u00a0native Hunt Group analysis<\/strong>\u00a0– in fact, the Control Hub tool doesn’t give any insight into native Webex Calling Hunt Groups.<\/p>\n\n\n\n

As Imagicle, we provide a specific set of reports to dig into Hunt Groups, starting with the Hunt Group summary<\/strong> report, showing you the best and worst Hunt Groups based on missed calls and the fastest and slowest to answer. <\/p>\n\n\n\n

Are you interested about the behavior of a specific Hunt Group destination? Refer to the Hunt Group by extension<\/strong> report.<\/p>\n\n\n\n

Are you curious about the busiest hours of the day? Those times when services may struggle and risk missing important calls? Our Hunt Group Busy Hours <\/strong>report has got you covered. <\/p>\n\n\n\n

And if you want to dive into the full details of all calls that have passed through the Hunt Groups, you can easily launch the Hunt Group Calls Details<\/strong> report. You even have the flexibility to select only the fields that interest you the most.<\/p>\n\n\n\n

\n\n\n\n
Want to launch these reports by yourself?<\/h5>\n\n\n\n

Book a free trial now.<\/p>\n\n\n\n

\n
BOOK A TRIAL<\/a><\/div>\n<\/div>\n\n\n\n
\n\n\n\n


Customer Service Call List. One report to rule them all.<\/h3>\n\n\n\n

Alright, it’s awesome to understand how our services perform, but it’s the overall experience we create for our customers that truly matters.<\/p>\n\n\n\n

It rarely happens that a call interacts with one service only.<\/strong> In everyday company life, calls go through numerous Call Queues, multiple Hunt Groups, and definitely more than one Auto Attendant before reaching their resolution. <\/p>\n\n\n\n

Traditionally, call tracking reports show you the performance of calls through a certain service on their own – there\u2019s a Hunt Group Report, a Call Queue report, and so on; but they don\u2019t communicate with each other. But, for example, a call might start its journey in your company through an IVR offering a multi-level menu. Then, it gets routed to a queue, or even more queues, or Hunt Groups, all based on which keys the user pressed in the IVR.<\/p>\n\n\n\n

And sometimes, it\u2019s even more complicated: imagine a queue that\u2019s full or that surpasses the maximum waiting time. At that point, the call, might fall into yet another queue, IVR, or Hunt Group.<\/p>\n\n\n\n

This means that it\u2019s almost impossible to understand the journey of a call, from the moment it enters our services to when it concludes, without mixing and matching reports (hence, wasting time). Questions like How long does a caller stay on hold in total? How many stops does a call make? Did a human agent interact with the caller at any point during the call? And at what stage in our infrastructure is a call abandoned?<\/em> are left unanswered.<\/p>\n\n\n\n

Well, you guessed it: not anymore. The magic lies in our Customer Service Call List,<\/strong> famously known as the cradle-to-grave report. It filters all incoming calls that have passed through at least one queue, a Hunt Group, an IVR, and provides both a concise and an extended version.<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n


The concise version reveals the last party that interacted with the caller, and whether there was any human operator involvement (this can also be filtered). And for those craving more insights, the extended version showcases every single step of the call, allowing you to easily reconstruct its entire journey through multiple services.<\/strong><\/p>\n\n\n\n

And the best part about all this is that, once you\u2019ve understood holistic customer service performances with this report, you can go back to the specific reports we\u2019ve mentioned above to learn more about specific services involved in the call journey.<\/p>\n\n\n\n

Bonus track. An old friend.<\/h3>\n\n\n\n

If you are curious to know which phone models are most used by your operators, whether these are physical phones or software clients such as the Webex App, now you can! The standard Device Model Adoption and Device Trend Usage reports<\/strong><\/a> work perfectly with Webex Calling calls too! <\/p>\n\n\n\n

Understanding how your devices are being used is the best way to optimize resources, cut costs, and make decisions that could change your business outcomes for the better.<\/p>\n\n\n\n

Conclusions.<\/h3>\n\n\n\n

Customer Service must be kept under control in the best possible way, as it can be both the strength and the weakness of your offer. With Imagicle’s new reports, specific for the services offered by Webex Calling, every detail of the calls is under control. <\/p>\n\n\n\n

And of course, don’t even for a second think that Imagicle is done innovating its reporting offer for Webex Calling. These reports will be available shortly <\/strong>(beginning of November\u201923)<\/strong>, but the best stays yet to come, but if you want to have a taste of the present, all you have to do is book a free demo<\/strong><\/a> or a free trial<\/strong><\/a> – the reports are waiting for you to launch them!<\/p>\n","protected":false},"excerpt":{"rendered":"

Explore Imagicle’s new reports for Webex Calling, optimizing Customer Service with comprehensive call analytics.<\/p>\n","protected":false},"author":8,"featured_media":47346,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[7002],"tags":[],"tax_labels":[148],"class_list":["post-47305","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-webex-integrations","tax_labels-products"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.imagicle.com\/en\/wp-json\/wp\/v2\/posts\/47305","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.imagicle.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.imagicle.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.imagicle.com\/en\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/www.imagicle.com\/en\/wp-json\/wp\/v2\/comments?post=47305"}],"version-history":[{"count":1,"href":"https:\/\/www.imagicle.com\/en\/wp-json\/wp\/v2\/posts\/47305\/revisions"}],"predecessor-version":[{"id":60266,"href":"https:\/\/www.imagicle.com\/en\/wp-json\/wp\/v2\/posts\/47305\/revisions\/60266"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.imagicle.com\/en\/wp-json\/wp\/v2\/media\/47346"}],"wp:attachment":[{"href":"https:\/\/www.imagicle.com\/en\/wp-json\/wp\/v2\/media?parent=47305"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.imagicle.com\/en\/wp-json\/wp\/v2\/categories?post=47305"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.imagicle.com\/en\/wp-json\/wp\/v2\/tags?post=47305"},{"taxonomy":"tax_labels","embeddable":true,"href":"https:\/\/www.imagicle.com\/en\/wp-json\/wp\/v2\/tax_labels?post=47305"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}