Every email about a flight, filed with the flight

The problem

Operations run on email, but the email lives in personal inboxes. When a controller is off shift, the conversation with the handler or the fuel supplier goes with them.

How BXI solves it

The BXI Mailbox is a shared three-pane inbox inside the platform. Each incoming email is matched to up to three candidate flights, so it can be linked in one click and found later from the flight itself.

Outgoing requests — handler, hotel, catering, fuel, GenDec, passenger lists — use templates with your signature and can be sent from department-specific mail servers.

Key capabilities

• Shared mailbox with unlinked and trash folders, threading, bulk actions and keyboard shortcuts.
• Automatic flight suggestions to link each email to the right flight.
• Reply, reply all and forward from inside BXI.
• Email templates for acknowledge, airport, catering, component, delayed reporting, dispatcher, fuel, GenDec, handler, hotel, passengers, expiring items and surveys.
• Separate SMTP per department (main, OPS, OCC).
• Group mail to crew.
• In-app user and system messages with a notification badge.
• Push notifications to BXI Mobile for flight changes and tasks shared with the crew.

What it changes in your day

Handover includes the conversation, not just the status. Anyone on shift can open a flight and read what was agreed with the handler yesterday.

Where Mailbox & Notifications sits in BXI

The Mailbox links to flights from Flight Planning; templates are used by Fuel, Handling and Passengers; push notifications reach crew through BXI Mobile.