Make operational messages easy to act on

Include the aircraft or route, current situation, requested action and relevant time. Keep each conversation focused on its audience.

1. Choose the recipient

Open Flying → Social → Messages or the messages workspace. Search conversations and confirm the selected person's username before writing.

Use Friends to manage personal connections. Company-wide HR messages and direct messages are different communication channels.

2. Send a useful message

  1. Choose the conversation or supported company/group channel.
  2. State the operation: aircraft registration, route, flight or contract ID.
  3. Explain the current state and what you need the recipient to do.
  4. Include the time and timezone when timing matters.
  5. Review recipients and any attachment before sending.

For example: “Aircraft ABC is due out of maintenance at the time shown on its profile. Please check its recorded status before preparing the next passenger flight.”

3. Use HR broadcasts for shared notices

Authorised staff can use HR → Messages for a notice to active employees. Read the audience and confirmation carefully; it is broader than a direct conversation. Avoid repeating a broadcast when a normal reply would close the loop.

4. Review your social preferences

Open Settings → Social for available messaging and group-invitation preferences. Check saved settings after changing them.

If messaging is blocked, read the page's explanation. A privacy or account restriction is different from an empty conversation or no unread messages.

Protect useful context

Do not include passwords, pairing codes or private webhook links in routine messages. When a task finishes, acknowledge the outcome so others know whether they still need to act. For a portal fault, open a support ticket with evidence rather than relying on a casual chat message.