# Meeting Channel Paste a Google Meet, Zoom, or Microsoft Teams link and your AI employee joins the call as a real participant. It listens the whole time, speaks up when you address it by name, and writes a summary to memory and Drive once the call ends. Paste a Google Meet, Zoom, or Microsoft Teams link and your AI employee joins the call as a real participant. It listens the whole time, speaks up when you address it by name, and writes a summary to memory and Drive once the call ends. One backend covers all three platforms, so you never pick a different setup for a Zoom call versus a Meet call. The employee joins in one of two modes. Silent mode is the default: it sits in the call, transcribes everything said, and never speaks. Active mode lets it talk back, but only when you address it directly by name, the same wake-word pattern used on the Voice channel. If it hears no one address it, it stays quiet and keeps listening, so a silent notetaker never accidentally interrupts a meeting it was only invited to watch. What separates this from a generic recording bot is that it is one of your named employees, not a faceless notetaker widget. It shows up under its own name and avatar, it carries whatever tools, memory, and permissions that employee already has, and the notes it takes land in the same Drive and journal the employee uses for every other channel. A recording tool hands you a transcript; this employee can be asked about the call afterward in the same thread it wrote its notes in. ## How Billing Works Meeting minutes bill in real time, about 8.3 credits per minute the employee spends in the call, charged every 60 seconds rather than as one lump sum at the end. That means you see the cost accrue as the call runs, and if your balance runs out mid-call, the meter ends the meeting instead of letting it continue for free. If the employee is speaking when the balance runs out, it finishes its current sentence before leaving rather than cutting off mid-word. Anything the employee says or thinks through during the call, in active mode, is billed the same way as any other chat message: through the normal token-credit pipeline, not the per-minute meeting rate. The two charges are separate and never double-counted. ## Why The Bot Leaves On Its Own Four timers protect you from a bot burning credits in an empty or stuck room. If everyone else leaves and the bot is the only one left, it exits after 30 seconds. If ten minutes pass with no audio at all, it leaves on silence. If it sits in a waiting room without being admitted, or a host never starts the meeting, it gives up after ten minutes on either. A separate 15-minute backstop clears a session that never confirms it joined at all, and a 4-hour cap force-ends any call that runs unusually long, in case the normal end signal is ever missed. Whichever timer fires, the employee can tell you plainly why it left rather than leaving you guessing. ## After The Call Ends The moment the call is over, the full transcript is written to Drive as a dated markdown file, so it is there to read or search even if the employee never says anything about it. Separately, the employee gets a short private nudge in its own thread, reads the transcript, writes a summary into its memory, and can recap the call back to you without you having to ask. Only that short summary, not the raw transcript, is written into the employee's longer-term memory graph, which keeps a single meeting from flooding its memory with page after page of transcript text. ## How It Works **The employee joins as a voice participant, answers from your knowledge, and turns commitments into tasks.** In the meeting, the employee listens and speaks like a participant rather than a silent recorder. Ask a question out loud and it answers in real time from your training data, documents, and past conversations, so decisions can be made in the room instead of deferred. Work assigned during the call is captured as real tasks on the employee's board, and a transcript and summary are filed automatically when the meeting ends. The attendee that contributes is also the one that follows up. ## Use Cases ### Silent notetaker on an internal call Invite the employee to sit in on a team call in silent mode. It transcribes the whole conversation, saves it to Drive, and writes a summary afterward, so nobody has to take notes by hand. ### Answering questions live on a customer call Put the employee in active mode and address it by name mid-call to pull up an answer, a number, or a status update on the spot, the same way you would ask a colleague sitting in the room. ### Joining straight from chat Paste a meeting URL into any chat with the employee instead of opening a separate invite screen, and it joins that call directly from the conversation you were already in. ### Picking up the thread after the call Because the meeting summary lands in the employee's memory, you can ask it what was decided or discussed in a past call from a normal chat message, well after the meeting itself has ended. ## Comparison | Before | After | |---|---| | Meeting AI listens silently and reports later. | The employee participates in the conversation live. | | Unanswered questions become follow-ups. | Answers from your knowledge arrive in the room. | | Action items depend on the note taker. | Commitments become tasks the employee executes. | | A bot that only records the meeting. | An attendee that contributes and follows up. | ## FAQ ### Does the employee talk during the call by default? No. It joins silent by default, listening and transcribing only. It only speaks in active mode, and even then only when you address it by name; otherwise it stays quiet and keeps taking notes. ### What happens if my credits run out while the employee is in the call? The per-minute meter checks your balance as it bills, and once it runs out the employee leaves the call. If it was mid-sentence in active mode, it finishes that sentence before exiting rather than cutting off mid-word. ### What if the bot never gets let in, or sits waiting for the host? It will not wait forever. A bot stuck in a waiting room, or waiting on a host who never starts the meeting, gives up and leaves after ten minutes, and tells you which of the two happened. ### Where do the notes go after the meeting? The full transcript is saved to Drive as a dated file automatically, whether or not the employee says anything about it. The employee also writes a short summary into its own memory and can recap the call to you in chat without being asked. ## Where Meeting Channel fits Meeting Channel is part of Ways you talk to them. Chat in the app with live reasoning, speak to your AI voice agent over a call, message on Slack or WhatsApp, send an email, or embed a widget on your website. Every channel connects to the same AI agent with the same memory and capabilities. Switch channels mid-conversation and your employee picks up right where you left off. - [Ways you talk to them](/en/features/channels): Every channel. One conversation. ## Read the guide - [Guide: Meeting Channel](/en/guide/channels/meeting) ## More in Channels - [Web Chat](/en/features/channels/channel_web_chat): Chat with any AI employee directly in the workspace, with a streaming reply, a live execution timeline showing what it is reading, thinking, and doing, and inline approve/reject buttons when it needs a sensitive action confirmed. It is the default channel: nothing to configure, works on desktop or mobile, and every conversation persists so you can pick it back up later. - [Voice Calls](/en/features/channels/voice_channel): Voice Calls is a planned channel for speaking to an AI employee out loud and hearing it reply in real time, instead of typing. It is not available yet: there is no voice button in the workspace today, and the feature is paused while the underlying voice flow is redesigned. When it ships, a voice call will run through the same skills, tools, and memory as a typed conversation. - [Connect an Email Provider](/en/features/channels/channel_email): Point your own SendGrid, Mailgun, or Postmark inbound-parse webhook at a tenant-scoped endpoint and every email that lands there gets turned into work for an employee. Forward support requests, sales inquiries, or internal approval emails and the employee reads the sender, subject, and body, then acts on it in the background. You get a 202 response immediately; there's no waiting on the request. - [Personal Mailbox](/en/features/channels/channel_mailbox): Every employee gets its own email address on the shared Sistava domain the moment you hire it, no setup. Email it directly, CC it on a thread with other people, or forward something over, and it reads and replies within seconds. Free to send from, with a monthly cap by plan. Control the shared employee signature in Company Profile, or connect your own Gmail or Outlook when you want it sending as you, with no cap. - [Send from Gmail or Outlook](/en/features/channels/connected_mailbox): The built-in employee address is free and always on, but it sends as the employee, not as you. Connect your own Gmail or Outlook instead and an employee sends and replies from your real address, in your name, with no monthly sending cap on any plan. - [Talk to Your Employee on Video](/en/features/channels/channel_in_app_video): In-App Video is a planned channel for live, face to face video calls with an AI employee, camera and microphone, directly inside the workspace. It has no working implementation today: it appears in Settings > Technical > Channels as a Coming soon placeholder only. Once it ships, it is meant to run on the same execution pipeline as every other channel, so the employee keeps its skills, tools, training, and conversation memory on a video call. If you need an employee in a live call today, it can already join a Google Meet, Zoom, or Microsoft Teams meeting as a participant, which is a different capability and available now. - [Chat Widget](/en/features/channels/channel_chat_widget): The Chat Widget will let you embed an AI employee directly on your public website so visitors can ask questions and get answers without leaving the page. It is on the roadmap and is not available to configure yet: today it appears in Settings > Technical > Channels as a Coming soon placeholder with no setup, embed snippet, or Manage action. - [SMS](/en/features/channels/channel_sms): SMS is a planned channel for reaching an AI employee by ordinary text message, with no app to install. It is on the roadmap and not available today: there is no SMS number, no inbound texting, and no way to turn it on yet. Until it ships, use web chat or Telegram for mobile access from any phone. - [WhatsApp](/en/features/channels/channel_whatsapp): WhatsApp is a planned messaging channel for talking with an AI employee from your phone. It is not connected yet: the card shows as coming soon and cannot be set up today. When it ships, it will carry the same employee memory, skills, and guardrails as web chat, Telegram, Slack, and the mailbox. Telegram and Slack are live now and give you the same access from a phone, so nothing you set up today has to be rebuilt when WhatsApp arrives. - [Discord](/en/features/channels/channel_discord): Discord is a planned channel for bringing an AI employee into the servers and direct messages your community already uses. It will connect the same way Slack does today: authorize a bot through OAuth, then map it to one employee. It is not available to connect yet, so no Discord traffic reaches an employee until it ships. Slack, Telegram, each employee's own email address, and web chat cover the same job in the meantime. - [Calendar Invites](/en/features/channels/channel_calendar): Add your employee's personal address as a guest on any Google, Outlook, or Apple calendar event and they show up for the meeting automatically, no RSVP or extra app on your side. Once the meeting starts, the employee joins the Meet, Zoom, or Teams call, listens, speaks when addressed, and writes a summary afterward. There is nothing to switch on for the invite itself, just turn on the Meeting Attender tool for that employee once. - [Slack Channel](/en/features/channels/channel_slack): Bring your AI employee into Slack as a real bot user your team can mention, DM, or trigger with a slash command. Every reply lands in the same thread, and memory, tasks, skills, and tools stay shared with web chat, so a conversation started on Slack continues anywhere else. You approve or reject requests right from Slack, and the bot only speaks when mentioned, DM'd, or already in a thread. ## Explore - [Every feature](/en/features) - [Hire an AI employee](/en/market) - [Pricing](/en/pricing)