Use email day setup to define when automated pre-stay, post-stay, and if enabled upgrade emails should be sent relative to a guest’s arrival or departure date.
This configuration applies to all hotels within the client’s CRM instance.
Field definitions
Before getting started with configurating the email day setup, it is important to outline some definitions.
Field | Description |
Pre stays | Days before arrival when the pre-stay email sends. |
Post stays | Days after departure when the post-stay email sends. |
Upgrade | Days before arrival when upgrade messaging sends. Only used if upgrade is enabled. |
Active | Enables the timing rules for all hotels. |
Configure email day setup
Follow the steps below to update pre-stay, post-stay, or upgrade timing.
From the left navigation menu, click CRM Setup and click Email Day Setup.
In the pre stays field, enter the number of days before arrival when pre-stay emails should send.
In the post stays field, enter the number of days after departure when post-stay emails should send.
If your organization uses the upgrade product, enter a value in the upgrade field. If upgrade is not enabled, this value will not be used.
Select the active checkbox to enable the timing rules.
Review the values entered to ensure they meet system constraints:
Zero is allowed.
Negative values are not allowed.
Maximum allowed value is 14 days.
Click Save to apply the configuration.
Once saved, these email timing rules apply immediately for all automated pre-stay, post-stay, and upgrade campaigns.
System rules and validation
Outlined are the system and validation of the email day setup.
Allowed values:
Zero is allowed: emails send on the arrival or departure day.
Negative values are not allowed: system blocks saving.
Maximum is equal to 14 days: higher values may cause unexpected or duplicate sends.
Upgrade field behavior:
Ignored unless the upgrade product is enabled for the client.
Validation outcomes:
Invalid values prevent saving.
Excessive values is less then fourteen may save but may produce unintended outcomes.
How pre-stay and upgrade timing works:
When pre-stay or upgrade values are greater than one, the CRM treats the number as a range, not a single target day.
For example if the pre-stay equals three the CRM selects guests arriving in one, two, or three days, and:
Sends the pre-stay email if the guest has not already received it.
Ensures last-minute bookings still receive messaging.
Prevents missed communication windows.
This range logic applies to pre-stay and upgrade only. Post-stay sends only on the exact defined day.
Scheduled processing times
These emails are sent via scheduled tasks, not campaign timing controlled by the client.
Server region | Daily send time | Time zone |
US CRM servers | 1:00 PM UTC | System-controlled batch process |
EU CRM servers | 6:00 AM UTC | System-controlled batch process |
Clients cannot adjust the time of day these messages are processed.
Best practices
Outlined below are some of the best practices of email day setup.
Pre-stay: One to three days is most effective.
Post-stay: One day is standard.
Upgrade: Seven to fourteen days, depending on operational needs.
Avoid values less than fourteen days.
Use zero only when same-day messaging is intended.
