Hey team, @Geovanna Pazmino, long time no see! @Jonathan (Yoni) Deutsch, we are still close in this group! I saw some of the videos there, and it is not clear to me the reason that we are treating a NDIS Client as a "Contact". For me, it would make more sense to assess them as an Account. So, I have some questions:
(1) Do you have different Contact Record Types for their Parents, Legal Guardian, or who is performing the services? Or do you simply have just one Contact form that shows everything to every contact even though they are not clients ? -- i.e. suppose we are creating a Client's Father contact , if we don't have different record types, then the Father will have a field "NDIS NUMBER" which might be unclear for the user
(1.1) Do you recommend to create additional record types for Contacts?
(2) if CPQ can consider "Client Account", can we create a special Record Type for Account and relate services to the Account Client (of course, connecting the Client's Household as a Field in Client's Account)? Or does CPQ need that we treat the Client as a Contact? #Best Practices
(answering 1.1 based on PowerOfUs -- Contact (force.com)) This is for EAD , though still applicable for NDIS, do you agree?
"Contact Record Types Because a Contact can play multiple roles at once—an alumni of one program, a current student in another program, a tutor, and also a sports team member—we don't provide record types out of the box. Creating custom record types that don’t conflict with each other can be tricky, so in general, we don’t recommend it. If you do create them, make sure they're for Contacts for whom only one record type applies. To track a Contact's roles with various organizational entities, consider creating Affiliation records instead."
