Hello! I'm curious how everyone is handling bounces and unsubscribes, from a contact permission perspective. Do you have that information synced between Wordfly/Prospect 2 and Tessitura?
My hesitation is that contact permissions apply to the constituent level. But many constituents have multiple email addresses. So it may be that only one email is bouncing, and/or they meant to opt out from a particular email address rather than their entire record.
However, because we don't have that information written back to their record from Wordfly, sometimes we are promoting emails to an account that won't actually receive it.
I'd love thoughts on this! I had asked around at TLCC this year and it didn't seem anyone had much of a solution, but perhaps there's something that's missing.
Sure, it seems to be working just fine. Our general move to Contact Permissions is treating us very well: it has radically improved the process of assembling mailing lists.
We had a "hiccup" when it came to my plan to eliminate the "unsubscribe" button in favor of being sent to a Contact Permissions page, which is that we do have a not-insignificant number of accounts in Wordfly that are not in Tessitura, and therefore can't have Contact Permissions set for them, so we do have to continue to offer unsubscribe.
Since implementation we've had a number of emails flagged for both hardbounce and for unsubscribe. It is instructive to see that a great many more customer accounts that distinct email addresses: that it to say that in a number of cases we are finding the email associated with the action on more than one account.
Great to read! apologies I missed this coming through last week for some reason.
Hi there, Gawain! A quick question - you have Wordfly syncing to these Contact Point Purposes, is that correct?
In list pulling, how are you excluding these emails?
I'm currently debating this setup, between using Hard Bounce/Unsubscribe as Contact Point Purposes OR as Email Types. I'm not sure if there's a strong argument in favor of one or the other, but I'd love to hear that.
On the one hand I dislike using Types for something like this because in engaging it you "destroy" the information contained in the original type. But to be fair this was a big problem when we used it for postal addresses and phones, and less of a problem for Emails, where I have managed to pare down the old list of email types to "Email".
Wordfly sends us response codes, and we translate those into Contact Point Purposes, but we're not syncing those Contact Point Purposes back into Wordfly. Wordfly has it's own "unsubscribed" flag, but it doesn't allow us to interact with that programmatically. What we do sync with Wordfly is Interests and Contact Permissions.
As for list pulling, we also inactivate and "de-primary" these email addresses, so they won't appear in a standard output set. With Extractions/Segmentations there's a button to check to just skip people without an active, primary contact type, but with Lists unless the user specifically queries for it they just get sent to Wordfly but without an email address to send to.