Previously, CS MNL agents followed a unique process of manually creating a task under their names for every interdepartmental concern raised, mainly for monitoring purposes.
This has now been automated and went live yesterday July 23, 2025.
update as of July 24, 2025
Automatic task creation for CS is now in place. CS MNL agents must avoid creating manual tasks moving forward. Two tasks will now be generated in the Notations playbook—one assigned to the other department and one to CS.
This automation currently covers Flights and Ops concerns.
ROLE OF TLs and SENIOR CS REPRESENTATIVES
TLs and Senior CS reps will help reinforce this process. If a task is visibly not being monitored or updated, and no action has been taken by the original agent, the TL may reassign the task at their discretion to another available agent, especially in cases where the original owner is:
Absent
On-leave
Unable to action the task for some reason
WHAT IF 7 DAYS HAVE PASSED WITHOUT ANY UPDATE?
The agent should follow up on the raised interdepartamental task, tagging the assigned owner for visibility.
For MNL-based teams, agents and TLs may also utilize the dedicated Helpdesk queues when referring to other departments.
The agent must also update the customer to advise that their request has been reviewed but is still pending feedback from the relevant team and need more time than initial advise.
This can be done via call or email.
After the customer has been informed, the agent should adjust the CS Follow-Up task due date to +3 days and continue monitoring.
STILL NO UPDATE AFTER 3 MORE DAYS?
The agent or TL should now escalate the concern to MEL CS for further intervention.
Keywords: task management, follow-up tasks, hubspot tasks, activity tracking, reminders, to-do list, interdepartmental tasks, task follow up timeline