Slash commands in a team chat: from message to task in a second
How commands like /task and /meeting save your team's time, and which actions to move into chat first.
Switching between tools is one of the least visible time sinks: open the tracker, find the right project, fill in a form, return to the chat and recall where you left off. Slash commands remove the switch.
How it works
Type / in the composer and a menu opens. Pick an action and it runs right where the conversation is. The result appears in the feed as a card: task, meeting, call, file. The full list is in the documentation.
Where to start
You don’t need to retrain the team on everything at once. Pick the three actions you perform most often:
- Creating a task (
/task) — the most frequent and the most useful. - A meeting (
/meeting) — when you agreed to “catch up” and the time must be fixed. - A call (
/call) — when talking is easier than typing.
The menu shows only what’s yours
An integration command — Jira or Google Drive, say — appears only when the service is connected, so the team never trips over something that isn’t set up. Connecting is covered in the integrations overview.
The effect on your process
When creating a task is as easy as sending a message, agreements stop getting lost on their own. Try it on one project for a week: count how many “we should do that” turned into cards.