Everyday work

Managers: understand what is waiting for a decision

Know what needs a decision and keep customer work moving when someone leaves, is absent or changes roles. Find the promises and open questions before assigning the next person.

See how it works See the workflow ↓Tools and access conditions

The useful result: understand where to intervene.

Managers need to distinguish available facts, open commitments and pending decisions within their scope. This internal use does not imply universal data access or inclusion in the initial customer application.

Workflow example

A concrete workflow, from the signal to the next step

A customer is waiting, but several teams hold parts of the context.
Identify the outstanding quote, missing document and responsible people.
The manager reviews the dependency that needs a decision.
The team continues the approved next step within its access rights.

Fictional illustration. Available capabilities, sources and access depend on your environment; conditions are explained below.

On this page

Visibility into work, not only messages

This workflow concerns business leaders, sales managers, team leaders, operations managers and coordinators. A file can combine a customer request, provider response, appointment and internal approval.

Reading messages separately is not enough to understand the blocker. Working memory must connect people, facts, commitments, missions and decisions accessible to the manager.

Your business cannot depend on who remembers.

A colleague leaves with several customer cases still open. Before reassigning them, find the promises, unanswered questions and appointments in the available history. Exchanges captured from connected sources reduce reliance on a report written at the last minute.

The replacement receives the appropriate assignments and permissions. From the web or a compatible assistant, they can ask what was promised and consult the shared procedures they are allowed to use. Missing information still needs checking; reassignment does not grant access to every former colleague’s message.

Questions that usually require several calls

Which customers are waiting for a reply? Which quote requires approval? Which intervention has no owner? Who is waiting for a document? What changed since the last meeting?

Answers use available contacts, missions, appointments, signals and groups. Missing information must remain missing; the briefing does not invent progress.

From a message to a management signal

A discount request is a message. A quote that cannot be sent without a decision is a work dependency. AlefOS helps keep that reason with the relationship and expected action.

The manager can consult the authorized file, decide within their role and continue the intended workflow. An oral decision does not automatically become recorded data if no source supplies it.

Example: one customer, three dependencies

A customer awaits a quote; the salesperson awaits price approval; installation depends on a time slot and a part. The briefing should show those dependencies, not three isolated reminders.

After the decision, the salesperson prepares the response, the appointment can follow its workflow and missions keep their owners. Each action’s result must be checked separately.

Groups organized around the activity

Groups can hold a department’s procedures, decisions, recurring questions or knowledge. They make it possible to find a rule and reuse it in an authorized file.

Shared groups must not mix customer, subsidiary or partner contexts without controls. An approved practice may be common; confidential file information does not become common with it.

What the OS does not decide

AlefOS helps retrieve context and prepare actions. It does not replace a manager’s judgement, guarantee performance or provide universal employee surveillance.

Views depend on roles, groups, connections and data actually available. Trend analysis is not an official accounting or HR indicator if that calculation does not exist in the product.

Turn a signal into a decision

Signal / blockage	Person expected	Decision to prepare
A quote is waiting for approval.	The designated approver.	Review scope and price before authorizing the next step.
An intervention lacks a part.	The owner of the supply follow-up.	Check availability before proposing another visit.
Two colleagues are following up the same request.	The relationship owner.	Clarify ownership and use the latest authorized context.

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.

Signals and controlled actions

Adding a signal can enrich memory and prepare pending work without executing an outbound action. An action_id identifies prepared work; its execution and result must remain distinguishable from a read-only answer.

Tool	Function and effect
`signals.search`	Search extracted signal titles and content by keyword.
`signals.get`	Read an accessible signal, its participants and linked missions.
`signals.add`	Enrich memory from a structured note or source; missing details can require clarification. No outbound action is executed.
`signals.update`	Correct or enrich an existing signal without creating another one.
`alefos.briefing`	Read a compact briefing across visible actionable work and recent context.
`alefos.daily_summary`	Read a summary for one local calendar day within the current scope.
`actions.confirm`	Execute previously prepared work identified by action_id after confirmation.

Read this module’s documentation →

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.

Tool	Function and effect
`groups.list`	List accessible private groups and recent shared context.
`groups.get`	Read a group and the membership context visible to the current user.
`groups.search`	Search group entries by text, topic, kind and date range.
`groups.digest`	Read a compact digest without publishing anything.
`groups.messages`	Read recent shared work entries in an accessible group.
`groups.draft_send`	Preview or publish a structured entry according to confirmMode.
`groups.message.update`	Edit an existing entry with the required author or administrator rights.
`groups.message.archive`	Archive an entry with the required author or administrator rights.
`groups.members.add`	Add an authorized company member or prepare an external contact invitation.
`groups.members.remove`	Remove membership within the role’s scope; the group creator cannot be removed.

Read this module’s documentation →

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.

Tool	Function and effect
`missions.list`	List the current user’s missions, optionally grouped by contact.
`missions.get`	Read a mission’s source, related objects and execution state.
`missions.confirm`	Confirm and execute a pending mission.
`missions.reject`	Reject a pending mission without executing it.
`missions.archive`	Archive a mission without executing or deleting its action.
`missions.assign`	Assign from the company queue or reassign with the required role; changes are audited.

Read this module’s documentation →

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

This workflow uses capabilities configured in your company’s environment, under your brand. Your team can use a compatible assistant to consult authorized context through its configured MCP connection. Understand your AI connection ↗

Prepare the team handover.

Assignments and access during a handover ↗