Temp Tabs Setup to keep Customer Entities Clean for Regular Customers [4K with Voiceover]


#1

USES: Ticket Tags, Display Ticket List & Ticket States

So I thought I would share a simple little setup I did for a couple of the local bars I do tills for to help avoid using Customer Entities for short term temporary bar tabs.
This saves having a cluttered customer entity list full of names which will not be used again.
Using the ticket tag it allows the ticket to be closed without an entity and the display ticket list allows you to view and recall the open ‘Temp Tabs’.
I also upgraded the setup for my original quick onsite solution to also include an ‘open’ Temp Tab count on the automation command button.

Hope the new mic makes for better tutorial :slight_smile:

Tutorial Video

Did you find this video useful?

To gauge the value of and demand for a possible new video tutorial section please mark if you found the video useful and would like to see more. [poll name=poll] - Yes - No [/poll]

V5 - Bar Tab Setup
Few Pre-Purchase Questions
Layaway/Switch User with Login Prompt and Ticket List Tutorial [4K with Voiceover]
Documentation for Version 5
How to create tabs with names without creating customer accounts?
Customer Loyalty Points Setup [4K with Voiceover]
Help me debug an error following the Temp Tabs Tutorial, please
How to edit table names when getting an order
Custom Command Button "New Orders" not returning from Menu
Name on (kitchen) Ticket
Force Staff to enter ticket note (NAME) before closing ticket
#2

Other Tutorials


#3

Reserved for updates…


#4

Tutorial video uploaded, 4k quality I think is still rendering on youtube servers or isnt showing as this pc isnt 4k but 1080 is ready.
Audio defiantly allot better with the new microphone :slight_smile:
This is another on the fly voice-over, speeds the process up allot recording audio as going through.
Didn’t do the zoom ins as suggested as would have taken a long time and my final cut skills are still fairly basic.
Also didn’t cut out mistakes etc as think it helps users see how to problem solve.
Let me know your thoughts or any questions.


#5

Thanks for the video, works perfectly. Is there any way so the current temp tabs are visible only for current user? Thanks


#6

Haven’t tried but might be doable.
Check the ticket list action parameters and see if a second filter can be applied.
I did it this was on purpose so that at end of day if someone has left a tab open it is visible for whoever is cashing up, else they have to try and find it in the main ticket list.


#7

Thanks the video is really helpful. keep up the good work


#8

Great tutorial. I have watched this several times and have followed it to every detail. I got the tag part to work, but the temp tabs screen which shows the open tabs will not fire. i was using the table entities to save my bar tabs. I think this is the problem but cannot figure that part out. Any help?




#9

Your trying to get a list for Temp Tags but the ticket tag is Tempt Tabs.


#10

I removed the table entities and create tickets without assigning an entity. It works fine now. Thanks


#11

Arrr, yes, that would be because the selection of an entity creates the ticket meaning that there is always a ticket started for your flow when you can see the button.
The temp tabs isnt really needed if you force table selection as ticket creation method as you would have already selected an entity by that point.
You could work around if preferred by changing the action constraints to something else.


#12

This could be useful for if you have multiple people at a table with separate tickets. I created something similar a while back but am no longer working with that setup but this way seems to be a good way of doing the same thing!


#13

JTRTech, is it possible to assign the bar tab to a loyalty customer entity instead of always entering a customer name? ex.(If I have a loyalty card customer loaded on the ticket screen and they want a tab, I need to figure out how to have temp tabs recognize the entity, bypass the customer name input screen, and then assign the LC entity to the temp tab automatically.) Any help would be appreciated.


#14

But if you assigning an entity you dont need temp tabs. The ticket can be closed on a customer/loyalty card etc entity without the need for temp tab ticket tag.
The temp tag setup is for senarios where you dont want to create an entity for a one off tab.
If they are a returning customer with entity be it loyalty card or customer entity you just need to use that and use the entity screen to see open tabs for those customers.


#15

Ok. Just tested that and you are correct. Thanks


#16

For that type of entity screen your best to have a state filter rather than a fixed grid like you would tables - think thats how customers is by default anyway.
That means it only shows entityes with open tickets rather than all like tables since you would typically/eventually have too many entitys to have a grid layout that was useable.
Typically you would have a state filter enity screen to show open ticket entities and a search screen for selecting entity for new ticket (again how customers is by default I think).