Salesforce uses "email" and "phone" as default fields if you call/email through it.
The fields that are used to populate these are controlled in NPSP by PreferredEmail and PreferredPhone.
We need a way to manage the case of a client being a juvenile or not the primary one we are contacting while still having that client's contact info and not overwriting it w/ the guardian.
Personal Email/ Personal Phone would be used for the client/contact just as they are now. (these are technically home email and home phone)
we already have a trigger to set personal email to whatever is in email. NPSP will set email to whatever is specified by "preferred email" if we set that, so we are fine there.
1) let's add that same trigger to set personal phone to whatever is in phone. Then we can use the NPSP preferred phone option safely since we will know both fields are always populated.
2) per our conversation, perhaps there is a dropdown called Guardian Contact that refers to related contacts already set.
then we would populate 2 fields
Guardian Email
Guardian Phone
w/ the email and phone of the chosen guardian contact. It sounds like you would prefer to add new fields than use the work ones. i'm cool w that,
We can then use the preferred email and preferred phone fields as intended. and have the guardian email and phone be options along w personal.
Documenting our conversation.
Salesforce uses "email" and "phone" as default fields if you call/email through it. The fields that are used to populate these are controlled in NPSP by PreferredEmail and PreferredPhone.
We need a way to manage the case of a client being a juvenile or not the primary one we are contacting while still having that client's contact info and not overwriting it w/ the guardian.
Personal Email/ Personal Phone would be used for the client/contact just as they are now. (these are technically home email and home phone) we already have a trigger to set personal email to whatever is in email. NPSP will set email to whatever is specified by "preferred email" if we set that, so we are fine there.
1) let's add that same trigger to set personal phone to whatever is in phone. Then we can use the NPSP preferred phone option safely since we will know both fields are always populated.
2) per our conversation, perhaps there is a dropdown called Guardian Contact that refers to related contacts already set. then we would populate 2 fields
We can then use the preferred email and preferred phone fields as intended. and have the guardian email and phone be options along w personal.