# Communication

## Slack

We use slack for communication. Every project has an internal and external channel. We invite customers to join the external channel. While using slack please follow these guidelines:

* **Avoid DMs:** Discuss everything about a project on that specific channel. This keeps everyone in the loop even if they're not working on that feature or module.
* **Come with a solution:** When in doubt don't ask "How you should proceed" rather try to think of solutions and ask which one is the best.
* **Be mindful of other people's time:** It's okay to ping people once in a while but be mindful that they have their own tasks to finish.
* **Statuses:** Use the different slack statuses to broadcast your availability.
* Don't use gifs in external channels.

## Meetings

Meeting your lead, team, and customer is required to understand priorities and tasks. Our philosophy here is to:

1. **Keep it short:** Meetings should be short, just enough time to go through the agenda and get everyone on the same page.
2. **Schedule check-ins:** Regular check-ins ensure everyone is aware of priorities and blockers can be discussed.


---

# Agent Instructions: 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:

```
GET https://playbook.wednesday.is/employee-handbook/how-we-work/communication.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.