Noots.ai alpha is live. Expect some bugs while we polish, and tell us when you meet one.Report a bug

Headline feature 01 · Meetings

Hold the meeting. The project updates itself.

A call inside Noots, a bot in Zoom, Meet or Teams, or the extension with nothing in the room - every route ends in one read of the transcript. That read puts the work on the board with owners and dates, moves the timeline, files the notes, logs the decisions and sets the reminders. Nobody retypes a word.

Noots calls Google MeetZoomMicrosoft Teamsand Webex, Slack huddle and GoTo Meeting links
noots.ai/app/chat · #launch-sync
REC · Noot botLaunch sync12:41
MA
DN
TH
SM
Noot bot · live notesOpt-in
  • Key point

    Pricing waits on the design review

  • Action

    Maya takes the onboarding migration, by Friday

  • Task

    QA pass on checkout - Sam, Tuesday

A draft of a call still in progress. The meeting itself is written from the full recording afterwards.

One read, six destinations

What one meeting changes on a project.

The transcript is read once. Every meaningful thing said gets a kind, a quote, a speaker and an owner, and is routed to exactly one place - and what the room decided about existing work is proposed against the cards that are already there.

Launch sync · 24 min · transcript, read once
  • 04:12
    Maya

    I'll take the onboarding migration - done by Friday.

    task
  • 09:40
    Dana

    Then the beta moves to the 28th.

    date
  • 17:05
    Theo

    Pricing is held until design signs off.

    decision
  • 21:30
    Sam

    Remind me to send the QA plan on Thursday.

    reminder
Board
LAU-42In progress

Migrate the onboarding flow

MAMaya Fri
  • Export the old flow
  • Map the fields
  • Run it on staging

A card with an owner from your roster, a date, and the steps as a checklist.

Timeline
7 Sep142128
Onboarding v2
21 Beta · 28

A deadline said out loud becomes a milestone. A moved due date is proposed, then applied.

Notes
Launch sync · notes

Linked back to the minute it came from

The write-up lands on the project's Notes tab and is filed as a document beside the work.

Goals and milestones
Ship onboarding v240%
Beta28 SepFrom the meeting

An objective the room set becomes a goal on the project; a dated one becomes a milestone.

Grids
BC3Design9,8004Build12,400
ProposedBudget!C4 · from Launch sync

A number said in the call is one proposed change per cell, in a Grid the run was shown.

Decisions, to-dos, reminders
  • Decision

    Pricing held for the design review

  • To-do

    Send the QA plan · Sam

  • Reminder

    Thursday 09:00 · Sam

The decision register, a personal to-do for the person who said it, and a reminder that fires when they asked.

Written once

Board cards, personal to-dos, decisions, calendar dates, notes and reminders. Run the analysis again and it reconciles against what is already there instead of writing duplicates.

Owners from your roster

A name in the room is matched against the people actually in your workspace. A name that matches nobody is left as text on the card rather than guessed at.

Proposed, never posted

A figure someone said out loud is a claim, not a ledger entry. Money arrives on the Budget tab as a proposed line, and a Grid cell as one reviewable change, for a person to confirm.

Inside Noots

Calls and chat that already live with the work.

Noots has its own voice and video calls, its own meeting rooms and a recorder in the browser. A call starts in a conversation and rides along wherever you go, the in-house bot records it into an ordinary meeting, and the chat around it can move the board too.

BoardNotesTimeline
To do
In progress

A call in any conversation

Start it from a channel or a direct message, then move to a board, your mail or the calendar - the dock comes with you: mute, camera, share your screen, a REC chip while the bot records, and Leave.

Tuesday · 10:00Noots room

Sprint review

45 min · 6 invited · on Launch

MADNTHSM+2

Its own address, in every invite

A scheduled meeting with its own room

Book it from the Meetings hub or a project's Calendar tab and it gets a room the moment it is booked. The invite carries the address, the bot is sent at start time, and the write-up lands on the project it was booked against.

# launch-sync
JO

Jo done - the legal mailbox is created

Suggestion

Tick 'Create the legal inbox' on the Launch checklist?

AL

Alex /summarize

Thread summarised and filed on Launch

Chat that updates the board

A channel message that says something is finished gets a card offering to tick the item or move the task. One click, the same permissions as doing it by hand, and nothing moves without it. When a thread matters, summarise it into the project.

  • Record straight from the browser on the Recording tab, with the transcript arriving as you speak
  • Live notes during a call are a draft that fills in as people talk - opt-in, and never promoted into the record
  • The in-house bot writes the same meeting a bot in Zoom or Meet would: transcript, panels, and the project update
  • Chat suggestions read channel messages only - never direct messages or group chats - and an admin can switch them off
