> For the complete documentation index, see [llms.txt](https://handbook.marsbased.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.marsbased.com/sections/howwecommunicate.md).

# How we communicate

Communication is the oxygen of our spaceship. As a remote company, staying aligned, connected, and efficient depends on how we write, share, and react ✨

Here’s how we utilize our tools, along with some friendly reminders to ensure everything runs smoothly:

## 💬 Slack

Use it for:

* Urgent topics.
* Quick syncs.
* Real-time info.
* Anniversaries.
* Sharing knowledge.
* Team-wise news.

**💡 Best practices**

* Use threads to keep discussions focused.
* Set working hours in your profile.
* Add a status when away or unavailable.
* Schedule messages if others are outside working hours.

## 📋 Linear

Use it for:

* Task creation and tracking.
* Async updates.
* Project communication.
* Decision documentation.
* Weekly highlights.
* Schedule reporting.

**💡 Best practices**

* Check your inbox regularly.
* Act on pending items.
* Keep tasks updated to inform your team.

## 📧 Gmail

Use it for:

* HR requests.
* Document submissions.
* Formal communication.
* Contact with clients.
* Communication with providers.
* Coordination with partners.

**💡 Best practices**

* Check your inbox daily.
* Keep only actionable items in view.
* Schedule emails when sending outside work hours.

## 📆 Google Calendar

* Use it to organise your day and make your availability visible.

**💡 Best practices**

* Review your calendar daily.
* Don’t rely only on notifications.
* Keep it up to date.
* Set your working hours.

## 📢 Tips

* Prepare for meetings.
* Be on time 🕐
* Communicate clearly.
* Ask questions ❔
* Share progress proactively.
* Use Martian Coffee slots ☕
* Let others know your availability.
* Offer and ask for help.
* Celebrate wins 🚀
* Give constructive feedback.
* Recognise others' work 🙌


---

# 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://handbook.marsbased.com/sections/howwecommunicate.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.