What Kanban can do for Call Centre Response Times

When a Toyota industrial engineer named Taiichi Ohno was investigating ways to optimise production material stocks in 1953, it struck him that supermarkets already had the key. Their customers purchased food and groceries on a just-in-time basis, because they trusted continuity of supply. This enabled stores to predict demand, and ensure their suppliers kept the shelves full.

The Kanban system that Taiichi Ohno implemented included a labelling system. His Kanban tickets recorded details of the factory order, the delivery destination, and the process intended for the materials. Since then, Ohno?s system has helped in many other applications, especially where customer demand may be unpredictable.

Optimising Workflow in Call Centres
Optimising workflow in call centres involves aiming to have an agent pick up an incoming call within a few rings and deal with it effectively. Were this to be the case we would truly have a just-in-time business, in which operators arrived and left their stations according to customer demand. For this to be possible, we would need to standardise performance across the call centre team. Moving optimistically in that direction we would should do these three things:

  • Make our call centre operation nimble
  • Reduce the average time to handle calls
  • Decide an average time to answer callers

When we have done that, we are in a position to apply these norms to fluctuating call frequencies, and introduce ?kanbanned? call centre operators.

Making Call Centre Operations Nimble
The best place to start is to ask the operators and support staff what they think. Back in the 1960?s Robert Townsend of Avis Cars famously said, ?ask the people ? they know where the wheels are squeaking? and that is as true as ever.

  1. Begin by asking technical support about downtime frequencies, duration, and causes. Given the cost of labour and frustrated callers, we should have the fastest and most reliable telecoms and computer equipment we can find.
  1. Then invest in training and retraining operators, and making sure the pop-up screens are valuable, valid, and useful. They cannot do their job without this information, and it must be at least as tech-savvy as their average callers are.
  1. Finally, spruce up the call centre with more than a lick of paint to awaken a sense of enthusiasm and pride. Find time for occasional team builds and fun during breaks. Tele-operators have a difficult job. Make theirs fun!

Reducing Average Time to Handle Calls
Average length of contact is probably our most important metric. We should beware of shortening this at the cost of quality of interaction. To calculate it, use this formula:

Total Work Time + Total Hold Time + Total Post Call Time

Divided By

Total Calls Handled in that Period

Share recordings of great calls that highlight how your best operators work. Encourage role-play during training sessions so people learn by doing. Publish your average call-handling time statistics. Encourage individual operators to track how they are doing against these numbers. Make sure your customer information is up to date. While they must confirm core data, limit this so your operators can get down to their job sooner.

Decide a Target Time to Answer Calls
You should know what is possible in a matter of a few weeks. Do not attempt to go too tight on this one. It is better to build in say 10% slack that you can always trim in future. Once you have decided this, you can implement your Kanban system.

Introducing Kanban in Your Call Centre Operation
Monitor your rate of incoming calls through your contact centre, and adjust your operator-demand metric on an ongoing basis. Use this to calculate your over / under demand factor. Every operator should know the value on this Kanban ticket. It will tell them whether to speed up a little, or slow down a bit so they deliver the effort the call rate demands. It will also advise the supervisor when to call up reserves.

Contact Us

  • (+353)(0)1-443-3807 – IRL
  • (+44)(0)20-7193-9751 – UK

Check our similar posts

Energy efficiency demystified

Energy bills are all about Energy efficiency but energy efficiency management is not all about bills. Energy efficiency means reducing carbon emissions, lowering energy costs and improving the quality of life. Energy efficiency is therefore about conservation of energy in a broader perspective; in fact energy efficiency is almost becoming a moral obligation.

Through adoption of appropriate energy efficiency measures, companies can significantly bring down the overhead costs making hundreds of dollars in savings. Energy efficiency is also synonymous with a better quality of life. Taking appropriate measures to ensure proper insulation protects your premises against extreme weather conditions leading to more productivity and an improvement in the bottom line.

Improved energy efficiency means a smaller amount of carbon emissions, less pollution and a better environment.

