Personalized Community is here!
Quickly customize your community to find the content you seek.
Check out the latest Sales updates!Learn about the key capabilities and features of Dynamics 365 Sales and experience some of the new features.
Dynamics 365 Sales in 2022 release wave 1
2023 Release Wave 1Check out the latest updates and new features of Dynamics 365 released from April 2023 through September 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I am new here and was hoping someone could point me in the right direction for this. My company is implementing D365 Customer Engagement and I am looking for advice on how to keep prospect files separate from customer files on the contact form.
We have customer files that pull over from a integrated solution on a daily and weekly timeline and are loaded/updated in CRM as Contacts as we sell to individuals not companies generally speaking. We are also looking to have leads come into CRM from multiple points that we will qualify as Opportunities and thus create a contact for. My question is as both these are contacts what are the best practices to keep them separate in the CRM for marketing, outreach, reporting etc. and what is the best practice to reconcile the to contacts when a CRM on Contact is also added into our integrated solution and becomes a customer.
Hope that makes sense and thank you for any help you can offer.
Hi Jordan, I had the same issue for a customer I was working with except that we needed this for accounts. For contacts I would use the oob field called "relationship type" with the options of prospect and customer and make it a required field. That way you could create a new view showing all contacts that have the relationship type = prospect and another view all contacts with relationship type = customer. Or just filter the all contacts by adding this column to a view.
You could also create separate contact forms for prospect or customer.
I also created a business rule that when a lead is converted into a contact to set the relationship type as prospect.
I also locked the "customer" on relationship type with field level security, since they were populated by a back end system. Not sure if this would be your requirement?
Thank you for your query.
I would use the same way as Debbie explained.
You can use the existing option-set field name Relationship Type (customertypecode).
Add the following options as per your need (out-of-the-box these options are not added):
Few more points to help segregate the two contact types:
Business Applications communities