For us it would be of help, if matukio yould assist us better with the noshow problem.
Ideas:
- Noshows can be entered into the database by typing the booking number (from the signature list), or by scanning a qr-code (by mobile phone) which calls the noshow-plugin with the booking-number. Of course, the user would have to login first on the website using his normal browser, or you sould encrypt and enlarge the booking number in the code so that no "accidental" entries happen.
- Statistics: Definable time range, total number and percentage. Statistics on Event, Event-Categories, Veranstalter, Event-Place, per User: How many bookings, how many noshows...
- Invoice for noshow: Send bill by mail or print or export the necessary address information. Our events are usually free, but in case of no-shows we sometimes try to motivate....
- BTW: The sort order on the statistics page should be the other way round. I do not care for events some years ago in the first place. So 2016 - 2015 - ... - 2009 ! and then the Total would be more practical for me.
Btw: Is there any real use for the qr-codes printed on the signature-list?
The mobile phone scan thing would also help to enter the "showers" instead of the no-showers.
