Slack won the argument about where work gets talked about. The question this page answers is what happens after the conversation — where the decision goes, who owns it, and whether the answer finds its way back to the channel.
Capability by capability
Every line about Slack was read on its own pages on 24 September 2026. Where we are still building something, the table says so.
| Slack |  |
|
|---|---|---|
| Conversation | ||
| Message history on the free plan | 90 days | 6 months |
| Audio and video meetings | Huddles: 1:1 on Free, group meetings from Pro up | A Google Meet or Teams event in one click, from the chat’s top bar, on every plan |
| Guests | Paid plans only: 5 single-channel guests per paid member; a multi-channel guest is billed as a member | One per user on Free, two on Workspace, three on Business OS — each with one channel and one project on Boards, and none of them billed as a member |
| From talk to work | ||
| What a message turns into | Slack Lists, from Pro up; the list is a separate object from the thread | From the message itself: a reminder, an event in a calendar — yours or somebody else’s — or a task on Boards in the project you pick. On every plan. |
| Boards and views | Lists, from Pro up | Boards in kanban, list, table and Gantt; 2 boards on Free |
| Repeatable processes | Workflow Builder, from Pro up | Workflow templates from Workspace up: steps, configurable deadlines, a named person or department answering for each stage, and conditions that branch the path |
| People and focus | ||
| Your day on one screen | — | A dashboard built on the Eisenhower matrix, plus the work about to reach you when the person ahead finishes |
| Several organisations in one inbox | Separate workspaces, each with its own notification list | Switch organisation without logging out; every notification from every module and every organisation in one list |
| Quiet by default | Do Not Disturb and a notification schedule | Availability schedules, automatic Do Not Disturb during recurring meetings, an absence about to start, per-channel rules |
| Culture, clients, tickets | ||
| Feedback, kudos, eNPS, pulse surveys | Third-party apps such as Matter, which do run inside the chat — but each is its own vendor, its own subscription and its own set of data | In the product: Feedback Friday, kudos and surveys from Free; pulse surveys and eNPS from Workspace |
| Clients and tickets | Not in the product — integrations with a CRM and a help desk you buy elsewhere | CRM, ticketing and email are in development, joining Business OS rather than arriving as a separate product |
| Where it runs | ||
| Where the data sits | Data residency from Business+ up | European infrastructure at OVHcloud on every plan |
| Who you contract with | Slack Technologies Limited, registered at Salesforce Tower, North Dock, Dublin — the entity for every country outside the United States, Canada and Japan | HOMtu® sp. z o.o., a Polish company — the same entity for every customer |
| Whose law the agreement is under | The law of England, with venue in London — outside the European Union. A Polish company falls under „Rest of World”, and no region setting changes that. | Polish law, in a Polish court |
Sources: Slack pricing · Slack: guest accounts · Slack supplemental terms (contracting entity, governing law, venue). Checked against Slack’s own pages on 24 September 2026.
Giving the point away
Three of them, and none is a throwaway. If these are what your team runs on, Slack is the right answer and we would rather you knew now.
Slack’s directory is the largest in the category. If your work runs through a tool that ships a Slack app, that integration exists today and ours may not. We would rather say so than pretend the catalogue does not matter.
Your new hire has used Slack before. Whatever we do with onboarding, we cannot beat a product that half the industry already has muscle memory for.
Slack Connect puts you in a shared channel with a client or an agency, each side in their own workspace. Our guests cover the same ground from one side; the symmetric version is Slack’s.
Where the difference shows
A message becomes a task with an owner and a deadline, and the comments left on that task come back as a reply in the channel the message came from. Nobody changes module to take part in a decision, and nobody reconstructs the reasoning a month later.
An agency, an accountant or a law firm lives in several client workspaces at once. In taos you switch between them without logging out, and every notification from every module in every organisation arrives in the same list, whatever your role in each.
Feedback Friday, kudos and surveys from the free plan up; pulse surveys and eNPS from Workspace. Slack has apps for this and the good ones work inside the chat — but each is a separate vendor, a separate subscription and a separate place your answers live.
A workflow template holds the steps, configurable deadlines, the person or department answering for each stage and the conditions that branch the path. Your dashboard then shows the work about to reach you, before the person ahead of you has finished.
One guest per user on Free, two on Workspace, three on Business OS. Ours sits in one named channel, exactly as Slack’s does — but gets a project on Boards along with it, so a client sees the work and not only the conversation.
A Polish company contracts with Slack Technologies Limited, registered in Dublin, under the „Rest of World” terms: governing law England, venue London. Irish entity, English courts, outside the European Union — and data residency, which starts at Business+, moves where the bytes sit, not whose law decides the dispute. Ours is Polish law in a Polish court, on every plan.