Push Button. Get IT.
The potential power of a single button is vastly understated. It can be a centerpiece of modern innovation (see iPhone) or a quick way to get a Diet Coke (citation omitted 🙄).
Recently, a group I work with has been trying to optimize support for 50+ meeting room spaces. For any team this responsibility would be no easy feat, but it’s compounded by challenges that can only be described as human.
As an example, Sarah is experiencing a display issue in a conference room preventing her from sharing her screen:
- Sarah calls the IT hotline to request support.
- The support line is busy, so she sends an email to IT requesting assistance.
- A technician from IT responds to the email and inquires which room Sarah is in.
- Sarah replies with an estimated location and IT dispatches a support engineer, only to discover they’ve been directed to an incorrect location.
While the above scenario is a worst case scenario in many ways, any one of those missed connections can delay resolution for precious (and painful) minutes.
Instead, imagine a similar scenario where once again Sarah is experiencing a display issue:
- Sarah pushes a small button conveniently located in the center of the table.
- The button triggers a service that sends a push notification preconfigured with the button location, to a group chat with all the on-hand support technicians.
- A technician claims the call and dispatches to the room to resolve the issue within a minute of the button-push.
You can see how the button might actually be a step up from a help desk call number or email address for on-hand support requests. So how do we get there?
Staff need a quick way to connect with IT and share their location.
Using a combination of Flic buttons and Microsoft Flow, pull together a system that pings available technicians in Slack.
Pre-deployment Flic buttons