Understand your work OS
Your phone system. Connected to the rest of the work.
Keep the phone service your team already uses. Its open interfaces can provide a path to connect calls, customer context and follow-up to your company’s OS, with an adaptation scoped to your provider.
Choose a connection based on its actual data.
Telephony deployment is separate from the initial customer application. This reference helps verify the provider, events and content actually available before defining the connection. Naming a provider does not prove that its connector is active.
Everyday work
The team already knows its phone system.
Keep that familiarity. The connection project starts with the useful outcome: let the next person understand the customer’s call without asking the team to enter everything again.
Keep the phone service. Share the useful context.
01The team calls as usualKeep the familiar workflow.
A colleague speaks with Marc using the existing provider.
“Please send the updated quote before Friday.”
The provider continues to handle the call.
02The configured connectionBring the useful exchange into the OS.
The connection retrieves the authorized content made available for this call.
Marc requested an updated quote before Friday. The call is linked to the customer relationship.
This example requires access to content, not just a call-ended event.
03Another colleague takes overFind the request before replying.
“What are we expected to send Marc?”
An updated quote, requested before Friday. Check the latest version and who owns the follow-up.
The context supports the next step; it does not claim the quote was sent.
Fictional example, not a product screenshot. Sources and access require configuration; illustrated answers use the information shown.
Bring your provider. Scope the connection.
An open interface gives us something concrete to assess and adapt. The delivered connection specifies what is received, what can be queried and which actions are enabled.
Find your integration starting pointOn this page
Start with the phone service you already use
Your numbers, team habits and existing setup are the starting point. The project identifies what to retain and which connection can bring useful call activity into AlefOS. Replacing the whole phone system is not a prerequisite for connecting its context.
An open interface, not a closed list of brands
Aircall, Ringover, Dialpad or another service: these names are examples of providers a company may use, not a list of promised ready-made connectors. We scope the adaptation from the provider’s actual API, webhooks, MCP tools or supported exports. Aircall has an existing ingestion path; each company’s connection still needs activation and validation.
Receive an event, retrieve content, enable an action
A webhook can announce an incoming or completed call. An API may provide its recording, transcript or participants. MCP tools may expose specific queries or actions. These interfaces serve different purposes: a call-ended event alone does not contain the conversation, and read access does not grant permission to place a call.
Connect a PBX, SIP service or telephony account
A company with a PBX or a service such as Telnyx or Twilio needs a connection plan, not merely another logo in a catalogue. Define numbers, trunks, routing, media access and the parties responsible for operating the service. A dedicated PBX or mobile-line project can be scoped separately; the CallOS page explains the resulting calling experience.
What changes for the team
The colleague keeps using the phone service. Authorized call content can join the right customer relationship, help an incoming colleague prepare and keep a promise visible after the call. A manager consults the information within their scope instead of asking everyone to reconstruct the conversation.
Agree the scope, then test a real workflow
Specify incoming and outgoing coverage, the provider account, available events and media, access rules, recording conditions, costs and expected delays. Test a call through to its correct company, colleague and customer; test missing content and disconnection too. WhatsApp Business Calling has its own account and calling prerequisites, documented separately.
What can your provider expose?
Scroll the table to read every column. With a keyboard, use the left and right arrow keys.
| Interface | Useful role | Scope to establish |
|---|---|---|
| Webhook | Notify the OS of call activity. | Events, identifiers and delivery behaviour. |
| API | Retrieve available content or invoke supported operations. | Media access, permissions and read/write operations. |
| MCP | Expose specific tools to a compatible client. | Tool contracts, authentication and actual supported actions. |
| SIP / PBX | Connect the voice setup itself. | Routing, media, numbers and operating responsibilities. |
Operational reference
Modules, tools and access conditions
This reference describes MCP operations and their effects. The list exposed to your assistant depends on the deployed server, enabled modules and permissions. Reading, preparing and executing are distinct operations.
Call context
An indexed call does not imply a transcript is available. Read the actual provider content; resolve an unknown contact explicitly before using its relationship context.
Scroll the table to read every column. With a keyboard, use the left and right arrow keys.
| Tool | Function and effect |
|---|---|
calls. | List the calls visible in the current scope. |
calls. | Read an identified call’s available details. |
calls. | Read the available transcript for an explicit call_id. |
calls. | Prepare an explicit link between an unresolved call and an existing contact. |
calls. | Assign a call within the authorized company workflow. |
Scroll the table to read every column. With a keyboard, use the left and right arrow keys.
| Source | What must be verified |
|---|---|
| CallOS | Select the calling mode, numbers, media path and recording conditions. An embedded WebRTC interface is one option, not a requirement for every calling setup. Reference → |
| WhatsApp Business | Messaging and calling are separate. Confirm the messaging scope; business calling remains a path in preparation, with availability to validate. Reference → |
The scenarios on this page illustrate workflows, not real customer data or guaranteed outcomes. Connections and capabilities must be enabled and verified for your environment. Official business systems retain their responsibilities.
Continue exploring
A capability of your company’s environment. Your team can use this capability from a compatible assistant through its configured MCP access. The deployment defines the enabled tools and permissions. Understand your AI connection ↗