To accommodate increasing customer demand for company and product information and for quick issue resolution, companies are now considering the benefits of online self-service systems. Knowledge management (KM) software is the key to such systems, as well as to integrating customer relationship management (CRM) and service resolution management (SRM).

For more background, please see Integrating Customer Relationship Management and Service Resolution Management and Knowledge Management: The Core of Service Resolution Management.

Bolstering Call Center (and Other CRM) Processes

The trend of customer service enablement and the nurturing of customer relationships (which have traditionally been the forgotten stepchildren of CRM) may be overtaking customer acquisition as a main driver of recent CRM deployments. Customer service has historically been provided primarily in person or over the telephone, with limited reference materials available for the customer service representative (CSR). This emerging business model assumes that companies that provide customer service over the telephone will find value in aggregating company knowledge by using the appropriate software, and will be willing to access the content over other channels, especially the Internet. The business model also assumes that companies will find value in providing some of their customer service over the Internet instead of by telephone.

In the past, customers would show a preference for a certain channel of communication with a company, but this is no longer the case. Customers now use several different channels available to ask for support and service and about upgrade issues, or to inquire about or request new products and services. And they expect to receive accurate, consistent information, regardless of the channel they are using. Service that does not meet these expectations is considered a waste of time, and a reason for the customer to seek out competitive offerings elsewhere.

The use of multiple channels for customer service and support, as well as the importance of consistent, accurate, and swift answers, is expected to only increase in the future. Companies are thus realizing that what their customers are seeking is knowledge (which is likely stored somewhere in the company, but more likely, scattered all over the company), and that these customers want it regardless of the channel they choose, be it telephone, Web self-service, e-mail, retail kiosk, or chat.

The logical question a company should ask itself is how it can provide customers with direct access to the knowledge they are looking for when that data may be residing in a variety of places. For example, product specifications, technical support, billing questions, and pricing and policy information can all be found in any number of places, such as CRM databases; legacy KM systems; frequently asked questions (FAQ) lists; intranets; content management systems; billing systems; or an automated response system. The goal here is to analyze the customer's problem, retrieve the information needed to solve that problem, and to do so in whichever contact channel the customer chooses. This process should not only minimize customer frustration and lower the cost of the support transaction, but it should also leave the customer delighted.

Although computer-telephony integration (CTI) systems do a great job at automating call routing and case management, web sites have become ever glossier and animated, and CRM systems do a decent job of handling customer contacts (and possibly preferences) and product information, something is still missing to enable cohesive customer service. The plethora of new self-service technologies, such as natural language search engines, knowledge bases, guided navigation, user forums, collaboration, personalization, multichannel (e-mail, instant messenger [IM], integrated voice response [IVR], call centers), and so on, lead us to the emerging part of CRM software applications, specifically applications that enable customer service organizations to more effectively resolve service requests and answer questions.
Built on KM and search technologies, SRM (not to be confused with supplier relationship management) applications optimize the resolution process across multiple service channels, including contact centers, self-service web sites, help desks, e-mail, and chat.

An SRM system creates a knowledge backbone for the seller company by creating a single interface that pulls vital information and knowledge from wherever it is stored, whether it is in the CRM system, legacy support systems, search engine, web site, document libraries, etc. It allows the company, as a business leader, to evaluate what processes are taking place in its support environment and to then determine how it would like those processes to be handled. With this, the company can guide users step by step through the process of answering their questions, applying the right process to each inquiry to drive the outcome it wants.

Service resolution systems enable the company to harness all the tools and knowledge it has already acquired to solve customers' issues, regardless of what channel they use to tell the seller company about their issue. These SRM applications have to complement, integrate with, and enhance traditional CRM areas like sales force automation (SFA), marketing automation, contact center, and help desk applications by providing knowledge-based solutions that improve service delivery. Although still an emerging software category, existing SRM customers include some of the largest companies in the world, and SRM products have reportedly enabled these companies to reduce operating and service delivery costs, improve customer satisfaction, and increase revenues.

Here is an illustration: A service call (customer inquiry, complaint, etc.) comes in, and the agent fields it by performing a search. A technical bulletin, written by a product manager and stored on a network drive, comes up in the query results because the knowledge base searches both structured and unstructured knowledge. This very issue has been documented, and a resolution has been built to ensure that an answer can be provided. A wizard pops up and prompts the technical support agent to walk the customer through a setup process. The new product can then be used successfully, resulting in a happy customer.

This is the type of service the customer wants and what support systems are really trying to provide—seamless service resolution, which can only be provided by effectively using and managing corporate knowledge (i.e., the knowledge of products and services; diagnostic troubleshooting; information stored in all documents on the network drives, intranets, and e-mail systems; and, most important, the knowledge of the customers and support agents).

Trend Analysis

The markets for KM and SRM solutions are still emerging, and it is difficult to predict how large or how quickly they will grow, if at all. Some companies have found that the productivity of customer service personnel initially drops while CSRs are becoming accustomed to using the software.

Self-service can cause conflicts, since it contributes to a general shift of control and resources away from the call center. Also, exposing some information can be risky. For example, logging complaints into the system and then displaying them on the customer portal can cause some users to regard giving out sensitive information as “hanging themselves." Resistance to the software by customer service personnel and inadequate development and maintenance of the system's knowledge resources, business rules, and other configurations have in some cases made it even more difficult to attract new customers and retain old ones.

Competition in the fragmented SRM marketplace is rapidly evolving and intense, and one should expect competition to further intensify in the future as current competitors expand their product offerings and as new competitors enter the market. One should also expect that competition will increase as a result of industry consolidation, which comes from the need for newer models of customer service, in which a single vendor provides solutions for both internal and external service, technical support, and search.

To accommodate increasing customer demand for company and product information and for quick issue resolution, companies are now considering the benefits of online self-service systems. Knowledge management (KM) software is the key to such systems, as well as to integrating customer relationship management (CRM) and service resolution management (SRM).

For more background, please see Integrating Customer Relationship Management and Service Resolution Management and Knowledge Management: The Core of Service Resolution Management.

Bolstering Call Center (and Other CRM) Processes

The trend of customer service enablement and the nurturing of customer relationships (which have traditionally been the forgotten stepchildren of CRM) may be overtaking customer acquisition as a main driver of recent CRM deployments. Customer service has historically been provided primarily in person or over the telephone, with limited reference materials available for the customer service representative (CSR). This emerging business model assumes that companies that provide customer service over the telephone will find value in aggregating company knowledge by using the appropriate software, and will be willing to access the content over other channels, especially the Internet. The business model also assumes that companies will find value in providing some of their customer service over the Internet instead of by telephone.

