Ticket Template Word
Autoguessing. The longer a ticket application is in use the more information flows through it about what options technicians are likely to select next. Is your application using this information to preselect and preload likely data including text templates button and screen workflows and the output of other applications and utilities? Is it personalising those preloads to enhance the skillset of individual technicians? Does it allow its autoguessing rules to be manually edited? Soft-required fields. Theres almost never an absolute requirement for a field. Dont prevent your technicians from completing 98% of a ticket because the one data item you marked as mandatory isnt available. Flag it if you want make it flash red or orange log it to a file to be assessed later by a supervisor or senior tech but dont force your people to spend their valuable time finding ways around your brick wall. Object attachability.
The time-strapped just want to arrive at the last possible minute and take their (good) seat. The elderly because of health or perceptual issues often have specific seating requirements e.g. up front on an aisle in the back or just the same seat they always have. They may just skip going if the event is general admission! Thats lost revenue for you. How do you comply with ADA regulations? Just save all the disabled seats for door sales? You are losing money because the person who might have committed to a ticket earlier might just decide not to go at the last minute. Difficult to track your customers. When your customers pay cash you have no idea who they are. If they pay by cheque this is somewhat better but someone has to key all that data into your database.
Too many technicians spend 90% of their time cutting and pasting when it should be automatic. Speed tweaks. Does your software allow you to change the default screen flow to suit the way your people do things? Does it keep track of how long it takes to perform certain tasks (including screenloads) and how long on average it takes for a technician to get from A to B in the interface? Does it allow itself to be adjusted to minimise these delays? Can it preload data? If not youre pretty much paying your entire team to sit around for three to four hours a day waiting for your software to stop twiddling its digital thumbs. Redundancy. Does your ticketing software use a back-end server to co-ordinate ticket numbers and store a centralised archive? And if a technicians PC loses its connection to that server or if the server goes down is the ticketing application smart enough to seamlessly switch over to non-networked mode then resynchronise with the back end later on - without slowing down anything else on the PC? Automation.