{
  "title": "Missions",
  "internal_name": "MissionOS",
  "slug": "missions",
  "url": "https://alefos.ai/documentation/missions",
  "json_url": "https://alefos.ai/documentation/missions.json",
  "summary": "Turn a promise made in a call or message into a contextual next action ready for review.",
  "description": "A customer says “call me Friday.” AlefOS keeps the reason, prepares the next step and waits for the user to approve it.",
  "category": "Core",
  "last_updated": "2026-07-23",
  "keywords": [
    "missions",
    "follow-ups",
    "callbacks",
    "validation",
    "execution"
  ],
  "sections": [
    {
      "heading": "Why missions exist",
      "content": "In a company, work does not usually disappear all at once. It disappears through small missed actions.\n\nA customer asks to be called back. A document is promised. A quote needs to be sent. A meeting needs to be confirmed. A manager gives an instruction. A salesperson says \"I will handle it.\" A decision is made during a meeting.\n\nThen the information stays inside a call, a message, a note or someone memory.\n\nThe problem is not only finding the information later. The problem is turning that information into action. That is the role of Missions."
    },
    {
      "heading": "What an AlefOS mission is",
      "content": "A mission is an operational action connected to context.\n\nIt does not only say: do something.\n\nIt explains:\n\n- Who is involved.\n- What happened.\n- Why the action exists.\n- What needs to be done.\n- When it should happen.\n- Who needs to validate it.\n- What the next step is.\n\nA mission can be a callback, follow-up, reply to prepare, document to request, quote to send, meeting to confirm, internal action, decision to apply, action from a Group or action that requires approval before execution.\n\nA mission is the bridge between memory and action."
    },
    {
      "heading": "Difference from a task",
      "content": "A normal task often looks like this: Call Marc.\n\nAn AlefOS mission should be able to explain:\n\nMarc asked for a callback on Friday after the last conversation. He is waiting for an updated proposal. He asked for details about deployment. A reply can be prepared before the call.\n\nThe difference is important.\n\nA task says what to do. An AlefOS mission explains why, with what context, and what can be prepared."
    },
    {
      "heading": "How a mission is created",
      "content": "A mission can be created manually, but its real value comes from signals captured in daily work.\n\nExamples:\n\n- In a call: call me back tomorrow.\n- In a message: send me the document.\n- In a meeting: David owns the follow-up.\n- In a Group: the procedure needs to be updated.\n- In an appointment: prepare the file before the meeting.\n- In a sales conversation: the customer wants to compare offers.\n- In a support exchange: reply with the approved procedure.\n\nAlefOS detects the signal, links it to the right context and prepares a mission."
    },
    {
      "heading": "AlefOS prepares, the user decides",
      "content": "AlefOS can prepare an action.\n\nBut it should not execute an engaging action without validation.\n\nAlefOS can prepare a message, follow-up, callback, summary, update, meeting proposal or action linked to a contact or Group.\n\nBut the user keeps the final decision.\n\nAlefOS prepares. The user validates."
    },
    {
      "heading": "Protected actions",
      "content": "Some actions must always go through validation.\n\nFor example:\n\n- Sending a message.\n- Publishing in a Group.\n- Creating a meeting.\n- Changing important information.\n- Triggering a customer-facing action.\n- Confirming an engaging mission.\n\nThe mission becomes a control point. It shows what is ready, what needs review and what can be executed."
    },
    {
      "heading": "Missions for a user",
      "content": "For a user, missions answer simple questions:\n\n- Who should I call back?\n- What did I promise?\n- Which message is ready?\n- What document is missing?\n- Which follow-up is late?\n- What do I need to validate today?\n\nInstead of searching through calls, WhatsApp, notes or calendar events, the user sees the important actions in one place."
    },
    {
      "heading": "Missions for a manager",
      "content": "For a manager, missions give a clear view of execution.\n\nThe manager can ask:\n\n- What missions are open?\n- Which follow-ups are late?\n- Which customers are waiting for a reply?\n- Which salesperson has blocked actions?\n- What missions need validation today?\n- What has been prepared but not executed yet?\n\nThe manager no longer depends only on messages or verbal updates. They can drive activity from structured AlefOS memory."
    },
    {
      "heading": "Concrete examples",
      "content": "Customer follow-up: a customer asks to be called back on Friday. AlefOS can create a mission with the contact, last exchange, reason for callback, planned time, information to prepare and a suggested message or call script.\n\nMessage to prepare: a user asks AlefOS to prepare a reply for a customer. AlefOS can draft a response linked to real context. The mission stays pending until validation.\n\nMeeting decision: during a meeting, a decision is made. AlefOS can create a mission with the decision summarized, owner identified, follow-up date, related Group and expected action.\n\nMissing document: a document is expected. AlefOS can create a mission with the requested document, related contact, follow-up date, prepared reminder message and tracking status."
    },
    {
      "heading": "Missions and operational intelligence",
      "content": "Missions are not only a list.\n\nWith enough missions, a manager can see which actions happen often, where teams get blocked, which customers wait too long, which documents are often missing, which follow-ups create sales, which types of actions should be automated and which teams execute properly.\n\nMissions become a management signal."
    },
    {
      "heading": "Assignment, takeover and the company queue",
      "content": "A Team mission can be assigned to one responsible member, explicitly reassigned or returned to the company queue.\n\nAssignment is never silent. The responsible member remains visible, takeover is explicit and every assignment or revocation is audited.\n\nReturning a mission to the company queue removes the individual assignee without making the work disappear. Authorized teammates can still see that the mission is waiting for responsibility."
    },
    {
      "heading": "Key takeaway",
      "content": "Without missions, memory stays passive. It knows what happened, but it does not help the company act.\n\nWith Missions, AlefOS connects three things:\n\nMemory -> Decision -> Execution.\n\nMissions are the bridge between what the company knows and what the company needs to do. AlefOS detects. AlefOS prepares. The user validates. The company moves forward."
    }
  ],
  "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?"
  ],
  "related_pages": [
    "contacts",
    "ibox",
    "groups",
    "calendar",
    "calls",
    "team-ownership"
  ],
  "important_notes": [
    "AlefOS detects and prepares. The user validates and executes."
  ],
  "markdown": "# Missions\n\nLast updated: 2026-07-23\n\nA customer says “call me Friday.” AlefOS keeps the reason, prepares the next step and waits for the user to approve it.\n\n## Why missions exist\n\nIn a company, work does not usually disappear all at once. It disappears through small missed actions.\n\nA customer asks to be called back. A document is promised. A quote needs to be sent. A meeting needs to be confirmed. A manager gives an instruction. A salesperson says \"I will handle it.\" A decision is made during a meeting.\n\nThen the information stays inside a call, a message, a note or someone memory.\n\nThe problem is not only finding the information later. The problem is turning that information into action. That is the role of Missions.\n\n## What an AlefOS mission is\n\nA mission is an operational action connected to context.\n\nIt does not only say: do something.\n\nIt explains:\n\n- Who is involved.\n- What happened.\n- Why the action exists.\n- What needs to be done.\n- When it should happen.\n- Who needs to validate it.\n- What the next step is.\n\nA mission can be a callback, follow-up, reply to prepare, document to request, quote to send, meeting to confirm, internal action, decision to apply, action from a Group or action that requires approval before execution.\n\nA mission is the bridge between memory and action.\n\n## Difference from a task\n\nA normal task often looks like this: Call Marc.\n\nAn AlefOS mission should be able to explain:\n\nMarc asked for a callback on Friday after the last conversation. He is waiting for an updated proposal. He asked for details about deployment. A reply can be prepared before the call.\n\nThe difference is important.\n\nA task says what to do. An AlefOS mission explains why, with what context, and what can be prepared.\n\n## How a mission is created\n\nA mission can be created manually, but its real value comes from signals captured in daily work.\n\nExamples:\n\n- In a call: call me back tomorrow.\n- In a message: send me the document.\n- In a meeting: David owns the follow-up.\n- In a Group: the procedure needs to be updated.\n- In an appointment: prepare the file before the meeting.\n- In a sales conversation: the customer wants to compare offers.\n- In a support exchange: reply with the approved procedure.\n\nAlefOS detects the signal, links it to the right context and prepares a mission.\n\n## AlefOS prepares, the user decides\n\nAlefOS can prepare an action.\n\nBut it should not execute an engaging action without validation.\n\nAlefOS can prepare a message, follow-up, callback, summary, update, meeting proposal or action linked to a contact or Group.\n\nBut the user keeps the final decision.\n\nAlefOS prepares. The user validates.\n\n## Protected actions\n\nSome actions must always go through validation.\n\nFor example:\n\n- Sending a message.\n- Publishing in a Group.\n- Creating a meeting.\n- Changing important information.\n- Triggering a customer-facing action.\n- Confirming an engaging mission.\n\nThe mission becomes a control point. It shows what is ready, what needs review and what can be executed.\n\n## Missions for a user\n\nFor a user, missions answer simple questions:\n\n- Who should I call back?\n- What did I promise?\n- Which message is ready?\n- What document is missing?\n- Which follow-up is late?\n- What do I need to validate today?\n\nInstead of searching through calls, WhatsApp, notes or calendar events, the user sees the important actions in one place.\n\n## Missions for a manager\n\nFor a manager, missions give a clear view of execution.\n\nThe manager can ask:\n\n- What missions are open?\n- Which follow-ups are late?\n- Which customers are waiting for a reply?\n- Which salesperson has blocked actions?\n- What missions need validation today?\n- What has been prepared but not executed yet?\n\nThe manager no longer depends only on messages or verbal updates. They can drive activity from structured AlefOS memory.\n\n## Concrete examples\n\nCustomer follow-up: a customer asks to be called back on Friday. AlefOS can create a mission with the contact, last exchange, reason for callback, planned time, information to prepare and a suggested message or call script.\n\nMessage to prepare: a user asks AlefOS to prepare a reply for a customer. AlefOS can draft a response linked to real context. The mission stays pending until validation.\n\nMeeting decision: during a meeting, a decision is made. AlefOS can create a mission with the decision summarized, owner identified, follow-up date, related Group and expected action.\n\nMissing document: a document is expected. AlefOS can create a mission with the requested document, related contact, follow-up date, prepared reminder message and tracking status.\n\n## Missions and operational intelligence\n\nMissions are not only a list.\n\nWith enough missions, a manager can see which actions happen often, where teams get blocked, which customers wait too long, which documents are often missing, which follow-ups create sales, which types of actions should be automated and which teams execute properly.\n\nMissions become a management signal.\n\n## Assignment, takeover and the company queue\n\nA Team mission can be assigned to one responsible member, explicitly reassigned or returned to the company queue.\n\nAssignment is never silent. The responsible member remains visible, takeover is explicit and every assignment or revocation is audited.\n\nReturning a mission to the company queue removes the individual assignee without making the work disappear. Authorized teammates can still see that the mission is waiting for responsibility.\n\n## Key takeaway\n\nWithout missions, memory stays passive. It knows what happened, but it does not help the company act.\n\nWith Missions, AlefOS connects three things:\n\nMemory -> Decision -> Execution.\n\nMissions are the bridge between what the company knows and what the company needs to do. AlefOS detects. AlefOS prepares. The user validates. The company moves forward.\n\n## Typical questions\n\n- What do I need to validate today?\n- Which follow-ups are late?\n- Which customer is waiting for a reply?\n- What has been prepared but not executed yet?\n\n## Important notes\n\n- AlefOS detects and prepares. The user validates and executes."
}