Solo · AlefOS Documentation
Stop carrying every customer follow-up in your head.
AlefOS remembers what customers asked, what you promised and what needs your attention across calls, WhatsApp, meetings and appointments.
One professional · Real customer context · Nothing sent without your decision
Your morning briefing
One userYou ask
What am I forgetting today?
Customers waiting
Marc needs a quote. Sarah asked for a callback after 15:00.
Preparation
One document is missing. Your 16:30 meeting needs context.
Ready for review
The next actions are prepared. You decide what happens.
A day with Solo
Your work stays connected from morning to follow-up.
Solo reduces the mental load at the moments when customer context is usually lost or rebuilt by hand.
See what needs attention
Ask who is waiting, what is late and which meeting needs preparation.
Recover the customer story
See the last exchange, promise, blocker and open mission before answering.
Keep the next step
A callback, quote or document request becomes a contextual mission.
Review before anything happens
Check what is ready, pending or still waiting for your decision.
Solo is not built around manually maintaining a complex CRM pipeline. It focuses on customer memory, contextual follow-up and prepared next actions from the work one professional already does.
Solo as an AI CRM for one professional
Solo can work as an AI CRM for one professional whose customer context is created through calls, authorized WhatsApp Business conversations, meetings, appointments and follow-ups. It reduces repetitive reconstruction while keeping protected actions under the user’s control.
Less mental load
Solo reduces the need to reconstruct work from memory, notes, WhatsApp, calendar and scattered tools.
Context before action
Contacts and missions preserve why each callback, follow-up or promised document matters.
More than a CRM or todo list
Solo does not ask you to rebuild your work inside a manual CRM or simple todo list. It keeps the useful context connected.
Ask about your own work
Ask which customers need a callback, what was forgotten, which appointments are coming and what is already known about a customer.
The right plan for one professional
Choose Solo when one professional needs AlefOS for real daily work without a company deployment.
Free
Limited real personal work inside clear usage limits.
Solo
One professional uses AlefOS continuously with higher volume and eligible integrations.
Team
A company deploys shared memory, manager visibility and role-based permissions.
Detailed Solo reference
Read the detailed Solo reference below for product behavior, permissions and limits.
Who Solo is for
Solo is designed for professionals who manage customers, appointments, calls and follow-ups on their own.
Examples:
- Independent professionals.
- Entrepreneurs.
- Salespeople.
- Consultants.
- Service providers.
- Real estate agents.
- Brokers.
- Insurance agents.
- Field operators.
- Business owners managing their own customers.
Their work is often spread across phone, WhatsApp, calendar, notes, email, spreadsheets, lightweight CRM and personal memory.
Solo connects that activity into one usable work memory.
The problem
When someone works alone, everything often depends on personal memory.
A customer calls. A message arrives. An appointment is scheduled. A follow-up is promised. A document is expected. An opportunity is noted somewhere. A decision is made quickly.
But hours or days later, the user needs to remember who to call back, what was promised, which document is missing, which customer is warm, which appointment is coming, which reply should be prepared and which action was forgotten.
Solo exists to reduce that mental load.
What Solo provides
Solo gives one professional a personal operational memory.
This memory can bring together:
- Contacts.
- Relationships.
- Missions.
- Follow-ups.
- Reminders.
- Important calls.
- Important messages.
- Appointments.
- Products or services.
- Accessible groups.
- Decisions.
- Actions to validate.
The goal is not to re-enter every conversation inside a CRM. The goal is to make real work understandable, searchable and actionable.
Solo capacity
Solo includes:
- 25,000 contacts.
- 500 active products or services.
- 50,000 Loop1 analyses per cycle.
- 10,000 successful Loop2 actions per cycle.
- 500 call minutes per month.
- Up to 100 personal Groups.
- Up to 1,000 members per Group.
- Eligible Solo providers where available.
Solo remains a personal workspace. Team assignment is not included.
Personal contacts
With Solo, contacts become more than an address book.
A contact can include recent interactions, linked calls, appointments, open missions, products or services discussed, promises made, planned follow-ups and useful information before a call.
The user can ask:
- Where am I with this customer?
- What did I promise them?
- Who should I call back today?
AlefOS answers with the available context.
Personal missions
Solo keeps important actions connected to the reason behind them.
A mission can be a follow-up, callback, message to prepare, document to request, appointment to confirm, action after a call, task linked to a contact or action to validate.
The difference from a simple todo list is that an AlefOS mission keeps the context.
It does not only say "Call Marc." It can explain why the call is needed, what was said, what is expected, what reply should be prepared and what the next step is.
Calls, messages and appointments
When the relevant sources are connected and permissions allow it, Solo can use context from calls, messages and appointments.
Examples:
- A call can generate a callback.
- A message can become a mission.
- An appointment can be linked to a contact.
- A promise can be found later.
- A follow-up can be prepared before validation.
AlefOS works alongside existing tools and keeps their useful work context connected.
Products, services and accessible groups
Solo can structure products, services or offers and connect them to the customer needs they address.
Solo can also use groups when the user has the required access and permissions.
Even as one person, the user can benefit from shared memory when they belong to an authorized group.
ChatGPT with AlefOS memory
With Solo, ChatGPT can answer natural-language questions about the work context AlefOS is allowed to access.
The user can ask:
- Which customers should I call back today?
- Prepare my follow-ups.
- What did I forget to do?
- What appointments are coming this week?
- Which contacts mentioned this offer?
- Summarize what I know about this customer.
ChatGPT answers from the available AlefOS work memory instead of relying only on generic information.
Validation and control
Solo follows an important rule: AlefOS prepares. The user decides.
Important actions remain under the user’s control.
AlefOS can prepare a message, follow-up, mission, summary, suggested action or appointment to confirm.
The user reviews and decides before any protected action is executed.
Difference between Free, Solo and Team
Free
A limited personal plan for real work.
Solo
A high-capacity personal plan for daily professional work.
Team
Shared company memory with roles, permissions and team execution.
Free handles a limited volume of real personal work. Solo gives one professional much higher capacity for daily work. Team adds shared company memory, roles, permissions and collective execution.
What Solo is not
Solo is not a Team plan.
It does not include multiple managers, manager cockpit, advanced company permissions, team deployment, global visibility across multiple users, 90-day Team onboarding or multi-manager structure.
Solo is designed for one professional: personal, focused and directly useful in daily work.
Key takeaway
Solo is AlefOS for one professional.
It is not a manual CRM. It is not a simple todo list. It is not just a calendar.
It keeps work context connected and prepares what comes next.
The simple idea: you already work. AlefOS makes sure your work does not disappear.
Choose your next step
Stop carrying every follow-up in your head.
Start Solo for one professional, or compare the plans before choosing your next step.
