Hi All,
Wondering what you do when a contact detail has been identified as needing to be updated. We currently have a contact restriction type for this, but in v16 those are going away, so I'm working on a migration plan. And I started wondering if it's even necessary. What if we just delete the outdated information?
What do you do in your organizations? An attribute seems like another logical option, but I'm wondering if those will be left as "update" even after the info has been updated. If you use attributes for this, do you feel like your staff have been trained well enough that you can trust it?
Thanks for your input,
Kanani
You might create a Contact Point Purpose Type for it, and inactivate the Contact Point after applying it?
Is that what you do at your org?
Not exactly. We don't really have a concept of "needs updating". We do use this for "bad addresses", i.e. where NCOA comes back with confirmation that a person is not at such and such address, but doesn't give us a forwarding address, but we don't have any specific process of checking up on them with an eye to fixing them.
Thanks. Yeah, bad address/needs updating same thing--it's really just for our staff if they have the person on the phone to ask for updated information. But I'm not sure it's worth it if it's not in their face. I suppose an attribute could be added as a visual icon in the header.