It is now easier than ever to visually identify where your facility is wasting energy, how much energy is being wasted while tracking the progress made in reducing energy consumption by turning that detailed, raw energy-consumption data into useful charts and figures.

Having visibility of your Energy usage gives you knowledge of what power you are consuming. This helps you change energy usage behaviours and this can have significant savings and reduction in your electricity bills. Real-time electricity consumption tracking is enough prodding for you to be on the lookout for inefficient energy consumption unit’s e.g.? Heating and cooling equipment, ducts insulation of your premises or a failure of one of these components to perform as intended. Pin-pointing the problem areas is not a walk in the park but fixing it can make your building more energy-efficient and comfortable.

A wide range of solutions are now available for charting and analysing energy consumption that helps energy managers, facilities managers, energy consultants and building-services engineers. These will not only offer advice but will enable you provide tailor made solutions for your organisation by assisting you in developing a sustainable energy strategy. Our energy monitoring software is one example.?

Network Security

The easiest way for an external threat to get to your private data is through your network. The easiest way to eliminate that threat? Get your data out of the network. Of course, we know you wouldn’t want to do that. We also know that while you may want to sniff every packet for anything suspicious, you wouldn’t want your network to crawl either.

That’s why we’re offering to put up the most efficient checkpoints on every route that leads into and out of your system.

So what can you expect from our brand of network security?

  • Review of your policies and processes for weaknesses – If we see a loophole, we’ll recommend modifications wherever necessary.
  • Protection for your applications and infrastructure – Since we’re familiar with both software and hardware-based protection systems, we can recommend which type is best suited for your setup.
  • Automated identification of business and mission critical applications – They’ll be given priority in your network to ensure bandwidth allocation is optimised.
  • Automated network audits and vulnerability management – Tired of getting prompted by pesky vulnerability notices and don’t know what to do with them? Well, that’s why we’re here.
  • Customisable security reports that contain only relevant and accurate data.

We can also help you with the following:

Becoming Nimble the Agile Project Management Way

In dictionary terms, ?agile? means ?able to move quickly and easily?. In project management terms, the definition is ?project management characterized by division of tasks into short work phases called ?sprints?, with frequent reassessments and adaptation of plans?. This technique is popular in software development but is also useful when rolling out other projects.

Managing the Seven Agile Development Phases

  • Stage 1: Vision. Define the software product in terms of how it will support the company vision and strategy, and what value it will provide the user. Customer satisfaction is of paramount value including accommodating user requirement changes.
  • Stage 2: Product Roadmap. Appoint a product owner responsible for liaising with the customer, business stakeholders and the development team. Task the owner with writing a high-level product description, creating a loose time frame and estimating effort for each phase.
  • Stage 3: Release Plan. Agile always looks ahead towards the benefits that will flow. Once agreed, the Product Road-map becomes the target deadline for delivery. With Vision, Road Map and Release Plan in place the next stage is to divide the project into manageable chunks, which may be parallel or serial.
  • Stage 4: Sprint Plans. Manage each of these phases as individual ?sprints?, with emphasis on speed and meeting targets. Before the development team starts working, make sure it agrees a common goal, identifies requirements and lists the tasks it will perform.
  • Stage 5: Daily Meetings. Meet with the development team each morning for a 15-minute review. Discuss what happened yesterday, identify and celebrate progress, and find a way to resolve or work around roadblocks. The goal is to get to alpha phase quickly. Nice-to-haves can be part of subsequent upgrades.
  • Stage 6: Sprint Review. When the phase of the project is complete, facilitate a sprint review with the team to confirm this. Invite the customer, business stakeholders and development team to a presentation where you demonstrate the project/ project phase that is implemented.
  • Stage 7: Sprint Retrospective. Call the team together again (the next day if possible) for a project review to discuss lessons learned. Focus on achievements and how to do even better next time. Document and implement process changes.

The Seven Agile Development Phases ? Conclusions and Thoughts

The Agile method is an excellent way of motivating project teams, achieving goals and building result-based communities. It is however, not a static system. The product owner must conduct regular, separate reviews with the customer too.

Ready to work with Denizon?