Implement Parent-Child Cases (Episode 19)

Posted on January 4, 2020 by Paresh Sharma

You might face situation where you receive similar cases and you would not like to pay attention to each case as since the nature of these cases are similar. In such a situation you can create a parent case, identify similar cases and link them as child cases. You can provide a solution to your customer and finally close the parent case and choose if you want to automatically close the associated child cases.

Following are some points to note regarding Parent-Child cases:

  • It is possible to create multiple cases associated with one parent case.
  • Parent-Child case relationship is used when you want to keep track of multiple issues for a customer or track the same issue for multiple customers.
  • It is an easy way to manage cases rather than handling multiple cases of similar nature.
  • Parent-Child case settings includes:
    • What fields must be populated from parent case when child case is created.
    • Closure preferences, such as:
      • Parent & Child cases can be closed independent to each other (default).
      • Close all Child cases when Parent case is closed.
      • Do not allow the Parent case closure until all Child cases are closed.

Scenario:

  • After Business Central training, customer’s employees face a lot of challenges in Setting up Business Central.
  • So, instead of creating individual cases, a Parent case is created for “Business Central Setup Issues”.
  • Whenever a new issue is raised by the customer related to system setup, a child case is created against the parent case.
  • After understanding all the issues/scenarios, the Tech Quantum team decided to create a Knowledge Base (training) so all the issues can be resolved.
  • Finally, to close all the child cases, the parent case is closed.

Process:

Click Advanced Setting > Settings > Service Management > Parent and Child Case Settings.

In Case Settings:

  • Select the attributes that you would like to inherit from parent to child case.
  • Specify closure preference, by selecting one of the following:
    • <Blank>
    • Close all child cases when parent case is closed
    • Don’t allow parent case closure until all child cases are closed

NOTE: When you select <Blank>, which is default, all cases (parent or child) have to be closed independently.

In this example, we will select the second option, i.e. “Close all child cases when parent case is closed”.

To test the settings, create a Parent Case and some Child cases. Then resolve the parent case and notice the result on child cases. They, all will be closed simultaneously.

Similarly choose another setting in Parent and Child Case Settings and see what results you get!

Posted in D365 Customer Engagement (CRM), D365 Customer Service, Microsoft Dynamics 365 | Tagged , , | Comments Off on Implement Parent-Child Cases (Episode 19)

Automatic Record Creation and Update Rules (Episode 18)

Posted on January 1, 2020 by Paresh Sharma

Automatic Record Creation and Update Rules allow creating records automatically when specific criteria is met.

The source type can be:

  • E-Mail
  • Phone Call
  • Appointment
  • Task
  • Social Activity
  • Service Activity
  • Alert Subscription
  • Invite Redemption
  • Portal Comment
  • Survey Activity

You need to activate the rules before they can be utilized.

It is also possible to send the created record to a specific queue.

There are different Record Creation Conditions available for each Source Type.

Scenario:

When an existing contact send an email with Subject that contains keyword such as “high”, the system should automatically create a Case with High priority and send it to High Priority Case Queue.

Process:

We are going to discuss how we can setup a mailbox in exchange and tie that to a support mailbox in Dynamics 365. When people send an email to this mailbox, a case will automatically be created by the system. We can then use a workflow to assign this new case to a queue or team.

Please note for this to work you’ll have access to Office 365 Admin Center and Dynamics 365 for Customer Service Hub.

Setup Exchange Mailbox (Prerequisite)

The first thing we’re going to do is setup a mailbox in exchange, this is also where we will define the email address for the support mailbox.

  • Navigate to Office 365 Admin Center.
  • Then expand ‘Groups’ on the left hand side and select Shared Mailboxes.
  • Click ‘+Add a Mailbox’ and set the mailbox name and email address.

Once the mailbox has been created remember to add members to the mailbox by selecting the mailbox and clicking ‘edit’ adjacent to Members.

You might get the following message and there may be some waiting time before changes can take effect.

Add Dynamics 365 Queue

Now we need to add a queue in Dynamics 365, where we will tie this exchange mailbox to the queue by using the support email address. This will be the place where the emails will be tracked in Dynamics 365 after they are received in the exchange mailbox.

  • Click Advanced Settings > Settings> Business Management >Queues.
  • In the following example we are using an existing queue created in previous episode (Episode 17) or you can create a new queue and enter the email address of the mail box you just created in the ‘Incoming Email’ field. Select whether this is a private or public queue add members (who can access the queue) if this is a private queue. Note the system will create a mailbox using the email address provided in the ‘Incoming Email’ field of the queue. Also set the ‘Convert Incoming Email to Activities’ field to ‘All Email Messages’.

