> For the complete documentation index, see [llms.txt](https://infinity-command.gitbook.io/infinity-command/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://infinity-command.gitbook.io/infinity-command/crew-stations/communications.md).

# Communications

<figure><img src="/files/HEHKGwqAPh0ebGuJ2KgD" alt=""><figcaption></figcaption></figure>

The **Communications** module handles all messages to and from the ship.

## Signal Spectrum

The signal spectrum shows all the comm traffic in the ship's vicinity.  The crew member can scrub through the spectrum, watching for strong signals.  When a signal is selected, the crew member can accept incoming or initiate outgoing calls.

## Mail & Cryptology

When written messages are received, they are often encrypted. The assigned crew member uses the cryptology controls to decode the message.

{% hint style="info" %}
You may notice that the ship can ***receive*** written messages but it cannot ***send*** them.  All outgoing messages must take the form of **voice calls**.  This is an intentional design choice for several reasons:

1. By forcing outgoing comms to be voice calls, it allows the entire bridge crew to hear the conversation.  Otherwise, the majority of the crew might miss important plot points, creating a confusing and disjointed experience.
2. Written messages can sometimes get overlooked by the Flight Director, breaking the immersion and making the communications officer feel unimportant.  Voice calls are much harder to overlook.

That all being said, if you'd like support for outgoing mail messages, please [let us know](https://discord.gg/wmNhfUksJP) and we can work it into our [roadmap](/infinity-command/development/roadmap.md).
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://infinity-command.gitbook.io/infinity-command/crew-stations/communications.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.