Explore AlefOS
Keep your tools. Find what gets lost between them.
Start with how your company already works: phone systems, WhatsApp, email or meetings. Choose what to retain, what to connect and what needs adapting so useful context follows the work.
Start with the work
Where do you need help?
On this page
Keep the tool that already works for the team
Start with a situation, not a catalogue of logos. A company with a phone service needs the provider connection path. A team choosing an integrated calling experience needs CallOS. Customer exchanges on WhatsApp belong to the messaging and business-calling paths. Email and meetings retain their own references.
Your tool is not listed? Start with what it exposes
Describe the tool, who uses it and what you want to carry forward. APIs, webhooks, MCP tools or supported exports may provide an adaptation path. The scope identifies the useful data and operations before choosing the connection; an open interface is a starting point, not a promise of universal compatibility.
An exchange becomes useful to the next person
A received message changes an access instruction. Available call content records an agreement. A meeting establishes the next owner. The useful connection keeps these sources with the right relationship and authorized team, so an assistant or the company interface can retrieve them.
Where MCP fits
Your company’s MCP server is an access point to authorized OS tools. A provider’s MCP interface, when available, is a separate potential connection to that provider’s capabilities. A protocol does not itself supply every recording, synchronize every tool or grant every action.
A scope that can be demonstrated
Define the account, permissions, received content, enabled actions and expected delays. Validate a useful end-to-end workflow, including missing data and disconnection. The result is a defined connection serving your work, with a clear distinction between what is delivered and what remains to adapt.
Connect a customer request to the team that handles it
A request starts in ChatGPT and continues in your company: a service inquiry reaches its recipient, a visit request follows your calendar rules, a document comes from the authorized source.
We define the whole journey, including sign-in when needed, the connected service, its response and what happens if it is unavailable. An assistant’s reply should never claim a booking or delivery that the connected service has not confirmed.
Which connection does your workflow need?
Scroll the table to read every column. With a keyboard, use the left and right arrow keys.
| Situation | What we configure | What the scope must confirm |
|---|---|---|
| Documented AlefOS connection | The selected provider and available workflow. | Account access, permissions, received content and supported actions. |
| Another tool with an API, webhook or MCP | An adaptation after reviewing the provider’s interface. | Required operations, identity matching, API limits and development in the quote. |
| A tool without usable access | An alternative workflow, if one can meet the need. | A practical solution before making any connection commitment. |
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.
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 → |
| Other tools and connections | Describe the desired workflow and available API, webhooks, MCP tools or exports. Define the adaptation from the actual content and permissions. 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