Presence Detection and Check In

Presence Detection and Assets with “Check In” policy set to true

The Presence Listener allows systems such as Physical Access Control Systems (PACS) to notify Tango Reserve of a user's presence event - meaning they are present in the building. This notification allows the Reserve platform to consume and process these events. Upon successful completion of a presence detection and when an Asset’s policy for “Check in” is to True, an End User’s presence event will translate to a check in to their workspace reservation in that building. This would also mean that if a User is not detected, and the User has not checked in another way, their reservations would be “bumped,” freeing that space to be available.

Examples:

• Sally has a workspace reservation at 9:00am and has not checked in via the Reserve mobile app installed on her iPhone. Upon a presence detection event, Sally would be checked into her reservation. Sally’s presence event will also be recorded and will appear in Reserve analytics.
• If Sally did not come in for the day, did not cancel her reservation and her presence was not detected, her reservation(s) would be “bumped” and thus freed for another User to utilize. This would also be recorded and appear in Reserve analytics as a “bumped” reservation.

*Check in to all is an option and may be turned on for both Workspaces and Collaboration Space assets in Reserve.

Presence Detection and Assets with “Check In” policy set to false

The Presence Listener allows systems such as Physical Access Control Systems (PACS) to notify Tango Reserve of individuals’ access events. This notification allows the Reserve platform to consume and process these events. Upon successful completion of Presence Detection configuration and with Asset’s policies set for “Check in” to be false, an End User will be able to be detected and their day-of reservations for workspaces* but will not be checked in to any reservation. This would also mean that their reservations would be not “bumped,” or be freed for use by another User. Without utilizing the check in feature, utilization data will not be gathered and presented in Reserve Analytics. *

Examples:

• Sally has a workspace reservation at 9:00am. Upon a presence detection event, Sally’s presence would be recorded and will appear in Reserve Analytics. However, her reservation would not be “checked in” to.
• If Sally did not come in for the day and her presence was not detected, her reservations would not be “bumped”, and the reservation would remain in the utilization count.

* Tango recommends that if your organization wishes to capture true utilization, to then set the “Check In” feature to true for each asset.