In the past, customers would show a preference for a certain channel of communication with a company, but this is no longer the case. Customers now use several different channels available to ask for support and service and about upgrade issues, or to inquire about or request new products and services. And they expect to receive accurate, consistent information, regardless of the channel they are using. Service that does not meet these expectations is considered a waste of time, and a reason for the customer to seek out competitive offerings elsewhere.

The use of multiple channels for customer service and support, as well as the importance of consistent, accurate, and swift answers, is expected to only increase in the future. Companies are thus realizing that what their customers are seeking is knowledge (which is likely stored somewhere in the company, but more likely, scattered all over the company), and that these customers want it regardless of the channel they choose, be it telephone, Web self-service, e-mail, retail kiosk, or chat.

The logical question a company should ask itself is how it can provide customers with direct access to the knowledge they are looking for when that data may be residing in a variety of places. For example, product specifications, technical support, billing questions, and pricing and policy information can all be found in any number of places, such as CRM databases; legacy KM systems; frequently asked questions (FAQ) lists; intranets; content management systems; billing systems; or an automated response system. The goal here is to analyze the customer's problem, retrieve the information needed to solve that problem, and to do so in whichever contact channel the customer chooses. This process should not only minimize customer frustration and lower the cost of the support transaction, but it should also leave the customer delighted.

Although computer-telephony integration (CTI) systems do a great job at automating call routing and case management, web sites have become ever glossier and animated, and CRM systems do a decent job of handling customer contacts (and possibly preferences) and product information, something is still missing to enable cohesive customer service. The plethora of new self-service technologies, such as natural language search engines, knowledge bases, guided navigation, user forums, collaboration, personalization, multichannel (e-mail, instant messenger [IM], integrated voice response [IVR], call centers), and so on, lead us to the emerging part of CRM software applications, specifically applications that enable customer service organizations to more effectively resolve service requests and answer questions.
Built on KM and search technologies, SRM (not to be confused with supplier relationship management) applications optimize the resolution process across multiple service channels, including contact centers, self-service web sites, help desks, e-mail, and chat.

An SRM system creates a knowledge backbone for the seller company by creating a single interface that pulls vital information and knowledge from wherever it is stored, whether it is in the CRM system, legacy support systems, search engine, web site, document libraries, etc. It allows the company, as a business leader, to evaluate what processes are taking place in its support environment and to then determine how it would like those processes to be handled. With this, the company can guide users step by step through the process of answering their questions, applying the right process to each inquiry to drive the outcome it wants.

Service resolution systems enable the company to harness all the tools and knowledge it has already acquired to solve customers' issues, regardless of what channel they use to tell the seller company about their issue. These SRM applications have to complement, integrate with, and enhance traditional CRM areas like sales force automation (SFA), marketing automation, contact center, and help desk applications by providing knowledge-based solutions that improve service delivery. Although still an emerging software category, existing SRM customers include some of the largest companies in the world, and SRM products have reportedly enabled these companies to reduce operating and service delivery costs, improve customer satisfaction, and increase revenues.

Here is an illustration: A service call (customer inquiry, complaint, etc.) comes in, and the agent fields it by performing a search. A technical bulletin, written by a product manager and stored on a network drive, comes up in the query results because the knowledge base searches both structured and unstructured knowledge. This very issue has been documented, and a resolution has been built to ensure that an answer can be provided. A wizard pops up and prompts the technical support agent to walk the customer through a setup process. The new product can then be used successfully, resulting in a happy customer.

This is the type of service the customer wants and what support systems are really trying to provide—seamless service resolution, which can only be provided by effectively using and managing corporate knowledge (i.e., the knowledge of products and services; diagnostic troubleshooting; information stored in all documents on the network drives, intranets, and e-mail systems; and, most important, the knowledge of the customers and support agents).

Trend Analysis

The markets for KM and SRM solutions are still emerging, and it is difficult to predict how large or how quickly they will grow, if at all. Some companies have found that the productivity of customer service personnel initially drops while CSRs are becoming accustomed to using the software.

Self-service can cause conflicts, since it contributes to a general shift of control and resources away from the call center. Also, exposing some information can be risky. For example, logging complaints into the system and then displaying them on the customer portal can cause some users to regard giving out sensitive information as “hanging themselves." Resistance to the software by customer service personnel and inadequate development and maintenance of the system's knowledge resources, business rules, and other configurations have in some cases made it even more difficult to attract new customers and retain old ones.

Competition in the fragmented SRM marketplace is rapidly evolving and intense, and one should expect competition to further intensify in the future as current competitors expand their product offerings and as new competitors enter the market. One should also expect that competition will increase as a result of industry consolidation, which comes from the need for newer models of customer service, in which a single vendor provides solutions for both internal and external service, technical support, and search.

Today's businesses are faced with the reality of customers expecting and demanding more multichannel information and better service from call centers than ever before. Integrating call center service resolution management (SRM) into customer relationship management (CRM) can help companies retain both their call center agents and their customers.

For more background, please see Integrating Customer Relationship Management and Service Resolution Management.

Knowledge management (KM) is at the core of integrating CRM and SRM. KM software aims at helping to unlock the power of a company's knowledge to improve efficiency, competency, and profitability. It does so by providing an environment in which companies can, more quickly and cost-effectively, create a company-wide knowledge base to store and index documents and to more accurately search for the answers to user questions.

Currently, the key trends in KM tools enable companies to perform the following: 1) target their online information to reflect what is most likely to interest customers, and 2) maintain online forums where customers can share amongst themselves what they know about the company's products.

