Skip to main content

Microsoft Dynamics Customer Service Best Practices

By Ayesha Mirza, senior consultant at InfoStrat

One of the key initiatives of customer service is to make tasks easier for both the customer and customer service agents. Customers want to find information and customer service agents have the need to process, absorb and promote information requests in order to provide an adequate customer experience.

Streamlining this flow of information requires planning and a robust platform such as Microsoft Dynamics 365 to bridge the gap between the customer experience and agent activities.

This post describes our approach and best practices to consider while implementing Microsoft Dynamics 365 Customer Service.
  • ·         Strategy – Plan out your implementation from the start. Define purpose, scale, budget, baselines, promotion, delivery, maintenance and escalation methods prior to kick-off. This will aid in clarifying internal and business expectations and help keep costs and schedule as projected. The approach can be defined with the following milestones.
  •       Knowledge - At the core of an effective customer self-service solution is a strong knowledge base. The knowledge base allows you to easily add, edit and deliver information and use customer feedback from across channels, agent knowledge of frequently asked questions, keyword search data and more to provide the answers and information customers want and need. It provides agents access to a central knowledge base of product, service and customer service information so that they can deliver current, consistent answers and train faster.
o    Knowledge Management Process: The following diagram describes the default process for creating and using knowledge articles in the Customer Service Hub in Microsoft Dynamics 365.
§  Create an article and mark it for review.
§  The reviewer can approve or reject the article.
§  If the article is rejected, it is sent back for edits or updates.
§  If the article is approved, it is published on the portal. It is also available in search and can also be translated.
§  For more information, please refer to Microsoft Documents “Create and manage knowledge articles”

Representation of a Knowledge Article Dashboard in Microsoft Dynamics 365

·         Visibility & Metrics - Provide each agent with individual productivity scorecard. Set targets and objectives for agents with weekly reports that show customer satisfaction score, tickets resolved, knowledgebase articles suggested, etc. These metrics can then be converted for leadership in accessing areas of improvement, training, issues and growth through KPIs. Microsoft Dynamics 365 provides interactive dashboards come in two forms:

o   Multi-stream dashboards: Primarily used for Tier 1 Support where representatives handle a large number of cases across multiple workstreams. Users can easily switch from a standard view to an interactive tile view to dissect and absorb data effectively. It further provides the ability to drill down to the emphasizing records.

o    Single-stream dashboards: Primarily used for Tier 2 support representatives that handle relatively small to medium sized caseloads and require more complex or escalated data breakdown in a single view.

o    Both multi-stream and single-stream dashboards contain interactive charts that give you a count of relevant records, such as cases by priority or by status. These charts also act as visual filters.
o    For more information, please visit Microsoft Documents “Manage service cases using interactive dashboards”

·         Collaboration - Promote instantaneous collaboration and knowledge sharing among agents. Use community (feedback form) and/or social tools (Yammer and / or Microsoft Teams) to help speed resolution of trending issues.

·         Consolidate - Implement an agent service desk that combines all channels. Merge channels for omnichannel service delivery so that agent can seamlessly transition across channels with the customer.

o    Businesses can utilize the unified routing and work distribution capabilities for Microsoft Dynamics 365 to route work items initiating from chat, messaging, and web portal channels to various customer service support teams within the company. Through setup and configuration, organizations have the ability to define the role, profile, permissions and makeup of the agents’ access and automate workflows (queues) based on their availability, capacity and team makeup.  This helps streamline the process and makes it easier for the business and respective agents to work effectively and proficiently.  For more information please visit Microsoft Documents “Unified routing and work distribution”

·         Delivery - Distribute reliable information that is searchable and well organized by topic, most-viewed, most-recently-added, etc.
o   You can search the knowledge base from the following areas in the Customer Service Hub app:
·         Select a case by navigating to Service à Cases
·         In the Related section, select Knowledge Base Search and search for knowledge articles using keywords in the search box.

·         Quick find in Grids - Go to Service à Knowledge Articles and select the search box to search the knowledge base using keywords.

·         Global search - Select the Search icon on the navigation bar to do a global search for knowledge base articles. Global search lets you use “Characterized” Search or “Relevance” Search.

·         For more information, please visit Microsoft Documents “Understand knowledge base search mechanisms”

·         360 View -  Provide a full circle view of the customer for personalized and appropriate service. Give agents a heightened view of customer information via custom widgets and dashboards so that they can have ease of access to data, product history, sentiment analysis, service history and other customer-centric material.

·         Feedback - Incorporate agent feedback to improve your service replies and delivery. Gather feedback from agents to improve procedures, efficiency, and self-service knowledge base with answers to most frequently-asked customer questions.
o   Improve your products and services by enabling users to provide feedback and ratings for entity records in Microsoft Dynamics 365. For example, you can enable feedback and ratings for the Product entity to know user's feedback on the products you sell, or on the Incident (case) entity to understand and improve the quality of your customer support team.

o   You can enable feedback and ratings for both system and custom entities in Dynamics 365. By default, the KnowledgeArticle entity is enabled for feedback and ratings. Use the new Feedback entity to create and manage feedback for entity records.

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

Updated 8/15/2022 To understand Microsoft Dynamics 365 (formerly Dynamics CRM) and Power Apps, you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises.  These concepts also apply to Power Apps.  The main difference is that with Power Apps you are not starting with a Microsoft app but more of a blank canvas for your custom apps.  This post introduces some key terms and how these concepts are important for planning your implementation. While Dynamics 365 is still available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds in several countries. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uni

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source: by James Townsend Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do