Best Practice Suggestions for Business Phone...

Options
All, I am relatively new to RE (have been working with org since July of this year) but have a lot of SQL db experience so data isn't anything new to me. The question I have relates to Business phone...or really, any other phone number other than the 'preferred address' phone. For example, John Doe has a Home address, a Seasonal address, and two business addresses. As I said, I've been here since only July of this year - previous procedure has been to place 'all' phone numbers on the 'Preferred' address - so that Dev Officers and others can see all the contact info on the first page (Bio 1). So phone types of "Home", "Home 2", "Cell", "Business", "Business 2", and so forth would be used. However, in my mind, how do you know what phone goes with what business or with a seasonal address and such. I would think that each phone number should reside with the appropriate address, which means yes, for someone to get to a phone outside of the "Preferred Address" phone, they have to click into the appropriate address record. Do those of you with more experience with RE have any 'best practices' with storing varying phone types? Should all go on 'Preferred', can they go on both 'Preferred' AND 'Other Addresses', should they ONLY go on their OWN address record? Any thoughts on best practice use would be much appreciated. Thanks, Nilsen Utah Valley University
Tagged:

Comments

  • Nilsen Septon:
    All, I am relatively new to RE (have been working with org since July of this year) but have a lot of SQL db experience so data isn't anything new to me. The question I have relates to Business phone...or really, any other phone number other than the 'preferred address' phone. For example, John Doe has a Home address, a Seasonal address, and two business addresses. As I said, I've been here since only July of this year - previous procedure has been to place 'all' phone numbers on the 'Preferred' address - so that Dev Officers and others can see all the contact info on the first page (Bio 1). So phone types of "Home", "Home 2", "Cell", "Business", "Business 2", and so forth would be used. However, in my mind, how do you know what phone goes with what business or with a seasonal address and such. I would think that each phone number should reside with the appropriate address, which means yes, for someone to get to a phone outside of the "Preferred Address" phone, they have to click into the appropriate address record. Do those of you with more experience with RE have any 'best practices' with storing varying phone types? Should all go on 'Preferred', can they go on both 'Preferred' AND 'Other Addresses', should they ONLY go on their OWN address record? Any thoughts on best practice use would be much appreciated. Thanks, Nilsen Utah Valley University
    If you search in past postings this gets discussed a lot. While your instinct is correct, the functionality in RE makes things more difficult to access if you separate them into different addresses. Exports and imports become quite difficult. And if you are linked to BBNC or Luminate Online the email used for blast emails has to be on the preferred address - even if the preferred address is home and the preferred email is business. It is quite frustrating.
  • Melissa Graves:
    If you search in past postings this gets discussed a lot. While your instinct is correct, the functionality in RE makes things more difficult to access if you separate them into different addresses. Exports and imports become quite difficult. And if you are linked to BBNC or Luminate Online the email used for blast emails has to be on the preferred address - even if the preferred address is home and the preferred email is business. It is quite frustrating.
    Thanks for your response - it is very much appreciated. I'll poke around a bit more to see what has already been discussed. I do have some thoughts on this that I'll test out in a test db and after researching a bit more on what others had to say on this. I'll post my findings/resolutions if I happen to come up with a good one. Thanks again, and any other insight from others appreciated too. Nilsen Utah Valley University
  • Nilsen Septon:
    Thanks for your response - it is very much appreciated. I'll poke around a bit more to see what has already been discussed. I do have some thoughts on this that I'll test out in a test db and after researching a bit more on what others had to say on this. I'll post my findings/resolutions if I happen to come up with a good one. Thanks again, and any other insight from others appreciated too. Nilsen Utah Valley University

    I agree with Melissa, this is quite an annoying feature but all phone types really need to be on the preferred address to easily access the phones in query/export/NetCommunity etc.... That doesn't mean you can't duplicate the proper # on the proper address if you are so inclined and have the resources.

Categories