Measuring Customer Experience with Dynamics 365 Customer Voice

"What you cannot measure you cannot improve" - I think you will agree to this statement. If you want to improve your customer experience than first you need to know how to measure it. Once you measure it than you can track and take action from your insights to improve customer experience.

Customer Experience is about how the customer feels after having an interaction with your business. The interaction can be of 3 main types

1. Products - You want to know how the customer feels after purchasing and using your product. 

2. Services - If you are selling services, how the customer felt after the service was delivered. Like automotive maintenance service

3. Processes -  How was the customer online buying process experience or experience with the case resolution process.

An enterprise may want to know all 3 of the above and get valuable feedback from the Customer. If you have large number of products and thousands of customers globally you need to have a Enterprise Feedback management system like Dynamics 365 #CustomerVoice. 

I have written 2 blogs earlier about Microsoft Dynamics 365 - Customer Voice. My blog-1 gives an overview about Customer Voice and blog-2 is about considerations when deploying #CustomerVoice.

This blog is about how to measure your Enterprise Customer Experience using #CustomerVoice.

Measuring of Customer Experience is done using Satisfaction Metrics. The metrics are mapped to questions in the Survey. As the survey responses come in Customer Voice services sends the responses to Azure Cognitive services for analysis and also to the Customer Voice analytics engine. After the analysis is done the results are stores in Dataverse. 

Response analysis

There are 4 types of Satisfaction metrics that you can use. 

Satisfaction metrics

1. CSAT or Customer satisfaction is measured by responses to rating type questions in survey and is normalized to a range of 1-5. The below are example of CSAT survey questions.

CSAT question types

 

2. NPS or Net Promote Score is a metric used to measure customer loyalty. It is based on NPS type questions with scale 0-10 as shown below. 

NPS questions

Customer voice will group the respondents as follows 

    i.   Detractors = response from 0-6 rating

    ii.  Passive = responses with 7 or 8 rating

    iii.  Promotes = responses with 9 or 10 rating 

The NPS is a number calculated using the formula 

NPS = (% of Promoters) - (% of Detractors) 

NPS can range from -100 (100% detractors) to 100 (100% Promoters).

3. Sentiment - this identifies how the customer feels about a product, service or process. This is done using a text based question response. Sentiment will group the response based on the text as positive, negative or neutral. 

4. Custom Score - You may want to have a custom scoring of the question in a Survey. The custom score allows you to assign a point value to the answer options. Based on the response the score is calculated and assigned to the Survey.  This can help you to add more weightage to certain question answers and thus get an custom measurement of the respondents satisfaction level.

Custom Score

As you are planning and designing the questionnaire make sure that you understand how the customer experience can be measured so you have the right insights. In my next blog I will discuss about tracking and actionable insights.

I hope this helps you in improving your enterprise customer experience with #CustomerVoice. Thanks for reading.

@mihircrm

365WithoutCode

Teams and Power BI - Enable visual collaboration

 The integration of Power BI with Microsoft Teams has enabled enterprise wide collaboration on data and visual presentations. This brings new ways of generating team insights where remote teams can review the data and provide feedback to improve the visuals. 

Power BI and Teams - Visual collaboration 

There are multiple ways you can share the Reports and Visuals from Power BI service into a Teams Chat or Channel. This blog describes some of the options for using Power BI within Teams.

1. Power BI App in Teams - You can add the Power BI app to teams which will enable directly working in the Power BI Service from within Teams itself. 

Power BI app in Teams

2. You can also add a Power BI tab to a Teams Channel. This enables to collaborate on the Power BI report within the channel. 

Power BI - Add as a tab to Teams Channel

Note - When selecting to add a tab - you can only add a Power BI Report but not a dashboard to the channel.

3. Chat in Teams - You can chat in teams from a Power BI Report / Dashboard or even a visual. This inserts a link in teams chat for the shared content. 

 

Visual tile - Chat in Teams

