Understand your work OS
Meetings: keep the decision working after everyone leaves.
Recover what was decided, who is responsible and what remains open from the meeting content made available to your OS.
A calendar meeting is not a transcript.
Meetings provide context when content exists, is accessible and can be used in the agreed journey. This connection is scoped separately from the customer application. Missing decisions and minutes are not invented.
Everyday work
The meeting is over. Are we all acting on the same decision?
The calendar has the date. The useful outcome is often in notes or a transcript. Connected meeting content can keep the decision with the customer and the work that follows.
From a meeting decision to a clear handover.
01DecisionKeep what was agreed.
The team changes the preparation for a visit.
“Léa asks the customer for the access plan. Alex checks the equipment before we confirm the visit.”
A meeting link alone does not provide these notes.
02ResponsibilityFind who takes the next step.
“What did we agree to prepare?”
Léa: access plan. Alex: equipment check. Visit confirmation still depends on those checks.
Review the recorded decision before creating or assigning follow-up work.
03Follow-upKeep the decision available.
The team prepares the next mission from the reviewed notes.
Request the plan, check the equipment, then review readiness. Publish a reusable method in the appropriate group if the team chooses to share it.
A summary does not automatically publish knowledge to every group.
Fictional example, not a product screenshot. Sources and access require configuration; illustrated answers use the information shown.
Keep your meeting tool. Define what it supplies.
Notes, transcripts and recordings depend on the provider, account and permissions. Setup verifies the actual content available. The calendar schedules the meeting; this connection supplies what can be retained from it.
Make shared knowledge reusableOn this page
The provider remains the meeting tool
Zoom, Google Meet or another verified provider continues to host the meeting. AlefOS uses only notes, summaries, transcripts or events actually available through the connected workflow.
Google Meet transcript processing requires an active connection, an eligible account and access to the meeting’s content.
From a meeting to a retrievable decision
Context can connect participants, decisions, owners and actions to the right customer, project, group or appointment. A useful result is more than a summary: it must preserve what was decided and what still needs doing.
Example: a meeting changes the scope of a visit and leaves a document outstanding. The next preparation must keep the new scope, the person supplying the document and the dependency before scheduling.
Prepare work after the meeting
Depending on the workflow and available data, the OS can prepare a mission, message, next appointment or briefing. A report can be published in the right group through an authorized workflow.
Executing an action and distributing a report remain separate from analysis. Information intended for an internal group must not automatically be sent to all external participants.
Prerequisites and missing data
Access depends on the provider account, permissions, generated content and consent rules. A calendar event with a meeting link does not guarantee a transcript.
If the provider does not produce or expose the content, the interface must say so. AlefOS must not invent a report or present itself as automatic surveillance of every meeting.
Check each provider’s content separately
Google Meet: transcript processing exists in the implementation; account eligibility and access to the artifact still need checking. Zoom: review which recording, summary or transcript the chosen account and connection can actually provide. Microsoft Teams and Webex: assess the account, permissions, artifact access and supported integration before committing to a workflow.
A provider named here is not an active connector guarantee. Confirm three things: the meeting took place, the content was generated, and AlefOS can access it through the delivered connection. If an artifact is absent, preserve that absence instead of inventing a recap.
Meeting sources: check each connection
Scroll the table to read every column. With a keyboard, use the left and right arrow keys.
| Path | What is received | Condition to verify |
|---|---|---|
| Google Meet | Available meeting material, including transcripts when supplied and authorized. | Implementation identified; activation, account permissions and source availability must be checked for your environment. |
| Zoom | The material that the selected account and connection can supply. | Connection to assess. A brand in the catalogue does not establish an active integration. |
| Teams / Webex / other | Scope to establish before use. | Assess compatibility, permissions and the actual input; do not assume a native connector. |
Operational reference
Modules, tools and access conditions
This reference describes MCP operations and their effects. The list exposed to your assistant depends on the deployed server, enabled modules and permissions. Reading, preparing and executing are distinct operations.
Calendar and booking context
An invitation, a booking link and a confirmed event are not the same state. Draft tools support review; authorized internal calendar operations can also run directly, according to the deployed tool policy.
Scroll the table to read every column. With a keyboard, use the left and right arrow keys.
| Tool | Function and effect |
|---|---|
calendar. | List appointments, optionally filtered by date range. |
calendar. | Read an event’s available owner, contact, mission and provider context. |
calendar. | Prepare an event creation preview with an action_id. |
calendar. | Prepare an update or move preview for an existing event. |
calendar. | Assign or reassign an event with the required company role and audit trail. |
GroupOS knowledge and publishing
Search and digest are read operations. Publishing uses its confirmation mode. Updating or archiving a post and changing membership require the relevant author or administrator rights.
Scroll the table to read every column. With a keyboard, use the left and right arrow keys.
| Tool | Function and effect |
|---|---|
groups. | List accessible private groups and recent shared context. |
groups. | Read a group and the membership context visible to the current user. |
groups. | Search group entries by text, topic, kind and date range. |
groups. | Read a compact digest without publishing anything. |
groups. | Read recent shared work entries in an accessible group. |
groups. | Preview or publish a structured entry according to confirmMode. |
groups. | Edit an existing entry with the required author or administrator rights. |
groups. | Archive an entry with the required author or administrator rights. |
groups. | Add an authorized company member or prepare an external contact invitation. |
groups. | Remove membership within the role’s scope; the group creator cannot be removed. |
Missions and responsibility
Read the source and execution state before acting. Confirming executes a pending mission; rejecting and archiving have different effects. Assignment follows company roles.
Scroll the table to read every column. With a keyboard, use the left and right arrow keys.
| Tool | Function and effect |
|---|---|
missions. | List the current user’s missions, optionally grouped by contact. |
missions. | Read a mission’s source, related objects and execution state. |
missions. | Confirm and execute a pending mission. |
missions. | Reject a pending mission without executing it. |
missions. | Archive a mission without executing or deleting its action. |
missions. | Assign from the company queue or reassign with the required role; changes are audited. |
Scroll the table to read every column. With a keyboard, use the left and right arrow keys.
| Source | What must be verified |
|---|---|
| WhatsApp Business | Authorized business messages; account permissions and received events must be verified. Existing private groups are not automatically imported into GroupOS. Reference → |
| Aircall | An ingestion path exists. Verify the company account binding, user mapping and actual call content before describing the connection as active. Reference → |
| Google Calendar / Google Meet | Calendar actions and Meet transcript processing depend on the configured connection. An event link does not guarantee a transcript: provider access and generated content are separate prerequisites. Reference → |
| Other providers | Check APIs, webhooks, exports, permissions and actual content. A provider name in an example is not a claim of a ready or active integration. Reference → |
The scenarios on this page illustrate workflows, not real customer data or guaranteed outcomes. Connections and capabilities must be enabled and verified for your environment. Official business systems retain their responsibilities.
Continue exploring
A capability of your company’s environment. Your team can use this capability from a compatible assistant through its configured MCP access. The deployment defines the enabled tools and permissions. Understand your AI connection ↗