Hi guys,
I am wanting to see if anybody has developed an automated way to build contact purposes or point against a list of constituents in V12. As in this is my list number, insert purpose ID x and populate with conact point ID x
Regards
Claire
Thank you for your ideas! J
From: Tessitura Shared Reports Forum [mailto:forums-shared.reports@tessituranetwork.com] On Behalf Of Heather KraftSent: Friday, 4 April 2014 7:03 AMTo: Claire HayesSubject: RE: [Tessitura Shared Reports Forum] V12 contact management
Hey Claire -
We do this through SQL on a nightly for a couple of clean-up things, it shouldn't be too hard to modify it for a list. Disregarding all the business practices/legal questions for the moment. The actual doing is pretty easy. The only trick is going to be telling it what email to you on the account - if it is just the primary email, good. If it is a bunch of specific emails that can be identified in some way, then you are going to run into having
In fake code it would look something like: (this is totally untested and won't work to run in SQL and for the love of pete don't run it on your live box because I just wrote it up out of my head which is always a scary place, but shows you the right tables to start poking into)
INSERT INTO
[dbo].TX_CONTACT_POINT_PURPOSE
(contact_point_id, contact_point_category, purpose_id)
SELECT
distinct(eaddress_no),
-2, [This is email]
YOUR PURPOSE ID HERE
FROM [dbo].T_EADDRESS e
JOIN [dbo].T_LIST l on e.customer_no = l.customer_no
where e.eaddress_no not in (select contact_point_id from [dbo].TX_CONTACT_POINT_PURPOSE where purpose_id = YOUR PURPOSE)
and SOMETHING TO DEFINE WHICH EMAIL (e.g. primary_ind = 'Y')
From: Claire Hayes <bounce-clairehayes3431@tessituranetwork.com>Sent: 4/1/2014 5:17:01 PM
My reasoning for this particular list is Education. Contacting different people, with different address, sometime with work title others not. We have a list for our Annual education book, this took a lot of time and effort to perfect for 2014 season and we are wanting to set a EDU-Annual purpose on the points that we sent this year’s season to, hence negating the need for the manual work in the future. Also, moving forward, it will make rearranging teachers/principals, simpler for the education and ticketing teams.
From: Tessitura Shared Reports Forum [mailto:forums-shared.reports@tessituranetwork.com] On Behalf Of Beth GillilandSent: Wednesday, 2 April 2014 6:19 AMTo: Claire HayesSubject: Re: [Tessitura Shared Reports Forum] V12 contact management
Nothing has been definitively decided here at UMS, but we've discussed using Contact Point Purposes for email lists instead of Interests. I would use something like Claire described to automate moving from Interests to Contact Point Purposes.
It seems to make more sense to attach the actual email address (Contact Point) directly to an email list (Contact Point Purpose) than to 'hope' that the email list (as an Interest) makes it to the correct email address. Much clearer for our staff when a patron calls and asks to "take my prodigy.net email address off the email list" or "what lists is my aol.com address signed up for?".
Our contact restrictions are also very specific, and they currently live in Attributes. Moving them to Contact Point Purposes would be a chance to apply them directly - i.e.: do not mail to THIS address - rather than blocking the constituent entirely.
Then again, putting opt-ins together with opt-outs might lead to some confusion. Based on all this, I can see where you are concerned about departments going a little crazy with them, Levi. :)
Anyway, those are the current thoughts - I'm always interested in others' views, too...
Beth
From: Levi Sauerbrei <bounce-levisauerbrei7046@tessituranetwork.com>Sent: 4/1/2014 11:47:31 AM
We haven't really spent much time thinking about contact points, but I can see a time about a year from now where we will start getting these requests from users. Having looked at the tables for this in V12, I don't think it will be much more complicated than adding attributes en masse.
I can see this taking two forms. One would be a user accessible utility for one time updates to a large number of patrons. The other would be a scheduled database job which would update the contact points based on business rules.
One concern I have is that some departments will go a little crazy with contact points. From my perspective, you should only add the contact point if there is a compelling reason to do so. For 98% of your patrons, there will never be a need. The biggest group it would affect are VIPs, Board Members and Major Donors. These records tend to get touched regularly by the Development Department anyway. My worry would be that any automatic manipulation of contact points would step on what the Devo folks are trying to do.
If someone asks to add a contact point to a large number of patrons, I'd want to have a very long and detailed discussion about what they are trying to accomplish with the request.
- Levi
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Shared Reports Forum. You may reply to this message to post to the 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!