The Hotline Magazine
No Churn - SaaS / Cloud Retention and Revenue Service
Customer Success Management Research
Contact Center Management Technology

Wednesday May 22, 2013





Page Two

Subscribe / RSS




Related Materials
Below Are Excerpts From Articles Related To The One You Are Now Viewing

SaaS/Cloud & Support: The Strategic Key

A customer support contact center is a knowledge inventory operation, and its process is very mathematical. The speed of response to incoming requests is determined by the average duration of the interaction, the volume of requests and the number of available, trained staff members. Customers want fast, courteous response and complete resolution, while the provider struggles to meet those expectations and the cost of the required resources. In a previous Briefing, I outlined some of the standard

More on page 47

Staffing Levels for Customer Success Management Groups

A common question keeps coming up in my conversations with SaaS/Cloud CxO’s all across the industry:  “How many Customer Success Managers does it take to keep customers from churning?”  The question appears in other forms, such as “how much CMRR (Contracted Monthly Recurring Revenue) should each CSM be responsible for?”  Or, “How many customer accounts can a CSM handle?”  Staffing level is a near universal challenge in the CSM profession.   But before staffing can be authentically evaluated for

More on page 3986

Benchmarks: Be Careful What You Ask For…

My new client proudly proclaimed that the FCCR (First Call Resolution Rate) for their customer contact center was well over 90%. Benchmarked against other software support centers, the operation was clearly a stunning success, and the senior executive had been invited to discuss his "secret sauce" at an upcoming professional convention's plenary session. Unfortunately, the metric wasn't quite telling the truth, as I discovered after a hour of observation and a quick querying of the database. The

More on page 29

The Customer Contact Center Training Inventory Costs

Traditionally, technology companies have often used their customer contact centers as an entry-level proving ground. The operational pattern is to hire young people as cheaply as possible, toss them to the phone lions and then transfer those that manage to survive and show some promise into "real" jobs elsewhere in the company. There are two costly effects of this strategy that don't appear on the financial statements, but are nonetheless damaging to the company's long term profitability. The fi

More on page 51

SaaS/Cloud & Support: A Competitive Advantage

I've had discussions with many senior executives over the years about the potential of using Customer Support quality as a competitive advantage. It has a nice ring to it, and in theory, sounds good. Here's an example one executive gave me. The sales rep for XYZ Corp., an enterprise software manufacturer, began the meeting with the prospect's senior management team by dialing the speaker phone in the middle of the boardroom table. After hearing the canned greeting and the on hold announcement fo

More on page 48

By Mikael Blaisdell

A company’s customer contact center should be designed, built and managed as a profitable knowledge inventory and distribution operation. One of the first strategic decisions senior management must make is: How fast does the center need to be in order to retain customers and maintain profitability? The decision on Responsiveness will be expressed in a target Service Level that will in turn dictate the staffing level required to consistently achieve that target. Here’s a simplified illustration of how the basic equation works.

The Resource Equation

Center Responsiveness means how fast the staff answers the phone, starts the Chat session or opens the e-mail. The overall technical name for it is the Service Level, expressed as responding to X percent of all incoming requests within Y seconds. (A typical Service Level target is: We will respond to 90% of all incoming requests within 60 seconds.)

The last factor is Staffing, the number of trained agents that are available and ready to immediately respond.

The pyramid in the center is made up of two elements: AHT and Volume. AHT, Average Handle Time, is the length of time it takes to interact with the customer and to complete the case notes after hanging up. Volume is the number of incoming service requests expected within a specific time frame, e.g. between 9 and 9:30 on Monday mornings.

Using the calculator is simple. If you expect 100 service requests between 9 and 9:30 Monday morning, for example, each of which will take an average of 8 minutes to handle, and the company’s desired Service Level is 90% within 60 seconds, the answer would be that about 33 trained agents will be required to meet the target Service Level. You can also use it in reverse; by leaving the service level target blank and entering the number of available agents, the calculator will tell you the best service level you can achieve with those resources.

Management Options

If the cost of maintaining a pool of trained representatives large enough so that 33 could be available at that time is beyond the budget, then Management has three main avenues it can use to address the problem:

Reduce the Average Handle Time:

Measures may be taken to reduce the AHT, the average time it takes to handle a service request, by investing in better tools and/or providing better training for the staff .

Allow a slower level of service

The Responsiveness target can be set higher, accepting that some customers will be unhappy with the slower service level.

Reduce the incoming Volume of requests

Efforts can be made to reduce the incoming Volume, to divert some of those service requests over to the website, and/or fix the bugs in the product so that it doesn’t generate as many calls.

All of these avenues are strategic issues, requiring further decisions to be made by senior management. Each will have implications and effects that can extend beyond the boundaries of the customer contact center. Keep in mind that Responsiveness is only one aspect of customer satisfaction and retention; we’ll discuss the others in subsequent Primer briefings.

Published: May 11, 2007

Revised: October 22, 2012