Since launching Personalised Travel Alerts, we’ve closely monitored usage and feedback. Based on this, we’re excited to share two enhancements designed to improve how disruptions are created and when travel alert notifications are sent.

1. Copying existing disruptions

We noticed some operators re-use resolved disruptions by updating the dates to notify users of new events. While this saves time and ensures consistent messaging it also prevents travel alerts from being sent. Alerts are only sent for new disruptions, meaning editing disruptions won’t trigger travel alerts for users.

To address this, we’ve introduced a streamlined way to create new disruptions based on existing ones. This change saves time and ensures consistent messaging for all operators while ensuring Travel Alerts are always delivered as intended. Creating a new disruption from an existing disruption in Passenger Cloud is as simple as navigating into an existing disruption, tapping ‘Clone alert’ and adding a start date for the new disruption.

2. Better timing for Travel Alerts

Operators who schedule disruptions far in advance raised concerns that sending Travel Alerts too early may lead to users forgetting them. To address this, we’ve implemented the same scheduling logic applied to network change travel alerts:

Travel Alerts for disruptions are now sent at midday, two days before the disruption start date, or immediately, if closer to the start time.

This ensures users receive timely and relevant notifications without compromising on their effectiveness.

We’re committed to continuously launching improvements that optimise your workflows and support the delivery of exceptional service to your passengers. Thank you for your ongoing feedback—it’s invaluable in helping us refine the system.

This feature will be available from Thursday, 2nd January. To find out more about Personalised Travel Alerts, please don’t hesitate to contact your Customer Success Manager.