> For the complete documentation index, see [llms.txt](https://seat-airlines.gitbook.io/seat-airlines-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://seat-airlines.gitbook.io/seat-airlines-docs/section-network/introductions-rooms-and-the-pa.md).

# Introductions, rooms and the PA

Write to anyone in your cabin, talk in your cabin's room, and — from the flight deck — address the whole aircraft.

All three need you to be [signed in to the directory](/seat-airlines-docs/section-network/cards-and-sign-in.md).

## Introductions

An introduction is a private message from one holder to another.

* **Who you can write to:** anyone whose card you can read — the people in your own section, and nobody outside it. See [Your seat is which room you are in](/seat-airlines-docs/section-network/how-far-you-can-see.md).
* **How:** open a holder's card in the roster, write in the box — *Introduce yourself…* — and press **Send**. A draft is kept per holder, so a note half-written to one card does not follow you to the next.
* **Your inbox:** **Introductions** lists what you have been sent. What you have sent a holder is listed above the box on their card.

Only the two wallets on a conversation can read it.

## Rooms

Every cabin is a room as well as a rank.

* **You speak in your own cabin's room, and only there.** Write in *Say something to Business…* (with your own cabin's name) and press **Post**.
* **You hear your own cabin's room, and only it.** A cabin's room belongs to the people sitting in it; no other section can read it.
* New messages appear on their own while the page is open.

## The PA

The flight deck has the PA — the promise printed on its boarding pass: *"You have the PA. One announcement a day. Use it well."*

* Only the two flight-deck seats, **CPT** and **FO**, can announce: **Announce**.
* **Each of them gets one announcement in any 24 hours.** Once today's is made, the box is replaced by a line saying when the PA is yours again.
* Everybody aboard hears it — every cabin, and the cargo hold too. The latest five are shown at the top of the hub, under **The PA**.

## Limits

| Limit               |                                                                                                       |
| ------------------- | ----------------------------------------------------------------------------------------------------- |
| Messages per wallet | **20 an hour** — introductions, room posts and announcements together                                 |
| Message length      | **1,000 characters**                                                                                  |
| PA announcements    | **1 in any 24 hours** for each flight-deck wallet                                                     |
| What the hub shows  | The latest 50 introductions each way, the latest 50 posts in each room, the latest 5 PA announcements |

You cannot send an introduction to yourself.

## Writing a message

Every message box — an introduction, your cabin's room, the PA — works the same way:

* It grows as you type, and shows a count toward the **1,000-character** limit, which turns red near the end.
* **Enter** is a new line. **Ctrl+Enter** (**⌘+Enter** on a Mac) sends.
* The button reads **Sending…**, **Posting…** or **Announcing…** while its message is on its way, and a line under the box says whether it went.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://seat-airlines.gitbook.io/seat-airlines-docs/section-network/introductions-rooms-and-the-pa.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.