Skip to main content

Basic Info

When editing an amenity, Basic Info tab has the following options.

  • Name and Description: Unique name for the amenity or asset, and a description which is visible to users when selecting the amenity.

  • Active: Whether users can book the amenity or request access to it at the moment. When the toggle is turned off, Deactivation Reason (for example "Under repair") can be entered so users know why they cannot access the Amenity.

  • Max Capacity: Maximum capacity of the amenity. For dedicated amenties, users cannot enter a value for number of people (or "Head Count") beyond Max Capacity. For shared amenities, no more reservations than this value can be made at the same time.

  • Slot Size: Smallest unit of booking or access by users. When defining schedule for the Amenity, each availability will be at least the duration set here. The default is 60 minutes because it matches the minimum duration that an offline PIN code can be generated for igloohome smart locks. Please note that for slot sizes less than 60 minutes, the system might be unable to generate an offline PIN code, but users can still use WiseIngress mobile application to unlock the smart lock via Bluetooth.

note

Updating Slot Size doesn't affect existing bookings and PIN codes generated previously. It is important that it is set carefully at the beginning with business requirements in mind.

  • Notes: Any text that should be visible to users when viewing details of the Amenity. For example, it can include instructions for using the amenity, or rules and regulations.

Terms and Conditions

Terms and Conditions section allows the administrator to define whether a waiver or user agreement should be displayed and accepted during the reservation process. This feature is useful for equipment rental, vacation rental, and other use cases like reservations made by tenants where users need to read and accept a binding document before gaining access to the amenity or asset.

  • Accept Type: There are multiple options to set the behavior of system regarding terms and conditions document:
  1. Not required: Terms And conditions are not presented to the user during booking process. It is useful for scenarios where the administrator doesn't see the need for the user to read and accept terms and conditions.

  2. Every reservation: terms and conditions content will be presented to the user every time they try to make a reservation. Even if the same user has made reservations for the same immunity or resource before, the system will still require the user to accept the contents of terms and conditions.

  3. First reservation for this amenity: terms and conditions content will be displayed to the user only the first time they are trying to make a reservation for the current amenity. If the user has made a reservation before for the current amenity, this step will be skipped during reservation process. This option is useful for scenarios when there are are multiple amenities under one location, but the nature of these ammenities are different. So, if the user has accepted terms and conditions for another amenity under that location before, it doesn't mean that they should not see, read and accept terms and conditions for the current amenity during booking.

  4. First reservation for this location: terms and conditions will be displayed to the user the first time they are trying to make a reservation for any of the amenities under the current location. For any subsequent reservations for any of the amenities under the same location, terms and conditions content won't be displayed to the user. This option is useful in scenarios when all amenities or resources under one location are of the same nature, and the administrator decides that if the user accepts terms and conditions for one of the amenities once it can be applied to all other amenities under the same location.

User Actions

Users may need to perform certain actions for a reservation they have made. To enable user actions for an amenity, the administrator can turn on Enable toggle. Then each type of action can be enabled or disabled individually.

When user actions are enabled, the text message sent to the user after successful reservation includes a special link. Tapping the link opens a page in user's mobile phone browser which displays available actions to perform. Currently, two types of user actions are supported both of which are more likely to be used in scenarios when paying deposit is required for making a reservation.

  1. Report Damage: allows the user to submit up to three photos and some notes/comments for damages they observe before using the amenity or resource. Reporting damage is allowed for 30 minutes from start time of the reservation. This feature is useful for many scenarios including equipment rental, vacation rental, and tenant and contractor access to building amenities.

  2. Return equipment or checkout: when this option is enabled, the user can submit up to three photos to prove return of equipment or checking out from the amenity (and locking it using the smart lock). In addition to photos, user can also provide feedback in terms of stars and some notes/comments. User can use this option any time before end time of the reservation (plus any grace period defined for Bluetooth access).

tip

Photos and notes submitted by users can be reviewed by administrator from Schedule tab and from Reservation Report.