Bookmark and Share

Tuesday, 27 April 2010

Mondial Assurance – extending CTI for agents

Today we’ve announced that Corizon has been chosen by Mondial UK to simplify its agent desktops. To quote from the press release
The new solution will combine Mondial’s established desktop applications with its Cisco Agent Desktop infrastructure to create a simple set of screens that are easy to use, and crucially minimise the time to identify, validate and record customer interactions.... It will optimise and automate the process of entering customer information, increasing efficiency and providing a quicker service for the customer.
Apart from providing another proof point of the ROI on streamlining agent desktops, a couple of things seem to me to interesting about this solution
- It provides a great example of one of the “mashup patterns” we described a while ago in this blog – “Extending interaction management and CTI applications” in this case integrating the Cisco Agent Desktop
- It shows the versatility of mashups by being able to integrate desktop applications as well as web applications and web services

Labels: , , , , ,


Friday, 5 February 2010

The Agent Desktop – the elephant in the contact centre?

A recent paper from Gartner (Top Business Processes for Customer Service, 2010 to 2012 - subscription required) about customer service process priorities adds to my impression that the agent desktop - and in particular the complexities of using the applications on it - is in danger of being the “elephant in the room” when improving service delivery in the contact centre.


The report discusses the process improvement priorities for customer service, looking at problem resolution, feedback management, workforce optimization and field service processes. Within the first category it examines agent facilitated, self service and collaborative problem resolution. As it suggests, it is essential – in both financial and customer experience terms- to move as much interaction as possible to the self service and social arenas. However, most organizations will still need high quality agent facilitated support, either because of the complexity of the issue or because of customer preference.


In this arena it cites a familiar set of challenges
  • Problem definition and understanding — both by the customer and the agent
  • Process handoff steps, both intra- and inter-departmental within the organization
  • Transfer of customer from one department to another, or transferring from one channel to another
  • Ability to resolve the problem for the customer
  • Cost to the organization of resolving the problem for the customer
  • Time to resolve the issue for the customer
  • Keeping the customer informed of the status of the issue resolution
  • Tracking inquires linked to the same issues over multiple contacts



I completely agree that the technologies cited as relevant to addressing these challenges - Call handling and case management, trouble ticketing, training, knowledge management, cobrowsing, automated call distribution (ACD), call recording and workforce optimization – are important. When it comes to the “moment of truth” and the customer is on the phone, the only thing that really matters is “do I have access to the knowledge, information and tools needed to fix the problem?”. And for most agents this all comes via the desktop, which will typically be cluttered with CRM, KM, trouble ticketing, case management etc as well as a set of operational applications such as billing, tests, returns management, field service bookings, logistics, order management and diagnostics. So we have all this investment in systems to help the agent, but then deliver them through an unusable clutter that frequently undermines the bigger strategic objective.


Like the proverbial elephant, this rarely gets mentioned, even though it’s a fundamental determinant of the agent’s performance and hence customer service. I can think of a few possible reasons
  • We are conditioned to having to work this way
  • Technologies that have offered a solution have failed, reinforcing acceptance
  • “The agents can manage” so we can act like it doesn't matter

This elephant needs to be sent on its way if the challenges are to be met. We need to give the agents the right tools, not handicap them with horrendous desktops. Why do you think we tolerate his presence?

Labels: , , , ,


Monday, 21 December 2009

Corizon introduction video

We've created a new video that provides an introduction to Corizon enterprise mashups and their use.

Please check it out and let us know what you think.






Labels: , , , , ,


Friday, 11 December 2009

Recognition

It’s always good to be recognized, and Corizon’s inclusion in the top 10 Contact Center Technologies from Call Center Helper magazine is great feedback directly from the market. It is especially significant when you remember how varied and complex the contact center technology industry is.

This provides another piece of tangible evidence of two changes that we’ve been seeing all year:
  • Fixing the desktop has continued to move towards the top the call center priority list as it is becoming recognised as a critical factor in many productivity and customer experience delivery issues
  • Enterprise mashups have jumped from “is that a serious business tool for important operational applications?” to being a recognized approach that is seen as a very effective way to integrate applications for people
It’s also testament to the great job that our partners, consultants and engineers do in creating implementations that make a significant difference to the work of contact center agents.

So, thanks to those who voted for us; for those who didn’t, we have plenty of ideas about how to change that in 2010!

Labels: , , ,


Friday, 27 November 2009

The futility of call centre coaching (or why not every attempt to cure the same symptoms is equal)

