One of our sites had a piece of software for their facilities management that allowed them to setup a QR code to open tickets. They posted QR codes around the property that pre-filled certain fields to help the facilities management team gather relevant meta-data without the requester needing to enter it. This allowed the team to have actionable meta-data without the friction of requiring the requester.

For example, there was one posted on the external door that led to the main employee parking lot. This let anyone on-site notice that there was an issue that required FacMgmt attention, scan the QR code, enter a subject, description, and take/upload photos of the issue very quickly and easily. The FacMgmt team knew exactly where the issue was and could report on tickets coming into their system.

For other business reasons we have moved away from that solution, but this functionality has left an impression on us that this is a very effective way to reduce the friction for requesters to open tickets in the first place, but also to gather the relevant meta-data that we want for high level reporting. The FacMgmt team has moved into FreshService Spaces and is really missing this function.

As of today, there is no such functionality in FreshService. We have attempted to create an external integration with a MS Form and a PowerAutomate flow, but this introduces several opportunities for something to go wrong for a critical support channel. 

Would like to see FreshService develop the ability to generate a QR code directly to an incident request and/or Service Request, and have the ability to include certain meta-data fields by default.

It would be ideal if the FreshService admins could allow ticket submission from unauthenticated sources as well as authenticated sources without opening up the whole tenant to unauthenticated sources. This is important because many shop floor employees do not have company issued mobile devices, but they do have a personal device that could be used for simple ticket submission.