Table of Contents
EMAIL TEMPLATES
MVT MESSAGES
This module allows to set up Movement Emails for each aircraft. You can define templates as well as add new templates. When Flight Watch data arrives to Leon a movement email will be sent out to the recipient.
Settings
By clicking the icon 
(next to 'Fleet rules by aircraft') Leon shows the below pop-up window where you can define:
- From label - a label/name which will appear when the MVT email will arrive.
- Reply to email - an email address to which a MVT email recipient should reply.
Once the MVT email has been sent (whether it's automatically or manually), Leon will use the above settings and will show the label.
Templates
There are 8 available default templates which can be modified. It is also possible to define your own templates.
A screenshot below shows an example of the Take Off template's text. In order to add a new template click + and add details such as:
- Template's name - i.e. “Aircraft owner movement email”.
- Subject - i.e. “Takeoff movement for (Aircraft registration number)”.
- Template - the text should contain tags available in Legend.
Once the Flight Watch data is filled in an email for the above template would be as on the example below:
“Dear Sirs,
We wish to inform you that the aircraft B-ARTI on flight no BAR21 from WARSAW FREDERIC CHOPIN WAW to GENEVA INTERNATIONAL (GVA) has taken off at 07:15. Aircraft is scheduled to arrive to GENEVA INTERNATIONAL GVA at 09:45. Aircraft has 23 passengers on board.”
Conditional Tags
It is possible to include or exclude empty fields from the MVT Message. In order to do it you need to use Conditional tags.
To create such condition you need to use '#' to open the sentence and '/' to close it, for example:
{{#PAX}} Passenger number on the flight is {{PAX}} {{/PAX}},
where {{#PAX}} is opening the condition and {{/PAX}} is closing it.
In the above case, if the Flight Watch does not include PAX number, or PAX number is 0, this information will not be included in MVT Message. If it is 1 and more, The above sentence will be included in the message.
It is also important to close one condition before opening another. Errors in the template will be highlighted orange in the template and 'SAVE' button will remain inactive until content error is amended.
Rules
By clicking on a particular aircraft in a section Fleet Rules Leon opens a new screen where sets of different rules can be added.
The 'Fleet Rule'setup contains the following:
- Rule - subsection where the rule/scenario that triggers the MVT Message can be set up. It consists of the following fields:
- Name - name of the rule
- Scenario - pre-defined scenario applicable to specific parts of the Flight Watch
- Template - list of available templates connected directly to the 'Scenario', e.g. if 'Take off' is selected as a scenario, one of the 'Take off' templates should be selected
- PAX/Ferry flight only - checkboxes allow selecting whether the MVT Message should be sent for flights with PAX or FERRY flights only. This is based on the FERRY checkbox in the tab 'PAX' in OPS/SALES sections - if the 'FERRY' checkbox is ticked it applies to 'Ferry flight only' rule and if it is unticked - to the 'PAX flight rule'
- Send for trip type - select a trip type for which MVT emails should be sent out. It doesn't apply to the subcharter trips
- Recipients - subsection where you define the recipients of MVT Emails
- TO/CC/BCC - fixed emails to receive MVT Messages
- From label - this could be the name of the Company/department within a Company. If it's not set up Leon will use these 2 details defined under
icon. - Reply to - by default, MVT Messages are sent from do-not-reply@leonsoftware.com email. In this field, another email can be defined. Additionally, if Mailboxes are set up, the email defined in the 'Mailboxes' can be inserted allowing sending the emails from Operator's mail servers
- Client representative - allows to include Client assigned to the trip in relevant MVT email (if there is a representative assigned to a company, the message will be sent to that representative only, if there is no representative assigned, the email will be sent to the email provided for the Client)
- Owner - allows sending the MVT Messages to the aircraft owners - defined in the Fleet setup>'SALES' tab. It doesn't apply to the subcharter trips
- PAX personal assistant - allows sending the MVT Messages to 'PAX personal assistant' defined in the PAX profile in the PHONEBOOK > 'DETAILS' tab > 'Personal assistant' field
- Send to departure/destination handler - allows to include Handling Agent at either ADEP, ADES, or both, assigned to the applicable flight in relevant MVT email
- Send to caterer - allows sending the MVT Messages to the Caterer selected in the 'Catering' element of the Checklist
- Aircraft - possibility to select the aircraft to which the rule should apply, including the SUBCHARTER aircraft. Clicking on the 'Aircraft' subsection name will select/deselect all the aircraft
It is also possible to set the MVT Messages to be sent manually only by selecting the 'Send manually only' option in the 'Scenario' dropdown.
A button ADD RULE allows to add of custom rules (i.e. a separate rule for a client).
To turn off the rule, use ON/OFF button next to the rule. Even if an aircraft have Rules assigned, switching it off will prevent MVT messages from being sent for the selected tails.
ETA UPDATE for next Client
One of the possibilities, when creating different MVT rules for aircraft, is sending ETA UPDATE for next Client MVT email, which can be sent to the next client assigned on the next trip informing him about estimated time of arrival of the aircraft (whether it is a ferry leg or a trip for a different client).
EXAMPLE 1 - the same Client on 2nd & 3rd leg of the trip.
0900 WAW GVA 1100 Ferry
1200 GVA AMS 1330 Client A
1500 AMS WAW 1700 Client A
In this case, when ETA is changed on the 1st leg, Leon will send MVT ETA Update email to Client A on the 2nd leg. But even if ETA changes on the 2nd leg Leon will not send another MVT email as it's the same Client.
EXAMPLE 2 - different Clients on 2nd & 3rd leg of the trip.
1000 WAW STN 1200 Ferry
1300 STN CIA 1530 Client A
1700 CIA WAW 1900 Client B
In this case, when ETA is changed on the 1st leg, Leon will send MVT ETA Update email to Client A on the 2nd leg. If ETA also changes on the 2nd leg, Leon will send a MVT ETA Update email to the Client B on the 3rd leg.
Similarly you can define a new rule for your fleet using a scenario Aircraft ready for next Client - Leon will automatically send a MVT email to the client assigned to the next leg (as long as it is a different Client).
Legend
The legend contains Tags and right next to them their description plus Test Data column showing examples (see below).
TAG DESCRIPTION TEST DATA
{{ADEP_ICAO}} Airport of departure (ICAO) EPWA
Documents Email Templates
In this panel you can set up email templates for: Quotes documents, Fuel Requests, Schedule Changes Summary, Crew Panel roster change, Crew Duties roster change, Fuel Requests, Permits or Schedule sending.
You can define multiple email templates for the same document or roster changes (for example depending on crew base or language), then select an appropriate template in OPS panel.
Click on any template and fill in 3 windows with appropriate HTML data. On the right-hand side Leon shows preview of the email body.
In a tab RECIPIENTS you can add default 'From' & 'Reply to' email addresses as well as 'CC' & 'BCC' emails.
Below you can find examples of how this section can be filled in.
Charter Agreement
SUBJECT
Preview:
Charter Agreement LFPG - OMDB 26 Apr 2019 Rev.1
BODY
Preview:
Dear James Smith
Please find attached your Charater Agreement from AirHeaven Airlines.
Kind Regards
Ann Davies
Fuel Order
SUBJECT
Preview:
UUWW FUEL REQUEST
BODY
'User sending email' located in the 'RECIPIENTS' tab next to 'Reply to' box allows setting up an email of the logged in User that is sending the message, as a 'reply to' email.
Landing Permit
An example of the full Landing Permit appears on the screenshot, on the right.