Hi Everyone:
I'm looking forward to joining you later for the User Group meeting. I have several things that I'd like to cover with the group:
Several of these things we'll be moving through quickly, so while there are several items I don't think we'll need more than the 30 minute allotted. I'm posting this in advance in case you have a few minutes to look at the links above prior to the TUG meeting.
Thanks!
Chris Szalaj
Product Owner, Business Facing Products
Tessitura Network
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
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
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.