4. Link preview - You can add a link to a Power BI - Report / Dashboard or App in Teams chat and a link preview is shown. The user can open the Power BI visualization from within Teams.

Link preview in Teams

Things to note -

1. In order for the Teams integration with Power BI - the users will need a Power BI Pro or Premium per user license or the Power BI Report is in a Power BI - Premium capacity. 

2. Users within the Team will need to be shared the reports and given access to the underlying dataset to enable them access to the content. One way to enable this is to share access to the Report workspace to the Microsoft 365 Teams group 

Microsoft 365 group access to Power BI workspace

3. Power BI dashboard cannot be added as a tab to Team channels. Also the Link preview does not work in Meeting Chat or Private Channels

4. Make sure that the Power BI Teams integration is enabled in the Admin Portal > Tenant settings. (by default it is enabled)

Teams integration is enabled

I hope that this helps you in integrating Power BI and collaborating within Microsoft Teams. Let me know how you have gained from the Team insights which are enabled with this new feature.

Thanks for reading

@mihircrm

365withoutCode

Considerations when deploying Customer Voice in the Enterprise

 In my previous blog I had written about Customer Voice - An Overview. This blog covers important topics to consider when deploying Customer Voice in the enterprise.

1. Customer Voice is an Enterprise Feedback management app. It is not customizable as other apps of Dynamics 365. So what you see is what you get. It is easy to use and may fit most of your business requirements. But if you want to further enhance it currently Microsoft has not allowed for enhancement of the Customer Voice app. Hence it is important to consider various aspects of the app to determine how to optimally deploy in the organization.

2. Data Storage - My first thought for any Customer app is - how is the Customer data managed ? In your org there could be many departments globally who will be using this app for creating customer surveys. The information collected from the Customers using the Survey may need to be kept secure due to many reasons (industry or government regulations, GDPR restrictions ...) and it is imperative to understand where the data is and who has access to the data. Below is a visual representation of the data flow.

Customer Voice - Data Flow

The data is stored in mainly 2 data stores - 1. Customer Voice App and 2. Dataverse environments. The data is also processes by Azure Cognitive Services and Dynamics 365 marketing sends the survey. 

Customer Voice app will store the data mainly in North America and for Europe Customers it will store in Europe data centers. The data stored in Dataverse is based on the local environment location.

3. Project - When a project is created the Dataverse environment is selected for the Project. So a user can have Customer Voice access to projects which are in Dev / QA / Test and Prod environments. They are all accessed from the same Customer Voice app. The contacts are populated into the project from the connected environment.

Project and Environment

3. Using with Customer Service - Chances are that you are going to use Customer Voice and Customer Service together. If so both Customer Voice and Customer Service (or any other D365 app) will need to be in the same tenant. This will enable functionality like auto send a survey when a case is closed in Customer Service.

4. Security - Users who need access to Customer Voice to create and send Surveys need to have the Project Owner security role (or custom role with the privileges)

Project Owner - security role

This will provide the user with the minimum privileges required in Customer Voice.

The system also create an Application user account to integrate with Azure services.

5. Record ownership - It is important to know who will be the owner of the records created in Customer Voice. (This is where it gets a little complicated)

1. Projects and Surveys - are created and owned by users in Customer Voice (no team ownership capability yet). If the Project is shared with other owners, a AAD team is created with the shared ownership. It is best to have a Project shared with multiple owners who are working together.

2. Survey response ownership is based on a logic as below

    a. Response to a Survey invitation - The invitation owner is the owner of the response

    b. If the invitation owner does not have the privilege to own response than the survey owner is the owner of the response. 

    c. If the response is anonymous than the Survey owner is the owner of the response

    d. If the Survey owner user account is disabled closed or deactivated or no longer has the license the application account becomes the owner. (Please note - If the survey owner account is closed or deactivated the Survey Customer data will be deleted by the System after 30 days) So be careful to select who is the owner of your Customer Voice data.

