Why Microsoft Dynamics CRM Beats Salesforce.com For Outlook To CRM Integration – Reason # 4, Delay In Synching Items To Salesforce.com

In the first installment we discussed why it is so important for your CRM system not only to be integrated with Outlook but to be WELL integrated with Outlook.  We also learned that I use both the Dynamics CRM client and the Salesforce.com client on a daily basis which puts me in a fairly unique position to be able to compare the effectiveness of each.  Which brings us to…

Reason # 4 – Delay in synching items to Salesforce.com

When I want to associate an Outlook Appointment, Contact, or Task to Salesforce.com, I click on the ‘Mark for Sync’ button on the Salesforce.com Outlook toolbar.  This button does just what it says, it marks the record for synchronization to Salesforce.com.  It does not, however synchronize the item to Salesforce.com.

In order for me or anyone else to be able to see the item in Salesforce.com, I have to either manually run a sync job (which takes a long time to execute and renders Outlook virtually useless while it is running – see reason #1) or I have to wait for the scheduled sync process to run (which can only run once an hour at the most frequent and which I had to adjust to run less frequently so it wouldn’t render Outlook useless 8 times a day while it was running).

Now you may not think this is a big deal, but what if you just entered some contacts or an appointment in Outlook and marked them for sync, but the sync did not run before you quit Outlook,  no one is going to know about those items in Salesforce.com until you open Outlook again and your sync process runs, after you get back from vacation.

Contrast this to Dynamics CRM which creates the Appointment, Contact, Task, and Email items in Dynamics CRM as soon as you hit the ‘Track in CRM’ button.  No waiting, no delay.

By NexusTek – Colorado Microsoft Dynamics CRM Partner

Show Buttons
Hide Buttons