Comms · Meetings · Support

Every conversation ends on the record.

Chat, video calls, customer support, scheduling — built in, not bolted on.

In most stacks the conversation happens in one tool and the work happens in another — and the decision dies in between. Here the call transcribes itself, the action items arrive on your board as drafted tasks, and a customer's support thread lands on their account as feedback. Nothing gets retyped.

The team's rooms

Chat, calendar and video — on the spine

Every conversation sits next to the work and the customer it is about. Click through the rooms.

Chat

Team chat and DMs

  • Channels and direct messages on the spine
  • Conversations sit next to the work they are about

Calendar

Calendar and meetings

  • Scheduling and recurring meetings
  • Tied to the accounts and work they concern

Video

Video calls, built in

  • Cloud video rooms — no extra vendor
  • Start a call from any record

Recaps

Transcription to tasks

  • Meetings transcribe themselves
  • An AI recap drafts action items onto your board

Team chat

Talk next to the work. Not in another tab.

Channels for the team, 1:1 and group DMs for the rest — scoped to your workspace, delivered live. No per-seat chat bill, no context switch.

    Channels

    Open rooms for the team and per-topic threads — the running conversation around the product.

    1:1 and group DMs

    Direct messages and ad-hoc groups, same inbox, same login as the rest of your work.

    Live delivery

    Messages arrive in real time over Supabase Realtime — no refresh, no polling.

    Edit and delete

    Fix the typo or pull the message back. Full control over what you said.

    Unread tracking

    Per-conversation unread counts, so the morning catch-up takes a glance, not a scroll.

    On the same spine

    The people in the picker are the same people on tasks, meetings, and reviews — one identity everywhere.

Video meetings

The call happens here too.

Built-in video meetings on LiveKit — no third-party meeting tool, no guest downloads, no separate bill. Put it on the calendar once and let it recur.

  • Video calls with the team, hosted inside the workspace — LiveKit under the hood.
  • A shared calendar with one-off and recurring meetings — the weekly sync schedules itself.
  • Recording is opt-in: the host turns it on, and only then does the transcription pipeline start.
  • Recorded meetings feed straight into transcription and AI recap — see below.

What a meeting leaves behind

  • 01A calendar entry — one-off or recurring, visible to the team.
  • 02A transcript — if the host opted in to recording.
  • 03An AI recap — summary plus proposed action items.
  • 04Drafted tasks — one click and the action items land on the board.

Most meeting tools leave behind a video file nobody rewatches. This one leaves work.

Transcription → recap → tasks

Hang up. The tasks are already drafted.

The pipeline you saw at the top of the page, step by step. No notetaker bot joining your call, no copy-paste afterwards.

1

Host opts in

Recording never starts on its own — the host explicitly turns it on for the meeting.

2

Deepgram transcribes

Speech becomes a live transcript as the meeting runs. Speakers are pseudonymized in the text sent for processing — names stay out of the model.

3

AI writes the recap

One click on Summarize: Claude returns a summary and a list of proposed action items in seconds.

4

Tasks land as drafts

“Add as tasks” puts every action item on the PM board as a draft — you review, assign, and ship. Nothing is created behind your back.

Because the recap lands on the same spine as your board, a decision made on a call becomes a task linked to the customer who asked — in the same minute.

Scheduling

Booking pages that land on the customer record.

Public booking links your customers can use — and unlike a standalone scheduler, every booked meeting attaches to the account that booked it. Engagement shows up on the customer's 360 view, next to their revenue and requests.

  • Three event-type shapes: 1:1, collective (whole group attends), and round-robin (next host up takes it).
  • Guests see real availability and book a slot — no email back-and-forth.
  • Every booking gets a LiveKit video meeting automatically, with optional transcription and recap.
  • The meeting ties to the guest's account — it appears on their Account 360 as proof of engagement.
  • Or embed it on your own site: the scheduling SDK is a 1.7 KB script tag.

Round-robin picks the host with the fewest bookings — simple and fair by design. No weighted rules or routing query builder.

Watch: the customer record a booked meeting lands on · Example data

Support inbox

Support threads become product decisions.

A 5.2 KB chat widget on your site, an inbox inside ProductOS — and every conversation lands on the spine as a customer insight, linked to the account and the feature it's about.

  • One inbox for every widget conversation — filtered by Open, Snoozed, Closed, or All.
  • Reply to customers without leaving the workspace where the product decisions happen.
  • Assign threads to teammates and leave internal notes the customer never sees.
  • Resolve when done — and the thread stays on the customer's record as feedback, feeding the same prioritization as every other request.

Your team answers — there's no AI bot replying to customers. We think that's a feature.

The honest edges

  • Video is built-in LiveKit only — no Zoom or Google Meet pass-through.
  • Team chat is native — no Slack, Teams, or Discord sync.
  • No email channel yet — chat, meetings, and booking pages are the ways in today.
  • Customers are answered by your team, not an AI bot.
  • Round-robin is fewest-bookings-first — no weighted routing rules.
  • Web-only in v1 — no native mobile apps or SDKs.

Early access

Stop retyping your meetings.

We're onboarding our first design partners now. Bring a real call — you'll watch it become drafted tasks on your own board within the walkthrough.

Explore more

Watch: support answered where decisions happen · Example data
Watch: booked — straight onto the record · Example data

FAQ

Questions, answered

What's included in Comms?

Team chat with channels and DMs, built-in LiveKit video meetings, a calendar with recurring meetings, public booking pages with round-robin routing, and a support inbox — all native to AIOProductOS.

Can meetings be transcribed and recapped?

Yes — meetings are transcribed with Deepgram, and an AI recap drafts the action items as tasks, so decisions and follow-ups don't get lost after the call.

Do meeting action items become real tasks?

Yes. The AI recap drafts action items straight onto your board as tasks, linked back to the meeting — so follow-ups land where the work already happens.

What happens to support conversations?

Support threads become product feedback on the customer spine — so a conversation can flow into your Insights feed and link to the account it came from, instead of dying in a separate helpdesk.

How is this different from bolting on Slack and Zoom?

Slack and Zoom are separate silos you stitch together and pay per seat for. Here chat, video, transcripts, booking and support sit on one shared spine, already connected to your product work — with no separate per-seat chat or video bill.