Hasil (
Bahasa Indonesia) 1:
[Salinan]Disalin!
TugasMK Sistem Informasi ManajemenMANAJEMEN PENGETAHUAN UNTUK LAYANAN PELANGGAN "STAND-OUT": 6 PRAKTIK TERBAIK DARI TAHUN 2000 GLOBALAbstrak (ringkasan dokumen) Perusahaan sering membuat kesalahan dengan bergantung pada para pakar domain internal fokus yang jarang berbicara kepada pelanggan. Kadang-kadang sulit bagi ahli untuk turun ke tingkat yang biasa Pelanggan yang mungkin tidak tahu istilah-istilah teknis seperti apakah mereka reksa dana adalah "tidak ada beban," "depan-penuh", atau "kembali-load". Menggunakan jargon dalam pertanyaan-pertanyaan yang diajukan oleh agen atau sistem mandiri adalah cara dijamin untuk meningkatkan escalations dan pembelotan pelanggan.Layanan pelanggan telah muncul sebagai salah satu dari beberapa differentiators tersisa yang bisnis dapat mempertahankan dari waktu ke waktu.Perusahaan yang menang dalam lingkungan ini menyediakan layanan pelanggan "stand-out" dengan menggunakan pengetahuan untuk memberdayakan Agent contact center dan mendorong interaksi layanan mandiri.Dalam memberikan solusi KM ke dunia kelas contact Center dan layanan mandiri operasi selama 15 tahun, kami telah mengumpulkan ratusan praktek-praktek terbaik yang meningkatkan kemungkinan keberhasilan dalam implementasi KM, sekaligus memaksimalkan ROI. Di bawah ini adalah beberapa yang populer.1. MENGUKUR NILAIMenilai diharapkan dan menyadari ROI sebelum dan sesudah penyebaran membantu Anda membenarkan investasi awal serta pemeliharaan basis pengetahuan (KB), sementara mengangkat visibilitas Anda sebagai pencipta nilai untuk bisnis Anda.Best Practice: Make sure the metrics you use are aligned with business objectives. For instance, if your main business goal is to increase upsell and cross-sell through knowledge-enabled contextual offers, reduction in call handle times will be a conflicting metric. As you assess ROI, keep in mind that KM delivers positive ROI in areas such as:* INCREASE IN FIRST-TIME FIXES AND REVENUE THROUGH UPSELL AND CROSS-SELL* REDUCTION IN ESCALATIONS, TRANSFERS, REPEAT CALLS, CALL HANDLE TIMES, TRAINING TIME, UNWARRANTED PRODUCT RETURNS, FIELD VISITS, AND STAFF WAGE PREMIUMS2. BUILD THE RIGHT TEAMSuccessful KM implementations start with the right team for knowledge capture and creation.Best Practice: Build a cross-functional team that can bring a 360-degree approach to knowledge creation. Best-practice teams typically include:* LEAD EXPERT: INDIVIDUAL WHO DECIDES HOW THE KB WILL BE ORGANIZED, WHICH TOPICS WILL BE COVERED, WHAT THE ROLES OF VARIOUS PEOPLE IN THE TEAM ARE, AND PLANS FOR MAINTENANCE AND USE* USERS: HIGH-PERFORMANCE CONTACT CENTER AGENTS WHO PROVIDE SUGGESTIONS* KNOWLEDGE AUTHORS: INDIVIDUALS WHO ARE TRAINED TO USE AUTHORING TOOLS* PROJECT MANAGER: INDIVIDUAL WHO KEEPS THE PROJECT ON TRACK3. AVOID THE "SWISS CHEESE" SYNDROMEAmbitious deployments almost always result in a KB that is solid in places, but full of holes, like a slice of Swiss cheese. This is a recipe for failure, because if users can't find the answers, or get inadequate or wrong answers, they will quickly stop using the system.Best Practice: Focus on depth and quality rather than breadth. For instance, if an enterprise sells printers, scanners, and copiers, the best approach would be to cover one product line thoroughly first.4. MAINTAIN VELOCITYA classic mistake in KM implementations is not making midcourse adjustments to keep the project on track.Best Practice: If the deployment appears to be falling behind schedule, narrow the scope of the KB and finish on schedule. In fact, it is better to widen the scope later to expand the benefits of the deployment. As a rough guide, a typical enterprise deployment should not take more than three months after the initial planning, with three or four full-time people engaged. Deployment includes software installation, knowledge gathering, and testing both the quality of the KB and system performance.5. BALANCE "IVORY TOWER KNOWLEDGE" WITH "STREET SMARTS"Enterprises often make the mistake of relying solely on internally focused domain experts who rarely speak to customers. It is sometimes difficult for experts to get down to the level of ordinary customers who may not know technical terms such as whether their mutual fund is "no load," "front-loaded," or "back-loaded". Using jargon in questions posed by agents or self-service systems is a guaranteed way to increase escalations and customer defections.Best Practice: Find KB contributors that are both technically competent and not too far removed from customer contact. Successful customer service depends as much on the questions posed to customers as the answers.6. PROVIDE FLEXIBLE CONTENT ACCESSPeople have different ways of finding information, or the same person may use different methods to suit the situation. A flexible approach to information access dramatically improves user adoption and ROI. For instance, novice agents, whether they are in-house or outsourced, may find it difficult to wade through hundreds of search hits to find the right answer, but may fare better if they are guided through a dialog, powered by an inference engine. On the other hand, experienced agents may prefer to quickly process search hits.Best Practice: Provide users multiple ways to access information-FAQ, browse, search, and guided help. The key here is to make sure that the KB remains the same and there are no content silos.GET TO KNOW EGAINFor over a decade, eGain has helped world-class companies achieve and sustain customer service excellence. eGain Service(TM), the company's top-rated customer service software suite, enables organizations to build customer interaction hubs to provide best-in-class customer service and experience, and reduce service costs. Available on-premise or on-demand, eGain Service includes integrated best-of-breed applications for self-service, contact center knowledge management, email, fax and letter management, chat, cobrowse, notifications, call tracking and resolution, case management and service fulfillment-all built on a common customer interaction hub platform.SEBUTKAN ISI MAKALAH TERSEBUT!
Sedang diterjemahkan, harap tunggu..
