I would like to know how your organization handle cases where customer A and customer B have a subscription together but the subscription they share is on customer A's record. Does your organization track such information in special requests at the lineitem level, or in associations, or somewhere else? What's the good and/or bad of doing it your way?We want to start tracking these cases with an eye toward treating customer B as a subscriber, and would like to hear your perspectives.
Thanks very much.Matt
Good points, Heather. To handle the gaggle situation my answer was to create multiple line items (one for each member of the gaggle), but that is pretty kludgy.
So if somebody stops sitting with somebody else, you just inactivate or put an end date on the association, I take it.
From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Heather KraftSent: Thursday, May 05, 2011 11:32 AMTo: Matthew HoytSubject: Re: [Tessitura Ticketing Forum] "Sitting Together" situations.
I think why you are seeing the overwhelming use of associations is that the association is easier to see at a glance, and is an easy way to put something in a header to alert the box office that there is a 'sits w'. It also requires less digging if you are in the main account and not in the actual order module.
The other reason is that we often have groups of sits w and the special request only allows for one other account to be tagged. We have gaggles of ladies and some have seats in their own account, some share, etc. It can get to be quite complicated trying to keep track!
- Heather
From: Matthew Hoyt <bounce-matthoyt5455@tessituranetwork.com>Sent: 5/5/2011 8:48:33 AM
So everybody's doing it the association way? Hm.... I was guessing the line item/special request method was the way to go since it offered more granularity, but maybe I'm over thinking things.
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing 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!
Exactly - because most of the sits w scenarios are dealt with in person or over the phone (we don't have anything coded to handle those situations online) we really were looking for a tool that the our front end users to be able to access quickly.
At the time of renewal we know to check the sits w and if they don't renew, we put an end date of the current season. We have a constituency that forms from this association and that automatically gets updated nightly which signals the box office to look (or ask about) a sits w.
I should note that we have two 'sits w' types of associations - one is just sits w/ and one is attends w/. We use the two attributes to show the difference between multiple patrons who sit together but all have tickets in their own account and those 'ghost people' who want all the mailings and the like, but don't actually have tickets in their account.
Which brings me to mailings - way easier to pull those 'ghosties' and make sure your show info/announcements/etc get to them via an association than it is to do it through special requests on an order.
HTH,
Heather
Hi All: We created a Co-Subscriber constituency along with an association type of Current Co-Subscriber. The end date of the consituency is the date of our season, unless there are specific reasons. These constituents can exchange tickets, get re-prints, etc. One advantage of having these folks easily identifiable is that we have the ability of suppressing them from list pulls along with any current subscribers should we be making offers we might not want to market to subscribers.
Best of luck!
Kindly,
Mark