Skip to main content

Two of a kind: Call Center and Soccer


What a Call Centre and Soccer do have in Common
One of the eternal problems in a call center is getting an enquiry routed to the right agent. This is doubly true in a mobile world that demands conversational support in near real time.
Add to this the fact that most customers seeking support already failed to find an answer to their inquiry using an FAQ, a community, or other self-services. In this situation customers expect an answer within few minutes, if not seconds.
On top of this, the ability to make engagements with the company easy, efficient, and ideally joyful, is becoming more and more a distinguishing factor for companies. Customer experience is the result of engagements, and for humans the experience gained from the most recent engagement tends to have a higher influence than older ones. Consequently, a positive customer experience matters, not only during marketing- and sales, but even more so in situations that require active help of the company that sold the product or service. So, getting a solution to an issue must be as easy and as human as possible.
The challenge is that every support organization needs to live and work with limited resources – human as well as technical ones.

It is Like a Good Game of Soccer

11 players and a ball. There is a goal keeper, are defenders, midfielders and attackers who play as a team against their opposition, trained by their coach and guided by the captain. There is a core team, and some players may be assigned to different roles, even within one game. Depending on the opposition team, the coach and the captain change player assignments, tactics and roles.
Together they play the ball with the objective of scoring.
Like a soccer team call center agents are organized around their strengths and like soccer players the agents are – or should be – carefully trained and assigned to roles on their field: the queues with which incidents are managed. Like the soccer players, agents can be assigned to different positions on the field: different queues.
The incident is the ball and the scoring is resolving the incident.
With all its intrinsics, soccer is a simple game. It has a few rules that dictate the do’s and don’ts. Following these rules, considering available players and their strengths, is the table stakes. Yet, this doesn’t make for a game that the spectators may find exciting – nor might it lead to scoring. There is an art to it, the art of how and to which player to move the ball in any given situation.
This is the same in a call center environment.
Yet, in some call centers, when receiving the incident, the team stops and asks the spectator where to start. The user is asked to qualify it and to route it into the right queue. This is a task (s)he is obviously ill prepared for.
Doing so would lead to a heavily disrupted game that no one would like to watch, not even talking of enjoying. Scores would be rare and far in between.
In a call center environment, this leads to unnecessary load. Load that is caused by re-routing the incident, delays in handovers and resolution, and ultimately frustration on both ends: The end user and the service agent.
In brief, it is causing a poor customer experience, following another poor experience.
There must be a better way.
And there is.
Back to our in-app support world.
Why not using the incident itself to automatically identifying the right queue and smartly routing it there? This is like the soccer players using the ball’s momentum and the given situation to proceed to score.
There are two basic possibilities to achieve this smart routing. One I would name the classic approach, the other one the text mining approach.

The Classic Approach

Automatic routing to the right queue can easily be achieved by using metadata that is provided by the app as part of the incident report. Incidents are tagged based on this metadata. The tags are used to route the incident to an appropriate queue or agent. A configurable automation does both, tagging and routing, without explicit intervention of the app user, who is already in distress enough as there is an issue that he or she couldn’t resolve.
This is a proven approach that requires an elaborate design of metadata and its collection within the app and the ability to build rule sets on top of this metadata in the service back end.
With sufficient data and advanced analytics tools this approach can also be used to offer pre-emptive support, which further improves the customer experience by avoiding the negative experience in the first instance.
This approach, however, finds its limits in the ability of instrumenting an app so that enough situations can be identified from the metadata for appropriate tagging. Not in the least because instrumenting has an adverse effect on the app.

The Text Mining Approach

With more and more service center software running in the cloud, massive improvements in AI, Natural Language Understanding (NLU) and machine learning technologies, additional information can be used: The description that gets submitted by the user as part of the incident report.
Albeit the users do not always provide accurate information, this is regularly enough to augment and improve the tagging, therefore getting a better routing and ultimately faster resolution.
Given that in many systems the first line service agents can resolve incidents by themselves consulting a knowledge base the AI might be able to resolve the issue before escalating it to an agent.

Smart Routing is the Future