Capture

Three ways in. One write-up.

A Noots call, the bot, or the extension. Whichever you use, the transcript, the panels and the project update are produced by exactly the same code - so the choice is about the room, not about what you get afterwards.

A Noots call

Voice or video, started from any conversation, or booked as a scheduled meeting with a room of its own. The in-house bot records it directly and writes the same meeting a bot in any other room would.

  • Nothing to install and no link to paste
  • Live notes beside the call, opt-in and off until an admin turns them on
  • REC is shown to everyone in the call, and calls carry on when you change page

The Noot bot

Paste a Zoom, Meet or Teams link and it joins as a visible participant, records, and hands the recording to the pipeline. Webex, Slack huddle and GoTo Meeting links are recognised too.

  • Joins from a pasted link, from a meeting on your calendar, or from a meeting Autopilot booked
  • One bot per meeting - only the inviter's joins, so there is never a second recorder in the room
  • Waiting rooms still apply; a host admits it like anyone else

The browser extension

Some rooms go quiet the moment a bot appears in the participant list. The extension records the tab in your browser and transcribes there, and nothing reaches Noots until you have read the transcript and pressed Save.

  • Nothing joins the call and nobody is notified
  • You review the transcript before any of it is sent
  • Chrome, Edge and Brave, installed from a downloaded zip in developer mode
Auto-join and calendar sync

Connect a calendar. The bot turns up by itself.

Every two minutes Noots reads your connected calendars. A meeting with a link that starts in the next five minutes gets the bot - if you said yes - and what the sweep decided about every event is written down.

noots.ai/app/meetings · Connections
Google CalendarSynced 2 min ago
Send the bot to my meetingsOn
Outlook calendarSynced 2 min ago
Send the bot to my meetingsOff
Workspace default: auto-invite a bot to every meetingOn
Starting soon
  • 10:00 Sprint syncBot joining
  • 10:30Budget checkSkipped: your Outlook answer is no
  • 11:00Desk timeSkipped: no link

Auto-join

Two switches decide it. Each connected calendar has its own answer, and a person's own answer always wins in both directions. The workspace switch - auto-invite a bot to every meeting - is only the default for a calendar whose owner has never answered, so an admin can never send a recorder into meetings somebody said no to.

  • Off until you turn it on - nothing is recorded by default
  • A scheduled Noots meeting gets the bot sent to its own room the same way
  • Zoom meetings booked elsewhere sync in and can get the bot too
  • A meeting with no link is swept and marked, so the question of why the bot did not join has an answer
Two-way sync
Noots.ai
  • Titleboth ways
  • Timeboth ways
  • Descriptionboth ways
  • Locationboth ways
  • Attendeesboth ways
Conflict check · Thu 14:00
  • AlexFree
  • JoBusy until 14:30 · Outlook
  • Ravi22:00 in Chicago · outside hours
  • MiaOn approved leave

Calendar sync

Google Calendar, Outlook and Zoom, two-way. Title, time, description, location and attendees travel in both directions; an edit made in the other calendar is adopted rather than mailed straight back; a push from the provider and the two-minute poll keep the copies together. And before any booking is written, the conflict check asks whether the slot is already taken for anyone meant to be in it.

  • Your own events by title, everyone else's as busy - two timestamps and nothing more reach the organiser
  • Approved leave, and each person's working hours in their own time zone
  • One live free/busy ask to the provider at booking time
  • Book anyway skips the check, and nothing else
The write-up

Six panels, one writer.

Every capture route ends in the same function, so every meeting carries the same six panels - and a field added to one of them appears on all of them at once. Underneath sits a transcript that is a sequence of turns, not a wall of text.

  • Speaker-labelled turns with timestamps, searchable inside the meeting
  • Talk share measured in seconds when the capture is timed and in words when it is not - and the panel tells you which
  • Two labels for one colleague are merged, so a rejoin does not split someone's talk share in half
  • Where the labels genuinely are not reliable, it renders as prose rather than inventing speakers
Transcript · speaker-labelled
“launch date” · 2 of 3
  • Dana07:12

    Can we still hit the 28th?

  • Theo07:19

    Yes, if scope holds at one page.

  • Dana07:26

    Then I'll take the migration.

Talk share · measured in seconds

  • Dana44%
  • Theo31%
  • Four others25%
Summary

What the meeting was for and where it landed, in plain language.

Key points

The substance - what was actually discussed, not a list of headings.

Decisions

Kept apart from the key points, because a decision is a different fact.

