We're finalizing our plans for WordFly implementation, and this is the first time that our email database will be in Tessitura and fully integrated.
How does your organization handle bad email addresses in Tessitura and why? Do you:
- Delete the bad email address from Tessitura totally- Mark the bad email address inactive- Mark the bad email address some other way
We want to make sure that we're making a good decision on what to do with bad email addresses and are curious how other organizations handle this.
Thanks!
Eric MuellerWebmaster & Social Media GuyScience Museum of MinnesotaEmail: emueller@smm.orgPhone: (651) 221-9455Twitter: @sciencemuseummn
We add a "Bad Email" attribute which then puts a red "Bad Email" sign on the header and then when have an extraction which removes them from future emails until the attribute is removed.