6. Data deletion - Do not delete the survey data in Dataverse. You will need to delete from Customer Voice and the same is than synced with Dataverse. Any other ways of data deletion may land you in trouble. 😀

I think that the above info is valuable when you want to deploy Customer Voice in your organization. Let me know about your experience with Customer Voice. Thanks for reading.

@mihircrm

365WithoutCode

Power BI with Power Apps Portals - Part-3

 Portals are now becoming ubiquitous as a Customer / Partner / Employee engagement channel. They can provide valuable information to a large audience. There is a need to embed dynamic visualizations, dashboard and reports in a Portal. This is very much possible now using Power Apps and this blog discusses how visuals from Power BI can be embedded into Power Apps Portals.

In my earlier blog I had mentioned about getting started with Power BI and Dynamics 365 Power BI template apps. This is a continuation and Part-3 of the Power BI with Dataverse series of blogs. 

An embedded Power BI dashboard can provide valuable information to the user when logged into the Power Apps Portal. Its great that one can create powerful visualizations but when the visuals drive insights and is showcased to a large # of users the value of the visual increases exponentially for the organization.

Power BI embedded in Power Apps Portals

Assuming you have a Power BI report or dashboard ready and a Power Apps Portal created in the same environment. The following steps will help you embed a Power BI report in Power Apps Portals. 

1. Configure Power Apps Portal

Go to Power Platform Admin Center and select your Portal 

Enable Power BI visuals

Click on Manage Power BI embedded service and select the workspaces that you have the Power BI reports and dashboards to be shown on the Portal.

Select Workspaces

Now you have configured the Portal for embedding Power BI. While you are on the managing Portal select Portal Details copy the application ID of the Portal. It will be useful in the next step.

Portal App ID

2. Set up Azure AD security group

We will need a Azure security group with the CRM Portal as a member. This security group will be given access to Power BI API. This will enable the display of visuals in the Portal.

Log in to Azure and create a new Security Group in Azure Active Directory. 

Security Group

Add Microsoft CRM Portal as member of the security group. Apply the Portal application ID to the member. 

Add member

Add the above security group to the Power BI Tenant Developer settings as shown below. This will allow the Portal to use Power BI API.

Allow to user Power BI API

Now we have completed most of the setup required. Next step is to configure the Portal and add the Power BI report and or dashboard to the Portal.

3. Embed Power BI visual in the Portal

Go to make.powerapps.com and select your portal and click on edit. This will open the Power Apps Portal Studio.

Here you can select to add a new page to the Portal or add a section to an existing page to display the Power BI visual.

One of the components you can add to a page or section is Power BI.

Add Power BI component

Once the component is added you will get the options to select the Workspace > Dashboard or Report to add to the Portal.

Add Power BI visuals as component

Things to note -

1. Users who log in to the Portal will need to be authenticated using AAD. 

2. Users will need Power BI license to view the visual

3. The Power BI dashboard or report will need to be shared with the user

I hope the above was helpful in embedding Power BI visualizations in to your Power Apps portals. Let me know if you have embedded Power BI in your Portal or custom websites.

Thank you

@mihircrm

365WithoutCode

 

   

Power BI Template Apps - Power BI with Dataverse (D365) Part-2

 In my earlier blog I had written about connecting with PowerBI and Dataverse (D365) using the CDS or Dataverse connector. You can also use the Power BI template Apps that Microsoft has provided to see your Sales or Service data in PowerBI.com

As always there are pre-requisites for using the Apps. They are - 1. You need to have a Power BI - Pro license for all users who want to consume the app and also 2. Admin access to install the App and connect to D365.

So now that we have the requisite license and access let us install the template app. There are 3 D365 - Power BI template apps. They are shown below with demo data

1. Sales Analytics. https://tinyurl.com/88g43r2m

Sales Analytics Power BI App

2. Process Analytics: https://tinyurl.com/5ybgdqze

