Recently I was trying out the new features introduced by Microsoft Dynamics CRM 2013 Spring ’14 release. I setup a public queue (called Support Queue) for tracking support tickets.
Thereafter created a mailbox for the Queue with Server-side synchronization for both Incoming and Outgoing emails using my Office 365 Exchange Online.
With these steps, my Support Queue was now ready for tracking support emails coming from Sales and Marketing executives (who are also CRM users for Salesforce and marketing features). Let us assume that Joe Bloggs is a Sales rep with email address (firstname.lastname@example.org) and has access to the CRM system.
Now Joe Bloggs send an email (Subject: Cannot connect to Printer) to our Support Queue email address (email@example.com). I could trace the email as Delivered in my Exchange Server.
Then I checked the CRM system and found that the email has been created as Joe Bloggs as sender and the email is assigned to the Support Queue as well. So far so good!
Now I wanted to test the Automatic Case creation feature. I created an Automatic Case creation rule for my Support Queue and activated the rule. Our intention here is to create an automatic support case when an email arrives to the Support Queue.
Then Joe Bloggs sends another email (subject : Laptop keyboard malfunction) to the support queue email address. I was able to trace this email too in my Exchange Server tracelog as Delivered.
Now when in CRM, I traced the email record which got created by the server-side synchronisation. To my surprise, I noticed that CRM did not resolve Joe Bloggs email address to a CRM user (as it did in the previous scenario); rather has created a new Contact in the system.
Hence, a same Support queue cannot be used to track support requests from both internal (CRM users) and external (contacts and accounts) support users. Queues having Automatic Case creation rule should only be usedto track emails coming from either a contact or an account to that Queue. Emails coming to such a queue from a CRM user or any other CRM queue could result in automatic contact record creation!!