Best Practice for Accounts and Contacts

  • Best Practice for Accounts and Contacts

    Posted by Scott Glisson on January 10, 2025 at 9:49 am

    Hello experts. I am part of an company that is just kicking off Dynamics 365 and as we are setting it up I need a little direction for what is the best practice for this scenario… we work with many organizations that will be added as Accounts as you would expect, but we also work with a lot of individual home owners directly that are not part of any organization. We still want to capture the services we provide for them, but would we just create a Contact record for them that isn’t connected to an Account? Or, do we create an Account that is the umbrella for all those homeowners that we work with, i.e., “Homeowner Account” and then all those individuals get added as a Contact record under that “Homeowner Account”?

    Neither really seems like a good solution. Curious what someone else has done that has worked well in a situation like this.

    Thanks!

    Scott Glisson replied 1 month ago 2 Members · 2 Replies
  • 2 Replies
  • Heidi Neuhauser

    Member
    January 13, 2025 at 1:40 pm
    Up
    0
    Down Accepted answer
    ::

    Hi Scott! Just from this post, I’d recommend using Contacts not tied to an Account. Contacts do not need an Account. The only reason to tie the people to one generic homeowner Account is if you need to see a 360 degree view of everything happening to every person who is tied to the generic homeowner account. If that is unnecessary, skip the generic account.

    If you have other questions, or more info on this scenario, feel free to reply here and I’ll pop back in!

    Welcome to CRM! 🙂

Log in to reply.

Start of Discussion
1 of 2 replies January 2025
Now

Welcome to our new site!

Here you will find a wealth of information created for people  that are on a mission to redefine business models with cloud techinologies, AI, automation, low code / no code applications, data, security & more to compete in the Acceleration Economy!