{
  "title": "Calls",
  "internal_name": "CallOS",
  "slug": "calls",
  "url": "https://alefos.ai/documentation/calls",
  "json_url": "https://alefos.ai/documentation/calls.json",
  "summary": "The call ends, but the customer promise and next action stay connected.",
  "description": "Add AlefOS to selected important calls so customer needs, objections, promises and follow-ups can become usable context instead of disappearing when the call ends.",
  "category": "Core",
  "last_updated": "2026-07-03",
  "keywords": [
    "calls",
    "CallOS",
    "PBX",
    "call context",
    "transcripts",
    "callbacks"
  ],
  "sections": [
    {
      "heading": "Why calls matter",
      "content": "Phone calls often contain the most important business information.\n\nA customer explains a need. A prospect gives an objection. A meeting is discussed. A document is requested. A promise is made. A follow-up is planned. A decision is made verbally.\n\nWithout AlefOS, this information often stays only in the memory of the person who took the call.\n\nWith AlefOS, a call can become customer context, a summary, a mission, a reminder, a follow-up, a manager signal and a trace that can be used later."
    },
    {
      "heading": "CallOS / AlefOS PBX",
      "content": "CallOS is the AlefOS call layer.\n\nIt can work as a phone number or participant that the user adds to a conference call.\n\nThe idea is simple: during an important call, the user can add AlefOS to the call to capture useful context.\n\nAlefOS then acts like an operational note-taking assistant inside the call.\n\nIt is not designed to automatically listen to every call in the company. It is added voluntarily by the user when the call is important enough to become memory."
    },
    {
      "heading": "Adding AlefOS during a call",
      "content": "A user can add the AlefOS number to an active call, just like adding another participant to a conference.\n\nTypical flow:\n\n- The user is already on a call with a customer or business contact.\n- The call becomes important.\n- The user adds AlefOS to the conference.\n- AlefOS joins the call.\n- The call can then feed operational memory.\n\nThis lets the user use AlefOS like an intelligent notebook during important conversations."
    },
    {
      "heading": "AlefOS numbers in the app",
      "content": "AlefOS call numbers should be visible inside the web app or desktop app.\n\nThe user should be able to quickly find the AlefOS number to add to a call, the numbers connected to their account, the numbers available according to their plan and the information needed to add AlefOS into a conference call.\n\nThe user should not need to search for the AlefOS number during an important call."
    },
    {
      "heading": "Save AlefOS as a favorite contact",
      "content": "For faster use, the user should save the AlefOS number as a favorite contact on their phone.\n\nRecommended contact name:\n\n- AlefOS Assistant\n- AlefOS Call Assistant\n\nThis makes it easier to add AlefOS quickly during a live call. It is especially useful for users who handle many business calls from their mobile phone."
    },
    {
      "heading": "Recommended iPhone Shortcut",
      "content": "On iPhone, the user can create a shortcut called Add AlefOS.\n\nThis shortcut can quickly call the AlefOS number during an active phone call, so the user can add AlefOS to the conference as an assistant.\n\nImportant: this is not a business validation flow inside AlefOS. This is a simple iPhone safety confirmation before the phone call is launched.\n\nRecommended shortcut flow:\n\n- Shortcut name: Add AlefOS.\n- Show a menu or confirmation: Add AlefOS?\n- Option: Yes.\n- If the user confirms, iPhone calls the saved AlefOS contact.\n\nThis prevents accidental calls and protects the user minute balance. The shortcut should not call AlefOS instantly without confirmation."
    },
    {
      "heading": "What AlefOS can extract from a call",
      "content": "When call data is available, AlefOS can help structure useful business context.\n\nA call can enrich the contact, relationship memory, missions, callbacks, promises, missing documents, objections, appointments, decisions and detected needs.\n\nThe call no longer disappears when it ends. It becomes part of operational memory."
    },
    {
      "heading": "Missions created from calls",
      "content": "A call can generate missions.\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 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 calls into management visibility. The manager no longer depends only on what the agent remembers after the call. They can ask AlefOS."
    },
    {
      "heading": "CallOS and external integrations",
      "content": "CallOS is the AlefOS call layer.\n\nCalls can also come from external integrations, depending on connected tools, permissions and plans.\n\nFor example, an external call platform may feed AlefOS with business call activity when connected.\n\nThe logic stays the same: useful calls should enrich operational memory. Whether the call comes from CallOS, a PBX, a conference call or an external integration, it should be able to enrich contacts, create missions and help the team follow real work."
    },
    {
      "heading": "Difference from a classic phone system",
      "content": "A classic phone system lets users make or receive calls.\n\nAlefOS goes further.\n\nThe question is not only: did the call happen?\n\nThe real questions are:\n\n- What was said?\n- What was promised?\n- Who needs to do what?\n- What should happen next?\n\nCalls in AlefOS turn phone conversations into usable context."
    },
    {
      "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 an iPhone shortcut 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": "Calls in AlefOS are not just telephony.\n\nThey are a source of operational memory.\n\nDuring an important call, the user can add AlefOS as an assistant in the conversation.\n\nAlefOS can then help turn the conversation into context, missions, reminders, decisions and actions to validate.\n\nThe simple idea: a call should not disappear when it ends. It should enrich the company memory."
    }
  ],
  "typical_questions": [],
  "related_pages": [
    "contacts",
    "missions",
    "call-provider"
  ],
  "important_notes": [
    "AlefOS is voluntarily added to selected important calls.",
    "AlefOS is not automatic listening on every call."
  ],
  "markdown": "# Calls\n\nLast updated: 2026-07-03\n\nAdd AlefOS to selected important calls so customer needs, objections, promises and follow-ups can become usable context instead of disappearing when the call ends.\n\n## Why calls matter\n\nPhone calls often contain the most important business information.\n\nA customer explains a need. A prospect gives an objection. A meeting is discussed. A document is requested. A promise is made. A follow-up is planned. A decision is made verbally.\n\nWithout AlefOS, this information often stays only in the memory of the person who took the call.\n\nWith AlefOS, a call can become customer context, a summary, a mission, a reminder, a follow-up, a manager signal and a trace that can be used later.\n\n## CallOS / AlefOS PBX\n\nCallOS is the AlefOS call layer.\n\nIt can work as a phone number or participant that the user adds to a conference call.\n\nThe idea is simple: during an important call, the user can add AlefOS to the call to capture useful context.\n\nAlefOS then acts like an operational note-taking assistant inside the call.\n\nIt is not designed to automatically listen to every call in the company. It is added voluntarily by the user when the call is important enough to become memory.\n\n## Adding AlefOS during a call\n\nA user can add the AlefOS number to an active call, just like adding another participant to a conference.\n\nTypical flow:\n\n- The user is already on a call with a customer or business contact.\n- The call becomes important.\n- The user adds AlefOS to the conference.\n- AlefOS joins the call.\n- The call can then feed operational memory.\n\nThis lets the user use AlefOS like an intelligent notebook during important conversations.\n\n## AlefOS numbers in the app\n\nAlefOS call numbers should be visible inside the web app or desktop app.\n\nThe user should be able to quickly find the AlefOS number to add to a call, the numbers connected to their account, the numbers available according to their plan and the information needed to add AlefOS into a conference call.\n\nThe user should not need to search for the AlefOS number during an important call.\n\n## Save AlefOS as a favorite contact\n\nFor faster use, the user should save the AlefOS number as a favorite contact on their phone.\n\nRecommended contact name:\n\n- AlefOS Assistant\n- AlefOS Call Assistant\n\nThis makes it easier to add AlefOS quickly during a live call. It is especially useful for users who handle many business calls from their mobile phone.\n\n## Recommended iPhone Shortcut\n\nOn iPhone, the user can create a shortcut called Add AlefOS.\n\nThis shortcut can quickly call the AlefOS number during an active phone call, so the user can add AlefOS to the conference as an assistant.\n\nImportant: this is not a business validation flow inside AlefOS. This is a simple iPhone safety confirmation before the phone call is launched.\n\nRecommended shortcut flow:\n\n- Shortcut name: Add AlefOS.\n- Show a menu or confirmation: Add AlefOS?\n- Option: Yes.\n- If the user confirms, iPhone calls the saved AlefOS contact.\n\nThis prevents accidental calls and protects the user minute balance. The shortcut should not call AlefOS instantly without confirmation.\n\n## What AlefOS can extract from a call\n\nWhen call data is available, AlefOS can help structure useful business context.\n\nA call can enrich the contact, relationship memory, missions, callbacks, promises, missing documents, objections, appointments, decisions and detected needs.\n\nThe call no longer disappears when it ends. It becomes part of operational memory.\n\n## Missions created from calls\n\nA call can generate missions.\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 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 calls into management visibility. The manager no longer depends only on what the agent remembers after the call. They can ask AlefOS.\n\n## CallOS and external integrations\n\nCallOS is the AlefOS call layer.\n\nCalls can also come from external integrations, depending on connected tools, permissions and plans.\n\nFor example, an external call platform may feed AlefOS with business call activity when connected.\n\nThe logic stays the same: useful calls should enrich operational memory. Whether the call comes from CallOS, a PBX, a conference call or an external integration, it should be able to enrich contacts, create missions and help the team follow real work.\n\n## Difference from a classic phone system\n\nA classic phone system lets users make or receive calls.\n\nAlefOS goes further.\n\nThe question is not only: did the call happen?\n\nThe real questions are:\n\n- What was said?\n- What was promised?\n- Who needs to do what?\n- What should happen next?\n\nCalls in AlefOS turn phone conversations into usable context.\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 an iPhone shortcut 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\nCalls in AlefOS are not just telephony.\n\nThey are a source of operational memory.\n\nDuring an important call, the user can add AlefOS as an assistant in the conversation.\n\nAlefOS can then help turn the conversation into context, missions, reminders, decisions and actions to validate.\n\nThe simple idea: a call should not disappear when it ends. It should enrich the company memory.\n\n## Important notes\n\n- AlefOS is voluntarily added to selected important calls.\n- AlefOS is not automatic listening on every call."
}