MEL Ops - Daily NL Trigger

Before your first run

You need three things working, worth checking a day ahead rather than at 8am:

● The naming-list-automation skill — This has been shared with everyone. Type / in a
chat to see your available skills and confirm it's there.
● The iv-dw connector, authenticated. This is where the passenger data comes from —
nothing works without it. If it ever says disconnected, just try anyway; it usually
authenticates on first use.
● Access to "Naming List Data Files" in Drive:
drive.google.com/drive/folders/1sEcseD2RXxEvHOqQbEtLYLLPeCKWIZmG

You don't need to read the skill to use it, it runs itself. It's there for reference if something
looks odd.


1. Work out which routes are due today

Open the current NL Pipeline

Naming List Due to Supplier is the trigger date. Anything falling due today needs running.

For each one you need two things exactly as they appear in the sheet:
● Route Start Date (column D)
● Route Name (column I)


2. Start a fresh chat

One new chat per day, not one thread you keep adding to across the week. A week's worth of runs in one thread accumulates enough data to slow down or hit a limit mid-week.

Everything the automation needs lives in the skill, not in the conversation, so starting fresh loses nothing.

Name it something like NL Trigger – 9 Sep.


3. Send the trigger

For the daily batch — paste this, one line per route:

This is today's Daily NL Trigger. Please run the Naming List automation
for the following departures and send the team update:

<Route Start Date> – <Exact Route Name>
<Route Start Date> – <Exact Route Name>

For a one-off route outside the daily run:

Please run a naming list for this route, which is separate to the
daily NL trigger:

<Route Start Date> – <Exact Route Name>

The difference matters. "Daily NL Trigger" is the phrase that tells it to produce both the
workbook and the team Slack message. The one-off wording produces just the file.


4. Check the numbers before you go any further

It reports a passenger count per route and reconciles it against the expected pax_sold.
If every route matches, carry on. If any route doesn't match, stop and look up “route
monitoring”.

The skill will flag any issues, expired or invalid passports, unpaid invoices, missing
mandatory insurance, name check flags. This is part of the MNL process but good to sweep your eyes over to check for any inconsistencies.


5. Open the file

It appears as a card in the chat, click to open. It's a Sheets file with one tab per route, so a five-route morning is one workbook with five tabs, not five files.


6. Save it to Naming List Data Files

Move it into Naming List Data Files Google Drive folder.


7. Copy the team message

The chat gives you a ready-made Slack message. Copy it as-is.

The word "Master list" are a placeholder. That's where the link goes.

Don't reword the rest. It's kept identical each morning so the team can scan it quickly.


8. Paste the link over "Master list"

Select the words Master list in your Slack message, and hyperlink them to the workbook you saved in step 6. Then post to the mnl-mel-allotment-tasks channel.


9. Timing

I try to run this between 8am and 9am each morning so it is there as soon as the MNL team starts their day.


10. If Something Goes Wrong

The MNL team can still run naming lists the old way through Tableau, that's their built-in fallback and it's in the message template. Nothing is blocked if a run fails; flag it and let them know.