Hi all,
I'm about to start working on migrating our contact permissions from the General tab (I know, bit late to the party...).
I thought I might take the opportunity to see whether there were any learnings, hiccups or roadblocks others found whilst working through this process so that I can plan ahead for these? I'm right at the start of the process so I'm open to any advice at this point!
Thanks in advance,Liz
We're in the process of hashing this out. Right now we're waiting for Tessitura Consulting to help us with setting up the TNEW Contact Permissions Plugin: we'll be fooling around with that in Test, and that will help inform some of our choices.
A few of things:
If you want to record granular things, like "No Solicit", but you don't want "No Solicit" from an email to affect postal mailings, you're going to wind up with a lot of permissions, versus the 3-4 I think Tessitura expects you to have. Right now I'm not really seeing a way around that.
We're not planning on making all permissions available to the Account pages in TNEW: some will require direct contact from the customer via phone or email.
As nice as the TNEW Contact Permissions Plugin seems to be (it looks very customizable), what it doesn't do is visual explain permission hierarchies. So if I have a Permission that says "Email" that you say "No" to, and another that says "Newsletter", which you say "Yes" to, it isn't made explicit that you're not going to get your newsletter. We're trying to figure out wording, organization, or specific permission types to try and deal with this.
Yep - that was my issue.
The feedback is that Permissions sit on the top of the hierarchy and Interests (etc) sit below. Permissions would then be for Opt-in or out of email for you or a resident-company/collaborator (served in the purchase pathway) and you'd rely on interests page for managing Yes-to-enews or No-to-education-comms.