Skip to content

Crew Messaging Overview#

Crew Messaging is a service that enables passengers using paired PEDs (Passenger Electronic Devices) to communicate with cabin crew through a simple text messaging interface. This feature enhances passenger experience by allowing them to share concerns or service requests discreetly, and also helps streamline crew communication workflows.

Functionality Overview#

Once the PED is paired with the seatback system, the Crew Messaging service becomes available to the passenger. The service supports sending text messages to the crew and viewing the entire message history sent from that specific device for the current flight. This ensures passengers have a consistent and contextual view of their communications throughout the journey. Messages are delivered in plain text as typed by the passenger—no censorship or filtering is applied. Crew members view these messages directly on their Crew Application interface.

1. Service Initialization#

Crew Messaging becomes accessible after successful seat pairing. Once initialized, the service enables sending and retrieving messages related to the current flight.

2. Validating Message Limits#

Before enabling the message composition interface, the application should retrieve and apply the messaging restrictions configured for the passenger’s current flight. These limits—such as the maximum number of messages allowed, character limit per message, and a warning threshold—are dynamically provided by the Crew Messaging service.

By default, passengers are allowed to send up to 15 messages per flight, with each message capped at 160 characters. These defaults can be customised by individual airlines based on their preferences. Once a passenger has sent all 15 messages, the application should inform them that no more messages can be sent for that flight.

To ensure a smoother user experience, the app should display a warning notification when the passenger has only 5 messages left, allowing them to manage their communication more carefully. This threshold helps prevent frustration and encourages responsible usage.

All of this information can be retrieved through the Crew Messaging service, and the logic to enforce it—such as disabling the message input or displaying alerts—is implemented by the app. Developers can find detailed, platform-specific guidance on how to handle these scenarios in the respective implementation guides.

3. Viewing Message History#

Once seat pairing is established between the passenger's device and the seatback, the application can display a chronological list of all text messages previously sent by the passenger to the crew during the current flight. This history helps passengers maintain continuity in their communication, especially when multiple messages are exchanged.

This functionality ensures that the Crew Messaging service not only supports real-time communication but also preserves message context as long as the PED remains actively paired.

However, access to this message history is strictly tied to an active pairing session. When the PED is not paired, no historical messages are visible to the passenger, even if the messages were sent earlier during the same flight. This ensures privacy and data consistency by maintaining a direct association between a passenger and their assigned seat.

4. Sending a Message#

It is recommended that the application allow the passenger to compose and send a new message to the crew after validating the limits and displaying the message history. Once sent, the message is delivered to the crew terminal, where it can be read and responded to by cabin staff.

Passenger messages are transmitted exactly as typed—no censorship or filtering is applied. This means that profanities or inappropriate content are not blocked at the messaging level and will appear as-is in the crew interface. It is therefore the responsibility of the airline or application to guide passenger behavior through UI hints or disclaimers if needed.

The app should indicate the status of each message to the passenger. Whether a message was successfully sent or failed due to a network or service issue should be reflected in the GUI. This gives the passenger confidence in the system and helps them take corrective actions (such as retrying) if something goes wrong.

Additionally, developers are expected to enforce the character limit defined earlier (default: 160 characters) when implementing the input field. Attempts to exceed this should be gracefully restricted in the UI. Once the passenger reaches their maximum message count (default: 15), the message input should be disabled, and a notification should be shown indicating that no further messages can be sent.

5. Note on Receiving Messages from Crew#

In addition to allowing passengers to send messages to the crew, the Crew Messaging service also supports receiving messages from the crew on the PED. These incoming messages can be delivered and presented to the passenger through the application interface.

For implementation guidance on handling such inbound messages, developers should refer to the platform-specific system event handling documentation, which outlines how to listen for and process messages sent from the crew to the passenger.

version 1.0