I know others have mentioned wanting check in times based on season. I was wondering if this feature request could be included in with the other seasonal request because to me, they will be used in similar ways--or at least I can see how the overlap of coding might exist. However, I was told this was unique enough to ask as a new feature request.
I don't often have a guest take me up on an offer to check in early for a fee but I do often have guests who request to check in an hour earlier than standard. The only way to manage this currently is to manually go in and change their check-in time on the booking. The new tags you have created allow for automation of this with a tag that prompts population of the field code for a different check in time. However, this does not quite meet all of my needs.
Right now, I have two check in/out times that are based on if there are same day check in/outs on either side. I had to create many message templates to cover all of these scenarios based on season and arrival/departure gap and manually type in the check in and check out times since the field code would not work in these scenarios. It would be nice if this was also automated via a tag or some other condition so that I don't have 5 different templates and triggers.
For example, I have created a tag for 11am standard check out and 10am same day booking check out. I can set up the 11am standard tag with automation to meet the conditions I have (departure gap (bookable) is more than 1 night and check-out status is standard), but the 10AM check out for same day bookings does not have the conditions I need. There is only "standard" or "late" check-out status. No "early". And even then, these tag automations are not yet set up to change the field code for those times because these times are based on departure or arrival gaps or seasons, not a time that was manually changed on the booking.
Hope that makes sense!
