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).
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).
No comments:
Post a Comment