Engagement

Team Chat for Your Project

Channels, direct messages and threads for the members of a project, with files, voice notes and @atty when you need help. It is for your team, not for chatting with customers.

Unified Organization & Productivity

Public and Private Channels

Connected to the same project, people, permissions, and AI context.

Direct Messages and Threads

Connected to the same project, people, permissions, and AI context.

Reactions and @Mentions

Connected to the same project, people, permissions, and AI context.

Files and Voice Notes

Connected to the same project, people, permissions, and AI context.

Mention @atty in a channel, direct message or thread to ask about the project, and Atty replies there. If it proposes a change, only the person who asked can approve it. @atty can be switched off per project.

Connected to the same project, people, permissions, and AI context.

Working guide

A team chat app keeps talk about a project beside the work it concerns, so decisions and files do not drift into private messages. In Conversations, members of a project use channels, direct messages and threads, and they can mention @atty for help that stays in the thread. It is for your team, not for conversations with customers.

Workflow map

Where a team conversation should live

JobAppWhat it does here
Open a channel for each topicConversationsCreate a channel with an optional topic, and make it public for the members of the project or private for the people you add. Use one channel per subject, such as a launch or a supplier, so a newcomer can find the right place quickly.
Move side talk into a threadConversationsReply in a thread when a side discussion would bury the main messages. The thread keeps the question with its answers, so the channel stays readable for people who check it only once a day.
Ask @atty inside the threadAtty ChatMention @atty in a channel, a direct message or a thread to ask about the project, and Atty replies in the same place. If it proposes a change, only the person who asked can approve it, and the approval card appears in that conversation.
Decide where the record livesTasksChat is not the record. When a message turns into an action, create a task with an owner and a date. Files and images shared in Conversations are also saved to the project's Documents, so the file can be found after the thread has moved on.
In practice

A week in a project channel

  1. Monday · open the launch channel

    The launch channel has a topic that says what it is for, and the team posts the scope for the week there. Each person who joins can see what belongs in the channel before they start a new thread about something else.

    Conversations
  2. Tuesday · split a side question

    Two people disagree about a supplier's delivery window. They move the argument into a thread under the original message. The main channel shows one line, and the agreed date goes into a task once it is settled.

    Conversations
  3. Wednesday · ask @atty in a thread

    Someone asks @atty what is still open in the thread. Atty replies there, using the most recent messages as context. Treat its reply as a prompt for a decision, and copy any decision into a task or a document yourself.

    Atty Chat
  4. Thursday · share a layout

    The designer posts a PDF of the new layout in the channel. The file is also saved to the project's Documents, so the team can find the same version later. Attachments can be turned off for the project in the Conversations settings.

    Documents
  5. Friday · a voice message from the field

    A crew member records a voice message in the channel about a delivery, and teammates play it back. The Conversations settings control whether members can record voice messages, so check them before the team relies on this.

    Conversations
Start here

Pages for what a channel should point to

Internal wiki page

Move a process that keeps coming up in threads onto one page, with an owner who keeps it current.

Decision log

Record each decision a thread reaches, with its reasons and an accountable owner, so the thread is not the only record.

Policy acknowledgement

Collect a named person's acknowledgement of a policy version, since a channel post shows that a message was sent, not that someone received it.

Employee suggestion box

Give ideas one form with the problem first, so suggestions do not get lost among unrelated channel messages.

Mistakes to avoid

Three ways team chat drifts

Letting decisions live only in the channel

A decision that scrolls out of view is a decision people will argue again. When a thread settles something, write it into a task, a decision log entry or a document with an owner, and link that record back in the thread so people can find it.

Using one channel for everything

A single busy channel hides the messages that matter. Split subjects into channels, keep private channels for the people who need them, and use direct messages for one-to-one matters only.

Treating an Atty reply as the decision

@atty answers from the recent messages in the conversation, and it can be wrong or incomplete. Decide in the thread, not in the reply. When Atty proposes a change, the person who asked decides whether to approve it.

Working checklist

Before a conversation turns into work

Set up the channel

  • Give the channel a topic that says what belongs in it.
  • Choose public or private before you add the first message.
  • Check the Conversations settings for files, voice messages and @atty.

Keep the record

  • Write each decision into a task, a document or a decision log.
  • Link the record back to the thread where it was agreed.
  • Let only the person who asked approve a change that Atty proposes.
What this agreement means

What Conversations includes

  • Public and private channels, direct messages and threads, for the members of a project.
  • Reactions, @mentions, and a Mentions list in your settings that shows where you were mentioned.
  • Files and images, which are also saved to the project's Documents, and voice messages, which members can record.
  • @atty replies in a channel, a direct message or a thread, and a change it proposes can be approved only by the person who asked.

Conversations is for the members of a project, not for conversations with customers. Attachments, voice messages and @atty can each be turned off in the Conversations settings.

Frequently asked questions

What does a team chat app do for a small business?

It gives the people on one project a place to talk about the work, in channels, direct messages and threads, with the files that go with the talk. A good one keeps decisions findable, so a conversation can be traced to the task or document it produced.

Is Conversations a group chat app for friends?

It is built for the members of a project, such as a team or a household's shared plans. It is not a public chat service, and outside people do not join a project's channels. Use it for the work and plans that members share.

Is this an internal communication app?

It can serve that job inside one project. Channels cover topics, direct messages cover one-to-one questions, and threads keep side discussions in one place. It is not a customer support inbox, and it is not a place for conversations with outside parties.

Can I share files in a team chat?

Yes. Members can attach files and images in a conversation, and they are also saved to the project's Documents. Attachments can be turned off in the Conversations settings. Use Documents to find a file again after the conversation has moved on.

Is Conversations for talking with customers?

No. It is for members of your project. Messages with customers belong in the tools built for them, such as an appointment's booking conversation, and not in a team channel.

Attain OS BETA