Action items

Every commitment, with the person who made it and the date they gave.

Topics and concepts

Chips you can click. Each one is explained from this meeting's own transcript.

Speaker activity

Who spoke and how much - derived from the transcript, never from the invite list.

Conversation statsBusiness

How the conversation actually went.

Real figures about the call, measured from the transcript Noots already stores. No model reads them, nothing new leaves your workspace, and they cost nothing against your AI allowance. Switch Conversation Stats on at setup or from your workspace's extensions list; it is offered whatever industry you picked.

  • The longest unbroken stretch of speech, and who took it
  • How many times the floor changed hands, and that count per 5 minutes of call
  • Questions asked, over the whole meeting
  • Words a minute of speech, measured against time actually spoken rather than the length of the call

These figures are measured from the transcript and can be wrong. They describe a conversation, not a person, and they are not a basis for pay, promotion, performance or any other decision about somebody's job.

Did this meeting land?

A separate answer, read off what the meeting pipeline already wrote down: 4 checks on the record the meeting produced, never on a person in it.

  • Next steps were stated
  • A decision was recorded
  • Every commitment has an owner
  • Every commitment has a date

A meeting that produced no commitments has no owner missing and no date missing, so it is not marked down for either. A check with no source to answer from comes back unanswered with the reason, and is not counted against the meeting.

Absent, never wrong

Every figure is gated before it is worked out. A recording that was never split by speaker, a capture known to be incomplete, or a meeting rebuilt from live notes after the recording failed produces no figures at all and a sentence naming which of those happened. Never a zero standing in for something nobody knows.

Shared facts are shared. The rest is yours.

Who spoke and for how long goes to everybody who was in the room, because everybody in the room could have counted it. The figures that read as a judgement about a person - your pace, your longest stretch, how long you leave before you speak - are shown to you and to nobody else, beside an anonymous average of everyone else, and only once at least 5 other people spoke.

No score, no ranking, no manager view

There is no composite number for a person anywhere in this, no leaderboard, and no screen that lists colleagues against each other. And somebody who would rather not read figures about themselves switches their own off in one click, from the panel they appear on.

Questions

What people ask first.

Do I have to put a bot in the call?
No. A Noots call is recorded by the in-house bot without you doing anything, and the browser extension records the tab with nothing in the call at all - it transcribes in your browser and nothing is sent to Noots until you press Save, so the participant list never changes.
Which platforms does the bot join?
Zoom, Google Meet and Microsoft Teams, and it recognises Webex, Slack huddle and GoTo Meeting links as well - plus Noots' own voice and video calls, which the in-house bot records directly. A workspace that has connected none of them still gets a recorded meeting: Noots makes a room of its own and sends the bot there.
Will auto-join record every meeting on my calendar?
Only a meeting with a link, starting in the next five minutes, on a calendar whose owner said yes. The workspace switch is the default for calendars nobody has answered for, and a no always wins over it. Every event the sweep looked at records why it was joined or skipped, so a bot that did not turn up is explained rather than a mystery.
Does anybody get reminded the meeting is starting?
Yes. Shortly before it begins, everybody on the invitation gets a nudge from Hoot - and only them; declining removes you. If the meeting has a link the nudge carries a Join button. It stays quiet while you have notifications muted, and in the middle of your own night.
What happens if the same meeting is analysed twice?
Nothing new. Before it creates anything the run matches what it heard against the board's open cards, this meeting's own tasks - deleted ones included, which it treats as a no - the previous run's record and any question still waiting for an answer. A re-run reconciles; it does not duplicate.
Can it write to a project nobody meant it to touch?
Attach a meeting to a project and its action items go there, full stop. Left unattached, Noots proposes a project and - depending on your organisation's setting - either applies it or asks first. There is also a meetings-only mode that never touches a board.
What happens to a meeting that was recorded before all this existed?
It lights up too. The transcript is re-read into speaker turns when the panels load, so older recordings gain the reader without anyone re-running anything.

What we don't claim

  • No cross-meeting search yet - you search inside a transcript, and the vault list filters by title.
  • Nothing is written from a meeting Noots did not capture.
  • Amounts, Grid cells and moved dates heard in a call are proposed, never posted.
  • Live notes and the meeting-suggestion switches are opt-in choices an admin makes, and each is enforced on the server.
  • Conversation figures need a transcript that was split by speaker. Where the capture cannot support one, it is absent with a sentence saying why, never estimated.
Record your next one

Stop writing up the meeting you just sat through.

Free to start, eight recorded meetings a month, and no credit card. Bring a bot or don't.

Set up in minutes · no credit card required