So users hit a physical button at the classroom so they can get assistance with the AV/Computer equipment. A team gets an email and they go to the classroom to troubleshoot. Meanwhile, our servicedesk creates the ticket to be documented and assigned to that team. I want to cut out the Service Desk in the creation of the ticket. The problem with the button press, it is pretty dumb, and if users spam presses the button more than once, mutiple emails go out at the same time.
In my current flow it will create the ticket, but multiple tickets will get created, I would like to include some logic to prevent or ignore duplicates emails for a certain time peroid since at minimum of about x minutes, and then after x minutes tickets can be created for that classroom again. The subject of the email will be something like this:
"NRC Message: User pressed AVHelp in CB 202"
The last bit is the building and room number, which can be different, about 60 rooms or so.