Hence, KM products typically fulfill two functions. KM accommodates self-service, meaning a customer can access a pool of public information that a company accumulates about itself, without the need for live assistance, to have his or her questions answered. Second, KM software helps call center agents to retrieve information from a repository that is often, obviously, larger than what is available to the public (since the aim of live assistance is the same as self-service—to answer customers' inquiries quickly and accurately, but with the preferred human touch).

The above considerations have marked a fundamental shift away from the time when any company could claim to perform a valuable service to customers simply by displaying information on its web site, without having to take into account who the customers were. Today however, virtually all companies must demonstrate their value to customers by segmenting information that is directly relevant to them.

Customer segmentation is not a new idea, since segmentation was supposed to be the way that—with the help of CRM tools—companies would offer the best possible service to their best customers. The problem with applying overt segmentation to customer service was that it then revealed a hierarchy that placed most customers at the bottom. This was so because, by definition, elite customers represent a small minority (the proverbial Pareto's 80/20 Rule). The premise of segmenting customers reinforced the idea that customers existed to create value for companies, rather than the other way around. Using this logic, most (up to 80 percent) customers were of little value to the companies that they bought products and services from.

By contrast, the practice of KM helps companies establish a bidirectional relationship with customers that rewards them for sharing knowledge (their product and service use experience), and not only for spending money. The latest generation of KM software makes this possible by enabling the company to combine what it knows about customers and what customers know about the company, and to offer this information as part of the resources available on its web site.

As discussed in Making the First Call Count by Greg McFarlane, an astute KM software has to make it easier for agents to author new knowledge when new services, products, or upgrades are in place. This reduces the need for agents (especially novice agents) to escalate calls to the upper service tier. This decreases the costs and the lengths of calls, but more importantly, it gets calls answered more quickly. In addition, the diagnostic search functionality helps resolve customers' issues quickly and accurately with its ability to pull answers from any data source an agent can connect it to, thereby giving agents the right information at the right time. Lastly, the automation of key resolution processes enables new agents to get up to speed more quickly. By pre-populating case notes and pre-establishing workflows and other techniques, the companies can create an environment that allows agents to operate as effectively as possible, regardless of their experience.

Today's businesses are faced with the reality of customers expecting and demanding more multichannel information and better service from call centers than ever before. Integrating call center service resolution management (SRM) into customer relationship management (CRM) can help companies retain both their call center agents and their customers.

For more background, please see Integrating Customer Relationship Management and Service Resolution Management.

Knowledge management (KM) is at the core of integrating CRM and SRM. KM software aims at helping to unlock the power of a company's knowledge to improve efficiency, competency, and profitability. It does so by providing an environment in which companies can, more quickly and cost-effectively, create a company-wide knowledge base to store and index documents and to more accurately search for the answers to user questions.

Currently, the key trends in KM tools enable companies to perform the following: 1) target their online information to reflect what is most likely to interest customers, and 2) maintain online forums where customers can share amongst themselves what they know about the company's products.