Process Analytics App

(I am not a fan of the background bluish color but that can be removed using PBI desktop as I have mentioned below)

3. Customer Service Analytics: https://tinyurl.com/3a2v2pmg

For this demo I was unable to get the demo data loaded in the app or connect the app to D365. This is from the Appstore -

Customer Service Analytics Power BI

I will write about the Sales Analytics App below -

1. Install - Go to https://tinyurl.com/88g43r2m  and click on Get it now (or in PowerBI.com go to Get Data and search for Sales Analytics app)

2. Once the app is installed you will see the App in PowerBI.com You will be able to see the App with demo data. You can also connect the App to your specific D365 / Dataverse instance. Once connected the D365 instance data will load into PowerBI.com

You get the below different reports in Sales Analytics App. 

3. You can than analyze the data in PowerBI or you can import the dashboard into D365. (I will write more about this in my later blogs)

4. The OOTB app does not have any custom tables and you will need to customize the App. This is now possible by downloading the Power BI report and importing the PBIX file into Power BI desktop.  Use the link below for downloading the Sales Analytics or Process Analytics Power BI report PBIX file.     

        https://tinyurl.com/1royw6my

5. Now you can add the custom tables and columns to the Power BI reports and create your own App.

I believe that the template apps are a very good starting point to use Power BI with Dataverse. Let me know if you have any questions or any other ideas of using Power BI with Dataverse / D365. 

Thanks for reading

@mihircrm / 365withoutcode

Getting started using Power BI with Dataverse (D365) - Part-1

Power BI has become one of the top data visualization tools. In every project that I have worked on, the default option to visualize, analyze and reporting tool with Microsoft Dynamics 365 is Power BI. It is a natural out of the box fit and Microsoft is doing its best to make the default choice with Dataverse. 

I have written earlier about D365 and Power BI but in the journey of evolution,  the Power Platform has very much changed and it is time to have a fresh look.  In this blog series we will ponder over the ways to -

1. Connect Power BI with Dataverse (D365) - This blog #1

2. Perform D365 data transformations & generate valuable AI insights in Power BI

3. Create and import data visualizations in Power Platform from Power BI

4. Limitations and things to consider (like security) when using Dataverse and Power BI

PBI dashboard with D365

Pre-requisite - In order to get started with Power BI you will need the following -

1. A D365 / Dataverse environment - You can get a trail of Dynamics 365 using trials.dynamics.com

2. Power BI (free or paid) license - PowerBI.com

3. Power BI desktop (download free from PowerBI.com)

Once you have done the above we are ready to play with D365 and Power BI

A - Setup needed - For this blog series we will need the capability of adding Power BI visuals into D365 (dashboards and visuals) as well as enable the TDS (Tabular Data Stream) endpoint. This is done by going to admin.powerplatform.microsoft.com and select your D365 environment (tip - its not the default one). Environment > Settings > Product > Features and enable the 2 highlighted below

B - Connecting Power BI with Dataverse (D365)

1. Once you have the above and downloaded the Power BI desktop latest version (note the version changes ever month) you can click on > Get Data. 

This will open up a myriad of options (enough to baffle you and maybe you feel like in a candy store), but lets focus on the Power Platform for now. Select Power Platform and you have 2 main options (dataflows is not the topic of my current blog, maybe in the future) 

Connect options

Dataverse connector is the latest one offered (I am going to use it for this blog) The limitation here is that the size of the dataset is limited to 80MB. If your needs are more than 80 MB (which is quite obvious when using large datasets) use the CDS legacy connector. I am hoping that the Dataverse connector allows larger datasets in the near future. 

Once you click on connect with Dataverse. it will ask you if you want to import data or do a Direct Query. For this blog I am going to import the data into Power BI. At this time it is important to note that there is an important security difference between importing data into Power BI and using Data query. I will revisit this in my next blog.

Connectivity mode

