So I'm trying to figure out how to conditionally require a few fields without creating stages on the Contact object. Doing that would send a lot of different processes into chaos, but at the same time we need to be able to trigger certain fields to be required at a certain point in the lifecycle of the contact, especially primary ones.
Have you had to do something similar? And if so, how did you achieve it? Was it tied to tasks or meetings booked or anything like that? One of the main problems I'm experiencing as an admin isn't necessarily in the backend setup of anything, but more in user adoption and having them actually USE it the way it was intended, so the fewer touch points for users, the better.
So we use Opportunities to track the lifecycle of a deal, it has stages, all that good stuff. Contacts we use really for just holding contact info, like you said. However, the company leadership wants me to essentially force users to be thorough in their data entry when it comes to a contact. We've had a lot of problems getting users to actually enter their data on the contact object.
As for Leads, those are not utilized correctly right now. We don't have a BDR team, so individuals aren't getting added as Leads and then qualified/converted to contacts. Everyone is just being added as a contact. I would LIKE to be using Leads the way they're supposed to used, but it's an uphill battle and I've been cut off at the knees, so-to-speak.
