One clock. One conversation.
Calendars that sync both ways, availability that reads every person in their own timezone, and a chat that already knows which project you are talking about — including the calls, which can put what was said back on the board.
- YouNew York · 10:00Free
- Design leadOslo · 16:00Free
- QA leadLondon · 15:00On leave · back Thu
- Ops leadDenver · 08:00Busy
Thursday 10:00–10:45 — everyone inside their own working day
One person's block is a private appointment. It rules the slot out; its title is never shown to anybody.
Synced both ways, so there is only one answer.
Task due dates, project target dates, milestones, meetings and events, on one surface — beside the calendar your organisation already runs on.
- Two-way sync with Google Calendar and Microsoft 365 — an event created in Noots appears there, and a change made there comes back
- Your local row is the source of truth: a provider outage never deletes an event, it marks the sync state and retries
- A remote copy that changed more recently wins, and the conflict is recorded rather than silently overwritten
- Reminders are a set, not a number — “ten minutes before” and “the day before” fire independently
Everybody's own clock, not yours.
One engine sits behind find-a-time, the in-project plan dialog and the meetings hub, so the three can never disagree about whether somebody is free.
- Every participant's working window is resolved on their local date, in their own zone — never in yours
- Approved time off blocks a slot, which it did not for the first three years this workspace had an approval workflow
- A private appointment blocks a slot too, and the payload carries two timestamps and no title
- Capped at fifty people, because a suggestion for two hundred looks complete and is not
- Q3 launchProject channel3
- Data migrationProject channel
- #generalEveryone
- #Cutover crewGroup · 5 people1
/summarize · /link MA-14
A project's channel already knows which project it belongs to, so the summary has a target without you naming one.
A chat that knows what you're working on.
One sidebar with a subtab, never a second rail. Channels, group chats and direct messages in one column, in an order that stays where you left it.
- A channel per project, per team and per division, with membership mirroring what that object's own audience already is
- A project's channel carries that project's own glyph and colour — the one place a channel earns a mark, because the mark is information
- Pin a conversation to a single task with /link, so the thread about MA-14 lives on MA-14
- /summarize a thread, bounded and on request — there is no popup asking whether you'd like it summarised
Each subtab's unread count is computed from the unfiltered list, so searching or filtering can never make a badge lie about what you have not read.
Talk, then let the board catch up.
Voice and video are part of the workspace rather than a tab beside it — and a Noots call is a meeting like any other, which is what makes the rest of this possible.
- Voice, video and screen share, started from any conversation
- The call survives navigating anywhere in the app — it lives above the router, not inside a page
- Minimise without hanging up, and it re-expands itself when something material happens
- A call that loses its last participant ends itself, instead of telling a channel somebody is still in it for ever
Live notes, while it runs
The in-house bot writes up short stretches as the call goes, so the panel has something in it in the first half-minute rather than the first two. It is opt-in and off until an admin turns it on, and an empty panel tells you which kind of empty it is.
And then the board
When the call ends the recording goes through the same pipeline as a Zoom or Teams meeting: summary, decisions, action items, and tasks on the project with owners. The live panel is a preview of it, never a substitute for it.
It knows what time it is where they are.
One definition of “is now a good time to message this person”, shared by the hint beside their name and the prompt before you press send — so the two can never disagree about the middle of somebody's night.
Asleep
A strict local band, 22:00 to 07:00. It outranks everything else, because it is the only signal that holds no matter what anyone configured.
Muted
They have told the product not to be disturbed. The composer says so before you send, not after.
Off the clock
Outside their working hours is a softer thing than the middle of their night, and the product treats it as one.
Unknown — and it says nothing
With no usable timezone there is no local time, so nothing is warned about. A warning built on a made-up clock is read once and never again.
Offer to send it in the morning and the message is held and delivered then. The prompt is skipped for a large group, because interrupting a note to forty people because one of them is asleep is noise nobody can act on.
Before you connect anything.
Does connecting a calendar mean handing over my whole diary?
Is this a second Slack?
Can I delete a channel that was created automatically?
Do the live notes during a call become the meeting record?
What we don't claim
- Two calendar providers are supported: Google and Microsoft 365.
- Availability suggestions are capped at fifty people.
- Live call notes are off until an administrator turns them on.
- Nothing is inferred from a timezone we do not have — the product stays quiet instead of guessing.
Stop paying three vendors to disagree about Thursday.
Chat, calendar, availability and calls, in the same place as the work they are about.
Free to start · no credit card required