{
  "title": "Call Provider",
  "internal_name": null,
  "slug": "call-provider",
  "url": "https://alefos.ai/documentation/call-provider",
  "json_url": "https://alefos.ai/documentation/call-provider.json",
  "summary": "Keep your phone system and make every useful call searchable as customer context, follow-up and manager signal.",
  "description": "Keep Aircall or another compatible provider while available, authorized call signals enrich contacts, next actions and manager visibility in AlefOS Team.",
  "category": "Integrations",
  "last_updated": "2026-07-03",
  "keywords": [
    "Call Providers",
    "Aircall",
    "calls",
    "webhooks",
    "call sync",
    "sales coaching"
  ],
  "sections": [
    {
      "heading": "What Call Providers means",
      "content": "Call Providers let AlefOS connect the calling tools already used by a team to AlefOS operational memory.\n\nThe objective is not to replace the phone system.\n\nThe team can continue using its usual calling tool.\n\nDuring a Team deployment, AlefOS can help connect a compatible provider so available call events, transcripts, summaries or data can feed the tenant memory.\n\nThe simple idea:\n\nThe provider handles calls.\nAlefOS turns calls into usable memory."
    },
    {
      "heading": "A guided Team integration",
      "content": "Call Providers is designed for Team tenants.\n\nIt is not a Solo self-service feature.\n\nWhy?\n\nAn external call tool usually concerns a whole team:\n\n- Several agents.\n- Several numbers.\n- Several managers.\n- Many calls per day.\n- Supervision needs.\n- Reporting needs.\n- Permissions.\n- Shared memory.\n\nThe connection therefore needs to be configured cleanly with the right tenant, access, events and tests.\n\nThis is why Call Providers belongs to Team deployment."
    },
    {
      "heading": "Keep your existing phone tool",
      "content": "AlefOS does not ask the team to immediately change its calling tool.\n\nIf the company already uses a compatible provider, AlefOS can study the connection.\n\nPossible providers depend on compatibility and may include:\n\n- Aircall.\n- Ringover.\n- Phone systems with webhooks.\n- Phone systems with usable APIs.\n- Calling platforms that can export call events or call data.\n\nThe principle stays the same:\n\nExternal call tool -> call event or call data -> AlefOS -> operational memory."
    },
    {
      "heading": "Compatible provider",
      "content": "A provider is considered compatible when it can send enough information for AlefOS to understand call activity.\n\nDepending on the provider, this can happen through:\n\n- Webhooks.\n- API access.\n- Event export.\n- Completed call access.\n- Transcript access.\n- Summary access.\n- User or agent access.\n- Caller and callee numbers.\n\nNot all providers expose the same data.\n\nThis is why the AlefOS team verifies compatibility during deployment."
    },
    {
      "heading": "What AlefOS can receive",
      "content": "Depending on the provider and available permissions, AlefOS can receive or use:\n\n- Call identifier.\n- Caller number.\n- Called number.\n- Call direction.\n- Duration.\n- Date and time.\n- Agent or user.\n- Call status.\n- Recording when available.\n- Transcript when available.\n- Summary when available.\n- Detected topics when available.\n- Follow-up points when available.\n\nAlefOS uses this data to enrich tenant memory.\n\nIf the provider does not supply certain data, AlefOS cannot invent it."
    },
    {
      "heading": "Connection support",
      "content": "During Team deployment, AlefOS can support the provider connection.\n\nThis can include:\n\n- Checking provider compatibility.\n- Identifying available data.\n- Configuring webhook or API access.\n- Generating or using a secure token.\n- Testing the first events.\n- Verifying reception in AlefOS.\n- Attaching data to the right tenant.\n- Checking the first received calls.\n- Validating data quality.\n- Explaining to managers what actually flows into AlefOS.\n\nThe goal is not only to connect a webhook.\n\nThe goal is to make calls genuinely useful inside AlefOS."
    },
    {
      "heading": "Webhooks and security",
      "content": "When a provider works with webhooks, AlefOS can provide a receiving URL and a secure token.\n\nThe token helps verify that received events belong to the authorized tenant.\n\nThe token must be treated as sensitive information.\n\nBest practices:\n\n- Do not share it publicly.\n- Do not send it through an unsecured channel.\n- Limit access to authorized people.\n- Regenerate it when necessary.\n- Test the first events with the AlefOS team.\n\nThis configuration is usually handled during Team deployment."
    },
    {
      "heading": "Aircall",
      "content": "Aircall is currently a call provider supported in AlefOS.\n\nWhen Aircall is configured for a Team tenant, selected call events can flow into AlefOS.\n\nAircall remains the calling tool.\n\nAlefOS receives the available information and connects it to operational memory.\n\nDepending on available data, an Aircall call can help feed:\n\n- Call history.\n- Customer context.\n- Contact memory.\n- Transcripts when supplied.\n- Summaries when supplied.\n- Manager visibility.\n- Sales analysis.\n\nAircall should not be presented as being replaced by AlefOS.\n\nAircall handles the call.\nAlefOS structures what can be learned from the call."
    },
    {
      "heading": "Other providers",
      "content": "Other providers can be connected when their data is usable.\n\nThe logic is open, but each provider may have its own format.\n\nSome providers may require:\n\n- A specific mapping.\n- An adapter.\n- Tests.\n- Event verification.\n- Field validation.\n- Additional configuration.\n\nAlefOS can receive events, but to turn those events into complete call memory, the data must be understandable and correctly structured.\n\nCorrect expectation:\n\nIf your provider is compatible, the AlefOS team can help connect it.\n\nIncorrect expectation:\n\nAll providers are automatically supported without configuration."
    },
    {
      "heading": "Difference between CallOS and Call Providers",
      "content": "Calls / CallOS and Call Providers are different.\n\nCalls / CallOS is the AlefOS call layer.\n\nIt can allow users to add AlefOS to selected important calls, for example like an assistant in a conference call, to capture useful context.\n\nCall Providers are external phone tools already used by the company.\n\nThe external provider handles the calls.\n\nAlefOS receives available events or data to enrich tenant memory.\n\nIn short:\n\nCallOS = AlefOS call layer.\nCall Providers = external calling tools connected to AlefOS."
    },
    {
      "heading": "What calls can become",
      "content": "A call received from a compatible provider can become more than a line in a call history.\n\nIt can enrich:\n\n- A contact.\n- A company.\n- A relationship.\n- Customer history.\n- A transcript.\n- A summary.\n- A sales objection.\n- A manager signal.\n- Follow-up information.\n- A potential action.\n\nThe objective is to connect the call to the rest of the work.\n\nAn isolated call has limited value.\n\nA call connected to a contact, a mission, a manager and team memory becomes much more useful."
    },
    {
      "heading": "Transcripts and summaries",
      "content": "Transcripts and summaries depend on the provider.\n\nIf the provider supplies a transcript or summary, AlefOS can use it to enrich memory.\n\nIf the provider does not supply them, AlefOS should not promise they exist.\n\nCorrect wording:\n\nTranscripts and summaries are available only when the provider supplies them and AlefOS receives them correctly.\n\nWhen available, they can help understand:\n\n- What was said.\n- What was requested.\n- What was promised.\n- Which objections come back.\n- Which actions may follow.\n- Which calls deserve manager attention."
    },
    {
      "heading": "Manager memory",
      "content": "For managers, calls are a major source of operational visibility.\n\nWithout structured memory, managers often need to ask:\n\n- What happened with this customer?\n- Why did this prospect not sign?\n- Who needs a callback?\n- Which objection came back?\n- Which calls are important?\n\nWith Call Providers, AlefOS can help managers use calls as signals.\n\nManagers can ask:\n\n- Which calls happened.\n- Which contacts are involved.\n- Which prospects seem warm.\n- Which objections come back.\n- Which calls should be reviewed.\n- Which agents need help.\n- Which follow-ups seem necessary.\n\nThe manager no longer depends only on manual agent reports."
    },
    {
      "heading": "Sales analysis",
      "content": "Connected calls can become a base for sales improvement.\n\nWith enough data, AlefOS can help understand:\n\n- Which objections come back.\n- Which scripts work.\n- Which arguments are effective.\n- Which prospects respond best.\n- Where conversations get blocked.\n- Which agents handle certain steps better.\n- Which niches or segments react best.\n\nThe goal is not only to store calls.\n\nThe goal is to learn from the field."
    },
    {
      "heading": "Missions and actions",
      "content": "Calls can contain actions to track.\n\nExamples:\n\n- Call a customer back.\n- Send a document.\n- Confirm an appointment.\n- Notify a manager.\n- Prepare a reply.\n- Note an objection.\n- Follow up with a prospect.\n\nDepending on the provider, received data and AlefOS configuration, some calls can help prepare actions or missions.\n\nBut AlefOS should not promise that every external call automatically creates a mission.\n\nCorrect wording:\n\nCalls can feed memory and help prepare actions. Mission creation depends on the available flow, received data and AlefOS configuration."
    },
    {
      "heading": "What Call Providers is not",
      "content": "Call Providers is not:\n\n- A replacement for Aircall or another phone provider.\n- A promise of automatic compatibility with every calling tool.\n- A system that perfectly understands every webhook without configuration.\n- A guarantee of transcription if the provider does not supply it.\n- A promise to automatically create missions for every call.\n- A Solo self-service module.\n- A tool to make all calls from AlefOS.\n\nCall Providers connects compatible calling tools to AlefOS memory in a Team context."
    },
    {
      "heading": "Why this is a Team module",
      "content": "Call Providers is especially useful in Team because it creates collective memory around phone activity.\n\nA team may have:\n\n- Several agents.\n- Several managers.\n- Several numbers.\n- Many calls.\n- Follow-ups.\n- Objections.\n- Important conversations.\n- Calls to review.\n- Performance patterns to understand.\n\nIn this context, the call becomes a company signal.\n\nAlefOS helps transform that signal into memory."
    },
    {
      "heading": "Key takeaway",
      "content": "Call Providers lets AlefOS receive call activity from compatible phone providers.\n\nThe company keeps its calling tool.\n\nAlefOS supports the connection during Team deployment when the provider can supply the required data.\n\nAircall is currently a supported provider.\n\nOther providers can be studied depending on their ability to send usable events or data.\n\nThe simple idea:\n\nThe provider carries the calls.\nAlefOS makes sure those calls enrich company memory."
    }
  ],
  "typical_questions": [],
  "related_pages": [
    "calls",
    "contacts",
    "missions",
    "team",
    "deployment"
  ],
  "important_notes": [
    "Call Providers is a Team deployment integration, not a Solo self-service feature.",
    "AlefOS does not replace the external phone provider.",
    "Aircall is currently a supported call provider.",
    "Transcripts and summaries depend on what the provider supplies."
  ],
  "markdown": "# Call Provider\n\nLast updated: 2026-07-03\n\nKeep Aircall or another compatible provider while available, authorized call signals enrich contacts, next actions and manager visibility in AlefOS Team.\n\n## What Call Providers means\n\nCall Providers let AlefOS connect the calling tools already used by a team to AlefOS operational memory.\n\nThe objective is not to replace the phone system.\n\nThe team can continue using its usual calling tool.\n\nDuring a Team deployment, AlefOS can help connect a compatible provider so available call events, transcripts, summaries or data can feed the tenant memory.\n\nThe simple idea:\n\nThe provider handles calls.\nAlefOS turns calls into usable memory.\n\n## A guided Team integration\n\nCall Providers is designed for Team tenants.\n\nIt is not a Solo self-service feature.\n\nWhy?\n\nAn external call tool usually concerns a whole team:\n\n- Several agents.\n- Several numbers.\n- Several managers.\n- Many calls per day.\n- Supervision needs.\n- Reporting needs.\n- Permissions.\n- Shared memory.\n\nThe connection therefore needs to be configured cleanly with the right tenant, access, events and tests.\n\nThis is why Call Providers belongs to Team deployment.\n\n## Keep your existing phone tool\n\nAlefOS does not ask the team to immediately change its calling tool.\n\nIf the company already uses a compatible provider, AlefOS can study the connection.\n\nPossible providers depend on compatibility and may include:\n\n- Aircall.\n- Ringover.\n- Phone systems with webhooks.\n- Phone systems with usable APIs.\n- Calling platforms that can export call events or call data.\n\nThe principle stays the same:\n\nExternal call tool -> call event or call data -> AlefOS -> operational memory.\n\n## Compatible provider\n\nA provider is considered compatible when it can send enough information for AlefOS to understand call activity.\n\nDepending on the provider, this can happen through:\n\n- Webhooks.\n- API access.\n- Event export.\n- Completed call access.\n- Transcript access.\n- Summary access.\n- User or agent access.\n- Caller and callee numbers.\n\nNot all providers expose the same data.\n\nThis is why the AlefOS team verifies compatibility during deployment.\n\n## What AlefOS can receive\n\nDepending on the provider and available permissions, AlefOS can receive or use:\n\n- Call identifier.\n- Caller number.\n- Called number.\n- Call direction.\n- Duration.\n- Date and time.\n- Agent or user.\n- Call status.\n- Recording when available.\n- Transcript when available.\n- Summary when available.\n- Detected topics when available.\n- Follow-up points when available.\n\nAlefOS uses this data to enrich tenant memory.\n\nIf the provider does not supply certain data, AlefOS cannot invent it.\n\n## Connection support\n\nDuring Team deployment, AlefOS can support the provider connection.\n\nThis can include:\n\n- Checking provider compatibility.\n- Identifying available data.\n- Configuring webhook or API access.\n- Generating or using a secure token.\n- Testing the first events.\n- Verifying reception in AlefOS.\n- Attaching data to the right tenant.\n- Checking the first received calls.\n- Validating data quality.\n- Explaining to managers what actually flows into AlefOS.\n\nThe goal is not only to connect a webhook.\n\nThe goal is to make calls genuinely useful inside AlefOS.\n\n## Webhooks and security\n\nWhen a provider works with webhooks, AlefOS can provide a receiving URL and a secure token.\n\nThe token helps verify that received events belong to the authorized tenant.\n\nThe token must be treated as sensitive information.\n\nBest practices:\n\n- Do not share it publicly.\n- Do not send it through an unsecured channel.\n- Limit access to authorized people.\n- Regenerate it when necessary.\n- Test the first events with the AlefOS team.\n\nThis configuration is usually handled during Team deployment.\n\n## Aircall\n\nAircall is currently a call provider supported in AlefOS.\n\nWhen Aircall is configured for a Team tenant, selected call events can flow into AlefOS.\n\nAircall remains the calling tool.\n\nAlefOS receives the available information and connects it to operational memory.\n\nDepending on available data, an Aircall call can help feed:\n\n- Call history.\n- Customer context.\n- Contact memory.\n- Transcripts when supplied.\n- Summaries when supplied.\n- Manager visibility.\n- Sales analysis.\n\nAircall should not be presented as being replaced by AlefOS.\n\nAircall handles the call.\nAlefOS structures what can be learned from the call.\n\n## Other providers\n\nOther providers can be connected when their data is usable.\n\nThe logic is open, but each provider may have its own format.\n\nSome providers may require:\n\n- A specific mapping.\n- An adapter.\n- Tests.\n- Event verification.\n- Field validation.\n- Additional configuration.\n\nAlefOS can receive events, but to turn those events into complete call memory, the data must be understandable and correctly structured.\n\nCorrect expectation:\n\nIf your provider is compatible, the AlefOS team can help connect it.\n\nIncorrect expectation:\n\nAll providers are automatically supported without configuration.\n\n## Difference between CallOS and Call Providers\n\nCalls / CallOS and Call Providers are different.\n\nCalls / CallOS is the AlefOS call layer.\n\nIt can allow users to add AlefOS to selected important calls, for example like an assistant in a conference call, to capture useful context.\n\nCall Providers are external phone tools already used by the company.\n\nThe external provider handles the calls.\n\nAlefOS receives available events or data to enrich tenant memory.\n\nIn short:\n\nCallOS = AlefOS call layer.\nCall Providers = external calling tools connected to AlefOS.\n\n## What calls can become\n\nA call received from a compatible provider can become more than a line in a call history.\n\nIt can enrich:\n\n- A contact.\n- A company.\n- A relationship.\n- Customer history.\n- A transcript.\n- A summary.\n- A sales objection.\n- A manager signal.\n- Follow-up information.\n- A potential action.\n\nThe objective is to connect the call to the rest of the work.\n\nAn isolated call has limited value.\n\nA call connected to a contact, a mission, a manager and team memory becomes much more useful.\n\n## Transcripts and summaries\n\nTranscripts and summaries depend on the provider.\n\nIf the provider supplies a transcript or summary, AlefOS can use it to enrich memory.\n\nIf the provider does not supply them, AlefOS should not promise they exist.\n\nCorrect wording:\n\nTranscripts and summaries are available only when the provider supplies them and AlefOS receives them correctly.\n\nWhen available, they can help understand:\n\n- What was said.\n- What was requested.\n- What was promised.\n- Which objections come back.\n- Which actions may follow.\n- Which calls deserve manager attention.\n\n## Manager memory\n\nFor managers, calls are a major source of operational visibility.\n\nWithout structured memory, managers often need to ask:\n\n- What happened with this customer?\n- Why did this prospect not sign?\n- Who needs a callback?\n- Which objection came back?\n- Which calls are important?\n\nWith Call Providers, AlefOS can help managers use calls as signals.\n\nManagers can ask:\n\n- Which calls happened.\n- Which contacts are involved.\n- Which prospects seem warm.\n- Which objections come back.\n- Which calls should be reviewed.\n- Which agents need help.\n- Which follow-ups seem necessary.\n\nThe manager no longer depends only on manual agent reports.\n\n## Sales analysis\n\nConnected calls can become a base for sales improvement.\n\nWith enough data, AlefOS can help understand:\n\n- Which objections come back.\n- Which scripts work.\n- Which arguments are effective.\n- Which prospects respond best.\n- Where conversations get blocked.\n- Which agents handle certain steps better.\n- Which niches or segments react best.\n\nThe goal is not only to store calls.\n\nThe goal is to learn from the field.\n\n## Missions and actions\n\nCalls can contain actions to track.\n\nExamples:\n\n- Call a customer back.\n- Send a document.\n- Confirm an appointment.\n- Notify a manager.\n- Prepare a reply.\n- Note an objection.\n- Follow up with a prospect.\n\nDepending on the provider, received data and AlefOS configuration, some calls can help prepare actions or missions.\n\nBut AlefOS should not promise that every external call automatically creates a mission.\n\nCorrect wording:\n\nCalls can feed memory and help prepare actions. Mission creation depends on the available flow, received data and AlefOS configuration.\n\n## What Call Providers is not\n\nCall Providers is not:\n\n- A replacement for Aircall or another phone provider.\n- A promise of automatic compatibility with every calling tool.\n- A system that perfectly understands every webhook without configuration.\n- A guarantee of transcription if the provider does not supply it.\n- A promise to automatically create missions for every call.\n- A Solo self-service module.\n- A tool to make all calls from AlefOS.\n\nCall Providers connects compatible calling tools to AlefOS memory in a Team context.\n\n## Why this is a Team module\n\nCall Providers is especially useful in Team because it creates collective memory around phone activity.\n\nA team may have:\n\n- Several agents.\n- Several managers.\n- Several numbers.\n- Many calls.\n- Follow-ups.\n- Objections.\n- Important conversations.\n- Calls to review.\n- Performance patterns to understand.\n\nIn this context, the call becomes a company signal.\n\nAlefOS helps transform that signal into memory.\n\n## Key takeaway\n\nCall Providers lets AlefOS receive call activity from compatible phone providers.\n\nThe company keeps its calling tool.\n\nAlefOS supports the connection during Team deployment when the provider can supply the required data.\n\nAircall is currently a supported provider.\n\nOther providers can be studied depending on their ability to send usable events or data.\n\nThe simple idea:\n\nThe provider carries the calls.\nAlefOS makes sure those calls enrich company memory.\n\n## Important notes\n\n- Call Providers is a Team deployment integration, not a Solo self-service feature.\n- AlefOS does not replace the external phone provider.\n- Aircall is currently a supported call provider.\n- Transcripts and summaries depend on what the provider supplies."
}