Hello all!
We've noticed a trend where staff will choose a generic source (walk-up or word of mouth) when unsure of the source. Unfortunately, this drastically (we suspect) inflates our walk-up and word of mouth sources.
We revamped our source codes which helped with our source code accuracy challenge. However, while ideally we would know exactly which marketing effort and therefore source brought a customer in this is not possible 100% of the time either because the customer themselves are unsure or the staff forget (or are unable to) ask during the transaction.
Has anyone implemented a miscellaneous or unknown source to use in these situations? Was it successful or detrimental? I'm hesitant because I do not want to encourage its use. Does anyone have ideas of another way to gauge the impact of these unknowns on source code accuracy?
Thanks!
Andrea
I work in a theater not in a museum environment, so I'm not sure this would apply, but you can associate each source with a different price type and set it in the correct MOS by clicking on "offers" in Performances - MOS. Your staff would have to enter the correct source to populate the correct price type. Once a price type is linked to a source in offers the price type can't be used without the corresponding source. I hope this is what you're looking for.
Hi Andrea,
I’m afraid I don’t have a brilliant answer…. In the past, I’ve looked at overall sales spikes rather than specific source codes used, because I *know* how easy it is to just select ‘word of mouth’. So if I sent out an e-blast with an offer for Show A, and then for the next few days we’re getting a lot more sales on Show A than usual, I’ll generally attribute it to the e-blast. For me, source codes are more of a general guide rather than a hard-and-fast thing.
Cheers
Kathleen
From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Andrea Williams Sent: Thursday, September 25, 2014 2:09 PM To: Kathleen Smith Subject: [Tessitura Ticketing Forum] Generic Sources and Source Code Accuracy - Best Practices?
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!
Thank you for the input Kathleen! We also watch for sales spikes, especially with our museum sales. I'm curious, have you done any analysis of the attributed spike verses the source code selections?
Regards,
Ellen, we use offers to hide many price types, especially discounted and voucher prices. I'm mostly brainstorming for our standard price types and day to day transactions. Were you suggesting hiding all price types?
Ellen, we use offers to hide many price types, especially discounted and voucher prices. I'm mostly brainstorming for our standard price types and day to day transactions. Were you suggesting hiding all price types? Regards, Andrea From: Ellen Holt <bounce-ellenholt3917@tessituranetwork.com> Sent: 9/25/2014 1:21:18 PM I work in a theater not in a museum environment, so I'm not sure this would apply, but you can associate each source with a different price type and set it in the correct MOS by clicking on "offers" in Performances - MOS. Your staff would have to enter the correct source to populate the correct price type. Once a price type is linked to a source in offers the price type can't be used without the corresponding source. I hope this is what you're looking for. 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!
From: Ellen Holt <bounce-ellenholt3917@tessituranetwork.com> Sent: 9/25/2014 1:21:18 PM