Seasonal Custom Codes
Problem:
Custom codes currently lack date range conditions for seasonal messaging. Hosts need to manually activate/deactivate custom codes for seasonal content like berry season recommendations, creating unnecessary maintenance work.
Current Limitations:
Available conditions are limited to check-in/check-out timing and guest-specific criteria
No seasonal date range options (e.g., "November-March" for berry season)
Requires manual on/off management for time-sensitive content
Proposed Solution:
Add date range conditions to custom codes:
"Active between [start date] and [end date]"
"Active during months: [select months]"
"Active on specific dates: [date picker]"
Integration with existing custom code system
Business Value:
Eliminates manual seasonal message management
Enables automated local business recommendations during relevant seasons
Improves guest experience with timely, relevant information
Reduces host workload for seasonal content updates
Use Case:
Host creates "Berry Season Recommendation" custom code active November-March, automatically including Ruakura Berry Shop info in messaging rules during berry season without manual intervention.
Log in to comment and vote
Comments4
Bronze Rice
Feb 8
I would add that there are 2 opportunities here: booking time and reservation/stay time. My initial thought aligned with the outline above (short code to include ski information, for example, based on stay dates). Additionally, there’s an opportunity for seasonality in short codes for booking time to humanize the language: example, “hope you’re having a great summer,” or “hope you’re staying warm,” or a “Happy holidays” salutation.
The former (stay dates) is more interesting to me, to support something like:
%%closing_message%%[Aug - Oct]: “The evening light through the fall leaves is something special, be sure to enjoy it from the deck.”
[Nov - Feb]: “Hope you're cozying up by the fireplace or braving the hot tub under the stars!”
Andrew Schorr
Dec 17, 2025
Thanks for taking the time to detail out the use-case so thoroughly @Isaac Tanner-Dempsey! 🙇 I like it!
Teal Savanna
Dec 24, 2025
Custom codes are currently limited by the small set of available conditions, which prevents many valid automation use cases from being implemented. Rather than addressing these gaps through individual feature requests, group custom code condition requests together for the development team to work on then release multiple high-impact new condition types together, unlocking more flexible automation while reducing fragmented requests. Hosts could comment with additional condition types as have I but your team should organise them under “custom code conditions” to help guide prioritisation and later create the training team can create content templates with examples of the requested usecases built out into automations using the new conditions available.
Teal Savanna
Dec 24, 2025
The guest has / does not have any contact information.
The guest has / does not have any reviews or recommendations.
The guest is / is not bringing children.
The guest has / does not have an email address.
The guest has / does not have a genuine (not hidden) email address.
The guest has / does not have a preferred check-in time.
The guest is / is not bringing infants.
The guest is / is not bringing infants or children.
The guest is missing either their email or phone number.
The guest is / is not bringing a pet.
The guest has / does not have a phone number.
The guest has / does not have a profile picture.
The guest has / has not filled in their profile description.
The guest has / has not verified their identity.
The guest has received… reviews.
The guest is likely to fly.
The guest has / has not created their account in the last 3 days.
The guest is / is not a returning guest.
The guest is a Superhost.
The guest last replied … hours ago.
The guest will take a plane.
There are … guests arriving.