Skip to main content
All CollectionsLivionKey RegisterAdvanced usage
LivionKey Register: Managing Contact Persons in Key Contracts
LivionKey Register: Managing Contact Persons in Key Contracts

This article explains how to efficiently manage contact persons within LivionKey Register, streamlining your key handover process.

Yassine Jouahri avatar
Written by Yassine Jouahri
Updated over 2 months ago

Efficiently managing contact persons within LivionKey Register streamlines your key handover process and ensures accurate communication with recipients. By saving and utilizing contact information, you can save time and reduce errors, ultimately improving the overall user experience.

Adding Contact Persons during Key Handover

When handing over keys, you'll need to provide the recipient's contact details. LivionKey Register offers the option to save this contact information for future use. This is particularly useful if you frequently interact with the same individuals or organizations.

During the key handover process, simply check the "Save contact" checkbox after entering the recipient's details. This will add the contact to your saved list, making it readily available for future key handovers.

Utilizing Saved Contacts

On your next key handover, you can use the contact search tool to quickly populate the recipient's information. This saves time and reduces the risk of errors when entering contact details.

Viewing and Managing Saved Contacts

You can access the list of all your saved contacts in the "Contacts" view.

  • Currently, you can only delete contacts from this list.

  • To update a contact's information, you have two options:

    • Edit the details directly during the key handover process by making the necessary changes and checking the "Update contact" checkbox.

    • Delete the existing contact and re-create it with the updated information during the next key handover.

Remember:

  • For further information and guides on using the LivionKey Register, refer to our help center or contact our support team.

Did this answer your question?