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
At my previous organisation, we used to have an eaddress type of "Hardbounce". The e-address was shown in the header and was set to display in red if it was of this type - as a visual cue for the operator to request clarification the next time someone spoke to the customer by phone. By leaving the eaddress in place, the operator is able to see that we had a bad address on file as customers will argue that their address is correct when in fact they have made a typo.
As an aside, the eaddress was displayed in blue to indicate that a)the address was good and b)that they had signed up to receive the e-newsletter. Another visual cue for the operator.