Folks,
We're looking to change the way we mark constituents when a piece of hardcopy mail is returned to sender when sent to a physical address. Using an RTS Contact Point Purpose to attach to the address seems the most logical thing rather than (as we currently do) attach an RTS Attribute or use the Mail Restriction element on the General tab. This is because we have many constituent with multiple, different addresses and we only want to flag the address that is not useable.
How are other people managing this - and if you use CPPs, how do you work with them in Extractions?
Martin
Hi Martin,
We change the Address Type to Returned Mail and suppress anyone with that address type from our extractions. We are also looking at adding a flag to the Constituent Header as a prompt for our ticketing hosts when the customer calls next, but that part is still to do.
Kelly
In order to record people that opted out from our promotion emails, we use “Opted out” contact point purpose. The reasoning was the same as your, people might have multiple email addresses and only opted out from one of those addresses.
Fernando Margueirat Senior Business Analyst The National Ballet of Canada 470 Queens Quay West Toronto, Ontario M5V 3K4 P: 416 345 9686 x453 F: 416 345 8323
http://national.ballet.ca
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Martin Keen Sent: Thursday, August 25, 2016 2:55 AM To: Fernando Margueirat <FMargueirat@national.ballet.ca> Subject: [Tessitura Technical Forum] Contact Point Purposes - Return to Sender
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical 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!
We have been using an attribute at the moment (but there have been at least two systems prior to that over the last few years!). But I do like the idea of doing it as a Purpose, especially if people have multiple addresses. I should suggest that to the team!I have, however, adjusted the header so that it throws up an obnoxious pointing finger "Return to Sender" graphic right over the top of the constituent header if there are any return to sender attributes which is designed to encourage the Box Office to get correct address details if they have the person on the phone.
We have been using an attribute at the moment (but there have been at least two systems prior to that over the last few years!). But I do like the idea of doing it as a Purpose, especially if people have multiple addresses. I should suggest that to the team! I have, however, adjusted the header so that it throws up an obnoxious pointing finger "Return to Sender" graphic right over the top of the constituent header if there are any return to sender attributes which is designed to encourage the Box Office to get correct address details if they have the person on the phone.
From: Fernando Margueirat <bounce-fernandomargueirat4910@tessituranetwork.com> Sent: 8/25/2016 1:35:02 PM