Skip to Main Content
Access Hospitality - Ideas Portal

Help us shape the future of our products by submitting your own ideas and reviewing ideas submitted by other users. If you see an idea you like, feel free to vote it up and add any comments that you feel would be beneficial.
This is a collaborative community, so please join in, contribute your innovative ideas and help our product teams to shape their roadmaps and future product development.

Our teams will review the ideas which have received the most votes on a regular basis, meaning that not all ideas will receive updates. When an idea has received enough votes, the status will be updated to 'Under Review' and then a decision made.

Status Idea Received
Product Access Collins
Created by Guest
Created on Sep 10, 2025

Follow-up Notifications Based on Site Time Zone

The Follow-up notification system currently operates exclusively on UK/London time zone settings. All notifications are triggered at midnight UK/London time, regardless of the site's configured time zone setting.

This creates confusion for users in different time zones, particularly those in regions like Australia where the time difference is significant. For example:

  • Notifications update at 12am UK/London time, which corresponds to 9am Australian/Sydney time

  • When users hover over the Follow-up icon, dates may appear one day earlier than expected

  • Users must mentally convert times to understand when notifications will actually trigger

Please modify the Follow-up notification system to operate based on each site's configured time zone setting rather than defaulting to UK/London time.

Expected Behaviour:

  • Follow-up notifications should trigger at midnight according to the site's local time zone

  • Date displays should align with the site's time zone setting

  • Users should see consistent timing across all booking-related notifications

This is to improve user experience for international clients, and to ensure consistent behaviour across all site functions for a better alignment with local business operations.

Ref ADO Case: BUG 1538064

  • Attach files