Topics for Today's TUG

I was not able to attend the meeting today. By any chance, was it recorded? Thanks.

Hi Folks, 

Huge thank you to all of you for the feedback today. It's really appreciated. And also thanks to those of you that sent over feedback on various items from the call. 

To recap, please send over the following if you have exmaples:

1. How do you use traffic counting data in Tessitura with Reporting and Analytics or other functions? Specific examples of reports would be really helpful. 

2. Any further thoughts or feedback you have on AutoAttend as described. Where we landed was that MOS would be potentially enough for marking something auto-attendable, when combined with Zone Times or Doors Open/Close, and Event. We will consider Pricetype and Event Type as well. If you have specific examples of why Pricetype is important here, please do email me examples. 

Also, I heard a request for Zone-based pricing rules on the call, and did some further digging on it with the team. You can actually do zone-based pricing and messaging rules today. You select the eligible zones from the product selection screen when you are choosing your criteria for the rule. See screen shot below:

Let me know if you are looking for something else in addition to this as it relates to pricing rules and zones. 

Thanks again, and I look forward to speaking to you again soon!

Chris Szalaj

Product Owner, Business Facing Products

Tessitura Network

Update from Tessitura Network <4U5MGFAOSK7O-jpg_2D00_70x70x2-jpg.jpg> Chris Szalaj Hi Folks,  Huge thank you to all of you for the feedback today. It's really appreciated. And also thanks to those of you that sent over feedback on various items from the call.  To recap, please send over the following if you have exmaples: 1. How do you use traffic counting data in Tessitura with Reporting and Analytics or other functions? Specific examples of reports would be really helpful.  2. Any further thoughts or feedback you have on AutoAttend as described. Where we landed was that MOS would be potentially enough for marking something auto-attendable, when combined with Zone Times or Doors Open/Close, and Event. We will consider Pricetype and Event Type as well. If you have specific examples of why Pricetype is important here, please do email me examples.  Also, I heard a request for Zone-based pricing rules on the call, and did some further digging on it with the team. You can actually do zone-based pricing and messaging rules today. You select the eligible zones from the product selection screen when you are choosing your criteria for the rule. See screen shot below: <Zones-jpg_2D00_600x0-jpg> Let me know if you are looking for something else in addition to this as it relates to pricing rules and zones.  Thanks again, and I look forward to speaking to you again soon! Chris Szalaj Product Owner, Business Facing Products Tessitura Network View online   You received this notification because you subscribed to the forum.  To unsubscribe from only this thread, go here. Flag this post as spam/abuse.

Hi Dan Ruth! Today's MZATUG meeting was not recorded, but we have captured a few notes from the Lean Coffee Discussions MZATUG 5.27.2020 discussion summary.pdf. Hope you can join the group for their next meeting scheduled for June 10th dedicated to discussing Timed Admissions. Cheers!

Hello Chris Szalaj and everyone,

Sorry I wasn't able to make the meeting yesterday, but I did want to add in my twopennyworth on a few of these items...

1. Auto Attendance - I might have got the wrong end of the stick here, but we've built a custom utility that will mark any tickets booked in person on the day as attended to avoid the need for scanning tickets when people are buying at a ticket desk on the day

2. Visitor Counts - We use Intelligent Counting to capture the number of visitors who enter the museum.  This data is then input into custom tables in Tessitura alongside daily visitor and income forecasts which we can pull through to Tessitura Analytics.  Our museums are free to enter with a number of paid for exhibitions and attractions, so having that data in Analytics allows us to track against daily forecast, monitor spend per head etc.

3. The only other admission based challenge we face (which I posted in the Response Readiness forum https://community.tessituranetwork.com/tessitura_software_forums/f/response-readiness/25352/allowing-only-one-family-group-to-book-a-timeslot) is around holding time slots off sale once one group has booked into them to help us effectively manage our small capacity attractions such as simulators.

Thanks very much

Grae

Good morning,

I'd be interested in learning more about this Auto-Attend utility. Could you share some details?

Hi Nathanael Pearson

Our Auto-Attend 'utility' is a SQL stored procedure that we've set up to run as an overnight scheduled job.  It looks for any tickets that were bought using our in-person modes of sale for events on that day and updates the relevant ticketing tables in Tessitura so those tickets appear as if they had been scanned with an NSCAN device.  It doesn't fake a scan, just marks the ticket as attended.

Does that help?  Are there any more details I can help with?

Grae

Hi Chris Szalaj

I also wanted to add in something here about taxes (as I can't post in the Canadian forum).  We've had challenges with using price layers to separate out VAT for ticketing.  The reason we don't use it is that you can’t do fractions of a pence, which is essential if we were to use Tessitura to calculate taxes on memberships and if the proposal is for a similar solution to be rolled out to ticketing in future versions.

Not sure if that's totally relevant here, but I thought I'd include it in the mix.

Thanks

Grae

It is relevant, thanks, and something I hadn't heard before. It also may be difficult to implement as our transaction amounts are defined as the money data type in the database which only goes to 2 decimal places. Ideally, how many decimal places would you want the calculation to go to?

Hey Mark Rhodes,

We've had a chat about this internally and the consensus is 8 decimal places.  Happy to talk through the challenges we've faced with using pricing layers to calculate taxes if you need any further details.

Grae