While there are numerous reports of "failed" implementations of various types of Customer Relationship Management (CRM) 客戶關係管理 projects, these are often the result of unrealistic high expectations and exaggerated claims by Customer Relationship Management (CRM) 客戶關係管理 vendors.
Many of these "failures" are also related to data quality and availability. Data cleaning is a major issue. If the company Customer Relationship Management (CRM) 客戶關係管理 strategy is to track life-cycle revenues, costs, margins and interactions between individual customers, this must be reflected in all business processes. Data must be extracted from multiple sources (e.g., departmental/divisional databases, including sales, manufacturing, supply chain, logistics, finance, service, etc.), requiring an integrated, comprehensive business processing system to be in place with defined structures and data quality. If not, interfaces must be developed and implemented to extract data from different systems. This creates a demand far beyond customer satisfaction to understand the full business-to-business relationship.
For this reason, Customer Relationship Management (CRM) 客戶關係管理 is more than a sales or customer interaction system.
The experience from many companies are that a clear Customer Relationship Management (CRM) 客戶關係管理 requirement with regard to reports (e.g., input and output requirements) is of vital importance before starting any implementation. With a proper demand specification, a great deal of time and money can be saved based on realistic expectations of systems capability. A well operating Customer Relationship Management (CRM) 客戶關係管理 system can be an extremely powerful tool for management and customer strategies.
訂閱:
張貼留言 (Atom)
沒有留言:
張貼留言