Setup guide – LivionKey

Background:
Because there are many components in motion, we've compiled a list outlining requirements, clarifications, and areas of responsibility to ensure the seamless integration between Inlet and the lock system.

Read more about the security principles for Inlet and the connections to locks here.

Practical and Technical Requirements:

1. Locksmith/installer/customer mounts the LivionKey devices.
2. The customer must request an API credentials to their LivionKey system from the Livionkey automat supplier
3. Inlet must receive:
   • LivionKey API Username
   • LivionKey API Password
   • List of Device ID's
   • List of Lock ID's
4. Inlet then retrieves the devices and keys to configure this in Inlet.
5. Inlet provides information to the top system/booking system that they can test.
6. Inlet requires at least 2 weeks of testing with the top system/booking system after the installer has completed the above points.
7. When customer buy more Livionkey devices they inform Inlet to configure the new devices via the same API credentials

Good to know

Key Return Status and Notifications 

Livionkey simplifies key management by offering tools to monitor whether keys have been returned or remain unreturned, providing timely notifications and follow-ups to ensure smooth operations. By streamlining the key return process, Livionkey helps Inlet's customers maintain efficient operations and deliver a better experience for their guests.

Configurable Notifications

• Thresholds for Overdue Keys: Property managers can configure when to be notified about overdue keys. They can decide how soon to receive notifications after a key is due but not returned—immediately after checkout or after a specified grace period.

• Checkout Confirmation: When a guest checks out and returns their key, Livionkey notifies the property manager. This confirmation signals that the accommodation is ready for cleaning or preparation for the next guest, ensuring a seamless transition between bookings.

Note: A default checkout time can be set in Livionkey, but this will be overwritten by Inlet when using the API to set up the from/to contract. This is important if a customer doesn't understand why the default time isn't used for notifications.

Code Validity After the End of the Contract

Inlet sets the contract's from/to times in Livionkey, which overwrites any default checkout time if set. Normally, an access code is invalidated when the "to" time passes or the customer checks-out, preventing the customer from returning the key. There are two ways to manage this:

1. Key Return Grace Period

This refers to the additional time allowed after a contract ends during which a guest can still use their assigned access code or key return system to facilitate smooth checkouts.

• Configurable Duration: Property managers can set the length of the grace period (e.g., 1 hour, 12 hours, or 24 hours) based on their policies and operational needs.
• Benefits: Ensures guests can still return keys and access the property for last-minute tasks even if the contract has ended.

2. Use of Static Return Codes

In Livionkey, static return codes are predefined, unchanging codes.

• Simplifies Key Return: These codes act as permanent identifiers for specific keys or properties, simplifying the key return process.
• Practical Solution: Useful when guests try to access the key box after their reservation contract has expired, such as during an auto check-out via an app or link.
• Considerations:
  • Per-Slot Assignment: Static codes are usually set per "slot" in the key box.
  • Communication Challenges: May require unique messages for each rental unit to account for its static code, which could complicate customer communication.
• Recommendation: The grace period solution is generally better when available, as it avoids the potential communication issues associated with static return codes.