Update address/phone/email flagging

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

Parents
  • Dropping a line to follow this conversation too - it sounds like we have a system similar to yours, Kanani, where the mail/phone/email dropdowns on the General tab have options built that indicate whether that contact channel needs verifying or updating. But as we look ahead to v16 I agree that it seems like we can find other solutions. If a contact channel is actively wrong (i.e. a phone number belonging to someone else) then deleting it entirely seems like the safest way to ensure it doesn't cause future trouble; and if contact info was once correct but no longer is, inactivating it and replacing with either nothing, or an 'Unknown' street address, seems like it might be able to capture the same story that the 'update me' restrictions currently do.

    I wonder if one could set up an attribute, header element, etc. that refreshes overnight and tags accounts that are entirely missing an active phone number, email, etc. so that customer-facing users have a reminder to try to get one, but it removes the risk of a manual 'update me' attribute hanging about even after corrected contact info has been gathered.

    We use meta-Contact Point Purposes (for lack of a better term) a bit right now, where unsubscribes in Wordfly get pushed back as a purpose applied to the related email address. I like this system since it ties things to specific emails, not the whole constituent. Haven't given much thought to how to use it beyond emails right now, though!

  • Ooh, that's a really great idea to use CP purposes for unsubscribes.  I'm going to have to talk to our marketing team and see if they agree with that direction.  I've often thought it's annoying that you can't see in the contact log which email was used for the unsubscribe.

Reply Children
No Data