Understand your work OS
CallOS: your calls belong in the flow of work.
From your usual phone, an integrated calling interface or a connected phone system: choose the calling setup that fits your team. Keep the useful conversation with the customer and the next step.
The provider handles the call; context supports follow-up.
This function concerns calls and content actually received through company connections. It extends the internal scope and is not automatically included in the catalogue-and-enquiry application. Missing transcripts cannot be reconstructed as facts.
Start with the work
Where do you need help?
Everyday work
Keep talking. Keep what matters.
Your team works on the phone: at a desk, on site or between appointments. Start with how people already call, then configure how the useful exchange joins your OS.
Two minutes to preserve the next step.
01The call is underwayAn agreement takes shape.
Marc and a technician agree on a visit.
“Thursday after 2 pm works. Enter through the courtyard.”
The conversation has started before AlefOS joins.
02Add the configured numberRecap the agreement together.
On a supported conference call, the technician brings AlefOS in.
“We have agreed on Thursday after 2 pm, through the courtyard. I will confirm the exact time.”
Only the part received after joining supports this recap.
03The next colleague takes overFind the agreement before calling.
“What should I confirm with Marc?”
Thursday after 2 pm. Courtyard access. Exact time still to confirm with the technician.
The agreement and the remaining question stay distinct.
Fictional example, not a product screenshot. Sources and access require configuration; illustrated answers use the information shown.
One calling capability. Several ways to use it.
Use an integrated interface, connect the existing phone system or scope selective participation. The right setup follows the team’s actual work; your company keeps the authorized context.
Connect your existing phone systemOn this page
- Call from your work interface
- Use your phone without an embedded dialer
- Already talking? Bring AlefOS into the conversation
- Keep or build the company’s phone setup
- Equip a mobile team
- Continue a WhatsApp exchange by phone
- Keep the agreement with the relationship
- What the selected setup captures
- Tools and prerequisites
Call from your work interface
An integrated WebRTC interface is one deployment option: the colleague starts a call from the company workspace, with the customer context close at hand. The delivered interface, supported devices and phone service are defined together.
Use your phone without an embedded dialer
A two-party calling setup connects the colleague’s phone and the customer’s phone. You speak using your usual handset; an embedded WebRTC interface is not required for this approach. The deployment specifies the callback behaviour, displayed number and provider charges.
Already talking? Bring AlefOS into the conversation
For a team member or subcontractor already on a call, selective participation can be the useful starting point. Where the phone and carrier support conference calling, add the configured AlefOS access number. A short recap can preserve the agreement without reconstructing it later in a separate note.
Capture starts when AlefOS joins. The earlier conversation is not recovered retroactively. The access number, conference capability and recording conditions must be established before use.
Keep or build the company’s phone setup
An existing PBX, a SIP connection or a telephony account such as Telnyx or Twilio can form part of the setup to assess. A dedicated PBX can also be scoped with the deployment. CallOS describes the employee experience; the phone-provider reference explains the connection and operational responsibilities.
Equip a mobile team
An eSIM rollout can be studied for teams that need company-managed mobile lines. Countries, devices, voice service, numbers and carrier arrangements define what can be delivered. An eSIM alone does not capture calls or make their content available to the OS: the voice connection must be designed as part of the rollout.
Continue a WhatsApp exchange by phone
WhatsApp Business Calling is a separate deployment path from ordinary phone calls and voice messages. Plan the business account, calling permissions, media connection and user interface together. The WhatsApp reference explains this path and its current preparation status.
Keep the agreement with the relationship
The useful outcome is not just a transcript. Find the customer’s need, the commitment made and what the next colleague should know. Available call content can support a callback mission, a draft reply or appointment preparation, according to the enabled workflows.
What the selected setup captures
During setup, define the incoming and outgoing calls covered, recording conditions, available content, retention and access. A phone log is not a transcript. A missing recording stays missing; an unresolved phone number must be matched to the correct contact before its context is used. An action prepared from an exchange still follows its own approval and execution rules.
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. |
Missions and responsibility
Read the source and execution state before acting. Confirming executes a pending mission; rejecting and archiving have different effects. Assignment follows company roles.
Scroll the table to read every column. With a keyboard, use the left and right arrow keys.
| Tool | Function and effect |
|---|---|
missions. | List the current user’s missions, optionally grouped by contact. |
missions. | Read a mission’s source, related objects and execution state. |
missions. | Confirm and execute a pending mission. |
missions. | Reject a pending mission without executing it. |
missions. | Archive a mission without executing or deleting its action. |
missions. | Assign from the company queue or reassign with the required role; changes are audited. |
Scroll the table to read every column. With a keyboard, use the left and right arrow keys.
| Source | What must be verified |
|---|---|
| Phone services and providers | Define the account, available interfaces, call content and enabled operations. Existing and custom connections have an explicit scope. 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 ↗