Please use the snippet: Bedding Config Change - OPS when making a request to Operations team
OUTSIDE 75 DAYS PRIOR TO DEPARTURE
No need to update Ops, just make change in BE.
INSIDE 75 DAYS PRIOR TO DEPARTURE
update as of 02/26/2025
If naming list has been sent, it will be hard to change. Hence, please pushback.
Template: CS - Bedding Request Allotment < 75 Days
BEDDING CONFIGURATION CHANGES AFTER NAMING LIST HAS BEEN SENT
update as of 19/03/2025
We cannot change bedding configurations after the naming lists have been sent to hotels.
Hotels typically hold a split of twin, double, or single rooms but this isn’t always the case. Once we send the naming list, they confirm all room types accordingly.
If a customer has booked a double room and it is reflected on the naming list, we cannot change it to twin.
HOW TO ASSIST CUSTOMERS IF THEY REQUEST AFTER THE NAMING LIST HAS BEEN SENT
update as of 19/03/2025
Advise customers to speak to the tour leader upon arrival or directly to the hotel staff at check-in to request their preferred bedding configuration.
Remind customers that bedding configurations cannot be guaranteed.
Important: Please do not raise tasks requesting bedding configuration changes after naming lists have been generated.
ALL TIMELINE
raise task to MNL Ops with snippet: 'Bedding Config Change - Ops'
OUTSIDE 75 DAYS PRIOR TO DEPARTURE
raise task to MNL OPS with snippet: 'Bedding Config Change - Ops'
INSIDE 75 DAYS PRIOR TO DEPARTURE
raise a task to MEL Ops with snippet: Bedding Config Change - Ops'
Keywords: room preference change, bed type request, bedding update, room setup request, hotel configuration change