Call Provider

Call Providers let AlefOS connect the calling tools already used by a team to AlefOS operational memory.

The objective is not to replace the phone system.

The team can continue using its usual calling tool.

During a Team deployment, AlefOS can help connect a compatible provider so available call events, transcripts, summaries or data can feed the tenant memory.

The simple idea:

The provider handles calls.
AlefOS turns calls into usable memory.

Call Providers is designed for Team tenants.

It is not a Solo self-service feature.

Why?

An external call tool usually concerns a whole team:

• Several agents.
• Several numbers.
• Several managers.
• Many calls per day.
• Supervision needs.
• Reporting needs.
• Permissions.
• Shared memory.

The connection therefore needs to be configured cleanly with the right tenant, access, events and tests.

This is why Call Providers belongs to Team deployment.

AlefOS does not ask the team to immediately change its calling tool.

If the company already uses a compatible provider, AlefOS can study the connection.

Possible providers depend on compatibility and may include:

• Aircall.
• Ringover.
• Phone systems with webhooks.
• Phone systems with usable APIs.
• Calling platforms that can export call events or call data.

The principle stays the same:

External call tool -> call event or call data -> AlefOS -> operational memory.

A provider is considered compatible when it can send enough information for AlefOS to understand call activity.

Depending on the provider, this can happen through:

• Webhooks.
• API access.
• Event export.
• Completed call access.
• Transcript access.
• Summary access.
• User or agent access.
• Caller and callee numbers.

Not all providers expose the same data.

This is why the AlefOS team verifies compatibility during deployment.

Depending on the provider and available permissions, AlefOS can receive or use:

• Call identifier.
• Caller number.
• Called number.
• Call direction.
• Duration.
• Date and time.
• Agent or user.
• Call status.
• Recording when available.
• Transcript when available.
• Summary when available.
• Detected topics when available.
• Follow-up points when available.

AlefOS uses this data to enrich tenant memory.

If the provider does not supply certain data, AlefOS cannot invent it.

During Team deployment, AlefOS can support the provider connection.

This can include:

• Checking provider compatibility.
• Identifying available data.
• Configuring webhook or API access.
• Generating or using a secure token.
• Testing the first events.
• Verifying reception in AlefOS.
• Attaching data to the right tenant.
• Checking the first received calls.
• Validating data quality.
• Explaining to managers what actually flows into AlefOS.

The goal is not only to connect a webhook.

The goal is to make calls genuinely useful inside AlefOS.

When a provider works with webhooks, AlefOS can provide a receiving URL and a secure token.

The token helps verify that received events belong to the authorized tenant.

The token must be treated as sensitive information.

Best practices:

• Do not share it publicly.
• Do not send it through an unsecured channel.
• Limit access to authorized people.
• Regenerate it when necessary.
• Test the first events with the AlefOS team.

This configuration is usually handled during Team deployment.

Aircall is currently a call provider supported in AlefOS.

When Aircall is configured for a Team tenant, selected call events can flow into AlefOS.

Aircall remains the calling tool.

AlefOS receives the available information and connects it to operational memory.

Depending on available data, an Aircall call can help feed:

• Call history.
• Customer context.
• Contact memory.
• Transcripts when supplied.
• Summaries when supplied.
• Manager visibility.
• Sales analysis.

Aircall should not be presented as being replaced by AlefOS.

Aircall handles the call.
AlefOS structures what can be learned from the call.

Other providers can be connected when their data is usable.

The logic is open, but each provider may have its own format.

Some providers may require:

• A specific mapping.
• An adapter.
• Tests.
• Event verification.
• Field validation.
• Additional configuration.

AlefOS can receive events, but to turn those events into complete call memory, the data must be understandable and correctly structured.

Correct expectation:

If your provider is compatible, the AlefOS team can help connect it.

Incorrect expectation:

All providers are automatically supported without configuration.

Calls / CallOS and Call Providers are different.

Calls / CallOS is the AlefOS call layer.

It can allow users to add AlefOS to selected important calls, for example like an assistant in a conference call, to capture useful context.

Call Providers are external phone tools already used by the company.

The external provider handles the calls.

AlefOS receives available events or data to enrich tenant memory.

In short:

CallOS = AlefOS call layer.
Call Providers = external calling tools connected to AlefOS.

A call received from a compatible provider can become more than a line in a call history.

It can enrich:

• A contact.
• A company.
• A relationship.
• Customer history.
• A transcript.
• A summary.
• A sales objection.
• A manager signal.
• Follow-up information.
• A potential action.

The objective is to connect the call to the rest of the work.

An isolated call has limited value.

A call connected to a contact, a mission, a manager and team memory becomes much more useful.

Transcripts and summaries depend on the provider.

If the provider supplies a transcript or summary, AlefOS can use it to enrich memory.

If the provider does not supply them, AlefOS should not promise they exist.

Correct wording:

Transcripts and summaries are available only when the provider supplies them and AlefOS receives them correctly.

When available, they can help understand:

• What was said.
• What was requested.
• What was promised.
• Which objections come back.
• Which actions may follow.
• Which calls deserve manager attention.

For managers, calls are a major source of operational visibility.

Without structured memory, managers often need to ask:

• What happened with this customer?
• Why did this prospect not sign?
• Who needs a callback?
• Which objection came back?
• Which calls are important?

With Call Providers, AlefOS can help managers use calls as signals.

Managers can ask:

• Which calls happened.
• Which contacts are involved.
• Which prospects seem warm.
• Which objections come back.
• Which calls should be reviewed.
• Which agents need help.
• Which follow-ups seem necessary.

The manager no longer depends only on manual agent reports.

Connected calls can become a base for sales improvement.

With enough data, AlefOS can help understand:

• Which objections come back.
• Which scripts work.
• Which arguments are effective.
• Which prospects respond best.
• Where conversations get blocked.
• Which agents handle certain steps better.
• Which niches or segments react best.

The goal is not only to store calls.

The goal is to learn from the field.

Calls can contain actions to track.

Examples:

• Call a customer back.
• Send a document.
• Confirm an appointment.
• Notify a manager.
• Prepare a reply.
• Note an objection.
• Follow up with a prospect.

Depending on the provider, received data and AlefOS configuration, some calls can help prepare actions or missions.

But AlefOS should not promise that every external call automatically creates a mission.

Correct wording:

Calls can feed memory and help prepare actions. Mission creation depends on the available flow, received data and AlefOS configuration.

Call Providers is not:

• A replacement for Aircall or another phone provider.
• A promise of automatic compatibility with every calling tool.
• A system that perfectly understands every webhook without configuration.
• A guarantee of transcription if the provider does not supply it.
• A promise to automatically create missions for every call.
• A Solo self-service module.
• A tool to make all calls from AlefOS.

Call Providers connects compatible calling tools to AlefOS memory in a Team context.

Call Providers is especially useful in Team because it creates collective memory around phone activity.

A team may have:

• Several agents.
• Several managers.
• Several numbers.
• Many calls.
• Follow-ups.
• Objections.
• Important conversations.
• Calls to review.
• Performance patterns to understand.

In this context, the call becomes a company signal.

AlefOS helps transform that signal into memory.

Call Providers lets AlefOS receive call activity from compatible phone providers.

The company keeps its calling tool.

AlefOS supports the connection during Team deployment when the provider can supply the required data.

Aircall is currently a supported provider.

Other providers can be studied depending on their ability to send usable events or data.

The simple idea:

The provider carries the calls.
AlefOS makes sure those calls enrich company memory.