Understand your work OS
Your business in your AI assistants. AlefOS connects the work.
AlefOS makes your business accessible from ChatGPT and compatible AI assistants. Your MCP access runs under your domain. Your team retrieves authorized context and acts on work; your customers reach the catalogue, appointment requests and documents you make available to them. Permissions and interfaces are defined for your project.
A customer application. A workspace for your team.
The first customer journey presents authorised offers and collects enquiries. Your identity, catalogue and submitted information are configured for your company.
Internal functions connect exchanges, knowledge and next actions under the selected modules and permissions. They are not all part of the customer base scope.
Workflow example
Capture. Retrieve. Act.
Supported, authorized connections bring useful exchanges into your company’s environment.
Your team retrieves the customer history, commitments and knowledge it is allowed to consult.
Authorized people prepare or carry out the available actions through the web or a compatible assistant, following each tool’s rules.
Fictional illustration. Available capabilities, sources and access depend on your environment; conditions are explained below.
On this page
- Several ways to access your work OS
- Work begins in conversations
- Your identity, shared services
- From context to a verifiable action
- Everyday tools keep their role
- OS, CRM, assistant and provider
- One company OS, configured around your work
- When connecting one tool is enough — and when your work needs more
- Your team works. Your customers can reach you.
- One relationship, from enquiry to follow-up
- Tools and prerequisites
Several ways to access your work OS
The MCP server lets a compatible assistant consult context and call authorized tools. The dashboard and web app provide the viewing, configuration and tracking screens available in the deployment. Booking, product and message links give access to a specific object under its own rules.
This does not mean installing an operating system on every employee’s computer. The company has a work environment accessible through the interfaces it needs. An MCP interface embedded in ChatGPT does not imply the same graphical interface in Claude or Grok.
Your MCP connection can use an address such as ai.yourcompany.com. This example represents the access point configured for your project, not a ChatGPT website or a transfer of AlefOS technology. The agreed scope defines connections, identity, permissions and interfaces.
Work begins in conversations
A customer calls, clarifies a need in a message, then changes a deadline during a meeting. A colleague takes over the file. Each tool holds part of the story, but the company still needs to understand what is true now, what was promised and who is waiting for what.
AlefOS connects those moments to the relationship and the work that needs to continue. A contact record, a mission, a group decision and an appointment become entry points into the same authorized context.
Your identity, shared services
The name, logo, workflows and useful modules are configured for the company. AlefOS remains the shared foundation: identity, work context, permissions, connections and execution of supported actions.
Personalizing an environment neither transfers ownership of AlefOS source code nor rebuilds a separate engine for each customer. Workflow adaptations are scoped from the existing foundation.
From context to a verifiable action
An authorized conversation can provide a need, an objection, an outstanding document or a promise. That context is attached to the right relationship. A mission keeps the reason, responsible person and deadline available.
Reading information, preparing a draft and executing an action are different operations. Sending follows the intended approval flow. Some internal changes can execute directly following an explicit, authorized request. The details depend on the tool, role and workflow.
Everyday tools keep their role
WhatsApp Business remains a conversation channel. The phone provider manages calls and numbers. The calendar organizes appointments. A meeting provider can supply notes or a transcript when they exist and are accessible.
Useful connections are enabled and checked during deployment: accounts, permissions and content actually received. Your team can then see which sources are available.
OS, CRM, assistant and provider
The work OS keeps relationships, shared knowledge and authorized workflows connected. CRM is one way to work on customer relationships. A compatible assistant is a conversational access surface. A provider supplies a channel or source, such as telephony or meeting content. Each keeps its own role.
One company OS, configured around your work
AlefOS provides the shared foundation, MCP access, permissions and supported connections. Configure the capabilities and workflows your company needs without rebuilding that infrastructure.
Contacts, IBOX, shared knowledge, calendar, calls and missions are capabilities of that environment. The scope defines which are enabled, which interfaces are delivered and which adaptations are needed. Branding does not transfer ownership of the shared AlefOS code.
When connecting one tool is enough — and when your work needs more
If your team only needs to consult a CRM from ChatGPT, check the connection offered by that CRM first. AlefOS addresses a broader situation: customer exchanges spread across channels, shared methods, responsibilities and actions that need to remain useful as people take over.
Your branded environment can bring those capabilities together around the workflow agreed for your company. An MCP address such as ai.yourcompany.com makes that environment accessible to compatible assistants. The value is the customer work your team can continue, not the domain name on its own. White-label presentation concerns the agreed identity and interfaces; it does not transfer ownership of AlefOS technology.
Your team works. Your customers can reach you.
Your team uses ChatGPT to retrieve the context needed to move work forward. Your customers use your business plugin to explore services, request an appointment or retrieve an authorized document.
These audiences have different access. AlefOS configures the journeys under your brand and domain, prepares the plugin for publication and handles the submission process and review feedback.
One relationship, from enquiry to follow-up
Your catalogue presents the offer. SalesOS prepares a personalised proposal. SignOS organises the document signing. The customer space keeps shared information available over time. Appointments, messages and tasks help your team accompany the same customer. We configure the useful functions around your business.
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.
Contacts and relationship context
Search identity fields, read linked context and inspect confirmed products. Adding or enriching a contact is a write operation; the preview mode depends on the tool policy.
Scroll the table to read every column. With a keyboard, use the left and right arrow keys.
| Tool | Function and effect |
|---|---|
contacts. | Search contacts by identity fields, with cursor pagination and source filtering. |
contacts. | Read one contact profile and its available relationship context. |
contacts. | Find confirmed products in the contact’s product memory. |
contacts. | Add or enrich a contact; preview behavior follows the selected mode. |
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. |
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. |
IBOX messages
A stored message, an external notification and a read receipt are different states. A temporary /m/:token link grants access to its message; keep that link private.
Scroll the table to read every column. With a keyboard, use the left and right arrow keys.
| Tool | Function and effect |
|---|---|
ibox. | List IBOX messages visible to the current user. |
ibox. | Read one accessible IBOX message. |
ibox. | Record a message as read. This does not send a reply. |
messages. | Prepare an outbound message preview with an action_id for confirmation. |
actions. | Execute previously prepared work identified by action_id after confirmation. |
ProductOS catalog
A detected suggestion, a confirmed internal product and a published /p/:productId page are distinct. Check the record and publication scope before sharing an offer.
Scroll the table to read every column. With a keyboard, use the left and right arrow keys.
| Tool | Function and effect |
|---|---|
products. | List managed products and services within current catalog limits. |
products. | Read a managed catalog product or service. |
products. | Prepare a product or service creation preview. |
products. | Update an internal product; preview mode returns an action_id. |
products. | Archive an internal product; preview mode is available. |
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.
What you avoid rebuilding.
You do not start with an empty development project: AlefOS provides the foundation, configures your identity and catalogue, and tests browsing and enquiry journeys. Your team can then update offers in the delivered interfaces. Additional integrations and changes are scoped separately.
Continue exploring