Configure Dynamics 365 Mailbox

Click on the mailbox under ‘Email Settings’ to open the mailbox. We will now configure the incoming and outgoing mailbox settings.

  • Set the ‘Incoming Email’ and ‘Outgoing Email’ fields to ‘Server-Side Synchronization or Email Router’.
  • Click ‘Approve Email’ on the ribbon and click ‘Test and Enable Mailbox’.
  • Once the email has been enabled you will see the Incoming Email status and Outgoing Email Status on the mailbox record showing as ‘Success’. We have successfully configured the mailbox in Dynamics 365 🙂

Automatic Record Creation and Update Rules:

In one of our previous posts we discussed how you can implement case routing rules (Episode 17). Let’s say you are converting a case from an activity, then you might want to apply the routing rule automatically. For that you can configure Automatic Record Creation and Update Rules.

In Dynamics 365, go to Advanced Settings > Settings > Service Management > Automatic Record Creation and Update Rules.

Click New, specify the following fields and click Save:

  • Name: “E-mail Incoming high Priority Cases”.
  • Source Type: Email.
  • Queue: High Priority Queue.
  • Create records for email from unknown senders: Yes.

Next, Specify Record Creation and Update Details, by specifying the following fields and conditions and action:

Name: Create High Priority Case

Condition: Email description contains “high” or “urgent”.

Action: Create Case. (Set the Properties such as Description, Priority, Owner, etc.)

Activate the Rule.

Now when an email is sent to the designated mailbox, a case is automatically created and is routed to the respective queue.

Open the case to check if all the fields that were mapped are populated correctly such as Name, Description, Priority, etc.

Posted in D365 Customer Engagement (CRM), D365 Customer Service, Microsoft Dynamics 365 | Tagged , , | Comments Off on Automatic Record Creation and Update Rules (Episode 18)

Implement Case Routing Rules (Episode 17)

Posted on December 30, 2019 by Paresh Sharma

Case Routing Rules can simplify the life of case service agents and service managers by automatically assigning cases based on specific requirements or conditions.

Few Points about Case Routing Rules:

  • Routing Rules allow assigning cases to the right resource without any manual intervention.
  • Routing Rules can also be used for routing cases to specific queues.
  • Routing Rules allow users to define Conditions and Actions.
  • Routing Rules can be applied automatically or manually.
  • You can have only one active Routing Rule at a time.

Scenario

We have a customer who would like to get response in:

  • 8 hours for High priority cases
  • 12 hours for Normal Priority cases
  • 24 hours for Low priority cases

So based on the priority, cases must be assigned to a queue, i.e.:

  • Cases with High priority, Route to High Priority Cases Queue.
  • Cases with Normal priority, Route to Normal Priority Cases Queue.
  • Cases with Low priority, Route to Low Priority Cases Queue.

Process

In Dynamics 365, go to Advanced Settings > Settings > Service Management > Routing Rule Sets.

Create a New Routing Rule Set, say “Assign Cases With Priority To Specific Queue” and Save.

Now, let us add Rule Items (by clicking on the + icon), say:

  • High Priority Cases – High Priority Queue
  • Normal Priority Cases – Normal Priority Queue
  • Low Priority Cases – Low Priority Queue

Note the condition and action in the following screenshot for High Priority. Similarly the conditions and actions are setup for Normal priority and Low priority cases.

Once the Rule Items are created, you can Activate the Rule Set. The Status changes to Active state.

Now go to cases, select multiple cases (with varying Priorities) and click Apply Routing Rule.

Once the routing rules are applied, go and check the Queues.

NOTE: There are more parts to it like queues, automatic case creation and update, etc. We will try to cover that in upcoming episodes.

Posted in D365 Customer Engagement (CRM), D365 Customer Service, Microsoft Dynamics 365 | Tagged , , | Comments Off on Implement Case Routing Rules (Episode 17)

Case Resolution Process (Episode 16)

