You can meet your AI employee. Two ways: in its chat, where a Meet button starts a meeting and the employee answers by voice within seconds, and in Google Meet or Zoom, where you add its email to the invite and it attends the way a colleague does. Both are meetings: the same employee, the same voice, the same tile, listed together in the Meetings app. This guide covers both: what happens in a meeting in the chat, what it costs, what is stored, and then the full chapter on outside meetings (inviting, invite policy, recording, the Meetings app, voice and Never-say lines, host prerequisites).
Every AI employee's chat has a Meet button beside the dictation microphone, with the same meeting glyph as the Meetings app. Click it and:
The employee's voice starts on its standing briefing: what the platform knows about it (its name, title, company, coworkers and your Never-say lines) plus the briefing the employee keeps for itself (its positions, what it is working on, the questions it expects). The tile reads "on briefing" for the first moments; the employee itself is woken the instant the meeting starts, and when its judgment is with you the tile changes to "judgment with you". From then on, anything that needs a decision, a commitment or its memory goes to the employee's own judgment while the conversation continues, exactly as in a meeting.
You can type while you talk. A message you type during a meeting in the chat is sent and answered exactly as it always is; the voice is aware that you typed and what you said.
Mute (on the tile) silences your microphone locally; the employee keeps talking. Ending: click End on the tile, click the Meet button again (or hold it), or say goodbye and let the employee end the meeting. The button shows Wrapping up, and when the meeting has ended the tile turns back into the Refer a Friend card. A meeting also ends on its own after 60 minutes, after 5 minutes with nothing said on either side, or 90 seconds after you close the last tab it was open in.
Reloading or moving to another page does not end a meeting. Come back and the tile is there; your browser reconnects the audio on its own, or shows a Rejoin button when it needs a tap first. A second tab shows the same tile, with the audio staying in the tab that had it.
One meeting at a time. You are in one meeting on CellCog at a time, whichever chat or employee it is with: End it before starting another. An employee, too, holds one live conversation at a time, whether in its chat, in a Google Meet or Zoom meeting, or on a call; if it is busy elsewhere, the Meet button tells you where.
Shared employees. A teammate you have shared an employee with can meet it from the shared chat exactly as you do. Their meeting counts against their own one-at-a-time limit, not yours, and the employee holds the conversation the way it holds yours. The credits are yours, as with everything a shared employee does, and your Meetings app names who started each meeting.
Some things the employee never does on its own, in a conversation as in a meeting: it does not commit your company to dates, prices, scope or promises, and it does not send, schedule or change anything on the strength of the voice alone. Anything binding comes from its judgment and your approvals, never from the voice.
A meeting in the chat costs what it used, the seconds of voice time and the quick-answer model's work, plus the employee's own thinking, like any meeting. The chat's credits header moves within seconds of the end, and the conversation's record in the Meetings app shows the exact amount charged. See the Billing Guide, "What Work Costs".
Records are kept with the employee and are deleted when the employee is deleted.
Before you ever click Meet, the employee keeps a briefing for exactly that moment: the positions it may state, what it is working on, the questions it expects and their answers. It refreshes this briefing when its work changes, so the first seconds of a conversation sound like the employee you know. The conversation's record shows how old the briefing was; an older briefing never delays a conversation.
Your AI employee can attend Google Meet and Zoom meetings the way a colleague does: you add its email to the calendar invite, it accepts, shows up on time under its own name, listens to everyone, answers what it is authorized to answer, and writes the notes afterwards. The rest of this guide covers what it does in a call, how to invite it, the settings you control, what is stored, and the Meetings app on its computer.
Your employee joins with its camera off and a small tile that shows its name, your company and whether it is listening or speaking. In the call it:
Some things it never does on its own. It does not commit your company to dates, prices, scope or promises, and it does not send, schedule or change anything during the call. When a question needs one of those, it says in its own words that it is looking into it and will come back, lets the conversation continue, and either brings the answer in at the next natural gap or follows up after the call. This is the same rule it follows in email: anything binding comes from a decision you or its brief already made, never from the voice in the room.
Your employee joins as {Name} (AI, {Company}); the name tag says it is an AI, and asked directly it says so plainly. It does not recite an introduction. It comes in quietly, answers a greeting, introduces itself when someone asks, and, when it organized the meeting, opens it, keeps it moving and closes with the decisions. When recording is on, it says so within the first minute. Your Never say lines still govern what it says, whatever it is asked and whatever its notes hold.
In a group, it takes part the way a colleague does. It joins as a participant, hears everyone in the call and takes notes for you. What you say in the room sets its role there: "just take notes today" or "we'll bring you in when we need you" reaches it as part of the conversation, the same way it reaches everyone else in the call. There is nothing to click.
Every employee has its own email address (shown in its settings and on the Meetings app's empty state). Add that address to a calendar invite in Google Calendar, Zoom or Outlook, as you would for a colleague. Your employee:
You can also ask it in chat ("join the Acme call at 3, here is the link") and it schedules itself the same way.
Before it joins, your employee edits a prepared draft. The platform fills in what it already knows (the meeting id, the times in your timezone, the organizer and attendees, the invite text, the employee's own role and settings); the employee adds its judgment: what this room may hear, the questions it expects, and what to defer to you. You can read the result in the Meetings app before the join and whisper a correction.
Your employee joins meetings you, your organization or people it has emailed with invite it to. For anyone else it decides the way a colleague would: who the person is, whether you or a teammate mentioned them, what the meeting is about, and whether you are attending. A stranger's invite that you are not part of is normally declined, and the employee mentions notable declines in its report so you can correct it. There is no approval to grant and no policy to configure; you can always ask it in chat to join or skip a meeting.
Every employee attends meetings by default; switch it off in the Settings app on its computer, under Meetings, and it then declines invites politely.
Recording is off by default. With recording off, your employee keeps a transcript and its notes and nothing else. Our meeting provider, which joins the call for the employee, captures the audio to transcribe it and deletes its copy when the meeting ends.
You can turn recording on per employee (Record meetings in its settings). When recording is on, the employee announces it at the start of the meeting; shortly after the call the recording is saved in its workspace next to the transcript, and our meeting provider deletes its copy. Recording laws differ by region; the announcement is there so every participant hears it.
Meeting records and transcripts are kept with the employee and are deleted when the employee is deleted. The voice service the employee speaks through stores nothing for us; it may keep the conversation for up to 30 days to monitor for abuse.
Each employee's computer has a Meetings app (the Employee Computer, in the chat header) with three tabs:
Whisper works before the meeting too: a brief sent from the Upcoming tab reaches the employee when it prepares.
Your employee speaks with one of a set of natural voices, the same voice in the chat and in meetings. It chooses its own when it names itself during onboarding: it declares whether it presents as female or male and picks a voice to match. You can change the voice any time under Voice in the Settings app on its computer, where the voices are grouped the way their maker labels them (feminine, masculine, and a few unlabeled). The voice is fixed for the length of a conversation.
Never say is a short list of lines the employee keeps out of every conversation and meeting, whatever it is asked: pricing beyond your public page, other customers' names, unannounced work. It applies these on top of its own judgment about what is public.
If your employee could not join, the meeting shows as "Was not let in" or "Did not join" in the Past tab, and the employee lets you know.
Attending a meeting is metered from what it used: the meeting bot's time in the call, the seconds of voice time and the quick-answer model's work during the meeting, each at the vendor's own price with the usual credit conversion; the employee's own thinking bills the way it always does. See the Billing Guide, "What Work Costs". The cost of each past meeting is shown on its record in the Meetings app in credits, the exact amount deducted from your balance for that meeting (it reads "Settling" for a few minutes after the call while the charge is recorded).
Your employee can also hold its own phone number. A call to it is the same conversation as a meeting in the chat: the same voice, the same judgment behind it, one live conversation at a time. Calls are listed in the Phone app on the Employee Computer rather than in Meetings. See the Phone Guide.
Yes, two ways: from the chat in a mobile browser with the same Meet button, or by calling your employee's own phone number from your phone once it has one (see the Phone Guide).
No. An employee holds one live conversation at a time, on any surface: its chat, a Google Meet or Zoom meeting, or a call. You, too, are in one meeting on CellCog at a time. The Meet button says who is busy where.
Nothing you need to fix. The meeting tile comes back and the audio reconnects on its own, or with one tap on Rejoin. A meeting ends by itself 90 seconds after the last tab it was open in is closed.
The employee attends to the conversation while it runs; everything else waiting for it (a task comment, an email, a routine) is picked up when the conversation ends.
Not yet. Today it joins with a presence tile that shows its name and whether it is listening or speaking.
It answers within what it prepared and what its brief allows; anything about dates, prices, scope or actions goes back to you before it is said. You can read everything it said in the transcript, whisper a correction mid-call, or mute it.
Say so in the meeting, the way you would to a colleague: "just take notes today" or "we'll call on you when we need you." Your words reach it as part of the conversation and set its role for that meeting. To stop it hearing the room altogether, use Mute in the Meetings app.
It stays until the meeting wraps up or it is asked to leave; when everyone else has gone, it leaves too.
Not yet.
Yes, if both are invited. Each joins under its own name.
It joins meetings you, your organization or people it has emailed with invite it to, and uses its judgment for anyone else: who they are, whether anyone mentioned them, whether you are attending. A stranger's invite you are not part of is normally declined. Tell it in chat to join or skip any meeting.