{
  "title": "CallOS",
  "h1": "CallOS keeps customer promises visible after the call ends.",
  "internal_name": "CallOS",
  "aliases": [
    "CallOS",
    "AlefOS Calls",
    "Calls"
  ],
  "slug": "callos",
  "internal_slug": "calls",
  "url": "https://alefos.ai/documentation/callos",
  "json_url": "https://alefos.ai/documentation/callos.json",
  "summary": "Keep your existing number and phone system. Add AlefOS to selected calls so important promises, decisions and next actions can become operational memory.",
  "description": "CallOS is the AlefOS call module for turning supported and authorized calls into usable work context.",
  "category": "Core",
  "last_updated": "2026-08-16",
  "keywords": [
    "AI call notes",
    "AI phone call notes",
    "phone call note taker",
    "AI call summary",
    "call recap",
    "call action items",
    "customer call notes",
    "call follow-up",
    "CallOS"
  ],
  "sections": [
    {
      "heading": "Keep your phone system",
      "content": "Keep your number.\nKeep your phone system.\nAdd AlefOS only when the conversation becomes worth remembering.\n\nCalls already happen through the phone habits, operators and systems the user has today. CallOS does not ask the user to port a number, replace an operator or start with a heavy telephony deployment.\n\nWhen a customer call becomes important, the user can add AlefOS like another participant in the conversation. The goal is selective AI call notes: preserve the useful promise, objection, decision or next step without turning every phone call into an automatic recording workflow."
    },
    {
      "heading": "Why AlefOS does not listen to every call",
      "content": "Not every call deserves to become company memory.\n\nSome conversations are private. Some are operationally irrelevant. Some calls only need a quick answer. AlefOS is designed so the user chooses the calls that should feed operational memory.\n\nThis keeps minutes focused on the moments that matter, lets users keep their normal phone habits and avoids treating every minute of every conversation as business context.\n\nAlefOS should not be described as permanent native listening, automatic recording of every call or a replacement for the phone system."
    },
    {
      "heading": "Two ways to use CallOS",
      "content": "### Mode A: selected important call\nThe user adds AlefOS when a customer call is important enough to preserve. AlefOS can use the call content available after it joins the conversation.\n\nExamples:\n\n- A prospect gives a clear objection.\n- A customer asks for a callback.\n- A decision changes the next step.\n- A quote, document or meeting is promised.\n\n### Mode B: closing recap\nThe user can add AlefOS near the end of the call and make an explicit recap.\n\nFor example: \"One moment, I'm adding my assistant so we can recap the next steps.\"\n\nThe recap can include:\n\n- appointment fixed\n- quote to prepare\n- document expected\n- objection to address\n- person responsible\n- callback date\n- next decision\n\nIf AlefOS did not participate in the beginning of the call, it does not automatically know the previous content. In closing-recap mode, the memory depends on what the user explicitly summarizes while AlefOS is present."
    },
    {
      "heading": "A short recap can preserve the entire next step",
      "content": "A call can last twenty or thirty minutes. AlefOS does not need to be present for every minute to help preserve the action that matters.\n\nThe user can add AlefOS during the final two or three minutes, recap the customer commitment and let the available recap become structured context.\n\n### Example: field service\nA customer calls about an intervention. The closing recap can preserve that the visit is tomorrow morning, access is through the building guard, a quote must be sent and a missing photo or document is still expected.\n\n### Example: real estate\nAfter a long buyer conversation, the recap can preserve the confirmed budget, a second visit on Thursday, financial documents expected and a callback planned for Friday.\n\n### Example: sales\nAfter a discussion about an offer, the recap can preserve the budget objection, the revised proposal to prepare, the manager validation needed and the follow-up planned after reception."
    },
    {
      "heading": "What AlefOS turns into memory",
      "content": "When call data is available and authorized, AlefOS can help structure useful business context:\n\n- customer request\n- promise\n- objection\n- callback\n- appointment\n- missing document\n- decision\n- owner\n- deadline\n- next action\n- product or service discussed\n\nThe distinction matters:\n\n### Call transcript\nThe available content of the conversation, when it exists, is authorized and was received by AlefOS.\n\n### Call summary\nA readable synthesis of what was understood from the available call content or recap.\n\n### Operational context\nThe useful elements connected to the contact, customer relationship, group or mission.\n\n### Mission\nAn identifiable action to prepare, verify or accomplish.\n\nNot every call automatically creates a mission. AlefOS can help detect actions, prepare follow-ups and surface next steps when call data is available and the user has permission to use it."
    },
    {
      "heading": "After the call",
      "content": "The call ends.\nThe customer commitment remains visible.\n\nAfter a selected call or closing recap, the user can:\n\n- find what was promised\n- prepare a callback\n- create or review a mission\n- prepare a message\n- recover context before the next call\n- ask an AI assistant such as ChatGPT, Claude or Grok about authorized call context\n- let an authorized manager understand the situation\n- validate protected actions before execution\n\nAlefOS prepares. The user decides."
    },
    {
      "heading": "Set it up once. Add it in seconds.",
      "content": "CallOS is the AlefOS call layer for selected calls.\n\nIn practical use, the user can keep the AlefOS call number available from the app when it is provided for the workspace and plan, save it as a favorite phone contact and use a quick phone method such as an iPhone Shortcut with confirmation.\n\nRecommended setup:\n\n- Find the AlefOS call number available for the account, workspace and plan.\n- Save it as AlefOS Assistant or AlefOS Call Assistant.\n- Create a shortcut or fast dialing method supported by the phone.\n- Keep a confirmation step before launching the call to AlefOS.\n- Add AlefOS to the conference only when the call should become memory.\n\nThe shortcut is not a business approval workflow inside AlefOS. It is a phone-level safety step to avoid accidental calls and unexpected minute usage."
    },
    {
      "heading": "Use minutes where they matter",
      "content": "Free includes 15 minutes of analyzed calls per cycle.\n\nSolo includes 500 call minutes per month.\n\nTeam may include up to 5,000 call minutes according to Team deployment and MinutesOS configuration.\n\nThe minutes do not need to cover every minute of every conversation. A short closing recap can preserve the decisions and next actions that matter.\n\nUsers can choose the calls that deserve AI call notes, use AlefOS for an important section of a conversation or invite AlefOS at the end for a structured recap.\n\nActual usage depends on the customer workflow, call length, connected tools, plan and available call data."
    },
    {
      "heading": "CallOS and connected call providers",
      "content": "CallOS and connected call providers are different paths.\n\n### CallOS selective participant model\nThe user voluntarily adds AlefOS to a call or closing recap. There is no mandatory number porting, no required replacement of the phone system and no automatic capture of every call.\n\n### Connected call provider\nSome customers may already use a compatible call provider. In that case, an external provider can transmit call data according to its own configuration, permissions, plan and available data.\n\nThe provider carries the call. AlefOS helps the useful call context become operational memory, missions and next actions."
    },
    {
      "heading": "How Calls differs from adjacent categories",
      "content": "### AI call notes\nAlefOS can structure the important information from a selected call or closing recap so the useful context remains available after the call.\n\n### Full call recording\nAnother category of product may record complete conversations. AlefOS should not be presented as automatically recording every call.\n\n### AI voice agent\nAn AI voice agent speaks to the customer in place of the user. CallOS helps the user preserve context from a human conversation.\n\n### Phone system\nThe phone system transports the call. AlefOS helps the useful content become memory and next action."
    },
    {
      "heading": "Missions created from calls",
      "content": "A call can help prepare missions when the available context contains an action.\n\nExamples:\n\n- Call a customer back on Friday.\n- Send a document.\n- Prepare a quote.\n- Confirm a meeting.\n- Notify a manager.\n- Follow up with a prospect.\n- Update a procedure.\n- Prepare a message after the call.\n\nAlefOS can help detect these actions, prepare them and present them to the user for validation."
    },
    {
      "heading": "Manager visibility",
      "content": "For teams, calls are an important management signal.\n\nA manager may need to understand which customers were called, which prospects are warm, which objections came back, which follow-ups are late, which calls created missions, which users need help and which conversations should be reviewed.\n\nAlefOS helps turn authorized call context into management visibility. The manager no longer depends only on what the user remembers after the call. They can ask AlefOS when permissions allow it."
    },
    {
      "heading": "Best practices",
      "content": "To use Calls effectively:\n\n- Save the AlefOS number as a favorite contact.\n- Use AlefOS only on important calls.\n- Create a shortcut or quick dialing method with a confirmation step.\n- Avoid launching calls without confirmation.\n- Review detected missions after the call.\n- Validate actions before execution.\n- Connect calls to the right contacts.\n- Monitor the minute balance.\n- Train teams to add AlefOS at the right moment.\n\nThe goal is not to add complexity. The goal is to avoid losing what was said in important calls."
    },
    {
      "heading": "Key takeaway",
      "content": "CallOS is not a new phone system.\n\nThey are a selective source of operational memory.\n\nThe user keeps the existing number and phone system, adds AlefOS when the call is worth remembering and reviews protected actions before anything is executed.\n\nThe simple idea: important calls should not disappear when they end. They should preserve the promise, decision and next step."
    }
  ],
  "typical_questions": [],
  "faq": [
    [
      "What are AI call notes?",
      "AI call notes are structured notes from available call content or a user recap. In AlefOS, they can preserve promises, decisions, objections, action items and follow-ups as operational memory."
    ],
    [
      "Do I need to change my phone number to use AlefOS?",
      "No. CallOS is designed so the user can keep the existing number and phone system, then add AlefOS to selected calls when needed."
    ],
    [
      "Does AlefOS listen to every phone call?",
      "No. AlefOS is added voluntarily to selected important calls or invited for a closing recap. It is not permanent automatic listening on every call."
    ],
    [
      "Can I add AlefOS only for the final recap?",
      "Yes. The user can add AlefOS near the end of a call and recap the next steps while AlefOS is present."
    ],
    [
      "Does AlefOS know what happened before it joined the call?",
      "No. If AlefOS joins late, it does not automatically know earlier content. The memory then depends on the recap or available call data."
    ],
    [
      "Can a call create action items or follow-ups?",
      "AlefOS can help detect and prepare action items when the available call context contains them. The user reviews protected actions before execution."
    ],
    [
      "Does AlefOS record the full call automatically?",
      "No. AlefOS should not be described as automatically recording every call. It can use selected call content or a closing recap when available and authorized."
    ],
    [
      "How are Solo call minutes used?",
      "Solo includes 500 call minutes per month. Users can spend those minutes on selected important calls or short closing recaps instead of every minute of every conversation."
    ],
    [
      "Can AlefOS work with an existing call provider?",
      "Yes, when a compatible provider is connected and the required permissions, plan and call data are available. That path is different from the CallOS selective participant model."
    ],
    [
      "Are messages or follow-ups sent automatically?",
      "No. AlefOS can prepare actions from call context, but protected execution remains subject to human review and validation."
    ]
  ],
  "related_pages": [
    "contacts",
    "missions",
    "mcp-cockpit",
    "call-provider",
    "whatsapp",
    "meeting-providers"
  ],
  "important_notes": [
    "AlefOS is voluntarily added to selected important calls or invited for a closing recap.",
    "AlefOS is not automatic listening on every phone call.",
    "AlefOS does not require number porting or replacing the user phone system.",
    "If AlefOS joins late, it does not automatically know what happened before it joined."
  ],
  "markdown": "# CallOS keeps customer promises visible after the call ends.\n\nLast updated: 2026-08-16\n\nCallOS is the AlefOS call module for turning supported and authorized calls into usable work context.\n\n## Keep your phone system\n\nKeep your number.\nKeep your phone system.\nAdd AlefOS only when the conversation becomes worth remembering.\n\nCalls already happen through the phone habits, operators and systems the user has today. CallOS does not ask the user to port a number, replace an operator or start with a heavy telephony deployment.\n\nWhen a customer call becomes important, the user can add AlefOS like another participant in the conversation. The goal is selective AI call notes: preserve the useful promise, objection, decision or next step without turning every phone call into an automatic recording workflow.\n\n## Why AlefOS does not listen to every call\n\nNot every call deserves to become company memory.\n\nSome conversations are private. Some are operationally irrelevant. Some calls only need a quick answer. AlefOS is designed so the user chooses the calls that should feed operational memory.\n\nThis keeps minutes focused on the moments that matter, lets users keep their normal phone habits and avoids treating every minute of every conversation as business context.\n\nAlefOS should not be described as permanent native listening, automatic recording of every call or a replacement for the phone system.\n\n## Two ways to use CallOS\n\n### Mode A: selected important call\nThe user adds AlefOS when a customer call is important enough to preserve. AlefOS can use the call content available after it joins the conversation.\n\nExamples:\n\n- A prospect gives a clear objection.\n- A customer asks for a callback.\n- A decision changes the next step.\n- A quote, document or meeting is promised.\n\n### Mode B: closing recap\nThe user can add AlefOS near the end of the call and make an explicit recap.\n\nFor example: \"One moment, I'm adding my assistant so we can recap the next steps.\"\n\nThe recap can include:\n\n- appointment fixed\n- quote to prepare\n- document expected\n- objection to address\n- person responsible\n- callback date\n- next decision\n\nIf AlefOS did not participate in the beginning of the call, it does not automatically know the previous content. In closing-recap mode, the memory depends on what the user explicitly summarizes while AlefOS is present.\n\n## A short recap can preserve the entire next step\n\nA call can last twenty or thirty minutes. AlefOS does not need to be present for every minute to help preserve the action that matters.\n\nThe user can add AlefOS during the final two or three minutes, recap the customer commitment and let the available recap become structured context.\n\n### Example: field service\nA customer calls about an intervention. The closing recap can preserve that the visit is tomorrow morning, access is through the building guard, a quote must be sent and a missing photo or document is still expected.\n\n### Example: real estate\nAfter a long buyer conversation, the recap can preserve the confirmed budget, a second visit on Thursday, financial documents expected and a callback planned for Friday.\n\n### Example: sales\nAfter a discussion about an offer, the recap can preserve the budget objection, the revised proposal to prepare, the manager validation needed and the follow-up planned after reception.\n\n## What AlefOS turns into memory\n\nWhen call data is available and authorized, AlefOS can help structure useful business context:\n\n- customer request\n- promise\n- objection\n- callback\n- appointment\n- missing document\n- decision\n- owner\n- deadline\n- next action\n- product or service discussed\n\nThe distinction matters:\n\n### Call transcript\nThe available content of the conversation, when it exists, is authorized and was received by AlefOS.\n\n### Call summary\nA readable synthesis of what was understood from the available call content or recap.\n\n### Operational context\nThe useful elements connected to the contact, customer relationship, group or mission.\n\n### Mission\nAn identifiable action to prepare, verify or accomplish.\n\nNot every call automatically creates a mission. AlefOS can help detect actions, prepare follow-ups and surface next steps when call data is available and the user has permission to use it.\n\n## After the call\n\nThe call ends.\nThe customer commitment remains visible.\n\nAfter a selected call or closing recap, the user can:\n\n- find what was promised\n- prepare a callback\n- create or review a mission\n- prepare a message\n- recover context before the next call\n- ask an AI assistant such as ChatGPT, Claude or Grok about authorized call context\n- let an authorized manager understand the situation\n- validate protected actions before execution\n\nAlefOS prepares. The user decides.\n\n## Set it up once. Add it in seconds.\n\nCallOS is the AlefOS call layer for selected calls.\n\nIn practical use, the user can keep the AlefOS call number available from the app when it is provided for the workspace and plan, save it as a favorite phone contact and use a quick phone method such as an iPhone Shortcut with confirmation.\n\nRecommended setup:\n\n- Find the AlefOS call number available for the account, workspace and plan.\n- Save it as AlefOS Assistant or AlefOS Call Assistant.\n- Create a shortcut or fast dialing method supported by the phone.\n- Keep a confirmation step before launching the call to AlefOS.\n- Add AlefOS to the conference only when the call should become memory.\n\nThe shortcut is not a business approval workflow inside AlefOS. It is a phone-level safety step to avoid accidental calls and unexpected minute usage.\n\n## Use minutes where they matter\n\nFree includes 15 minutes of analyzed calls per cycle.\n\nSolo includes 500 call minutes per month.\n\nTeam may include up to 5,000 call minutes according to Team deployment and MinutesOS configuration.\n\nThe minutes do not need to cover every minute of every conversation. A short closing recap can preserve the decisions and next actions that matter.\n\nUsers can choose the calls that deserve AI call notes, use AlefOS for an important section of a conversation or invite AlefOS at the end for a structured recap.\n\nActual usage depends on the customer workflow, call length, connected tools, plan and available call data.\n\n## CallOS and connected call providers\n\nCallOS and connected call providers are different paths.\n\n### CallOS selective participant model\nThe user voluntarily adds AlefOS to a call or closing recap. There is no mandatory number porting, no required replacement of the phone system and no automatic capture of every call.\n\n### Connected call provider\nSome customers may already use a compatible call provider. In that case, an external provider can transmit call data according to its own configuration, permissions, plan and available data.\n\nThe provider carries the call. AlefOS helps the useful call context become operational memory, missions and next actions.\n\n## How Calls differs from adjacent categories\n\n### AI call notes\nAlefOS can structure the important information from a selected call or closing recap so the useful context remains available after the call.\n\n### Full call recording\nAnother category of product may record complete conversations. AlefOS should not be presented as automatically recording every call.\n\n### AI voice agent\nAn AI voice agent speaks to the customer in place of the user. CallOS helps the user preserve context from a human conversation.\n\n### Phone system\nThe phone system transports the call. AlefOS helps the useful content become memory and next action.\n\n## Missions created from calls\n\nA call can help prepare missions when the available context contains an action.\n\nExamples:\n\n- Call a customer back on Friday.\n- Send a document.\n- Prepare a quote.\n- Confirm a meeting.\n- Notify a manager.\n- Follow up with a prospect.\n- Update a procedure.\n- Prepare a message after the call.\n\nAlefOS can help detect these actions, prepare them and present them to the user for validation.\n\n## Manager visibility\n\nFor teams, calls are an important management signal.\n\nA manager may need to understand which customers were called, which prospects are warm, which objections came back, which follow-ups are late, which calls created missions, which users need help and which conversations should be reviewed.\n\nAlefOS helps turn authorized call context into management visibility. The manager no longer depends only on what the user remembers after the call. They can ask AlefOS when permissions allow it.\n\n## Best practices\n\nTo use Calls effectively:\n\n- Save the AlefOS number as a favorite contact.\n- Use AlefOS only on important calls.\n- Create a shortcut or quick dialing method with a confirmation step.\n- Avoid launching calls without confirmation.\n- Review detected missions after the call.\n- Validate actions before execution.\n- Connect calls to the right contacts.\n- Monitor the minute balance.\n- Train teams to add AlefOS at the right moment.\n\nThe goal is not to add complexity. The goal is to avoid losing what was said in important calls.\n\n## Key takeaway\n\nCallOS is not a new phone system.\n\nThey are a selective source of operational memory.\n\nThe user keeps the existing number and phone system, adds AlefOS when the call is worth remembering and reviews protected actions before anything is executed.\n\nThe simple idea: important calls should not disappear when they end. They should preserve the promise, decision and next step.\n\n## Important notes\n\n- AlefOS is voluntarily added to selected important calls or invited for a closing recap.\n- AlefOS is not automatic listening on every phone call.\n- AlefOS does not require number porting or replacing the user phone system.\n- If AlefOS joins late, it does not automatically know what happened before it joined.\n\n## FAQ\n\n### What are AI call notes?\n\nAI call notes are structured notes from available call content or a user recap. In AlefOS, they can preserve promises, decisions, objections, action items and follow-ups as operational memory.\n\n### Do I need to change my phone number to use AlefOS?\n\nNo. CallOS is designed so the user can keep the existing number and phone system, then add AlefOS to selected calls when needed.\n\n### Does AlefOS listen to every phone call?\n\nNo. AlefOS is added voluntarily to selected important calls or invited for a closing recap. It is not permanent automatic listening on every call.\n\n### Can I add AlefOS only for the final recap?\n\nYes. The user can add AlefOS near the end of a call and recap the next steps while AlefOS is present.\n\n### Does AlefOS know what happened before it joined the call?\n\nNo. If AlefOS joins late, it does not automatically know earlier content. The memory then depends on the recap or available call data.\n\n### Can a call create action items or follow-ups?\n\nAlefOS can help detect and prepare action items when the available call context contains them. The user reviews protected actions before execution.\n\n### Does AlefOS record the full call automatically?\n\nNo. AlefOS should not be described as automatically recording every call. It can use selected call content or a closing recap when available and authorized.\n\n### How are Solo call minutes used?\n\nSolo includes 500 call minutes per month. Users can spend those minutes on selected important calls or short closing recaps instead of every minute of every conversation.\n\n### Can AlefOS work with an existing call provider?\n\nYes, when a compatible provider is connected and the required permissions, plan and call data are available. That path is different from the CallOS selective participant model.\n\n### Are messages or follow-ups sent automatically?\n\nNo. AlefOS can prepare actions from call context, but protected execution remains subject to human review and validation."
}