Posted on December 27, 2019 by Paresh Sharma

        Scenario:

  • The company is: Tech Quantum
  • The customer who is dealing with company is : Adventure Works
  • The solution/ Services that company has provided to customer is: Trained Employees on Microsoft Dynamics 365 (with 30 days of support)
  • Issues raised by the customer is: Not able to qualify leads in Microsoft Dynamics 365
  • Issue Assigned to CRM User: Kelly Krout (Support Expert)

    Case Resolution:

    In Dynamics 365, click Cases in Customer Service Hub.

    Search for the case logged in by the customer, i.e. “Not able to qualify Leads in Microsoft Dynamics 365”

    Open the case. You can click Assign to change the owner to a support engineer, say “Kelly Krout” in this example.

    When the user Kelly Krout looks into “My Active Cases”, she will see the case that has been assigned to her for resolution.

    Kelly now opens the case and there is step by step business process to guide Kelly on how to go about resolving the case, for example: Identify > Qualify > Research > Resolve.

    So to get past the Identify stage, Kelly fills out the necessary case details. In this example Kelly discusses the case with the customer and specifies necessary details such as Contact, Description and Type of the case.

    Kelly Adds a Phone Call activity in the timeline to record the conversation she had with the Customer.

    After gathering required information, Kelly moves the case to the next stage, i.e. Qualify.

    In this example, there is no Entitlement attached to the customer, Kelly moves case to the Research stage.

    Since Kelly has already identified the issue, she can look for a similar case or a related KB article or even assign the case to a consultant to get the right resolution. In this example, Kelly has taken an online session with the customer to basically resolve the issue.

    So Kelly Adds a Task to record the online session, i.e. the resolution in this case. Note that Kelly also provides duration for the task.

    Since the task is complete, Kelly closes the task and marks as complete in the Timeline.

    So Kelly has now resolved the issue, she can change the state of the case to Resolve and click Finish to mark it complete.

    For the final step click Resolve Case. The system will automatically calculate the Total Time. You can also overwrite the Billable Time and click Resolve.

Posted in D365 Customer Engagement (CRM), D365 Customer Service, Microsoft Dynamics 365 | Tagged , , | Comments Off on Case Resolution Process (Episode 16)

Create A New Case Record (Episode 15)

Posted on December 25, 2019 by Paresh Sharma

There are three ways to create a Case in Dynamics 365:

Scenario:

  • The company is: Tech Quantum
  • The customer who is dealing with company is : Adventure Works
  • The solution/ Services that company has provided to customer is: Trained Employees on Microsoft Dynamics 365 (with 30 days of support)
  • Issues raised by the customer is: Not able to qualify leads in Microsoft Dynamics 365

Quick Create:

On the Customer Service Hub, click the New (+) button on the menu bar and select Case. This will open the Quick Create form for a Case.

Please note that you cannot use quick create for all the records in Dynamics 365, but most of them.

Fill out the information and click Save and Close.

This is the fastest way to create a case in Dynamics 365 by a support engineer. The case will now be available under Active Case, which you can also see on your Dashboard and can be further worked upon.

If you open the case you can specify more details.

Case Form:

To create a Case using Case Form you need to go to the entity Cases and then click New Case.

This will open a new case form where you can enter the case details.

Here you can use the Business Process Flow specific to your company and also specify and view much more information.

From Activities:

Let us say a customer has sent an email with an issue and as a Support Engineer you convert the email activity in to a case using Convert To Functionality.

Open the relevant activity from the Activities and click Convert To > Case.

Posted in D365 Customer Engagement (CRM), D365 Customer Service, Microsoft Dynamics 365 | Tagged , , | Comments Off on Create A New Case Record (Episode 15)

Search For Case Records (Episode 14)

Posted on December 24, 2019 by Paresh Sharma

There are three ways to search case records within Dynamics 365:

  1. Quick Search
  2. Global Search
  3. Advanced Find

In Customer Service Hub, open Cases. The following screenshot shows the three ways of searching:

For Quick Search

  • Search for records, say “Product”. Irrespective of the view selected, the system will display a search result with list of all the records that being with the search term. In this example it shows all the case titles that begin with the term “Product”.

  • There may be instances where the case tile may not begin with the term you are looking for. In such cases you can use wild card characters, for example: *product*. In this example the system will populate a search result with all the case titles that has the term “product” in it,

For Global Search

  • Type the search criteria in the global search, for example: “Adventure”. You can use wild card characters as well, such as “*Adv*”.
  • The system will look into all the entities and display categorized search results as shown below. You can also apply filters to show the results for a particular entity.

For Advance Find

  • Click on the funnel icon to open the Advance Find.
  • Here you can create a simple or complex query, edit columns, provide filtering criteria and click on Results to see the result based on your query.
  • You can also save the query as your personal view.
  • So for example:
    • Use an existing view, say Active Cases.
    • Click on Details to change the filters.
    • Select a filter: Case Title Contains *adv*.
    • Select the filter lines and group them as OR.
    • Click Results.

