Skip to main content

How to use Operations codes

Article describing operations codes, where they're found & how to use them

Tim Parry avatar
Written by Tim Parry
Updated this week

๐Ÿ” Using Operations Smart Lock Codes

Hospitable now supports Operations Smart Lock Codes โ€“ unique access codes generated for teammates like cleaners and maintenance workers. These codes are tied to tasks, not reservations, and can be used with Hospitable tasks and Cleanster bookings. This helps your operations team access the property securely and efficiently, without needing the guest code.

What are Operations Smart Lock Codes?

Operations Smart Lock Codes are automatically generated when a task is created or assigned to a teammate. These codes are separate from the guest access codes and are designed to give temporary, restricted access to the property during a specific operational task (e.g., cleaning after checkout, mid-stay maintenance).

They help:

  • Improve security by assigning unique codes to each teammate.

  • Ensure teammates have timely, task-specific access.

  • Eliminate the need to share guest codes with cleaners or other staff.

How to Enable Operations Smart Lock Codes

You can enable operations codes from your Task Rules. Hereโ€™s how:

  1. Go to Operations > Task Rules.

  2. Select an existing rule or create a new one.

  3. Check the box: Generate a smart lock code for this task.

  4. Save the rule.

How to Send Operations Codes to Teammates

Operations codes are sent using a new short code:
โ€‹%operations_smartlock_code%

Youโ€™ll need to add this to your notification rules for the teammate assigned to the task. Here's how:

  1. Go to Operations > Notification Rules.

  2. Create a new notification rule (or edit an existing one).

  3. In the message content, include %operations_smart_lock_code% where you want the code to appear.

๐Ÿ”” Example Message:

You have a cleaning task today at 123 Main St. Use the following code to access the property: %operations_smart_lock_code%

๐Ÿงผ Cleanster Tasks:
Weโ€™ll automatically send the operations code to the assigned cleaner 1 hour before the task start time - no need to configure notification rules for those tasks.

โš ๏ธ What Happens if the Code Fails?

In rare cases, a code might fail to provision on the lock - for example, due to poor connectivity or a lock sync issue. In these cases, Hospitable will email or text a back-up code to the assigned teammate 1 hour before the task starts, using their preferred contact method.

๐Ÿ“Š Operations Codes Dashboard

You can view all active and scheduled operations codes in the Smart Lock > Operations dashboard. This dashboard provides full visibility into codes assigned to Hospitable tasks and Cleanster bookings, along with their activation settings and timing.

Each code is labeled by its activation mode to help you understand how and when itโ€™s applied:

  • Manual Dates โ€“ Manually configured code with custom start/end times

  • Always On โ€“ Code thatโ€™s always active, with no end time

  • Task Synced (Task Rule Name) โ€“ Code generated via a Hospitable task rule

  • Task Synced One-off Task โ€“ Code linked to a one-time task created in the calendar

  • Task Synced, Cleanster โ€“ Code automatically generated for a synced Cleanster booking

Best Practices

  • โœ… Use %operations_smart_lock_code% only in task-based notification rules.

  • โŒ Avoid using %smart_lock_code% in task-based notifications โ€“ itโ€™s for guest codes tied to reservations.

  • ๐Ÿ‘€ If no notification rule exists for the task, teammates may not receive the code.

FAQ

Can I use the same code for multiple tasks?
No. Each task generates a unique operations code for improved security.

Can I use this with any smart lock integration?
Currently, operations codes are supported with our existing lock integrations (August, Yale, Schlage, etc.) where provisioning is possible.

How can I see the generated code?
The operations code will appear directly on the task in the task calendar or the smartlock operations dashboard within Hospitable once generated.

Did this answer your question?