Features
Six areas, and the fact that they know about each other
Each of these exists on its own elsewhere, and if you only need one of them you should buy that. What is hard to assemble from separate tools is the part where a message becomes a task, the task becomes a request, the request finds the right approver, and the document it produced keeps the trail.
Communication
The chat your team already knows how to use, and then some.
- Channels, public or private, with a directory to browse and join
- Direct messages and group conversations
- Threads and replies, notifying the people in the thread
- Mentions, including @everyone and @here where a channel allows them
- Emoji reactions
- Pinned messages, saved messages and starred conversations
- File sharing, with a files tab for every conversation
- Search by words, sender, date, or whether it carried a file or a link
- Voice huddles, started from any conversation
- Polls, for the decision that only needs a show of hands
- Edit, delete, mark unread, and retention set per conversation
Work and tasks
What the conversation asked somebody to do, tracked as a thing rather than a memory.
- Create a task from a message, keeping the message
- Assignee, due date, priority and labels
- Projects, to group the tasks that belong to one piece of work
- Complete and reopen, with the order you want them in
- My Day — what is yours today, across every project
- Comments on a task, so the discussion stays on it
- A per-task activity trail of what changed and who changed it
- Reminders before a deadline rather than after it
Approvals
Requests that move through the people who have to sign them.
- Approval flows built once and raised against repeatedly
- Steps assigned to a seat, a unit or a role, resolved to whoever holds it today
- Approve, reject, or return for changes with a reason
- Quorum — two of three, or whatever the rule is
- Escalation when a step sits too long, and reminders before that
- Delegation while somebody is away, without handing over a password
- Forward a step, or add and remove approvers on one
- Recall, resubmit or cancel a request you raised
- Signatures, with a default and a set of private approval phrases
- Full approval history, and nobody approves their own request
Documents
Files that know where they came from and who they belong to.
- Upload and share, with versions kept as versions
- Preview in the browser, page by page, without downloading
- The unit that owns it, the person who answers for it
- Effective and expiry dates, for the document that comes into force
- Activity per document: uploads, versions, ownership changes
- Access follows what the file is attached to, checked per file
- Encrypted with a key of its own, served through short-lived links
Calendar, meetings and rooms
The hour it takes to finish the thing, and the room it happens in.
- Events, with attendees who can accept or decline
- Recurring events, and cancelling a single occurrence of one
- A deadlines view, so due dates and meetings sit on one calendar
- Find a room that is free by day, time, size and equipment
- Book with the meeting; the room comes back if the meeting is cancelled
- Rooms that need permission ask the people who can give it
- Waitlist for a room that is taken, check-in, extend, or end early
- A door sign for one room and a lobby board for the building
Notifications
Loud enough to work, quiet enough to live with.
- Mentions, thread replies, task updates and approval requests
- Three levels per conversation: everything, only what involves you, or nothing
- Quiet hours, holding a buzz until morning
- In-app and push to the mobile apps, chosen per kind of notice
- Email and Telegram are not delivered. They are in the schema and the product refuses to let you select them, because a preference nothing drains is a way to configure silence — you would receive nothing at all, approvals included
- Muting suppresses the interruption and never the record — it is still in your activity feed
- Being named still reaches you, and a ringing call always does
Underneath all six: the organisation itself
Units, seats, appointments and reporting lines — including the person acting in a post this month. It is what makes “send this to the head of Procurement” something the system can act on, and what keeps a workflow working after somebody transfers.
It is also how permission is granted: authority moves with the post, so a vacancy is a question somebody can see rather than a request quietly going nowhere.
Waiting on me
The question everybody opens the product to ask: am I the reason something has stopped. Raised by me and waiting on me are counted separately, because they are different anxieties.
Finding the message it was decided in
Search your conversations by words, by who said it, by a date range, or by whether it carried a file or a link — grouped by the room the hit came from, because the answer to “where did we agree that” is usually a place before it is a sentence.
Scoped to your membership rather than filtered down to it: the set being searched is the rooms you are in, so search can never become a way to read one you are not. Khmer and English both. One box across every kind of record — requests and documents too — is not built yet; today it searches messages.
The decision follows the person, not the desk
Approvals stall on whoever is travelling. The same request, the same decision bar and the same trail on a tablet in a meeting or a phone in a car — with native apps for iOS and Android that carry the notification which gets you there. Chat is the same story: the channel list and the transcript together on a tablet, one room full-width on a phone.
Put the conversation and the work in one place
Free while you try it. Nothing to install.