Another thing that you will need to enter is the environment domain. It used to be simply coping your D365 domain url but Microsoft has made it a little complex. Now you are supposed to enter the url without https:// and remove the / in the end (had to do this twice just to get it right) If you don't know what is your environment domain url Go to Make.powerapps.com select your environment (not default) and click on Settings > Session details. 

Instance url

Once you have the details and click 'ok' you may be prompted to sign in (if you are not already signed in) and then shown the Navigator window to chose from the tables to import into Power BI. 

Select Table

Once you select a table make sure to select 'Transform Data' which will open up the Power Query Editor 

Select columns to import

Here click on Manage Columns and you will be able to select which columns you want to import. It is important to know the Dataverse data model to be able to understand what columns you will need to create your visualizations.

Once you have selected the columns click on Apply and this will start the import process. In my next blog we will look at the options for working with D365 data in Power BI. 

Hope this helps you to get started with using Power BI with Dataverse (D365). Thanks for reading.

@mihircrm

365WithoutCode

Microsoft Dynamics 365 - Customer Voice - An Overview - Part-1

 Microsoft has created Dynamics 365 - Customer Voice and this blog is to provide an overview of the features.

Customer Voice is an Enterprise Customer feedback design, collection and management app. It allows you to design / send surveys and collect / analyze feedback from the surveys sent. Customer Voice is an enhancement to and re-branding of Microsoft Forms Pro. The data is stored in Dataverse (another rebranding - previously CDS) and it can be connected to a Dynamics 365 environment. 

1. Demo - To setup a demo of Customer Voice - go to this link. https://dynamics.microsoft.com/en-us/customer-voice/overview/ and sign up for a 30 day demo. 

2. Project - Once the demo environment is up you will be creating a Project. The project is a repository for all your Survey related data (Surveys, Satisfaction metrics, Email templates, Power Automate flows and Reports). Project is linked to a specific Dynamics 365 / Power Platform Dataverse environment. So if you have Dev / QA / Prod environments you can create and link a project for each specific environment. 

Microsoft provides easy to deploy Project templates or you can select a Blank template. 

You can also share a Project with other users so that other users can design and send their own Surveys. 

3. Design Surveys - Once you have created the Project, now you are ready to design your own Surveys. If you selected a Project template the first survey is already created for you to customize and built upon. You can modify / add questions to the survey.

Design Survey

You can customize your survey to include -

1. Personalization - Adding upto 15 variables in your survey (First Name, Last Name, ...)
2. Branding - Changing theme, font and background 
3. Metrics / KPI - Adding upto 10 customer satisfaction metrics per Project
4. Add Survey Language - You can add upto 23 languages and the Survey question translation
5. Add Branching - using Power Automate flows
6. Formatting - Add Progress bar, question #'s and shuffle questions

You can also preview and test the Survey to make sure it works as designed.

4. Send Survey - Once the design is done you can send the Survey using multiple options

1. Email - Send the survey using email.
2. Power Automate - Trigger a survey email using Power Automate
3. Embed - the survey in a web page
4. Send a link to the Survey in an email or add to web page 
5. Send a QR code of the survey by email or add to web page

    The Distribution settings allow you to customize the survey send settings.

Send Survey

A survey invitation record is created for every survey sent by email or using Power Automate to trigger an email. Statistics is collected on the survey invitation and analyzed.

5. Analyze responses - 

The response received are analyzed and reports generated. There are 2 types of reports.

1. Satisfaction metrics (Customer KPI reports) - They are based on the answer to the questions linked to metrics. The satisfaction metrics can be - CSAT / NPS / Sentiment

2. Survey response - A report is generated for every survey sent and response received.

Metrics report

Survey report

Hope this blog helps you getting started on the Customer Voice and let me know about your specific questions / experience using it. In my next blog I will write about some important considerations for using Customer Voice. Thanks for reading. 

@MihirCRM

365WithoutCode