This paves the way. Currently leading systems smartly queue and route incidents based upon an elaborate architecture of metadata and tags that are automatically given based upon the metadata. This already tremendously helps companies in providing good service.
The next step is including the descriptions given by the users into the mix and to use it to suggest solutions to agents until confidence is high enough to have the software independently suggest solutions to the users or to route the incidents. NLU in combination with machine learning / deep learning are nearly at this stage.
In either case, smart routing is reducing the friction in the support process and therefore improving customer- and service agent experience. The result of this concentration on positive experience is a measurable benefit for the business – because of adding value for the customer.


Comments

Last Year's Top 5 Popular Posts

SAP CRM for S/4HANA - News from the Customer Frontier

It has been a little more than half a year now that I didn’t update on what is going on with SAP CRM and S/4HANA (which I will refer to as S/4 from now on; SAP it is time for you to change the unwieldy name to something more manageable). What Happened – So FarAs you are well aware SAP is working on integrating a simplified version of SAP CRM into S4. The original roadmap offered a first customer release of an integrated product in early 2018, based on the September 2017 release of S4. The integration was planned as an add-on to S4. The initial scope of this CRM add on for S/4 was supposed to cover what is referred to as ‘core service’ functionality. This initial release shall be followed by ‘core sales’ functionality later in 2018. 2019 then is supposed to be dedicated to another round-off release covering further sales and service functionality, including loyalty management and migration tools. Roadmap and statements also so far have been fairly fuzzy about the strategic distinction b…

More Nimble News

The NewsIn the past 5 weeks or so, there have been quite a few news items about Nimble, with the biggest product news dated September 28 and the most interesting business development dated October 11. The headlines include Nimble’s deeper collaboration with Microsoft and its channel partners, as well as product innovations intended to increase the value delivered to Office 365- and G Suite users. In particular, Nimble: ·Now integrates with Circleback, an AI-powered contact capture and cleaning tool as well as their business card scanner. Nimble is now able to extract high quality contact information from email signatures and to add it to the Nimble contact record. This way it becomes easier to keep contact information current. ·Has partnered with NeoCloud. NeoCloud is a managed cloud services company that deploys and manages Office 365. The company now bundles Nimble into all its Office 365 deals and thus offers business applications on top of its infrastructure- and productivity-focused…

Oracle Ups The Ante - Does the Salesforce Empire Strike Back?

The fall conference season is in full swing. Of the big 4 we had Oracle Open World and the SAP Hybris Summit, with Dreamforce, SAPPHIRE, and Microsoft Connect() still to come. I have covered the SAP Hybris Summit, so do not need to say much about it anymore. The event was short on great announcements – maybe they will come at SAPPHIRE – but certainly contributed to showing the clear vision forward that SAP has. And it is a compelling and consistent vision. OOW 17 was a different beast, most notably with the announcement of Oracle 18c. A year ago Oracle took Amazon full on, declaring it enemy number 1. Many analysts, including myself, were confused about this. Why Amazon and not Microsoft? After all Microsoft is the company that has a very credible IaaS, PaaS, and SaaS. Add the operating system and productivity software and you have a company with a formidable software stack that can be on the winning side of a Clash of Titans. While CTO Larry Ellison still took pot shots at Amazon in his …

SAP CRM into S/4HANA - Did SAP Hit Bulls Eye?

After having talked with Volker Hildebrand about the future of SAP CRM and whether or not there will be a CRM component in S/4HANA at CRM evolution 2017 I now had the chance to follow up with some folks back at SAP in Walldorf. A little RecapVolker told me that, unsurprisingly, SAP is working actively on adding CRM functionality into S/4HANA. In fact, they are merging SAP CRM into it. This is in my eyes meanwhile also the preferred of the two possible options; the other one would be marrying SAP Hybris C4C into S/4HANA. This is the approach which I originally preferred as it would lead to a cleaner code base. I changed my mind, putting customer friendliness reasons over technological cleanliness. The main advantages of merging SAP CRM into S4/HANA over SAP Hybris C4C are that this approach a)Opens a future roadmap for current SAP CRM customers that stretches beyond 2025. These customers else are at risk of defecting. b)Provides the continued chance for customers to run their SAP instance…

Clari - Nipping at Salesforce's Heels?