Hi all,
I've seen this issue at three different orgs so I'm posting here in hopes that someone has found a solution.
There is a segment of patrons who really care about their salutation - what they see on the envelope or postcard they receive. Some people don't want to see a prefix at all. Some people don't want their spouse on the label. There are many other scenarios.
Delivering on some of these preferences can be tough because "Gen Sal" so easily overrides the field based on A1 and A2 values. I would love to see a little "padlock" symbol next to Gen Sal that you can toggle on an off, but it doesn't exist.
Has anyone a good way to manage these accounts? For people that don't want their spouse to appear, we keep the spouse as an Adult Member but remove A2 - so that scenario is OK. But for many others, we don't have a solution.
Thanks in advance,Megan
Seattle Symphony
That padlock next to the button sounds like such a great idea! Have you submitted an enhancement request?
HI Megan,
Would it be possible to create a salutation type called ‘preferred’ or something similar, and then enforce organization rules on using that when pulling addresses?
Cheers, Kathleen
From: Tessitura Development Forum [mailto:forums-development@tessituranetwork.com] On Behalf Of Megan Hall Sent: Wednesday, November 04, 2015 1:44 PM To: Kathleen Smith Subject: [Tessitura Development Forum] Salutations for patrons who are particular
Thanks in advance, Megan
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development 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!
Hi Nick
Back in the days of annual enhancement voting, we put something like that ( it might have been exactly that) up as an enhancement request several years in a row, but nobody else voted for it, so it never got up.
Now that we have Interceptors, it would probably be an easy one to make - set an attribute called NoGenSal on the constituent, and make an interceptor for salutation changes that reverted any changes for constituenti with that attribute.
¿Perhaps this would be a case where someone could make one, and then share it?
Although the padlock would still be better.
Ken
I continue to fail to understand why enhancement requests are not visible and votable year-round. This would hardly be a major project--and it makes sense that when organizations have a limited number of votes per cycle, that they will naturally assign those to topics with higher priority. Then things like this get artificially buried.
Nick, I wholeheartedly agree.
Ken, thanks for the interceptor idea. I'm not familiar with that technology but have sent to IT for input. Your description sounds very promising.
Megan
We at Seattle Opera essentially do what Kathleen suggests with a special salutation type called "Salutation Exception Rule." Meaning this person doesn't conform to our nightly salutation job's set of salutation rules. In that nightly job we have it overrwrite the default salutation with this special salutation type. So every day the default/general tab salutation is replaced with the special case exception. There are a few special work-arounds to handle patrons who update their own salutation online in a way that conflicts with our special salutation type. But on the whole this does a great job of keeping those oddball salutations as you need them to be.
This still continues to be an issue for us. We want the padlock!
Me too. :)Megan
Here at Cal Performances, UC Berkeley we have a different salutation type that we use when we pull our donor mailings so that we make sure their name is correct when we send solicitations or other donor communications. This doesn't solve the issue for their general salutation, however, we don't really run into issues of people regenerating their default salutation so when their default and donor salutation are updated by fundraisers or other staff members it generally doesn't get overwritten but it's nice to have a separate salutation type to pull from to be sure. I love Seattle Opera's set-up and nightly procedure - wish we could get that set-up.
Laurel
Hi Laurel,
What do you do about canned reports? For example, something like the Event Listing Report would just pull the default salutation, correct? So you couldn't be sure that their name at check-in would be right. Let me know if I'm not understanding this correctly.
Thanks,
Amy
Unknown said: This still continues to be an issue for us. We want the padlock!
Just chiming in to join the chorus; a padlock, that the Tess client (and (especially?) TNEW) observes, would be great.
We have a custom Devo sal type, and that solves some things, but a padlock would be better yet. (We do no mass updates of salutations, FYI.)
Adding my voice as well - the idea of being able to "lock" salutations in some way is really great!
We struggle with this constantly, both within our organization and on a larger level across our consortium (where we have many patrons who are shared among organizations).
Hi Amy,
Most/many of the canned reports we use, like the Event Listing Report, pull the account household name but this may be a system configuration we have set-up, I’m not 100% sure. There are definitely some canned reports that do pull the incorrect salutation but as far as I can remember it hasn’t been an issue because they are for internal purposes only.
For the Event Listing Report, when we enter special event attendees we link the individual attendees and manually type in the name of each individual as it should appear for place cards, etc. (we have other data points for collecting/recording name info such as preferred special event host committee or program listings).
For most donors, when we create the preferred salutation type for donor purposes and then will check the box to make that the default salutation pulled but there will still be a default salutation type. Then the organization knows when doing any mass system updates or anything, to not touch the donor salutation type.
From: Tessitura Development Forum [mailto:forums-development@tessituranetwork.com] On Behalf Of Amy BrittSent: Wednesday, April 20, 2016 9:52 AMTo: lskehen@calperformances.orgSubject: Re: [Tessitura Development Forum] Salutations for patrons who are particular
Hi, Megan and Stacey:
We have the added headache that if someone updates their prefix on our web site, Gen Sal gets triggered.
All I can think of is creating a salutation type that is not the default and always pulling that when running lists/printing tickets/sending letters.
Lucie
_____________________________________________
Lucie Spieler IT Development and Training Manager
Florida Grand Opera