Integrating HelloShift + RemoteLock

Connect RemoteLock to HelloShift for automated guest access — PIN codes generated and shared at check-in.

Integration between RemoteLock and HelloShift allows your guests to use digital keys to access their hotel rooms. Below, you’ll find an outline of the steps required to integrate your RemoteLock account with HelloShift. 

Set your Digital Key solution

Once in, HelloShift! Navigate to ADMIN > Settings and set your digital key solution to RemoteLock

Once you’ve selected RemoteLock as your solution, you’ll see a new Admin option available, called Integrations. 

Activate RemoteLock

Go to ADMIN > Integrations, click on Connect to RemoteLock button to connect your RemoteLock account to your HelloShift account.

This will prompt you to log into your RemoteLock account and approve the connections between the two. 

Map RemoteLock locations to property rooms

Once you connect RemoteLock with HelloShift, all your locations are imported into HelloShift. The system automatically matches locations to rooms based on the names. If the location names in RemoteLock are different from the room names, you can map them manually by selecting a room and mapping it to a device.

If you later add or rename a lock in RemoteLock, clickRefresh devices and users from RemoteLock to pull the changes in.You no longer need to disconnect and reconnect just to pick up a new device, andrefreshing never disturbs mappings you made by hand.

Issue/Revoke keys 

You can set up HelloShift to automatically issue keys, send those keys to guests, and revoke keys at the end of the guests’ stay. Once keys are issued, if the reservation dates are changed, the keys are automatically extended for the new dates.

Key Automation

Go to Guest > Automations > Key and customize the automations for issuing and revoking keys.

You can change the time the actions are taken and the optional message that goes out to guests after a key is issued.

Manual Keys

On guest profile and under guest reservation, there is a section for RemoteLock

You can just issue a code or issue and have the system automatically send the keys to the guest. You can also revoke the code issued to a guest.

Backup Code

Occasionally HelloShift cannot issue a guest their own key — RemoteLock rejectsthe request, the connection has expired, or the room has no lock mapped to it. Without abackup, the guest arrives with no code at all.

Set a backup code and HelloShift will send a permanent PIN from one of your RemoteLockusers instead, so the guest still gets into the room. The failure is still reported in theguest conversation, so your team can fix the underlying cause.

Choose a RemoteLock user first

The backup comes from a RemoteLock user — the permanent people inyour RemoteLock account, such as staff, owners or cleaners. It cannot be a RemoteLockguest: guests are tied to a single stay and expire with it.

Before setting this up, in RemoteLock:

  • We recommend creating a dedicated user for this, named somethinglike “HelloShift Backup”, rather than using a staff member’s own code.This PIN goes out to guests, so you will want to change it without disturbing anyone’spersonal access — and it keeps your RemoteLock access log clear about which entriescame from the backup.

  • Give that user a PIN.

  • Give that user access to your door locks — every lock you wantthe backup to cover.

Set the backup code

Go to ADMIN > Integrations > Digital Keys and find theBackup Code section. Pick your user from the RemoteLock userlist and click Save Backup Code.

If the list is empty, click Refresh devices and users from RemoteLockand try again.

HelloShift checks your choice and will not save a user who has no PIN, or who cannot openany of your locks. Once saved, the panel shows how many locks the backup covers, and namesany mapped room it cannot open so you can grant that access in RemoteLock.

Before you turn this on

A backup code is a shared, permanent code. It is a deliberate trade-off — a guestwho can get into their room versus a code that is not unique to them:

  • Every guest who hits a failure receives the same PIN.

  • It opens every lock that user can open.

  • Revoking a guest’s key does not change it, so a past guest keepsa working code until you rotate it.

Change the PIN in RemoteLock once it has been handed out, and treat repeated backupfallbacks as a signal to fix the real cause rather than a steady state.

To turn the backup off, choose None — do not send a backup code andsave. Guests will then receive no code when key issuing fails.

Deactivate RemoteLock

At any time, you can deactivate the integration between RemoteLock and HelloShift by going to ADMIN > Integrations.

Deactivating disconnects your RemoteLock account but keeps your room-to-devicemappings. When you reconnect, those mappings are still in place and any new devicesare added alongside them — you do not have to map your rooms again.

Related Articles