We have recently integrated out Tess account with WordFly. After our inital list manager pull from Tess(email only). We had a large amount of constituents emails come back as hard bounces. We would like to know how other organizations handle their hard bounces. Do you treat them with an E-Market Restriction, or do you delete their email address from their constituent account? Is there another option we are not considering?
Thank you...
We aren't using WordFly but when we receive hard bounces from our e-blasts we inactivate the email address on the account. That way we aren't sending another email to that address but we can see that it was on their account at some point if it comes up during a conversation with the customer or something.
We don't use the email restrictions on the general tab for bad emails because these apply to the entire Const ID which may have more than one e-address. Instead we use 1 of the 10 available mail purposes which are email address specific. One of our mail purposes is called B for Bad Email and we track inactive/bad emails accordingly. Deleting bad or hard bounced email addresses is probably not a good idea because you will lose that data trail. You can also check the inactive box on specific email addresses once it is confirmed to be a bad email.
I'll second or third the conclusion that you don't want to interpret Hard Bounces as a full on Do Not Email restriction. Hard bounce means that the address doesn't work, not that permission has been limited.
Among the other things that we do (which I'm not sure I could recap with 100% accuracy—it's been awhile since we set them up), we add a CSI to records with bounces. The idea is that our Ticket Services staff will know to ask for a new address if they're on the phone with someone with a flagged record. The downside though, is that this does leave us with lots of open CSIs.
Jamie O'Brien
Senior Manager/Web & Digital Services
The New 42nd Street, Inc.
From: Tessitura Marketing Forum [mailto:forums-marketing@tessituranetwork.com] On Behalf Of Charles Buchanan Sent: Thursday, July 26, 2012 10:51 AM To: Jamie O'Brien Subject: Re: [Tessitura Marketing Forum] Hard Bounce interpretation
From: Aaron Wilkinson <bounce-aaronwilkinson1329@tessituranetwork.com> Sent: 7/25/2012 3:57:56 PM
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Marketing Forum. You may reply to this message to post to the Marketing forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Thank you all, these are all great points!~
Aaron WilkinsonIT SupportThe Mahaffey 400 First Street SouthSt. Petersburg, FL 33701Direct: 727.892.5727Cell: 727.744-9554
Connect with us!
From: Tessitura Marketing Forum [mailto:forums-marketing@tessituranetwork.com] On Behalf Of Beth HawrylukSent: Wednesday, July 25, 2012 7:12 PMTo: awilkinson@themahaffey.comSubject: Re: [Tessitura Marketing Forum] Hard Bounce interpretation
From: Aaron Wilkinson <bounce-aaronwilkinson1329@tessituranetwork.com>Sent: 7/25/2012 3:57:56 PM
I have a procedure that runs nightly and:
· takes e-mail addresses that have hard-bounced three times and removes the primary and marketing flags;
· changes the eaddress type from Primary Email Address or TMS Second Email to TMS Hard Bounce;
· closes the hard bounce CSI created by the procedure we set up when we went with TMS/WordFly;
· sends me output of any eaddresses that don’t match the login (we ask people to use their e-mail address as the login) or eaddresses that have been updated by constituents to receive no e-mail where the marketing flag is checked.
(We use the eaddress mail purposes for constituents to indicate what they want to receive from us.)
It was not easy (for me) to set up; but it saves me lots of time, because I was doing this manually for a while.
With no primary eaddress, ticket office reps know to ask for an update of e-mail address.
Lucie
_____________________________Lucie SpielerIT Development and Training Manager
Editor, Season Program BookFLORIDA GRAND opera