Hi all,
We’re new to packages so might be missing something simple (hopefully!). When trying to return a package, which has two performances- one with a ticket that has been printed and one with a ticket that hasn’t been printed- we’re hitting a roadblock.
In the subline items we can return the ticketed event but we can’t delete the non-ticketed event (the non-ticketed event is a GA performance which we sell to everyone through the door, but it is set up for the ticket to never print, to save on ticket stock). The message we get when trying to delete it reads “Package subline items cannot be deleted from the subline view. Entire packages can be deleted from the Lineitem view”. However, when you click delete in the lineitem view, the error message reads “One or more of the rows selected is ticketed and cannot be deleted”.
Any ideas anyone please?
Thanks,Alison
Hi Alison,
We've encountered similar issues in the past. From our end, when returning a package like this, we needed to go to the seat map then ensure that the seats are de-selected in all of the base seat maps leaving you with 0/2 in each of the seats assigned/seats needed section of the performance list.
I hope this helps.
All the best, Aoife
Hi Aoife,
Thanks for your response.
As the packages we have are flex packages, they don't have a base seat map unfortunately.
We are actually dealing with the exact same problem this year. We have a dummy house as part of our packages that we obviously don't want tickets printing for so we set them up not to print when we printed the rest of the subscription tickets.
Unfortunately, the only way I have found to completely return the package is to go into my setup, assign a ticket design to those performances, print them, return the package, then go back in and remove the ticket design from the performances again.
To make it a little mor manageable, I get the entire box office staff to record the returns they need, then once a day, one person goes in and does them all at once. there is usually some overlap in the dates that need to be printed which reduces the time spent on this.
If you have any more specific questions about how it works, I am happy to help or if anyone else has a better solution I would love to know it.
We set up a 'FAKE BOCA.' This allows are team to 'print' a ticket (least according to the system) and then be able to return said ticket. Tessi thinks the ticket is printed and we don't waste our ticket stock, so win win.
Hope that helps!
-Krys
Hi Joshua, Krys,
I ended up getting some help from the Tessitura team on this one. We thought about changing the ticket design, but that wasn't feasible for us as tickets would randomly start printing for other orders too. We also strongly limit who has access to change the ticket designs.
Here’s our solution:
Go to Season Manager and then Batch Ticket Printing. When you click on the “Add” we then fill in the fields in the “Setup” section (can leave the rest of the fields on their default), then select the appropriate package. From here you click “preview” and then select “print to file” and “print”. You just have to save that file somewhere and then it thinks it’s printed (without printing any ticket stock).
We’ve used it a few times now and it seems effective, but is a little time consuming if you’ve got a queue of visitors waiting. We have a number of people in the organisation who we've trained to be able to do this process though, which makes it much easier than changing ticket designs.
Alison