You can also use filter on the columns in a view as well:

  • Open an existing view. Say, “All Cases”
  • Click on the filter icon beside a column header.
  • You can apply filtering criteria for each column. You can also apply filters on multiple columns at a time.
  • Click Apply to see the result.

Posted in D365 Customer Engagement (CRM), D365 Customer Service, Microsoft Dynamics 365 | Tagged , , , , , , | Comments Off on Search For Case Records (Episode 14)

Manage Case List and Views (Episode 13)

Posted on December 23, 2019 by Paresh Sharma

A Case is a single incident of service raised by the customer. It can be an issue, query or a feedback. The customer service representative will work on this incident and try resolving the case.

A Customer (Account or Contact) can raise multiple cases in Dynamics 365. There is no limit on how many cases can be raised. However, there might be restrictions based on Service Level Agreements (SLA) signed with the service provider. These cases can have different statuses as well.

Views allow users to see multiple cases at the same time (active cases, my cases, closed cases, etc.)

Let’s have a look in Dynamics 365:

  • Open Customer Service Hub in Dynamics 365.

  • Click Cases in the Navigation bar.

  • This page shows the cases as per the view selected. For example, the current view show “My Active Cases”, i.e. all the cases assigned to the user currently logged in.

  • Similarly there are many other views which can be useful in you day to day activity. You can also Pin the view to be you default view when you open the Case list.

  • Note that each View has different filtering criteria and can have different number of columns relevant to the view.
Posted in D365 Customer Engagement (CRM), D365 Customer Service, Microsoft Dynamics 365 | Tagged , , , | Comments Off on Manage Case List and Views (Episode 13)

Case Management Process Flow (Episode 12)

Posted on December 22, 2019 by Paresh Sharma

We are going to discuss the default out of the box case process flow that is there is Dynamics 365, however, you can also add new steps and change the process according to the customer needs.

Following is the flow:

  • A case starts when a customer raises an issue or asks a question or sends a feedback. Now this can happen outside Dynamics 365 either manually or they could use Customer Service Portal to log the case.
  • A case is created when customer calls a customer service representative or sends an email, or the case can be created automatically by when the customer logs the case via customer service portal. When the case is created, the status of the case is set to Active.
  • The next step is to assign the case to the relevant person. The cases can be assigned manually to relevant customer service agent or automatically using the Case Routing Rules. So, the objective is to assign the case to a customer service agent who can resolve the case. The status of the case is still Active.
  • The next step is research, where the customer service agent may call the customer or send an email or ask for more information to really understand the issue. Many a times when customer raises an issue it may not be clear and the customer service agent may need more information, or do internal research, to give the real solution to the customer. The status of the case is still Active.
  • Next the case can be resolved once the research is done and the issue is solved, or the question is answered, or the feedback is taken and noted. The case is closed, and the status is set to Resolved.
  • The other possibility (from Research stage) is that the cases was resolved by customer themselves and it is no longer required for the customer service agent to work on it then the case can be cancelled. The status is set to cancelled.
  • If required, you can reactivate the case from the resolved or cancelled status. The status of the case is set to Active.
Posted in D365 Customer Engagement (CRM), D365 Customer Service, Microsoft Dynamics 365 | Tagged , , , | Comments Off on Case Management Process Flow (Episode 12)

Important Terms in Customer Service for Dynamics 365 (Episode 11)

Posted on December 21, 2019 by Paresh Sharma

Overview

Customer Service Hub for Dynamics 365 can be utilized for:

  • Solving Issues
    • When a customer raises an issue, this module can be used to resolve those issues.
    • The customer may or may not have a service contract with you.
  • Answering Questions
    • When a customer has any doubts or questions about the purchased product/service.
    • This module can be used to send information and answering customer’s questions.
  • Feedback Analysis
    • When customer provides any feedback about your product/services.
    • This module can be used to capture feedback and improve your products/services.

Understanding Core Records