The first part of the title isn’t original, but it’s certainly attention grabbing! It comes from an article by Denis Adsit. Apart from its title, I found it interesting because it has implications for the choices that call centre managers have to make when they are looking to improve performance. Anybody wanting to improve call handling time or first call resolution (to take but two common measures) is confronted by a wide range of options - all offering the same results – so it’s not easy to know where to attack.
There’s a fair bit of maths in the article, but the discussion makes the situation clear without worrying about that too much! The point is not that training or coaching are inherently bad, it’s just that they are never ending activities that are constantly diluted by agent turnover:
The conclusion … is that coaching in systems with a broad mix of tenure and even a modest level of turnover will have little effect on the performance of the entire system. To improve the outputs of a system, managers must find an approach to process improvement which lifts the performance of all the agents at the same time, not one at a time.
So, everything else being equal, it’s better to improve processes and systems that affect the whole agent population than to focus on activities that address agent (or presumably customer) problems one at a time. The effectiveness of the desktop is perhaps the prime example of the former. It is a key determinant of how easy / hard it is to get up to speed and perform effectively as an agent. Until recently, the problems of integrating applications for people has meant that everything else has been far from equal in the area of desktop streamlining, and a fear of high risks, costs and slow projects have stood in the way of improvement. This might perhaps explain the variety of other approaches (even if they are “futile”!!) , and indicates the size of the opportunity that exists with modern, pragmatic enterprise mashup technologies

Labels: , , , , ,


Tuesday, 20 October 2009

Why are contact centre desktops so broken?

My colleague, Toby Baker has created this guest posting based on his observations from working with Corizon's customers and partners applying enterprise mashups to integration problems in contact centres.

I spend a lot of time in contact centres, analyzing applications in use on the desktop, and see the same challenges and issues again and again. This is my top ten:
  1. Too many applications, each with their own login, UI and screen layout
  2. Applications that time out when they are used, forcing another login
  3. Applications with too many screens, each in a tab, sub-tab or sub-sub-tab
  4. Applications that require way too many clicks to get the job done
  5. Applications that show you the customer name on the first screen, only to not show it on all subsequent screens, forcing the user to write it down on paper
  6. Applications that perform so badly the agent has to become an expert in ad-libbing
  7. Screens where the information is way down below the bottom of the screen, or all the way across to the right
  8. Screens that are so crowded with information, it’s hard to pick out what you need
  9. Screens that are so visually unappealing it makes them hard to use
  10. “Customer Records” that are split across many applications and so require a large amount of copy/alt-tab/paste to see the whole picture
Everyone knows that a unified desktop is a good idea, and fixing the ten problems above is a good thing. So why is it so hard to do? Let’s look at the problem in more detail:

First of all, the applications - why are there so many of them?
  1. Companies merge, acquire and get acquired. Technology stacks don’t get integrated quickly, or at all.
  2. Core CRM applications have huge programmes associated with them to implement front- and back-end CRM processes. It takes years to get round to doing “the other apps” so we end up with original apps as well as a new CRM front end.
  3. To stay ahead of the competition, enterprises launch new products and services before the core applications can really support them, so new applications are built.
  4. Agents build their own applications to help navigate through the complex desktop. These are known as “Shadow IT” or “Guerrilla” applications.
  5. Technology is “improving” all the time. There are new widgets and frameworks and standards and approaches that IT tries to keep up with.
Secondly, why is the data all over the place? Why is the thing that I want buried deep, across multiple screens or a few scrolls away? Why are apps so hard to use?
  1. Databases organize information in a way that works for databases. Customers have orders, addresses, contact details. Orders have statuses, products, dates. Products have prices, catalogue entries. All too often, applications use the structure of the database to drive the structure of the screens. Mostly, users don’t look at information in the same way as computers, and nor do customers when they are asking for it.
  2. The tools used to create applications make it easy to use the data layout to drive the screen layout.
  3. Tabs, tabs, tabs. It seems like the right way to organize information, but demands change, so it rapidly becomes the wrong way to organize information.
  4. It’s sometimes easier to add something to a screen than it is to create a new screen. You then get a crowded screen with loads of unnecessary fields on it.
  5. The people designing the applications understand about data. The people who use the applications understand about the servicing of customers and their products. There is a mis-match here!
  6. The people building applications don’t sit down with call centre advisors enough. If they did, they would not build apps in the way that they do!

Thirdly, why do I have to look in lots of places? Why aren’t the sequences of activities I need to go through - the "user processes" - catered for?
  1. User processes change faster than apps do. Customer service organizations manage sales processes, retention processes, diagnostic and fix processes. They need to learn based on what works and what does not work. They need respond to market conditions, competition, regulations. Importantly, they need to do this without changing systems. Unfortunately, as user processes are all too often wired in to applications (or on paper), this is too hard to do.
  2. Sometimes it’s easier to create a new application than modify an existing one.
  3. “One size fits all” does not work in a customer service organization where you have a variation in process across each user group. Maybe you have retention, inbound, outbound, first line and second line. Maybe you have organized teams based on product specialty. Either way, using traditional development techniques, it’s almost impossible – or very costly – to create applications that are tailored to the needs of each user group.

Any more thoughts? Please leave a comment. Toby will be back with more on addressing these problems in a future blog.

