# AlefOS Full Documentation AlefOS is a work operating system connected to AI assistants. It turns contacts, calls, messages, groups, missions, calendar context and business signals into operational memory and controlled actions. Canonical domain: https://alefos.ai # MCP Cockpit Last updated: 2026-07-03 MCP Cockpit is the public operational surface of AlefOS for AI assistants such as ChatGPT, Claude and Grok. ## MCP endpoints These are the public MCP connection endpoints for supported AI assistants: - ChatGPT: https://alefos.ai/mcp/gpt - Claude: https://alefos.ai/mcp/claude - Grok: https://alefos.ai/mcp/grok ## Purpose MCP Cockpit is not a debug panel and not a raw database browser. It is the operational cockpit used by AI assistants to work with AlefOS from the user point of view. ## What assistants can do Assistants can search contacts, open contact context, list missions, inspect groups, read call context and transcripts when available, view calendar context, prepare drafts and route protected actions through confirmation. ## Validation rule AlefOS can prepare work, but protected actions must not be executed silently. Messages, group posts, calendar creation, product creation and other engaging actions must go through confirmation. AlefOS prepares. The user decides. ## What AlefOS is and is not AlefOS is a work operating system, an operational memory, an AI cockpit for real business context and a protected execution system. AlefOS is not a generic chatbot, a manual CRM, a social network, a phone operator, a WhatsApp replacement or a Google Calendar replacement. ## Typical questions - What missions do I need to validate? - Who is waiting for a callback? - What did we decide in the team group? - Which client needs a follow-up? - What happened in the last call? - Prepare a message draft, but do not send it yet. ## Important notes - AlefOS prepares. The user decides. - Protected actions must go through confirmation before execution. # Contacts Last updated: 2026-07-03 Contacts in AlefOS are not static records to fill manually. They become living operational memory, enriched from real work. ## The problem Customer information is often scattered across calls, WhatsApp, calendar events, group decisions and personal memory. AlefOS connects those fragments so a team can understand where a relationship stands. ## What a contact becomes An AlefOS contact can include recent calls, important messages, meetings, open missions, planned follow-ups, requested documents, discussed products or services, decisions, objections, promises and next actions to approve. ## Automatic enrichment AlefOS can connect useful information from calls, messages, meetings and groups to the right contact. The contact becomes richer as the company works, without asking the team to manually enter every detail. ## AI over contact memory Once context is connected, an assistant can answer using real AlefOS memory: history, missions, signals, meetings, products, groups and recent interactions. ## Key takeaway In AlefOS, contacts are the living memory of company relationships. They help answer what is known, where things stand and what should happen next. ## Typical questions - Where are we with this person? - What did we promise them? - Who should I call back today? - Which contacts mentioned the Team offer? # Missions Last updated: 2026-07-03 Missions are the execution engine of AlefOS. They transform captured work into clear, tracked and validated actions. ## Why missions exist Work disappears through small missed actions: callbacks, promised documents, quotes, meeting confirmations and decisions. Missions turn those signals into action. ## What a mission is A mission is an operational action connected to context. It explains who is involved, what happened, why the action exists, what needs to be done, when it should happen and who needs to validate it. ## Difference from a task A task may say "Call Marc." An AlefOS mission should explain why the call is needed, what was said, what is expected and what can be prepared. ## Protected actions Sending a message, publishing in a group, creating a meeting, changing important information or confirming an engaging action must go through validation. ## Key takeaway Missions are the bridge between what the company knows and what the company needs to do. AlefOS detects. AlefOS prepares. The user validates. ## Typical questions - What do I need to validate today? - Which follow-ups are late? - Which customer is waiting for a reply? - What has been prepared but not executed yet? ## Important notes - AlefOS detects and prepares. The user validates and executes. # Groups Last updated: 2026-07-03 Groups are shared operational memory spaces. They make collective work searchable, understandable and reusable. ## What a group is A Group is a shared memory space around a team, topic, process, department, customer segment, professional network or business workflow. ## Internal team memory Groups can preserve important decisions, pricing updates, objections, scripts, instructions, meeting summaries, procedures, repeated questions and customer feedback. ## Professional networks Groups can also support partner networks, professional communities, shared opportunities, product availability, service requests and field coordination. ## From message to action A Group can help create a mission, prepare a message, suggest an introduction, detect an opportunity, alert a manager, prepare a summary or suggest the next step. ## Key takeaway A Group should not only talk. It should remember, find and help act. ## Typical questions - What changed this week? - What did we decide during Monday meeting? - Which objection comes back most often? - Does anything match this customer request? # Calls Last updated: 2026-07-03 Calls in AlefOS turn important phone conversations into operational memory. ## Why calls matter Phone calls often contain the most important business information: needs, objections, promises, appointments, documents and decisions. ## CallOS and AlefOS PBX CallOS is the AlefOS call layer. It can work as a phone number or participant that the user adds to a conference call. It is not designed to automatically listen to every call in the company. ## Adding AlefOS during a call During an important call, the user can add AlefOS like another participant. The call can then feed operational memory, summaries, missions and follow-ups. ## External call integrations Calls can also come from external platforms when connected, authorized and available. The logic stays the same: useful calls should enrich contacts, create missions and help the team follow real work. ## Key takeaway A call should not disappear when it ends. It should enrich the company memory. ## Important notes - AlefOS is voluntarily added to selected important calls. - AlefOS is not automatic listening on every call. # Calendar Last updated: 2026-07-03 Calendar in AlefOS is operational memory around appointments, meetings, reminders, field visits, customer follow-ups and planned actions. ## The problem A calendar often says when something happens, but not why it exists, what was promised or what needs to be prepared. ## Appointment memory A calendar event can be connected to a contact, company, mission, call, message, group, address, phone number, field note, decision or action to validate. ## Before and after meetings AlefOS can prepare context before an appointment and help create follow-up actions after it: messages, missions, documents, summaries and next calls. ## Google Calendar When Google Calendar is connected, AlefOS can use calendar context to enrich operational memory while Google Calendar remains the calendar tool. ## Key takeaway An appointment should not only be scheduled. It should help the company remember, prepare and act. ## Important notes - AlefOS does not replace Google Calendar. # WhatsApp Last updated: 2026-07-03 WhatsApp can become part of AlefOS operational memory when connected and authorized. ## What WhatsApp means in AlefOS AlefOS helps structure business context around authorized WhatsApp conversations when the integration is connected and allowed. ## WhatsApp memory Authorized conversations can contain customer requests, addresses, documents, voice notes, promises, appointment details and follow-up needs. ## Follow-ups from messages When message data is available, AlefOS can help answer what a customer asked for, what is waiting and which follow-up should be prepared. ## Key takeaway WhatsApp remains the communication tool. AlefOS adds memory, structure and action around authorized business conversations. ## Important notes - AlefOS does not replace WhatsApp. - Discovery should not be presented as including a full WhatsApp connection. # Aircall Last updated: 2026-07-03 Aircall can feed AlefOS with business call activity when connected and authorized. ## Call activity Aircall can provide business call activity that helps AlefOS enrich contacts, detect follow-ups and create missions. ## Contact matching When data is available, AlefOS can connect calls to the right contact and relationship memory. ## Manager visibility Managers can use call summaries, missions and follow-up signals to understand what happened and where help is needed. ## Key takeaway Aircall is an input. AlefOS turns useful call context into operational memory and action. # Google Calendar Last updated: 2026-07-03 Google Calendar connects external scheduling context to AlefOS. ## Connected agenda When connected, Google Calendar can provide appointments and scheduling context that AlefOS can connect to contacts, missions and follow-ups. ## Meeting preparation AlefOS can help prepare meeting context from available memory: recent exchanges, promises, missing documents and points to check. ## Protected actions Calendar-related actions such as creating or updating events should be prepared by AlefOS and validated by the user before execution. ## Key takeaway Google Calendar remains the calendar. AlefOS adds business memory around the agenda. # Discovery Last updated: 2026-07-03 Discovery is the free access level for AlefOS. It is a real limited personal workspace, not an empty demo account. ## What Discovery is Discovery gives limited access to selected AlefOS features so users can understand contacts, visible memory, missions, allowed actions, invited groups, limited products or services and assistant answers based on permissions. ## Current limits Discovery currently includes up to 25 visible contacts and up to 3 active products or services. It allows search over visible work memory and limited AlefOS access from compatible assistants. ## What is not included Discovery does not include full WhatsApp connection, outbound message sending, full call automation, full calendar automation, Team management, managers, company deployment or full advanced integrations. ## Key takeaway Start small, understand AlefOS memory and upgrade when real work needs to be connected more deeply. ## Important notes - Use Limited AlefOS access, not Limited ChatGPT access. - Do not promise full WhatsApp connection, outbound messages or Team features in Discovery. # Solo Last updated: 2026-07-03 Solo is the AlefOS plan for one person who wants to organize real work without needing a full team setup. ## Who Solo is for Solo is designed for independent professionals, entrepreneurs, salespeople, consultants, service providers, agents, brokers and business owners managing their own customers. ## What Solo provides Solo gives one user a personal operational memory across contacts, relationships, missions, follow-ups, reminders, important calls, messages, appointments, products, services, accessible groups and actions to validate. ## ChatGPT with AlefOS memory The user can ask practical questions such as which customers to call back, what was promised, which appointments are coming and which contacts mentioned an offer. ## Validation and control AlefOS prepares messages, follow-ups, missions, summaries and suggested actions. The user keeps the final decision before engaging actions. ## Key takeaway Solo is not a manual CRM or a simple todo list. It is a memory and action layer above real work. # Team Last updated: 2026-07-03 Team is the AlefOS plan for companies, sales teams, field teams, managers and organizations that need shared operational memory. ## Who Team is for Team is built for organizations with several people: sales teams, phone teams, field teams, agencies, professional firms, partner networks, support teams and small or medium businesses. ## Shared operational memory Team brings together contacts, calls, messages, appointments, missions, groups, products or services, decisions, scripts, objections, field feedback, customer follow-ups and actions to validate. ## Owner, users and managers The Tenant / Owner is the central company memory and first management layer. Field users feed memory through daily work. Managers have authorized visibility and a cockpit for their scope. ## Permissions and visibility Team is based on permissions. Not everyone sees everything. Visibility can be organized by roles, managers, teams, groups, contacts, missions and authorized scope. ## Deployment Team is not only a subscription. It includes deployment work such as tenant setup, owner and manager configuration, permissions, groups, integrations, training and onboarding support. ## Pricing model Team pricing depends on the company structure, number of users, number of managers and deployment needs. For a Team plan adapted to the company structure, contact AlefOS Sales. ## Key takeaway Team is not several Solo accounts. It is operational memory with users who feed it, managers who drive it and an Owner who controls the tenant. ## Important notes - Do not expose the full internal pricing formula publicly. - Detailed pricing belongs in sales conversations. # Deployment Last updated: 2026-07-03 Deployment is the setup process that helps Team customers configure AlefOS correctly. ## Purpose Deployment makes sure the company structure is correctly represented in AlefOS before memory starts growing. ## What deployment includes Deployment can include tenant creation, owner setup, manager setup, permissions, teams, groups, integrations, initial configuration, manager training and onboarding support for the initial deployment. ## Managers require configuration Adding a user is usually simple. Adding a manager requires configuration, permissions, visibility rules, groups, cockpit setup and onboarding. ## Pricing-safe description Deployment starts from an entry-level Team setup and grows with the company structure. Exact deployment pricing should be confirmed with AlefOS Sales. ## Key takeaway Deployment is what turns a Team account into a working company memory with the right roles, permissions and habits.