Hence, KM products typically fulfill two functions. KM accommodates self-service, meaning a customer can access a pool of public information that a company accumulates about itself, without the need for live assistance, to have his or her questions answered. Second, KM software helps call center agents to retrieve information from a repository that is often, obviously, larger than what is available to the public (since the aim of live assistance is the same as self-service—to answer customers' inquiries quickly and accurately, but with the preferred human touch).

The above considerations have marked a fundamental shift away from the time when any company could claim to perform a valuable service to customers simply by displaying information on its web site, without having to take into account who the customers were. Today however, virtually all companies must demonstrate their value to customers by segmenting information that is directly relevant to them.

Customer segmentation is not a new idea, since segmentation was supposed to be the way that—with the help of CRM tools—companies would offer the best possible service to their best customers. The problem with applying overt segmentation to customer service was that it then revealed a hierarchy that placed most customers at the bottom. This was so because, by definition, elite customers represent a small minority (the proverbial Pareto's 80/20 Rule). The premise of segmenting customers reinforced the idea that customers existed to create value for companies, rather than the other way around. Using this logic, most (up to 80 percent) customers were of little value to the companies that they bought products and services from.

By contrast, the practice of KM helps companies establish a bidirectional relationship with customers that rewards them for sharing knowledge (their product and service use experience), and not only for spending money. The latest generation of KM software makes this possible by enabling the company to combine what it knows about customers and what customers know about the company, and to offer this information as part of the resources available on its web site.

As discussed in Making the First Call Count by Greg McFarlane, an astute KM software has to make it easier for agents to author new knowledge when new services, products, or upgrades are in place. This reduces the need for agents (especially novice agents) to escalate calls to the upper service tier. This decreases the costs and the lengths of calls, but more importantly, it gets calls answered more quickly. In addition, the diagnostic search functionality helps resolve customers' issues quickly and accurately with its ability to pull answers from any data source an agent can connect it to, thereby giving agents the right information at the right time. Lastly, the automation of key resolution processes enables new agents to get up to speed more quickly. By pre-populating case notes and pre-establishing workflows and other techniques, the companies can create an environment that allows agents to operate as effectively as possible, regardless of their experience.

A customer relationship management (CRM) system that accommodates complex customer-facing processes requires four key factors to give the system a competitive advantage.

The first key factor lies in the application's ability to develop a complete customer profile that supports multiple business units and products. Service organizations need a wide range of customer data, including demographics, financial status, and current and anticipated lifestyle changes (for example, college-age children, retirement concerns, newborn kids, house or condo purchase, changing insurance requirements, etc). To gain a true understanding of customers' needs and wants, any interaction with them must be captured and analyzed.

For example, when a customer with a savings account inquires about a home loan, a full-service financial services company would want the customer-facing employee, whether in the branch or contact center (if not even an intelligent online software agent), to recognize that here lies an opportunity to cross-sell a home insurance policy to the client as well.

Having a complete customer profile enables users to quickly identify key attributes about a customer, such as whether the customer has multiple accounts with the bank, and therefore is a customer the bank would not want to lose. Naturally, customers are highly sensitive to how they are treated; they notice such things as whether their service institutions answer the phone quickly and recognize the customer when he or she calls, or whether the establishments answer questions astutely or resolve issues promptly. Also of importance is whether the institution provides rapid turnaround for specific offerings, such as new account origination, new loan origination, refinancing a home, and so on.

Most customer-serving institutions need software solutions that can deliver services that are personalized to the customer's needs. Take, for example, an insurance company that has many distinct lines of insurance products but no common customer database, leading to the disastrous result of several agents calling on the same accounts. Such disorganization is not only costly and inefficient, but it also creates a great deal of customer dissatisfaction, annoyance, and ultimately, defection. By implementing a unified solution to market more than one product to the right customers, the service company should be able to improve revenues while driving down the costs—and retaining customers.

The second key factor is that the CRM application should provide companies with the ability to customize their solution to address their unique business needs and evolving external requirements. In a dynamic business environment, the service enterprise must be able to sense and react, almost instantly, to changing market conditions. These conditions vary depending on whether they are caused by shifts in market structure, new competitive threats, micro- or macro-economic changes, or other factors. A company must also adapt to its users' needs, since not all users are alike; an adaptable system should provide a personalized interface for the user, based on his or her specific information needs. Ideally, the system should also be able to dynamically modify its behavior, depending on what the user is doing.

Financial industry enterprises—especially those competing with larger organizations—claim that they win and keep customers because they leverage their in-depth knowledge about the client to offer more personalized service. These clients do not want a cut-and-dried solution that looks and acts like the same CRM system that their next-door competitor uses. Rather, they want a flexible solution that they can tailor to their products, services, and business operations.
The third essential factor of a CRM system that accommodates customer-facing processes is that it should offer organizations the ability to adapt to customer and market changes, since most traditional enterprise CRM offerings require users to write lots of expensive, time-consuming custom code as part of their deployment. This often creates many problems, starting with most customers finding that by the time they have completed the development cycle and are ready to roll out the software, something in their business has yet again changed (such as a new, fierce competitor has entered the market; new legislation has been passed; the company is involved in a merger; management has decided to add or drop a new product line, etc.). Thus, these firms may find themselves stuck using their old model and needing to go through another long, expensive software development cycle to add the changes they need. On the other hand, customized environments can be very difficult to upgrade when the vendor comes out with a new release of its software.

The fourth factor is the CRM application's ability to integrate, in near real time, with other complex systems, and its adaptability to users' existing infrastructure. It is not at all uncommon to find dozens of systems in the service firm's back offices, all of which have data that needs to be integrated with the new CRM system. Some of these systems can even go back a decade or more. Many of these systems, although ancient in the IT timescale, still deliver mission-critical services reliably and effectively, day in and day out. Thus, a modern CRM solution must easily and seamlessly share data bi-directionally with these systems, using open industry standards.

As the first factor indicates, an adaptive service enterprise must be sensitive to ever changing customer requirements, and must foster an optimal customer experience by creating and delivering incremental services that customers want and are willing to pay for. This requires an IT infrastructure capable of seamlessly tracking and managing interactions across all customer touch points, such as the retail store, the Internet, e-mail, fax, the call center, etc.

Though CRM mega-vendors often want users to rip and replace their entire IT infrastructure with the mega-vendor's software stack, many clients view their legacy systems as mission-critical, and might prefer a CRM solution that will protect their investment by plugging into their existing infrastructure.

To be sure, services institutions live and die by the services and products they provide to fickle and demanding customers, and they need to be able to change direction quickly in order to meet competitive challenges or to take advantage of emerging opportunities. Only by deploying astute CRM technology will they be able to capture customer and market data, sense and understand how their customer segments want to be served, and be able to analyze and respond to changes in customer needs and wants.

Because CRM processes touch so many parts of a business, they can have a major impact on both cost and revenue. The improvement of sales and marketing processes can bring in new revenue, while call center productivity can drive down the costs of servicing customers, as well as present up-sell and cross-sell opportunities (and maintain customer satisfaction).

The business case for call center applications is becoming increasingly obvious, especially given the recently established National Do Not Call Registry in the US. The revenue driver will thus become inbound customer calls rather than companies trying to generate leads via outbound telemarketing efforts, which have too often proved to be annoying to customers, and ultimately counterproductive.

A customer relationship management (CRM) system that accommodates complex customer-facing processes requires four key factors to give the system a competitive advantage.

The first key factor lies in the application's ability to develop a complete customer profile that supports multiple business units and products. Service organizations need a wide range of customer data, including demographics, financial status, and current and anticipated lifestyle changes (for example, college-age children, retirement concerns, newborn kids, house or condo purchase, changing insurance requirements, etc). To gain a true understanding of customers' needs and wants, any interaction with them must be captured and analyzed.

For example, when a customer with a savings account inquires about a home loan, a full-service financial services company would want the customer-facing employee, whether in the branch or contact center (if not even an intelligent online software agent), to recognize that here lies an opportunity to cross-sell a home insurance policy to the client as well.

Having a complete customer profile enables users to quickly identify key attributes about a customer, such as whether the customer has multiple accounts with the bank, and therefore is a customer the bank would not want to lose. Naturally, customers are highly sensitive to how they are treated; they notice such things as whether their service institutions answer the phone quickly and recognize the customer when he or she calls, or whether the establishments answer questions astutely or resolve issues promptly. Also of importance is whether the institution provides rapid turnaround for specific offerings, such as new account origination, new loan origination, refinancing a home, and so on.

Most customer-serving institutions need software solutions that can deliver services that are personalized to the customer's needs. Take, for example, an insurance company that has many distinct lines of insurance products but no common customer database, leading to the disastrous result of several agents calling on the same accounts. Such disorganization is not only costly and inefficient, but it also creates a great deal of customer dissatisfaction, annoyance, and ultimately, defection. By implementing a unified solution to market more than one product to the right customers, the service company should be able to improve revenues while driving down the costs—and retaining customers.

The second key factor is that the CRM application should provide companies with the ability to customize their solution to address their unique business needs and evolving external requirements. In a dynamic business environment, the service enterprise must be able to sense and react, almost instantly, to changing market conditions. These conditions vary depending on whether they are caused by shifts in market structure, new competitive threats, micro- or macro-economic changes, or other factors. A company must also adapt to its users' needs, since not all users are alike; an adaptable system should provide a personalized interface for the user, based on his or her specific information needs. Ideally, the system should also be able to dynamically modify its behavior, depending on what the user is doing.

Financial industry enterprises—especially those competing with larger organizations—claim that they win and keep customers because they leverage their in-depth knowledge about the client to offer more personalized service. These clients do not want a cut-and-dried solution that looks and acts like the same CRM system that their next-door competitor uses. Rather, they want a flexible solution that they can tailor to their products, services, and business operations.
The third essential factor of a CRM system that accommodates customer-facing processes is that it should offer organizations the ability to adapt to customer and market changes, since most traditional enterprise CRM offerings require users to write lots of expensive, time-consuming custom code as part of their deployment. This often creates many problems, starting with most customers finding that by the time they have completed the development cycle and are ready to roll out the software, something in their business has yet again changed (such as a new, fierce competitor has entered the market; new legislation has been passed; the company is involved in a merger; management has decided to add or drop a new product line, etc.). Thus, these firms may find themselves stuck using their old model and needing to go through another long, expensive software development cycle to add the changes they need. On the other hand, customized environments can be very difficult to upgrade when the vendor comes out with a new release of its software.

The fourth factor is the CRM application's ability to integrate, in near real time, with other complex systems, and its adaptability to users' existing infrastructure. It is not at all uncommon to find dozens of systems in the service firm's back offices, all of which have data that needs to be integrated with the new CRM system. Some of these systems can even go back a decade or more. Many of these systems, although ancient in the IT timescale, still deliver mission-critical services reliably and effectively, day in and day out. Thus, a modern CRM solution must easily and seamlessly share data bi-directionally with these systems, using open industry standards.

As the first factor indicates, an adaptive service enterprise must be sensitive to ever changing customer requirements, and must foster an optimal customer experience by creating and delivering incremental services that customers want and are willing to pay for. This requires an IT infrastructure capable of seamlessly tracking and managing interactions across all customer touch points, such as the retail store, the Internet, e-mail, fax, the call center, etc.

Though CRM mega-vendors often want users to rip and replace their entire IT infrastructure with the mega-vendor's software stack, many clients view their legacy systems as mission-critical, and might prefer a CRM solution that will protect their investment by plugging into their existing infrastructure.

To be sure, services institutions live and die by the services and products they provide to fickle and demanding customers, and they need to be able to change direction quickly in order to meet competitive challenges or to take advantage of emerging opportunities. Only by deploying astute CRM technology will they be able to capture customer and market data, sense and understand how their customer segments want to be served, and be able to analyze and respond to changes in customer needs and wants.

Because CRM processes touch so many parts of a business, they can have a major impact on both cost and revenue. The improvement of sales and marketing processes can bring in new revenue, while call center productivity can drive down the costs of servicing customers, as well as present up-sell and cross-sell opportunities (and maintain customer satisfaction).

The business case for call center applications is becoming increasingly obvious, especially given the recently established National Do Not Call Registry in the US. The revenue driver will thus become inbound customer calls rather than companies trying to generate leads via outbound telemarketing efforts, which have too often proved to be annoying to customers, and ultimately counterproductive.

In today's dynamic manufacturing industry, companies are feeling the squeeze of fierce competition, as goods are being produced more cheaply in developing countries. Because of this, global sourcing for parts is a huge factor in cost reduction.

In the project-based nature of the engineer-to-order (ETO) world's manufacturing processes, specific parts are needed at precise times. As well, because ETO manufacturing must meet stringent milestones and deadlines, it is critical that firms obtain parts on time. Otherwise, project costs go up, timelines are extended, and budgets are blown.

How can these manufacturers mitigate the pressures of this competitive landscape? Supply chain management (SCM) can play a vital role in an ETO manufacturing environment, enabling milestones to be met and parts to arrive on time so that production can continue on schedule.

This article details how SCM helps firms that manufacture ETO goods, as well as how SCM integrates with ETO to improve business processes.

The Role of SCM in ETO Firms

The ETO environment is a very detailed type of manufacturing because it involves many changes in the engineering and design of a product throughout its production. In this manufacturing environment, orders are based on contracts as opposed to work orders, which means it is crucial that the manufacturer meets its project deadlines.

ETO enterprise resource planning (ERP) software manages project deadlines and milestones within the manufacturing environment. However, with today's increasing amount of global sourcing, additional functionality is required, and this is where SCM software comes into the picture.

Because precise components need to be routed from different sources during the process of designing and manufacturing of the product, suppliers need to be made aware of the product requirements in enough time to be able to deliver these requirements to the client.

How can suppliers be linked into the operations of the manufacturing firm, which can make demands on a whim?

How SCM Software Components Relate to the ETO Manufacturing Environment

The main modules of SCM software include the following:

*

Warehouse management system (WMS)—enables firms to optimize methods of storing and moving inventory through the warehouse.
*

Transportation management system (TMS)—enables transportation firms to manage and optimize any mode of transportation.
*

International trade logistics (ITL)—helps organizations with the logistics of importing and exporting, the finances related to these activities, and collaboration between firms across multiple locations.
*

Supplier relationship management (SRM)—manages the relationships between suppliers, distributors, and manufacturing firms. SRM is one of the key features that enables manufacturing firms to source products quickly.
*

Demand management (DM)—forecasts how much product to move through the supply chain, how much product to produce, and how much product will need to be produced in the future, based on historical data.
*

Supply chain analytics—enables supply chain managers to create work-arounds if problems within the supply chain occur. Supply chain analytics is comprised of supply chain optimization, supply chain event management (SCEM), and production and supply planning.
*

Order management—enables suppliers (or manufacturers) to take an order, search within their inventory to see if the item is available, and ship the item to its final destination.

SCM software integrates into the ETO software infrastructure, enabling manufacturers to source goods from multiple suppliers. Because of the project-based nature of ETO manufacturing, the need for different and multiple components, as the engineering of a product changes, is essential for the manufacturing project to succeed.

Here's a look at how the seven main SCM modules can be applied to the ETO manufacturing environment:

*

Using warehouse optimization techniques built into the software, the WMS will facilitate the quick movement of goods coming into the manufacturing environment in order to get the goods to the workstations as soon as possible.
*

The TMS will enable ETO manufacturers to obtain the components as quickly as possible by choosing the most appropriate means of transportation. Also, if a transportation route is blocked, the TMS will help drivers find an alternate route, which ensures and improves delivery times, and enables the project costs of the ETO product to fall within a tolerable range.
*

The SRM software will choose the appropriate supplier. (A detailed example is shown below.)
*

Finally, because multiple orders are being delivered to the manufacturer at the same time as engineering changes are happening throughout the design of the good, the order management system will integrate with the ETO software to send out the appropriate orders to each supplier. This helps to ensure that suppliers send the correct components needed for ETO production.

In today's dynamic manufacturing industry, companies are feeling the squeeze of fierce competition, as goods are being produced more cheaply in developing countries. Because of this, global sourcing for parts is a huge factor in cost reduction.

In the project-based nature of the engineer-to-order (ETO) world's manufacturing processes, specific parts are needed at precise times. As well, because ETO manufacturing must meet stringent milestones and deadlines, it is critical that firms obtain parts on time. Otherwise, project costs go up, timelines are extended, and budgets are blown.

How can these manufacturers mitigate the pressures of this competitive landscape? Supply chain management (SCM) can play a vital role in an ETO manufacturing environment, enabling milestones to be met and parts to arrive on time so that production can continue on schedule.

This article details how SCM helps firms that manufacture ETO goods, as well as how SCM integrates with ETO to improve business processes.

The Role of SCM in ETO Firms

The ETO environment is a very detailed type of manufacturing because it involves many changes in the engineering and design of a product throughout its production. In this manufacturing environment, orders are based on contracts as opposed to work orders, which means it is crucial that the manufacturer meets its project deadlines.

ETO enterprise resource planning (ERP) software manages project deadlines and milestones within the manufacturing environment. However, with today's increasing amount of global sourcing, additional functionality is required, and this is where SCM software comes into the picture.

Because precise components need to be routed from different sources during the process of designing and manufacturing of the product, suppliers need to be made aware of the product requirements in enough time to be able to deliver these requirements to the client.

How can suppliers be linked into the operations of the manufacturing firm, which can make demands on a whim?

How SCM Software Components Relate to the ETO Manufacturing Environment

The main modules of SCM software include the following:

*

Warehouse management system (WMS)—enables firms to optimize methods of storing and moving inventory through the warehouse.
*

Transportation management system (TMS)—enables transportation firms to manage and optimize any mode of transportation.
*

International trade logistics (ITL)—helps organizations with the logistics of importing and exporting, the finances related to these activities, and collaboration between firms across multiple locations.
*

Supplier relationship management (SRM)—manages the relationships between suppliers, distributors, and manufacturing firms. SRM is one of the key features that enables manufacturing firms to source products quickly.
*

Demand management (DM)—forecasts how much product to move through the supply chain, how much product to produce, and how much product will need to be produced in the future, based on historical data.
*

Supply chain analytics—enables supply chain managers to create work-arounds if problems within the supply chain occur. Supply chain analytics is comprised of supply chain optimization, supply chain event management (SCEM), and production and supply planning.
*

Order management—enables suppliers (or manufacturers) to take an order, search within their inventory to see if the item is available, and ship the item to its final destination.

SCM software integrates into the ETO software infrastructure, enabling manufacturers to source goods from multiple suppliers. Because of the project-based nature of ETO manufacturing, the need for different and multiple components, as the engineering of a product changes, is essential for the manufacturing project to succeed.

Here's a look at how the seven main SCM modules can be applied to the ETO manufacturing environment:

*

Using warehouse optimization techniques built into the software, the WMS will facilitate the quick movement of goods coming into the manufacturing environment in order to get the goods to the workstations as soon as possible.
*

The TMS will enable ETO manufacturers to obtain the components as quickly as possible by choosing the most appropriate means of transportation. Also, if a transportation route is blocked, the TMS will help drivers find an alternate route, which ensures and improves delivery times, and enables the project costs of the ETO product to fall within a tolerable range.
*

The SRM software will choose the appropriate supplier. (A detailed example is shown below.)
*

Finally, because multiple orders are being delivered to the manufacturer at the same time as engineering changes are happening throughout the design of the good, the order management system will integrate with the ETO software to send out the appropriate orders to each supplier. This helps to ensure that suppliers send the correct components needed for ETO production.

To accommodate increasing customer demand for company and product information and for quick issue resolution, companies are now considering the benefits of online self-service systems. Knowledge management (KM) software is the key to such systems, as well as to integrating customer relationship management (CRM) and service resolution management (SRM).

For more background, please see Integrating Customer Relationship Management and Service Resolution Management and Knowledge Management: The Core of Service Resolution Management.

Bolstering Call Center (and Other CRM) Processes

The trend of customer service enablement and the nurturing of customer relationships (which have traditionally been the forgotten stepchildren of CRM) may be overtaking customer acquisition as a main driver of recent CRM deployments. Customer service has historically been provided primarily in person or over the telephone, with limited reference materials available for the customer service representative (CSR). This emerging business model assumes that companies that provide customer service over the telephone will find value in aggregating company knowledge by using the appropriate software, and will be willing to access the content over other channels, especially the Internet. The business model also assumes that companies will find value in providing some of their customer service over the Internet instead of by telephone.

In the past, customers would show a preference for a certain channel of communication with a company, but this is no longer the case. Customers now use several different channels available to ask for support and service and about upgrade issues, or to inquire about or request new products and services. And they expect to receive accurate, consistent information, regardless of the channel they are using. Service that does not meet these expectations is considered a waste of time, and a reason for the customer to seek out competitive offerings elsewhere.

The use of multiple channels for customer service and support, as well as the importance of consistent, accurate, and swift answers, is expected to only increase in the future. Companies are thus realizing that what their customers are seeking is knowledge (which is likely stored somewhere in the company, but more likely, scattered all over the company), and that these customers want it regardless of the channel they choose, be it telephone, Web self-service, e-mail, retail kiosk, or chat.

The logical question a company should ask itself is how it can provide customers with direct access to the knowledge they are looking for when that data may be residing in a variety of places. For example, product specifications, technical support, billing questions, and pricing and policy information can all be found in any number of places, such as CRM databases; legacy KM systems; frequently asked questions (FAQ) lists; intranets; content management systems; billing systems; or an automated response system. The goal here is to analyze the customer's problem, retrieve the information needed to solve that problem, and to do so in whichever contact channel the customer chooses. This process should not only minimize customer frustration and lower the cost of the support transaction, but it should also leave the customer delighted.

Although computer-telephony integration (CTI) systems do a great job at automating call routing and case management, Web sites have become ever glossier and animated, and CRM systems do a decent job of handling customer contacts (and possibly preferences) and product information, something is still missing to enable cohesive customer service. The plethora of new self-service technologies, such as natural language search engines, knowledge bases, guided navigation, user forums, collaboration, personalization, multichannel (e-mail, instant messenger [IM], integrated voice response [IVR], call centers), and so on, lead us to the emerging part of CRM software applications, specifically applications that enable customer service organizations to more effectively resolve service requests and answer questions.
Built on KM and search technologies, SRM (not to be confused with supplier relationship management) applications optimize the resolution process across multiple service channels, including contact centers, self-service Web sites, help desks, e-mail, and chat.

An SRM system creates a knowledge backbone for the seller company by creating a single interface that pulls vital information and knowledge from wherever it is stored, whether it is in the CRM system, legacy support systems, search engine, Web site, document libraries, etc. It allows the company, as a business leader, to evaluate what processes are taking place in its support environment and to then determine how it would like those processes to be handled. With this, the company can guide users step by step through the process of answering their questions, applying the right process to each inquiry to drive the outcome it wants.

Service resolution systems enable the company to harness all the tools and knowledge it has already acquired to solve customers' issues, regardless of what channel they use to tell the seller company about their issue. These SRM applications have to complement, integrate with, and enhance traditional CRM areas like sales force automation (SFA), marketing automation, contact center, and help desk applications by providing knowledge-based solutions that improve service delivery. Although still an emerging software category, existing SRM customers include some of the largest companies in the world, and SRM products have reportedly enabled these companies to reduce operating and service delivery costs, improve customer satisfaction, and increase revenues.

Here is an illustration: A service call (customer inquiry, complaint, etc.) comes in, and the agent fields it by performing a search. A technical bulletin, written by a product manager and stored on a network drive, comes up in the query results because the knowledge base searches both structured and unstructured knowledge. This very issue has been documented, and a resolution has been built to ensure that an answer can be provided. A wizard pops up and prompts the technical support agent to walk the customer through a setup process. The new product can then be used successfully, resulting in a happy customer.

This is the type of service the customer wants and what support systems are really trying to provide—seamless service resolution, which can only be provided by effectively using and managing corporate knowledge (i.e., the knowledge of products and services; diagnostic troubleshooting; information stored in all documents on the network drives, intranets, and e-mail systems; and, most important, the knowledge of the customers and support agents).

Trend Analysis

The markets for KM and SRM solutions are still emerging, and it is difficult to predict how large or how quickly they will grow, if at all. Some companies have found that the productivity of customer service personnel initially drops while CSRs are becoming accustomed to using the software.

Self-service can cause conflicts, since it contributes to a general shift of control and resources away from the call center. Also, exposing some information can be risky. For example, logging complaints into the system and then displaying them on the customer portal can cause some users to regard giving out sensitive information as “hanging themselves." Resistance to the software by customer service personnel and inadequate development and maintenance of the system's knowledge resources, business rules, and other configurations have in some cases made it even more difficult to attract new customers and retain old ones.

Competition in the fragmented SRM marketplace is rapidly evolving and intense, and one should expect competition to further intensify in the future as current competitors expand their product offerings and as new competitors enter the market. One should also expect that competition will increase as a result of industry consolidation, which comes from the need for newer models of customer service, in which a single vendor provides solutions for both internal and external service, technical support, and search.

To accommodate increasing customer demand for company and product information and for quick issue resolution, companies are now considering the benefits of online self-service systems. Knowledge management (KM) software is the key to such systems, as well as to integrating customer relationship management (CRM) and service resolution management (SRM).

For more background, please see Integrating Customer Relationship Management and Service Resolution Management and Knowledge Management: The Core of Service Resolution Management.

Bolstering Call Center (and Other CRM) Processes

The trend of customer service enablement and the nurturing of customer relationships (which have traditionally been the forgotten stepchildren of CRM) may be overtaking customer acquisition as a main driver of recent CRM deployments. Customer service has historically been provided primarily in person or over the telephone, with limited reference materials available for the customer service representative (CSR). This emerging business model assumes that companies that provide customer service over the telephone will find value in aggregating company knowledge by using the appropriate software, and will be willing to access the content over other channels, especially the Internet. The business model also assumes that companies will find value in providing some of their customer service over the Internet instead of by telephone.

In the past, customers would show a preference for a certain channel of communication with a company, but this is no longer the case. Customers now use several different channels available to ask for support and service and about upgrade issues, or to inquire about or request new products and services. And they expect to receive accurate, consistent information, regardless of the channel they are using. Service that does not meet these expectations is considered a waste of time, and a reason for the customer to seek out competitive offerings elsewhere.

The use of multiple channels for customer service and support, as well as the importance of consistent, accurate, and swift answers, is expected to only increase in the future. Companies are thus realizing that what their customers are seeking is knowledge (which is likely stored somewhere in the company, but more likely, scattered all over the company), and that these customers want it regardless of the channel they choose, be it telephone, Web self-service, e-mail, retail kiosk, or chat.

The logical question a company should ask itself is how it can provide customers with direct access to the knowledge they are looking for when that data may be residing in a variety of places. For example, product specifications, technical support, billing questions, and pricing and policy information can all be found in any number of places, such as CRM databases; legacy KM systems; frequently asked questions (FAQ) lists; intranets; content management systems; billing systems; or an automated response system. The goal here is to analyze the customer's problem, retrieve the information needed to solve that problem, and to do so in whichever contact channel the customer chooses. This process should not only minimize customer frustration and lower the cost of the support transaction, but it should also leave the customer delighted.

Although computer-telephony integration (CTI) systems do a great job at automating call routing and case management, Web sites have become ever glossier and animated, and CRM systems do a decent job of handling customer contacts (and possibly preferences) and product information, something is still missing to enable cohesive customer service. The plethora of new self-service technologies, such as natural language search engines, knowledge bases, guided navigation, user forums, collaboration, personalization, multichannel (e-mail, instant messenger [IM], integrated voice response [IVR], call centers), and so on, lead us to the emerging part of CRM software applications, specifically applications that enable customer service organizations to more effectively resolve service requests and answer questions.
Built on KM and search technologies, SRM (not to be confused with supplier relationship management) applications optimize the resolution process across multiple service channels, including contact centers, self-service Web sites, help desks, e-mail, and chat.

An SRM system creates a knowledge backbone for the seller company by creating a single interface that pulls vital information and knowledge from wherever it is stored, whether it is in the CRM system, legacy support systems, search engine, Web site, document libraries, etc. It allows the company, as a business leader, to evaluate what processes are taking place in its support environment and to then determine how it would like those processes to be handled. With this, the company can guide users step by step through the process of answering their questions, applying the right process to each inquiry to drive the outcome it wants.

Service resolution systems enable the company to harness all the tools and knowledge it has already acquired to solve customers' issues, regardless of what channel they use to tell the seller company about their issue. These SRM applications have to complement, integrate with, and enhance traditional CRM areas like sales force automation (SFA), marketing automation, contact center, and help desk applications by providing knowledge-based solutions that improve service delivery. Although still an emerging software category, existing SRM customers include some of the largest companies in the world, and SRM products have reportedly enabled these companies to reduce operating and service delivery costs, improve customer satisfaction, and increase revenues.

Here is an illustration: A service call (customer inquiry, complaint, etc.) comes in, and the agent fields it by performing a search. A technical bulletin, written by a product manager and stored on a network drive, comes up in the query results because the knowledge base searches both structured and unstructured knowledge. This very issue has been documented, and a resolution has been built to ensure that an answer can be provided. A wizard pops up and prompts the technical support agent to walk the customer through a setup process. The new product can then be used successfully, resulting in a happy customer.

This is the type of service the customer wants and what support systems are really trying to provide—seamless service resolution, which can only be provided by effectively using and managing corporate knowledge (i.e., the knowledge of products and services; diagnostic troubleshooting; information stored in all documents on the network drives, intranets, and e-mail systems; and, most important, the knowledge of the customers and support agents).

Trend Analysis

The markets for KM and SRM solutions are still emerging, and it is difficult to predict how large or how quickly they will grow, if at all. Some companies have found that the productivity of customer service personnel initially drops while CSRs are becoming accustomed to using the software.

Self-service can cause conflicts, since it contributes to a general shift of control and resources away from the call center. Also, exposing some information can be risky. For example, logging complaints into the system and then displaying them on the customer portal can cause some users to regard giving out sensitive information as “hanging themselves." Resistance to the software by customer service personnel and inadequate development and maintenance of the system's knowledge resources, business rules, and other configurations have in some cases made it even more difficult to attract new customers and retain old ones.

Competition in the fragmented SRM marketplace is rapidly evolving and intense, and one should expect competition to further intensify in the future as current competitors expand their product offerings and as new competitors enter the market. One should also expect that competition will increase as a result of industry consolidation, which comes from the need for newer models of customer service, in which a single vendor provides solutions for both internal and external service, technical support, and search.

We've all been there at one time or another, in a crowded place or driving while holding a cell phone to our ear in a tight embrace—and why? Because the automated attendant on the other end of the line can not quite make out our "command" to her (or him?) ... usually because of the tiniest bit of background noise or maybe she or he is just having a bad day ... whether it's trying to book a flight, find out the status of a flight, or check the status of an order or place a new order, the frustration can be massive. The flight from Atlanta to Austin can be twisted into the flight from Atlanta to Boston, and incorrect information given out to the unsuspecting party or the maze of options, keys to press, frequent flyer, or shopper numbers to enter can be daunting. And, let's not forget the other frequent headache that many of us encounter daily—trying to return an item purchased online to the retail store ... only to be told "sorry, but we don't stock or accept that item here". And, how many times have you received an "invitation" in the mail to join a "frequent somebody" program that you are already a member of? And last, the age old nightmare of trying to get reliable tech support for that laptop or camera we recently purchased only to be put on hold (or bounced around to countless different "desks") for an extended period of time and when we do get a "live individual", they are fifteen time zones away and speak another language as their "mother tongue" with English as a distant second. A very distant second.

All is not negative, as some positive experiences do occur, but it seems that those are few and far between, and in many instances those positive experiences only occur after a very bad experience has occurred and only occur then as a means of "making it up to" the innocent consumer, thus not really even seeming positive.

We may all chuckle at the horror stories mentioned above, but it is no laughing matter. Especially when horror stories like the ones above cause a consumer to "tell all of their friends" or more importantly, to take their business else where. These experiences are all a direct result of decisions made every day by manufacturers, distributors, retailers, service providers, and technology providers. Executives and middle management are constantly faced with determining policy, process, and technology around managing one or multiple channels.
orcing such decisions such as what or when to outsource in the channel, how many channels to have and what products to push through which channel, what skills and associated organizational models to put into place, what to spend on elaborate mailing and marketing campaigns, and what technologies to utilize to enable the plethora of channel management business processes—the channel management shuffle!! So, you may say "same old stories" regarding the ones mentioned above... but, you won't yawn and say "same old research" when you are finished reading the new report from Chainlink Research on channel management.
The report explores a number of areas that are critical to successful channel management:

1. "Dance with the one who brung ya'"... or channel conflict and multi-partner management—management of channels, minimization of conflict in and across channels, as well as management of multiple partners in and across channels. We will cover the strategies and decisions that a well known technology company is employing and facing moving from a totally direct channel to a mix of indirect and direct.

2. "Save the last carton for me"... or inventory management and returns management—the user experience, returns, distribution challenges, and inventory management areas such as locating, managing, and allocating.

3. "The Tennessee Waltz"... or channel management technologies—the underpinning solutions and technologies to support channel management business processes, as well as what is on the horizon of future plans and initiatives for these solutions. For these technologies and associated vendors, we will look at the delivery architecture options that are available, as well as key strategies that the vendors are employing to assure domain expertise throughout their technology or product lifecycle.

4. "Do the Hokey Pokey"... or emerging best practices—for skill development and organizational models to ensure success in channel management.

We've all been there at one time or another, in a crowded place or driving while holding a cell phone to our ear in a tight embrace—and why? Because the automated attendant on the other end of the line can not quite make out our "command" to her (or him?) ... usually because of the tiniest bit of background noise or maybe she or he is just having a bad day ... whether it's trying to book a flight, find out the status of a flight, or check the status of an order or place a new order, the frustration can be massive. The flight from Atlanta to Austin can be twisted into the flight from Atlanta to Boston, and incorrect information given out to the unsuspecting party or the maze of options, keys to press, frequent flyer, or shopper numbers to enter can be daunting. And, let's not forget the other frequent headache that many of us encounter daily—trying to return an item purchased online to the retail store ... only to be told "sorry, but we don't stock or accept that item here". And, how many times have you received an "invitation" in the mail to join a "frequent somebody" program that you are already a member of? And last, the age old nightmare of trying to get reliable tech support for that laptop or camera we recently purchased only to be put on hold (or bounced around to countless different "desks") for an extended period of time and when we do get a "live individual", they are fifteen time zones away and speak another language as their "mother tongue" with English as a distant second. A very distant second.

All is not negative, as some positive experiences do occur, but it seems that those are few and far between, and in many instances those positive experiences only occur after a very bad experience has occurred and only occur then as a means of "making it up to" the innocent consumer, thus not really even seeming positive.

We may all chuckle at the horror stories mentioned above, but it is no laughing matter. Especially when horror stories like the ones above cause a consumer to "tell all of their friends" or more importantly, to take their business else where. These experiences are all a direct result of decisions made every day by manufacturers, distributors, retailers, service providers, and technology providers. Executives and middle management are constantly faced with determining policy, process, and technology around managing one or multiple channels.
orcing such decisions such as what or when to outsource in the channel, how many channels to have and what products to push through which channel, what skills and associated organizational models to put into place, what to spend on elaborate mailing and marketing campaigns, and what technologies to utilize to enable the plethora of channel management business processes—the channel management shuffle!! So, you may say "same old stories" regarding the ones mentioned above... but, you won't yawn and say "same old research" when you are finished reading the new report from Chainlink Research on channel management.
The report explores a number of areas that are critical to successful channel management:

1. "Dance with the one who brung ya'"... or channel conflict and multi-partner management—management of channels, minimization of conflict in and across channels, as well as management of multiple partners in and across channels. We will cover the strategies and decisions that a well known technology company is employing and facing moving from a totally direct channel to a mix of indirect and direct.

2. "Save the last carton for me"... or inventory management and returns management—the user experience, returns, distribution challenges, and inventory management areas such as locating, managing, and allocating.

3. "The Tennessee Waltz"... or channel management technologies—the underpinning solutions and technologies to support channel management business processes, as well as what is on the horizon of future plans and initiatives for these solutions. For these technologies and associated vendors, we will look at the delivery architecture options that are available, as well as key strategies that the vendors are employing to assure domain expertise throughout their technology or product lifecycle.

4. "Do the Hokey Pokey"... or emerging best practices—for skill development and organizational models to ensure success in channel management.