Automatically Create Cases from Customer Service Emails
Monitoring a customer service inbox and manually turning incoming emails into Cases can be tedious. Dynamics 365 Customer Service can automate this process so customer service representatives can spend more time helping customers instead of performing repetitive data entry. The setup centers around two components:
- A basic queue for receiving customer service emails
- An Automatic Record Creation and Update Rule that converts those emails into Cases
What You Need
To configure automatic Case creation, you need a Dynamics 365 Customer Service license or appropriate add-on. You'll also need one of these security roles:
- Customer Service Manager
- System Administrator
- System Customizer
Create a Basic Queue
Start in the Copilot Service admin center and navigate to the basic queue configuration. Create a new queue with a recognizable name, such as Support Queue. Queues can be public or private. A private queue allows you to specify which users can access its contents, while a public queue is available more broadly. For automatic Case creation, one of the most important parts of the queue is its incoming email address. This is the mailbox that will receive your customer service requests.
Convert Incoming Emails to Activities
Configure the queue to convert incoming email messages into CRM activities. For this scenario, select the option to convert all incoming email messages. This allows incoming support emails to appear as activities that can ultimately be tracked to the automatically created Case. Once the queue has been saved, configure its mailbox. The email address needs to be approved, tested, and enabled before Dynamics 365 can process its incoming messages.
Create an Automatic Record Creation and Update Rule
Next, configure the automation that turns your incoming emails into Cases. In the Copilot Service admin center, navigate to Case Settings and open Automatic record creation and update rules. Create a rule and select the queue you just configured. For this scenario, configure:
- Activity type to monitor: Email
- Queue to monitor: Your support queue
Selecting Email as the activity type is essential because the goal is to create Cases from incoming email messages.
Configure the Conditions
The next step is configuring the conditions for your rule. This step is required even if you want every incoming email to create a Case. If every email should qualify, simply don't add a condition. This portion of the rule creates the Power Automate flow responsible for automatically creating the Case. You also have the option to select an email template if you want Dynamics 365 to automatically send a response when a Case is created.
Decide How to Handle Unknown Senders
The Advanced tab provides additional options for determining how different messages should be handled. One useful setting allows Cases to be created from unknown senders. An unknown sender is someone whose email address doesn't already correspond to a Contact in your CRM. You can allow these emails to create Cases and configure Dynamics 365 to create Contacts for those unknown senders. This can be helpful when your support inbox regularly receives requests from people who haven't previously been entered into CRM.
Avoid Creating Duplicate Cases from the Same Conversation
You can also configure Dynamics 365 to wait for a specified amount of time before creating another Case from a related email conversation. When this option is enabled, Dynamics 365 won't create another Case if the email thread already has a related active Case within your specified timeframe. This can help prevent a single support conversation from generating unnecessary duplicate Cases as the customer and your service team continue replying to the same email thread.
Save and Activate the Rule
Once your configuration is complete, save and activate the Automatic Record Creation and Update Rule. Behind the scenes, the rule uses Power Automate to create the Case. If you receive an error while saving or activating the rule, check whether your Case table contains custom required fields. For example, your organization may have added a required field that isn't included in the standard automatic Case creation process. If so, the generated Power Automate flow may need to be updated to populate that field. You can access the flow through Power Automate or through the rule while it's deactivated.
Test Automatic Case Creation
After everything is configured, test the process by sending an email to your newly configured support email address. The message should first arrive in the queue. Dynamics 365 then processes the activity according to the Automatic Record Creation and Update Rule and creates the corresponding Case. The incoming email is tracked to that Case, giving the customer service representative both the support request and the original communication in CRM.
Monitor Automatic Case Creation
The Automatic Record Creation and Update Rule provides an Activity Monitor that helps you understand how your automation is performing. The monitor shows whether processing succeeded or failed. If an email fails to produce the expected result, the monitor provides information about the failure that can help you investigate the problem. This makes it easier to troubleshoot the automation without simply wondering why a particular customer email didn't result in a Case.
Reduce Manual Work for Customer Service Teams
Automatically creating Cases from a support inbox requires two primary records: a basic queue and an Automatic Record Creation and Update Rule. The queue receives and processes your incoming customer service emails. The rule then uses Power Automate to automatically create the corresponding Cases and connect the original emails to them. With this configuration in place, customer service representatives no longer need to continually monitor an inbox and manually recreate support requests in CRM. Dynamics 365 can handle that repetitive work automatically, allowing your team to focus more of its time on helping customers.
