Your AI should understand the work before it helps you act.

AlefOS is designed to help an AI understand the work before it helps someone act.

First, AlefOS can read the authorized context around a customer, mission, appointment, call, message or group. It can then help find what matters, explain what happened or prepare the next step.

That first part is an AI analysis. On plan surfaces, this capacity is shown as AI reads. Internally, it is Loop1.

An analysis does not send anything, change a record or make a decision for the user.

An AI action is used when AlefOS prepares a supported change or next step from the available context. Internally, this is Loop2.

For example, AlefOS may prepare a customer reply, a follow-up mission, an appointment or a booking link when the relevant tool, plan and permissions support it.

The important distinction is simple:

• An analysis helps understand the work.
• An action prepares something to happen in the work.

Protected or engaging actions remain drafts until the responsible user reviews and confirms them.

A customer has asked for a revised proposal and wants to meet on Tuesday.

1. The user asks: “What did Marc ask for, and what is still open?”
2. AlefOS uses the authorized customer context to prepare a readable answer. This is an AI analysis.
3. The user asks AlefOS to prepare a follow-up or a booking link with the times they want to offer. This can be an AI action when the workflow is supported.
4. The user reviews the draft and confirms only what should happen.

The value is not automatic execution. It is moving from the right context to a prepared next step without losing control.

Available actions depend on the connected tools, plan, configuration and permissions. When supported, AlefOS can help prepare:

• A customer message or follow-up for review.
• A Mission linked to the customer and the reason behind it.
• A personal appointment or calendar change for confirmation.
• A booking link with the availability and supported questions needed for one appointment.
• A supported ownership, assignment or workflow change in a Team workspace.

AlefOS should never be presented as silently sending every message, changing every record or acting outside the user’s authorized scope.

AlefOS does not turn a question into an uncontrolled automation.

• It works only with context that is available and authorized.
• Permissions still limit what a person or assistant can access.
• A prepared message, appointment or other engaging action can remain a draft.
• The responsible user reviews protected actions before execution.
• An analysis can explain what is missing; it does not invent the missing information.

The user remains responsible for the decision. AlefOS makes the context and next step easier to review.

Plans include a monthly amount of AI capacity.

• AI reads are the included capacity for analyses of new, connected work context.
• AI actions are the included capacity for supported draft-and-confirm workflows.

Free includes 100 AI reads and 5 AI actions each month. Solo plans provide more monthly capacity while keeping the same AlefOS features. In Team, seat capacity contributes to one shared monthly pool.

Existing AlefOS data remains available when a capacity is reached. The available next step is shown by the plan and configuration in use.

AI capacity is not a charge for mysterious background activity.

It is the capacity AlefOS uses to understand new authorized work context and to prepare supported next steps.

First understand. Then prepare. The user remains in control of what happens next.

An AI analysis helps AlefOS read, organize or explain authorized work context. An AI action prepares a supported next step, such as a draft message, Mission, appointment or booking link, when the workflow is available.

Yes. Loop1 is the internal name for the analysis capacity shown publicly as AI reads. Loop2 is the internal name for the supported action capacity shown publicly as AI actions.

No. An analysis helps understand the available context. It does not send a message, change a record or execute an external action.

No. AlefOS can prepare supported actions, but protected or engaging actions remain subject to the required review, confirmation, configuration and permissions.

That depends on the plan, connected tools, configuration and permissions. AlefOS shows only the actions supported in the current context; it should not imply that every possible action is available to every user.

Existing AlefOS data remains available. New analyses or supported actions resume in the next monthly plan cycle or when the available capacity is increased according to the plan in use.