Labels: , , , , ,


Thursday, 8 October 2009

The contact centre dilemna

Recent studies have highlighted the current dilemma most companies have with contact centres: they are both critical in maximising customer value and considered poor in meeting customer expectations. A YouGov survey conducted in the UK showed that phone and email were by a significant margin the most likely channels used by customers to contact a company for customer service (75% and 70% respectively). Self service comes third with 43%. At the same time, consumers were unhappy with the quality of service provided: 83% were frustrated with the interaction and 60% of agents agreed with them!

This matters enormously because “on average, 40% of customers who suffer through bad experiences stop doing business with the offending company” according to a recent survey published in the Harvard Business Review by Dave Dougherty and Ajay Murthy from Convergys. They go on to define the same reasons for the frustration as identified in the YouGov survey: lack of knowledge of the agent and incapacity to resolve the query on the first call. With increasing access to relevant information online through the internet and social networks, I expect customers to become more and more demanding of the contact centre agent in the future. With the simpler queries being increasingly resolved thorugh self-serivice, interactions will become more complex and more critical and the cost of failure will increase.

So what stops contact centres providing the right customer interaction? The main reason is the proliferation of applications on the desktop. The Corizon Contact Centre survey of 90 Contact Centre Managers shows that agents have to use on average 5 different applications during a call. It is not uncommon to find more than 20 on each desktop. In such an environment, it is proving very difficult to provide to the agent, cost effectively, the right information at the right time and, crucially, the tools that allow them to resolve the query in a fast and efficient way and stop customers needing to call back.

Fixing this problem has proved very difficult as demonstrated by the generations of legacy applications one can find by walking in a contact centres, from ancient green screen applications to the most recent CRM systems. Resolving this issue cost effectively requires a new approach. This is where process mashups come in. They deliver a step change in agent productivity by providing a dynamic UI that guides the process and gives agents the right information at the right time. Agent desktops can be integrated using a step by step approach, fixing the most broken processes first and delivering immediate improvement. The process mashup approach enables the easy creation of fit for purpose desktops, changing the economics of integrating applications for people by extracting “mashable” components from existing systems to deliver an initial solution in days. Once initial process hotspots have been fixed the business can iteratively work towards delivering the ‘perfect’ application for the contact centre agent that can constantly evolve with the business needs, all within a governed and secure IT infrastructure.

Labels: , , , , ,


Friday, 7 August 2009

How do contact centres adapt to the Big Shift?

I have just experienced two very different contact centre interactions. In the first, the contact centre agent was able to address my questions and resolve my issue in a personable dialogue, making decisions along the way and accessing information easily and rapidly to make these decisions. The result was successful and my perception of the company enhanced. In fact, this was a better experience than resolving the same issue online. I can clearly see how this contact centre could engage in social CRM and graduate to a two way relationships world, interacting on multiple platforms.

In the second experience, with a different company, the agent followed an inflexible script in an impersonal manner and was unable to resolve the query (systems too slow, needed to swivel between several applications, and ultimately the key data required was on a system the agent did not have access to). The result was a highly frustrating experience and need for a second call. Argh...

These two experiences made me realise how tough the job of a contact centre agent is. On very little pay and in a pressurised environment, these guys deal day in day out with often angry customers and are supposed to resolve all their issues rapidly and pleasantly. And we are increasingly expecting more from them: issues are getting more difficult to resolve because the simpler tasks are now done online, we expect a higher standard of service from the agent because we get already so much from self-service, and finally we expect them to make decisions there and then. In some industries, contact centre interactions are becoming a key driver of customer churn.

I can only see this trend accelerating. Younger generations are not willing to deal with companies in one way, push type relationships. They expect two-way relationships across multiple platforms where they take control of the relationship with the brand. This will put even more responsibility on contact centres agents and will fundamentally alter the role of the contact centre:

1. Contact centre agents’ value will increase as they to take on greater responsibilities and capacity to make decisions. Talent retention will become more important, compensation will increase and the role will shift from transaction to relationship management;

2. The contact centre itself will become a strategic asset essential for customer relationships. Investment decisions will shift from minimizing costs of interaction to maximising interaction value;

3. Off shoring decisions will need to include whether the processes and/or customer interactions require complex interactions where local knowledge is important to build the customer relationship;

4. Systems supporting contact centres will need to be more integrated (social media, self-service etc.) to enable support of customer interactions across platforms and at different steps of the interaction process (e.g. interaction initiated in self-service and completed with an agent);

5. Flexible, dynamic and user centric systems will become essential to ensure fit for purpose IT that empowers agents to do their jobs in ever changing environment.

I believe this is part of the Big Shift described by John Hagel in his latest blog. In a further blog, I will develop our thoughts on the implications of this type of shift for organizations processes and supporting IT systems. But first off on holidays!

Labels: , , ,