
April 1999
Keeping The Machine Humming
BY MICHAEL LEVINGER
Companies are increasingly relying on complex, geographically dispersed call centers to
deliver the superior customer service today's markets demand. These centers succeed in
part through the use of state-of-the-art call center and enterprise customer management
(ECM) systems. ECM systems provide tremendous benefits to companies, such as one-to-one
marketing, more personalized service, and reduced customer churn (see
sidebar). But they also create a new set of challenges, one of which is to realize the
intended benefits of ECM while maintaining the technical support and operations necessary
to keep the systems running.
ECM systems consist of many components, including sophisticated routing tools,
client/server customer information systems, and Web sites. Call centers rely heavily on
computer telephony integration (CTI) systems to unify data networks, computers, and
telephony systems. CTI systems are especially difficult to support because they are often
integrated with enterprise applications such as legacy and enterprise resource planning
(ERP) systems. If the ECM system fails, a chain reaction can result in availability
problems with these other important systems.
Successful ECM system support is difficult. Maintenance and enhancements to ECM systems
must respond to business and user requirements, and they must be implemented in a way that
minimizes downtime and disruptions. When problems do arise, support staff must diagnose
and resolve them fast, often on a 24-hour basis, which requires the availability of a wide
range of skills, including knowledge of voice and data systems, CTI, and customer
management systems.
Faced with this complex environment, organizations must decide if they can handle
support in-house or if they should outsource it to third parties experienced in supporting
complex, multi-vendor environments. Regardless of the path a company chooses, however, it
needs the right staff levels and skills, experience supporting multi-vendor environments,
strong product vendor relationships, and a sophisticated change management policy.
SUPPORT STAFF: HOW MUCH IS ENOUGH?
Whether outsourced or in-house, cost-effectively maintaining adequate technical support
staffing is tricky. Not only do companies need to have enough support staff on hand, they
need to ensure staff members have the right skill levels to deal with problems in a
multi-vendor environment. A company may need skills in dozens of different technologies to
maintain its ECM system.
Companies also have peaks and valleys when it comes to skill needs. When a company
installs a new version of a software application, for example, it has a high need for a
particular skill set. When the application is stable, there is less of a need for those
skills. This creates complications when deciding where to set staffing levels. Staffing to
accommodate the peaks will cost a lot, while staffing only to accommodate the lows runs
the risk of extended downtime.
A company may need an expert in telephone switches, for example, only 15 percent of the
time. What do they do with that person the rest of the time? This person will most likely
be assigned to other projects, which means they won't stay focused on their original area
of expertise. Their skills may suffer, and when they are needed, the other projects may
impinge on their time.
One solution is to outsource some of the support skills needed. By partnering with a
third party, companies can share the skills of people who are intimately knowledgeable
about the technology without having to pay for dedicated support staff members.
Regardless of whether companies outsource their support or keep it in-house, they need
to build a solid knowledge management system that captures essential knowledge and makes
it readily accessible to support staff. As companies build bigger and more complicated ECM
systems, even the most highly skilled and knowledgeable support people can't know
everything. They need libraries of information that make it easy to look up answers and
access information from vendors, as well as information about a company's internal
systems. When they are equipped with the right tools, support staff can more easily solve
even the most complex problems.
PROBLEM IDENTIFICATION AND RESOLUTION
Once staffing is resolved, the next challenge is to accurately identify the cause of any
problems and apply a solution. Because ECM systems are highly integrated technologies, it
can be difficult to determine where the real problem lies and which vendor can help solve
it.
Consider this analogy: You have a car where different companies manufacture the engine,
transmission, and instrument panel. Suddenly, a red light on the instrument panel goes on,
telling you there's a problem with the engine. Who do you call to fix the problem? The
instrument panel manufacturer because the light is on? The engine company because the
light indicates a problem with that component? Or is the transmission causing a problem
with the engine, in which case you would call the transmission company. If you don't have
the right knowledge, it would be difficult to know who to turn to. When you finally decide
to call one company, it may claim the problem lies with one of the other manufacturers,
not with its product.
The same thing happens with ECM systems. Just because one part is failing doesn't mean
it is the real cause of the problem - it might just be a symptom. CTI systems are
particularly difficult to fix, for example, because they are inherently a point of
integration for all the pieces. When there is a problem, it isn't necessarily with the CTI
system. Calling the CTI vendor for help might be fruitless if the problem lies elsewhere.
This issue hearkens back to staffing. To successfully identify and resolve ECM
problems, companies need individuals cross-trained about the many components of the ECM
system. Staff with the right knowledge management tools can follow the path of a problem
across a company's different technology components. Once they find the problem, they can
then determine which vendor to call for help.
Of course, vendor relationship management is also important. Before a company rolls out
a new system or piece of software, support people need to build a relationship with the
vendor and clarify how the company is managing the multi-vendor environment. If the vendor
knows the support staff is knowledgeable about its products and how they interact with
other products, the vendor will be more eager to help and less likely to ignore the call
or blame the problem on another vendor's product. It is also important to have clear-cut
service level agreements (SLAs) to ensure the vendor provides the service it has agreed to
in writing.
MANAGING CHANGE
Another support challenge in supporting complex ECM systems is managing configuration and
change. Because the component systems of an ECM solution are so intertwined, changing one
part can have a significant impact on another. The goal of an ECM system is to improve
customer relationships. But if the system is regularly crashing because of tweaking and
fine tuning, that goal is hard to achieve. Key to successful configuration and change
management is knowledgeable staff, well-defined processes, and management focus and
commitment to following the processes.
A formal configuration and change management process ensures that the benefits of
changes outweigh the costs. Formal processes compel support and maintenance staff to look
at every possible area of impact and to run the appropriate tests to be sure that the
changes won't cause costly problems. Also, it is critical that upper management support a
company's change management processes and enforce the use of formal processes throughout
the organization. A lack of such commitment defeats the purpose of having the processes in
the first place.
BRINGING IN A THIRD PARTY
After reviewing the challenges of supporting complex ECM systems, some organizations may
choose to outsource some or all of their support to third-party vendors. Outsourcing
provides skilled staff when a company needs it. Because support is their specialty,
third-party support vendors also have strong relationships with hardware and software
vendors, making it easier for them to get cooperation from these companies when problems
occur.
There are several issues companies should consider before farming out their support.
First is cost. Don't count on saving money. In fact, it could be more expensive to
outsource support than to keep it in-house. But companies will make up for the cost in the
quality of support they receive. Companies must decide on their support goal: is it just
to drive costs down, or do they want to have the best possible quality?
Another issue is loss of self-reliance. Many companies feel that outsourcing support of
mission-critical applications erodes their self-reliance. This is a valid concern. If for
some reason the third-party support staff fails to provide support - or worse, goes out of
business - a company could be left without the proper knowledge and skills to support its
key systems. To reduce this risk, companies may choose to outsource only a portion of
their support, or they might share support tasks with a third party so they can
cost-effectively maintain the knowledge in-house. Of course, companies should seek vendors
who are experienced in ECM systems and who are committed to supporting these systems.
Third party considerations
There are several key services companies should look for when signing a contract with a
third-party support organization:
- Availability, as required: 24x7 or 8x5.
- Appropriate coverage of their locations and ECM components.
- Handling inbound product question calls.
- Managing problem resolution and bug fixing.
- Commitment to SLAs based on problem severity, time of day, and day of week.
- Regular status and call prevention reviews.
- Regular call activity summaries.
A BALANCING ACT
Complex ECM support presents many challenges for today's service organizations. To be
successful in handling these challenges, companies need to take a balanced approach that
includes in-house and outsourced technical support staff, knowledge bases that arm support
staff with the information they need, and change management processes that help companies
realize benefits from the changes they implement. With all of these components in place,
support becomes less daunting, and once the support pieces fall into place, it is much
easier for organizations to keep the ECM machine humming and keep customers satisfied.
Michael Levinger is senior vice president of Technology Solutions Company.
Technology Solutions Company (TSC) is a leading international consulting and systems
integration firm. For more information, please visit their Web site at www.techsol.com.
|