The channel is unreadable by the time you wake up
Four conversations happened at once, interleaved, and reading them means reconstructing which reply belongs to which question. So people skim, miss things, and ask again.
Use case · distributed teams
A working day that does not require everybody awake at once
Enclessa supports a written-first rhythm for a distributed team: threads keep a busy channel readable instead of turning it into interleaved conversations, scheduled messages let somebody write now and deliver inside a colleague’s working hours, mentions reach a person, a role or a custom group, and a call can be started from the room the moment writing has stopped being the faster option. Search covers the whole record, so somebody two time zones away catches up by reading rather than by asking.
Open betaThe platform is being built in the open, so parts of it are not there yet, behaviour changes between releases, and no availability figure is committed while it is in beta. What is still being built.
At a glance
- Default
- Written, in a channel, where it can be read later
- Threads
- A dedicated thread inbox, so replies do not flood the channel
- Timing
- Scheduled messages and reminders
- Reach
- Mentions for a person, a role, a custom group or the channel
- Quiet
- Mute per channel and per category
- Available on
- Every plan, including Free
The situation
The team is spread across time zones and there is no hour when everybody is available. Coordination has to happen anyway: what is in flight, what is blocked, who needs something from whom. The failure mode is a calendar full of meetings that exist because nothing was written down, attended by people for whom it is very early or very late.
What goes wrong when this is spread across four products
A message sent at the wrong hour is either ignored or intrusive
Writing at your midnight either lands as a notification in somebody’s evening or is buried by morning. Both outcomes push the team back towards a meeting.
Everything becomes a meeting
Without a written record people default to synchronous, and the calendar fills with recurring calls whose real function is to compensate for nothing being written down.
Notifications are all or nothing
Muting everything means missing what mattered; muting nothing means being interrupted constantly. People end up leaving the channels where the work is discussed.
How Enclessa handles it
Decide what belongs in a channel and what belongs in a call
Write the decision, the status and the question in a channel by default, and reserve calls for the things that genuinely need everybody at once. The rule matters more than the tool: a written default only holds if the answers to written questions also appear in writing.
Use threads for everything that has replies
Replies collapse under the message that started them and have an inbox of their own, so a busy channel stays a narrative rather than four tangents competing for the same space. That is what makes catching up possible rather than merely theoretically available.
Write on your hours, deliver on theirs
Schedule the message for the recipient’s working day rather than sending it at your midnight, and set a reminder for the thing you will otherwise forget. Nobody has to choose between writing when they are thinking and interrupting somebody’s evening.
Mention deliberately, and let people mute deliberately
Mentions reach a person, a role, a custom group or the whole channel, and people can mute a channel or a whole category. Precise mentions are what make muting safe, and muting is what keeps people in the channels where the work is.
Start the call from the room when writing stops working
When a thread has gone three rounds without converging, start a call in the channel. Everyone already in the room can join without an invitation, and the outcome goes back into the thread so the people who were asleep get the conclusion.
Let people catch up by searching, not by asking
Managed channels are indexed with full-text search across message text and the text extracted from uploaded files, with modifiers for who wrote it and when. Somebody returning from leave reads their way back in.
Which plan this needs
Everything here is on every plan, including Free for up to ten people. The one difference is search: the Free plan searches the last ninety days, and full-history search starts at the Starter plan — which matters more for a team that coordinates in writing than for one that does not.
Compare the plansWhat this will not do
- There are no mobile apps. Enclessa runs in the browser and on macOS, which is a real constraint for a team that coordinates from phones.
- There is no automatic standup bot, no check-in prompt and no digest email. The rhythm is a habit the team keeps, not a workflow the product enforces.
- End-to-end encrypted rooms are not searchable on the server. Search there runs locally on your own device, which means a device that has not synchronised cannot find old messages.
- Calls are not recorded to a file somebody can watch later, so a colleague who was asleep gets the summary that was written into the thread, not the call.
- There is no presence-based status automation and no working-hours enforcement: scheduling a message is a choice the sender makes, not a policy the platform applies.
Where the detail is
Questions
Remote-first daily coordination: common questions
Can I schedule a message to arrive during someone else’s working hours?
Yes. Messages can be scheduled, so somebody can write when they are thinking about it and have it delivered inside a colleague’s working day rather than at their midnight.
How do threads help a distributed team?
Replies collapse under the message that started them and have a dedicated inbox, so a channel stays one readable narrative instead of several conversations interleaved — which is what makes catching up across time zones practical.
Can people mute channels without missing what matters?
Yes. Channels and whole categories can be muted per person, and mentions can be aimed at an individual, a role, a custom group or the channel — so precise mentions are what makes muting safe.
Does Enclessa run daily standups automatically?
No. There is no standup bot, check-in prompt or digest. A written-first rhythm is a habit the team keeps; the product provides threads, scheduled messages and search rather than enforcing a ritual.
Encrypted collaboration, hosted in Europe.
Create a workspace in a couple of minutes. It is yours at your-team.enclessa.app, hosted in the European Union, with encrypted direct messages from the first one you send.
Open beta. Free plan, no payment card to start.