Skip to main content

How to Use Custom Property Fields as Variables

Written by Sergey Zhizhoma

Custom Property Fields allow you to create property-specific content that can be reused as dynamic variables in automated messages and guidebooks.

This is useful when each property needs different information, such as access instructions, Wi-Fi details, parking notes, house rules, or any other custom text.

What are Custom Property Fields?

Custom Property Fields are reusable fields created at the account level.

After a field is created, it appears on each property page. You can then enter a different value for each property.

For example, you can create a custom field called:

Pool Instructions

The system will automatically generate a variable like:

{Pool_Instructions}

You can then use this variable in your guidebooks or automated messages. When the message is sent or the guidebook is viewed, the variable will be replaced with the content entered for that specific property.

Where to Manage Custom Fields

Go to:

Settings → Preferences Settings → Custom Fields

From this page, you can create and manage custom property fields.

How to Create a Custom Property Field

  1. Click New custom field.

  2. Select the Field type.

  3. Enter the Display name.

  4. The Variable name will be generated automatically.

  5. Click Save.

Example:

Display name:
Test

Generated variable:
{Test}

The variable name can then be used in automated messages and guidebooks.

Field Types

When creating a custom field, select the field type based on the content you want to store.

For longer instructions or descriptions, use Long Text.

This is recommended for content such as:

  • Property access instructions

  • Parking information

  • Wi-Fi details

  • House rules

  • Check-in notes

  • Guidebook content

Where to Add Property-Specific Values

After a custom field is created, go to the property where you want to add the value.

Open:

Property → Property Info → Guidebook Content → Custom Property Fields

The newly created field will appear in this section.

Enter the content that should be used for that specific property, then click Save Property.

Example:

Custom field:

Test

Property-specific value:

Add some content here

When the variable {Test} is used in a message or guidebook, the system will replace it with the value saved on that property.

How to Use Custom Variables

Once the custom field is created, copy the generated variable name and insert it into your automated message or guidebook content.

Example message:

Your property instructions: {Test}

If the property has the value “Add some content here” saved for the Test field, the guest will see:

Your property instructions: Add some content here

Important Notes

Custom variables are created automatically for every custom field.

Each property can have its own value for the same field.

If a custom field has no value on a property, the variable may appear empty in the guest-facing content.

Always save the property after adding or updating custom field values.

Use clear display names so your team can easily understand what each field is for.

Recommended Use Cases

Custom Property Fields are useful for any information that changes from property to property but needs to be reused in templates.

Common examples include:

Access instructions
Use for smart lock codes, door codes, or key pickup instructions.

Wi-Fi details
Use for Wi-Fi network names, passwords, or troubleshooting notes.

Parking instructions
Use for property-specific parking locations or restrictions.

Guidebook notes
Use for custom recommendations or property-specific guest information.

Special house rules
Use when certain properties have unique rules or instructions.

Summary

Custom Property Fields help you avoid creating separate message templates for each property.

Create the field once, add property-specific values on each property page, and use the generated variable in your automated messages or guidebooks. The system will automatically replace the variable with the correct content for each property.

Did this answer your question?