The following terms are essential for you to get acquainted with, before you can work with Customer Service Hub for Dynamics 365:

  1. Accounts

    An Account is an Organization. This includes:

  • Customer
  • Vendor
  • Partner
  • Affiliate or Other
  1. Contacts

    A contact is an individual:

  • Associated with maximum one Account (through contact form)
  1. Cases

    A case represents a single incident. A case can be:

  • An Issue
  • A Query
  • A Feedback
  • Activities
    • Activities are the interactions between customers and the business.
    • Activities are based on incidents.
    • Every activity should be resolved in order to close any incident.
  • Queues
    • Queues are the place or location where activities and cases are stored to be processed.
    • Queues are created based on users and teams.
  • KB Articles
    • KB Articles stand for Knowledge Based Articles.
    • These are Information Articles Repository to help resolve cases.
    • Used by the support users / service engineers.
  • SLA
    • SLA stands for Service Level Agreements.
    • SLA explains the level of service offer to customers.
    • Define Metrics and KPI (Key Performance Indicators) to attain service levels.
  • Subject Tree
    • Subject Tree helps you categorize Service Cases, KB Articles, Product Catalog Items, Sales Literature.
    • Makes it easy for users to search and use information to resolve cases.
Posted in D365 Customer Engagement (CRM), D365 Customer Service, Microsoft Dynamics 365 | Tagged , , , , | Comments Off on Important Terms in Customer Service for Dynamics 365 (Episode 11)

Work With Status Reason Transitions (Episode 10)

Posted on October 10, 2019 by Paresh Sharma

<–Previous Episode

The status of a record helps identify where the record is in a specific process. For example, if you’re currently working on a case in the system, the case is considered to have a status of Active. After the case is closed, it can be set to a status of Resolved. These statuses make it easier to sort, filter, and query specific records in the system.

Out of the box, specific statuses are available for each Dynamics 365 record, depending on the type of record. Cases have three statuses that they can be in:

  • Active: The case is currently open and is actively being worked on in the application.
  • Resolved: The issue for the case has been fixed.
  • Cancelled: The case is no longer active in the system, but it wasn’t resolved.

You can’t change the statuses that are available for a specific record type. But it’s often important to have more specific information about the status of a record. For example, a case might be active in the system, but what exactly is being done on the case? Is the agent researching the problem? Is the agent waiting for the customer to provide more information? Knowing these details can be critical to effective service delivery.

Each record type has what’s called a status reason. A status reason is associated with a specific record status and provides more information about why the record is in that status. For cases in Dynamics 365, several status reasons are available out of the box:

Active:

  • In Progress: The case is currently being worked on by a customer service agent.
  • On Hold: The case is active, but it isn’t currently being worked on.
  • Waiting for Details: The case is active, but you’re waiting for more information from the customer.
  • Researching: The case is currently being researched.

Resolved:

  • Problem Solved: A successful resolution was found for the case.
  • Information Provided: The customer was given satisfactory information, and the issue was fixed.

Cancelled:

  • Cancelled: The case was cancelled.
  • Merged: The case was cancelled because it was merged with another record.

You can add, remove, or change case status reasons as needed by going to Customizations > Cases > Fields and selecting the drop-down arrow in the Status Reason field. Multiple status reasons are available for each status, and they can be changed.

Status Reason Transitions

Often, organizations have a specific process that they follow to resolve cases. Case statuses and status reasons might play a role in that process. To help organizations more clearly define and enforce those processes, Dynamics 365 lets them create customer status reason transition paths.

Status reason transitions add an additional level of filtering to define a specific list of status reasons that can be selected for a specific status reason. For example, when a case has a status reason of Waiting for Details, it’s technically already on hold. Therefore, letting a technician change the status reason to On Hold is redundant. Additionally, On Hold just might not be the best status reason to transition to. By using status reason transitions, you can define the specific transitions that an agent can go to from the Waiting for Details status reason.

The following image shows an example.

As you can see, when a case has a status reason of Waiting for Details, the only transition options are:

  • Cancelled
  • Service Escalated
  • Researching
  • In Progress

For each of those status reasons, in turn, multiple transitions can be selected. Therefore, status reason transitions make it easier for organizations to help guarantee that agents use only valid reasons, based on the current status reason.

Status reason transitions are available only on the case entity and custom entities. You can change them by selecting the Edit Status Reason Transitions button on the status reason field customization page. After you turn on the status reason transitions feature, you define the specific status reasons that are available.

Status Reason Transitions

When you define reason options for an active status reason, there must be at least one path to an inactive status. For example, if a case has a status reason of In Progress, it must be possible to transition to at least one of the following status reasons: Cancelled, Merged, Problem Solved, or Information Provided. If at least one path to an inactive status isn’t provided, you won’t be able to save the new transitions.

After the transitions are saved and published, agents will see the changes reflected in the application.
For more about status reason transitions, see Define status reason transitions for the Case or custom entities.

Posted in D365 Customer Engagement (CRM), D365 Customer Service, Microsoft Dynamics 365 | Tagged , , , | Comments Off on Work With Status Reason Transitions (Episode 10)