Below is the update on handling schedule changes and how the Operations Team should be notified of the Sched Change:
SCHEDULE CHANGE TASK - WHEN TO ADVISE OPS?
Only raise a task to Operations (Ops) for a schedule change if:
The tour is allotment, and
The booking is traveling within 65 days, and
One of the following applies:
The time change is over 60 minutes, OR
The flight number has changed (regardless of time change).
Handling Third-Party & Allotment Bookings
If the booking is third-party, it will be managed by MNL OPS.
If the booking is outside 65 days of departure and allotment, no need to raise a task.
Instead, ensure Perseus reflects the updated details, as this will pull into the naming list.
If the schedule change is under 60 minutes and the flight number remains the same, no need to raise a task.
Suppliers review flight numbers before arrivals.
Subject: Schedule Change Notification
Hi Team,
Please note that there has been a schedule change as follows:
Original Flights:
[Flight details in correct format]
New Flights:
[Flight details in correct format]
⚠ Do not send screenshots – Provide flight information in the correct format:
Example: LA2405 Y 02NOV 6 GIGLIM GN20 0715 1045
The Operations Team typically receives schedule changes from:
CS MEL/MNL or MNL OPS Teams – When there is a schedule change to a customer's overall flight.
Flights Team – When there is a schedule change to an IV-ticketed flight.
New Snippets for Task Submission:
Two new snippets have been created for teams to use when sending a task:
One snippet for CS/OPS
One snippet for Flights
Task Assignment:
Assign the task to the "Ops Sch Change Advice" queue (no specific owner).
Snippet Name: Ops Sch Change Advice (from Manila) - Allotment
Keywords: schedule change process, itinerary updates, tour reschedule, departure changes, handling tour amendments