Docs · Meetings
Send Cedric to the meeting.
Two ways in, notes throughout, answers when addressed, and a summary in the channel before people have left the room.
- Two ways to invite it: drop the call link in the thread, or add its address to the calendar invite like any colleague.
- It takes notes for the whole call and posts the summary to the channel when the call ends.
- Address it by name during the call and it answers out loud, from your connected tools.
- Actions it picks up are queued for approval afterwards, never executed live in the room.
- When the last person from your workspace leaves, Cedric leaves too.
Why the notes are the smallest part
Plenty of tools transcribe a call. The transcript is rarely the thing anyone wanted; nobody reads a transcript, and the parts worth keeping are the decisions, the commitments, and the things somebody now has to do.
What makes an in-meeting Cedric different is that it is the same Cedric as the one in your channel, with the same connected tools and the same shared memory. It can answer a question during the call from live data, and when someone commits to something it treats that as work to queue, not a sentence to write down.
The summary lands in the channel where the work happens, so the people who were not in the room get the outcome in the place they already look, next to the conversation it came out of.
Getting Cedric into a call
Pick whichever fits how the meeting was arranged.
- 01
Option one: drop the link in the thread
Paste the call link and ask Cedric to join. Best for ad-hoc calls and for the meeting somebody started five minutes ago.
- 02
Option two: put it on the calendar invite
Cedric has its own address. Add it as an attendee when you create the meeting and it joins on its own at the start time, like a colleague who is never late.
This is the better default for recurring meetings. Set it once on the series and every occurrence is covered.
- 03
Tell the room it is there
Cedric is a visible participant, not a hidden listener, and saying so once at the start is both courteous and, in many places, legally necessary.
- 04
Address it by name to ask something
Say "Cedric, what did we ship last week?" and it answers in the call. It stays quiet otherwise; it does not interject.
- 05
Read the summary afterwards
Posted to the channel when the call ends, with the decisions, the open items, and anything it has queued for approval.
During the call
Answering when addressed, from live data.
Lucia Moreau9:14 AM
Cedric, what did we ship last week?
CedricAPP9:15 AM
Eleven pull requests merged last week. The notable ones: the checkout null-guard fix, the new pricing page, and the billing test suite. The referral leaderboard was merged but not deployed, it is still waiting on a release. I will put the links in the channel after the call.
Only when addressed
It answers to its name and stays silent otherwise. It does not interrupt, summarise as you go, or offer opinions nobody asked for.
From your real systems
The answer comes from the tools you have connected, so it is as current as your systems are.
Follows up in the channel
Anything with links, files, or detail goes to the channel afterwards, where you can actually use it.
Actions are queued, never taken live
When someone says "we should send Halcyon the security pack", Cedric registers that as an action rather than a line in a transcript. What it does not do is send it during the call.
Every action picked up in a meeting is queued and appears for approval in the channel afterwards, with the context of who said it and when. This is the same approval gate that applies everywhere else, and it matters more in a meeting, not less: conversation is full of hypotheticals, half-decisions, and things people said before changing their mind two minutes later.
The summary also separates what was decided from what was only discussed. Something the room concluded is reported as a decision. Something raised and left hanging is reported as open, which is usually the more useful half.
After the call
The summary, and what it queued.
CedricAPP10:02 AM
Weekly growth sync, 31 minutes, six attendees. Decisions: paid social restarts Monday at the previous budget, and the pricing page test is extended two weeks for significance. Open: nobody owns the Q3 forecast rewrite yet, and the tracking issue from the site migration is unresolved. One action queued for approval: send Halcyon the security pack, which Devin offered to do. Full notes attached.
Consent, and the things to decide first
Recording and note-taking law varies by jurisdiction, and it is your responsibility. Some regions require all-party consent. Announce Cedric's presence at the start, and treat that as a floor rather than a full compliance programme.
External calls need more thought than internal ones. For customer and candidate calls in particular, decide your policy before it becomes a question in the room.
It leaves when your team leaves. If the last person from your workspace drops off, Cedric goes too, so it never sits in a room with only external participants.
Noisy calls are harder. Crosstalk, poor audio, and six people at once degrade the notes exactly as they degrade a human note-taker's.
It is not a participant in the decision. It answers what it is asked. Judgment in the room stays with the people in the room.
FAQ
It joins by call link or by calendar invite, which covers the common platforms teams use. Drop a link in the thread and it will tell you plainly if it cannot join that one.
It takes notes and produces a summary. Announce its presence at the start regardless, and check what your jurisdiction requires for external calls.
No. It answers when someone addresses it by name and stays quiet otherwise. It does not narrate, summarise as it goes, or volunteer thoughts.
It queues the action for approval afterwards. Nothing is sent, changed, or spent during the call itself. See [how approvals work](/docs/how-approvals-work).
Cedric leaves too. It will not remain in a room with only external participants.
Yes, and it is the best use. Add it to the calendar series once and every occurrence is covered without anyone remembering.
To the channel you asked from, so they sit with the work they came out of. The dashboard keeps a copy too.
Ready when you are
Put Cedric on the next invite.
Install it where your team talks, then add it to a recurring meeting and read the summary afterwards.
$50 in free credits, no card needed.