Hello everyone!
We are bringing on a new organization to our Consortium and today we discussed the use of QuickSale. They have a cafe/small restaurant style setup rather than a standard concessions and so they had some specific questions on how the following might be/could be handled. Thought I'd throw it out there if anyone has any thoughts or ideas:
1. Running open tabs: Folks like to purchase but then pay at intermission or the end of the night, leaving a CC or something but not closing out the tab until later. I know that orders can be left open without payment, but how easy than from the TRBO QuickSale set up is it to retrieve those orders? If using the GenPublic setting too so you don't need all Constituent information, how do you differentiate one order from another.
2. Gratuity: How can folks add gratuity after the payment is made, or can it only be added before hand with a button?
3. Table #: They do use a table # system if folks are ordering food for it to be delivered, anywhere on the order this could be added (again working in the TRBO QuickSale setup). I didn't see notes on the screen.
Thanks for any feedback!
-Maureen Cotellese
Hi Maureen!
1: Open tabs. Is there a reason you need to use TRBO to process their payments as well, or can they have a stationary location that is set up to use the full Tessitura application? Servers could add orders in TRBO, they just wouldn't be able to re-open them on a tablet. Sort of in the check-out style of a diner, where the payments are all processed at a central register. I would def avoid general public accounts. (Wouldn't most in attendance already have an account, since they have purchased tickets?)
2: Gratuity. If you don't mind standardizing gratuity options, you can add a button for gratuity options in Quick Sale. They wouldn't be able to enter any amount, but they could select from flat amounts ($5, $10) If the gratuity can be manually added at the register within the full Tessitura application, you can build it as an editable fee so that the cashier could enter whatever the patron desires.
3: For table numbers: that depends on how many tables they have. If it's a small cafe, you could build unique buttons for each item for each table. That way, the server would select "Table 1 Asian Salad" or "Table 6 Cola," etc. For a bigger restaurant, you could set up Navigator buttons for the initial Quick Sale screen, so they would navigate to "Table 1 Options" before selecting food or bev for Table 1. If they plan to print tickets from a Boca, similar to restaurant tickets, you could use different price types (and therefore different ticket designs) for each table.
I hope this helps a little, it sounds like you have quite the adventure ahead of you!
Best,
Darryl