
Need advice on establishing an MS Dynamics CRM 2011 physical data model
I’m looking for advice on establishing an MS Dynamics CRM 2011 with a Physical Data Base that will support two distinctly different customer groups that need to be handled and processed quite differently.
There will be a common contact centre who will provide customer support and some back office processing on both groups of customers.
The first is for customers (currently over a hundred thousand) who are “Organisations” having the usual contacts … plus the additional custom information entities that will need special workflows and business rules applied … there will be several key “types” of the Organisation customer and each will have discreet sets of additional information associated, but they may belong to one or more sets of these key types.
The second customer group (growing to several million) is as “Individuals” who will need to have their “life time” record built up over an extended period (starting from age 15 so will need strong data access security) with regular interactions over several years.
Have you seen this successfully implemented ?
What works well in these situations ?
Can you help give us advice ?
*This post is locked for comments
I have the same question (0)Hello,
CRM 2011 workes perfectly for this type of set up.
"Accounts" will handle the first groups of customers and "Contacts" will handle the individuals. The customer support team will be using the Case Management capabilities of CRM when working with these two groups. You can create two different forms for cases, one form will handle the fields regarding Accounts and One form will handle the fields regarding Contacts.
Here at Zero2Ten we have done many (300+) of these implementations and if you would like more detailed information or help, you can send us an email to info@zero2ten.com
Thanks.