Abstract: Techniques are described herein for generating service tickets. Embodiments include receiving first button data from an internet-of-things (IOT) button, the first button data comprising button identification information that uniquely identifies the IOT button and first button state information that specifies a button state, from a plurality of button states, of the IOT button, wherein the first button data corresponds to a first button press of the IOT button. The first button data is processed using a custom function associated with a service provider to cause: determining, based on the button identification information, a service location associated with the first button press; determining, based on the first button state information, a service issue associated with the first button press; and generating a service ticket corresponding to the first button press, wherein the service ticket indicates the service location and the service issue.

Abstract: Techniques are described herein for generating service tickets. Embodiments include receiving first button data from an internet-of-things (IOT) button, the first button data comprising button identification information that uniquely identifies the IOT button and first button state information that specifies a button state, from a plurality of button states, of the IOT button, wherein the first button data corresponds to a first button press of the IOT button. The first button data is processed using a custom function associated with a service provider to cause: determining, based on the button identification information, a service location associated with the first button press; determining, based on the first button state information, a service issue associated with the first button press; and generating a service ticket corresponding to the first button press, wherein the service ticket indicates the service location and the service issue.