AlefOS pricing
Capture calls, WhatsApp conversations, meetings, decisions and follow-ups, then turn them into clear context and actions for yourself or your team.
From one professional managing daily work to a company connecting teams, providers and operational workflows.
No payment required.
Explore the AlefOS workspace, understand the memory logic and see how conversations become context.
Catalog price: 100 USD
500 minutes included per month.
For one professional managing customers, calls, WhatsApp, meetings, decisions and follow-ups.
Starting at
Guided setup. No direct online checkout.
For companies that need shared context, permissions, manager visibility and provider setup.
Solo is not a list of modules. It is one professional's work memory: calls, messages, meetings, contacts, groups and follow-ups connected around real relationships.
Call customers from AlefOS where supported, keep what was discussed, and identify what should happen next instead of relying on memory after the call.
When WhatsApp is connected and authorized, important customer exchanges can enrich the right contact or work group. AlefOS is not an automatic WhatsApp bot and does not reply alone.
Zoom or Google Meet conversations can feed AlefOS when meeting data, transcripts or recordings are enabled, generated and accessible through the connected provider permissions.
A group in AlefOS is not just a chat. It is a structured space around work, people, context, messages and decisions.
Team is for companies that need shared context, configured visibility, roles and provider setup. It is prepared with the organization before activation.
Several users can contribute to the same company context so customer history is not locked inside one employee's phone, notes or private conversations.
Managers can get configured visibility into active relationships, pending actions, blockers and important customer situations according to permissions.
Supported business telephony providers such as Aircall can be configured during Team deployment so call activity can feed operational context. Other providers are reviewed based on compatibility.
Team deployment defines users, roles, groups, providers, permissions and workflows before the tenant is activated.
Different businesses use different tools. The pattern is the same: inputs become context, then context becomes the next clear action.
Visits, offers, buyers, sellers and follow-ups stay connected to the same transaction context.
Decisions, meetings, documents, contacts and pending actions stay attached to the same client matter.
Properties, maintenance issues, installations, providers and customer requests can be organized in groups.
Calls, messages, meetings and opportunities can become shared signals across agents and managers.
Sites, appointments, technicians, customer decisions and intervention history stay connected.
Proposals, meetings, client context, decisions and next steps stay in one operational memory.
The goal is not to count checkmarks. It is to understand how much work context each plan can capture, structure and share.
| Category | Discovery | Solo | Team |
|---|---|---|---|
| Best for | Exploring the AlefOS logic | One professional managing daily work | Companies and teams that need shared context |
| Operational memory | Limited discovery workspace | Personal operational memory around real relationships | Shared company memory configured by tenant |
| Customer relationship context | Sample or visible context | Calls, messages, meetings, promises and follow-ups around one relationship | Company-level context across several users, roles and groups |
| Calls | Not included | Supported calls can feed memory and next actions | Calls can feed team context through supported setup and providers |
| WhatsApp context | Not a full WhatsApp connection | Where connected and authorized, customer exchanges can enrich context | Shared WhatsApp signals where company setup and permissions allow |
| Zoom / Google Meet | Not included | Meeting context when transcripts or meeting data are available | Meeting context connected to groups, customers or projects when configured |
| Calendar and appointments | Limited | Prepare appointments with relationship context and follow-up memory | Calendar context can support workflows during deployment |
| Business groups | Invited groups when permissions allow | Groups for customer projects, files, sites, suppliers or opportunities | Groups by team, customer, property, case, region, provider or department |
| AI assistant / MCP | Limited | Ask supported assistants for context and prepared actions | Assistant access according to tenant, role and manager scope |
| Call minutes | Not included | 500 minutes per month | Scoped during deployment |
| Shared company context | Not included | Not included | Included with tenant structure |
| Manager visibility | Not included | Not included | Configured visibility into follow-ups, blockers and team signals |
| Roles and permissions | Basic access | Single-user scope | Roles, groups and permissions defined during deployment |
| Business telephony providers | Not included | Not included | Aircall supported; other providers reviewed by compatibility |
| Guided deployment | Not included | Not included | Organization, users, workflows and integrations are prepared before activation |
| Support and onboarding | Basic support | Product support | Guided deployment and onboarding |
Start with the plan that matches how work happens today: alone, inside a small professional routine, or across a company with several people and providers.
For discovering the AlefOS logic, testing the workspace and seeing how conversations, contacts and missions become structured context before paying.
For a real estate agent, consultant, installer, salesperson or independent professional who needs memory around calls, WhatsApp, meetings, contacts, decisions and follow-ups.
For organizations where several people touch the same customers, cases, sites or projects and managers need visibility without endless status chasing.
Team deployment
AlefOS Team is not activated by a simple online payment. Deployment starts by understanding the organization, mapping users and roles, identifying providers, defining permissions, connecting supported tools, preparing groups and onboarding the team progressively.
Practical answers about what the plans can do and where setup or permissions matter.
Yes. Discovery is free and does not require payment. It is designed to let you explore the AlefOS workspace and understand the product logic before moving to a paid plan.
Solo is available at 50 USD or 50 EUR during the launch offer. The catalog price is 100 USD or 100 EUR.
Solo includes 500 minutes per month.
Yes, where WhatsApp is connected and authorized. AlefOS can use business conversation context to enrich contacts, groups, missions and follow-ups. It is not an automatic WhatsApp bot, does not launch campaigns and does not reply to customers alone.
Meeting context can feed AlefOS when transcripts, recordings or meeting data are enabled, generated and accessible through the connected provider permissions. AlefOS does not replace Zoom or Google Meet.
Aircall is currently documented as a supported call provider for Team deployment. Other providers can be reviewed depending on available APIs, webhooks and the data they expose.
A business group is a structured workspace around real work: a customer project, property sale, legal case, hotel site, installation team, sales pipeline or supplier coordination topic. It is not just a generic chat room.
In Team, manager visibility is configured during deployment according to roles, permissions and groups. The goal is to surface follow-ups, blockers, customer situations and team signals without exposing everything to everyone.
The public plans available are the plans shown at the time of subscription.
No. Team requires guided deployment adapted to the organization, users, workflows, permissions and provider configuration.
AlefOS is designed around work patterns rather than one single industry. Teams can structure groups and workflows around sales, real estate, legal files, hotel operations, installations, support or partner coordination during deployment.
AlefOS can prepare drafts and next actions, but external or engaging actions remain under user validation. The user decides before sending or executing.
In Team, the goal is to preserve authorized company context in tenant memory so the organization is less dependent on individual memory. Visibility still depends on roles, permissions and deployment configuration.
Team permissions, manager scopes and group access are defined during deployment. Users should only see the context they are allowed to access.
This page shows USD and EUR only. It does not perform dynamic conversion.
Additional minutes may be available from the account or through support. This page does not list topup packs.
Use the deployment request path on this page or contact AlefOS Support.
