Contact AlefOS · AlefOS Documentation
Choose the right route and contact AlefOS now.
Use this page to choose the right path: product support, Solo questions or a guided Team deployment.
Three clear routes · Minimum useful context · No secrets or payment data
Choose a route
3 optionsSupport
Something is blocked, broken or unclear in your account.
Solo
You want to know whether AlefOS fits the way you work alone.
Team deployment
You need shared memory, managers, providers and rollout support.
Next step
Choose the closest route, then use Support to send the request.
Three simple routes
Start with the outcome you need.
You do not need to understand AlefOS internals. Choose the route that matches your goal, then use the public Support page to send the request.
I need help
Report account access, billing, product or provider problems through the support form.
I work on my own
Ask how AlefOS can help one professional remember customers and follow-ups.
I need company memory
Share the company size, managers, workflows and providers needed for deployment.
Support sends the request to the right path
Prepare the desired business outcome and the minimum context needed to help.
Use support@alefos.ai or the public Support form. Never include passwords, tokens, card details or private company data exports.
Choose the right AlefOS path
Use this page to choose between product support, Solo, Team deployment, provider compatibility and sales enquiries.
One public support surface
Product support, Solo questions, Team deployment and sales enquiries can all start from the public Support surface.
Provider questions
AlefOS can review compatibility for Call Providers, Meeting Providers and WhatsApp onboarding when data is available and authorized.
Safe messages
Support messages should not include secrets, access tokens, payment data or private company data exports.
What to include
A useful request includes the relevant plan or workspace, the provider or feature involved and the business outcome you need.
Share useful context safely
The public Support page routes requests using the business context you provide. You do not need to include internal system details.
Product support
Use support@alefos.ai for product and workspace questions.
Team enquiries
Share company size, managers and provider needs.
Result
AlefOS can route the request without sharing private company or workspace data.
Detailed contact reference
Read the detailed reference below for support, provider compatibility, Team deployment and safety guidance.
Contact paths
AlefOS support can help route the request to the right path.
Common paths include:
- Product support.
- Solo questions.
- Team deployment.
- Call Provider compatibility.
- Meeting Provider compatibility.
- WhatsApp onboarding questions.
- Sales enquiries.
The public support email is support@alefos.ai.
Product support
For product support, include a short description of the issue, the affected workspace when relevant, and the page or feature where the issue happens.
Do not include passwords, API keys, access tokens, payment data or private data exports in a public support message.
AlefOS Support can ask for more information when needed to identify the account, workspace or request.
Solo questions
Solo questions usually concern personal operational memory, contacts, missions, accessible groups, offers, follow-ups and assistant access.
AlefOS can help explain what Solo includes, what remains limited, and when a Team setup becomes more appropriate.
Team deployment
Team deployment questions usually concern company workspace setup, Owner configuration, managers, permissions, groups, integrations, onboarding and shared company memory.
Team is not only a subscription.
It is a guided deployment for shared operational memory, manager visibility and controlled execution.
Provider compatibility
Provider compatibility depends on the source, permissions, plan and data available from the provider.
For Call Providers, compatibility depends on whether the configured provider can supply usable call events, metadata, transcripts or summaries with the required permissions.
For Meeting Providers, compatibility depends on whether transcripts, summaries, participant information, recording metadata or meeting context are available and permitted.
AlefOS only uses data that exists, is connected and is authorized.
WhatsApp onboarding
WhatsApp questions can concern onboarding, authorized business conversations, voice notes, Meta WhatsApp Business Platform usage, provider setup and message validation.
AlefOS is not an automatic WhatsApp bot.
It can extract, organize, structure and prepare drafts.
Any external or engaging WhatsApp message prepared by AI must be validated by the user before sending.
Sales enquiries
Sales enquiries can cover Solo, Team, deployment, provider compatibility, onboarding needs and the structure of a company workspace.
For Team, the useful information is usually:
- Company name.
- Approximate company size.
- Number of managers.
- Main communication and call tools.
- Whether WhatsApp, calls or meetings are important sources of work.
- What the company needs managers to see or validate.
Key takeaway
Use Contact AlefOS to choose the right path.
Product support, Solo questions, Team deployment, provider compatibility and sales enquiries all start from the public Support surface.
The goal is simple: send the useful business context without sharing secrets or private company data.
Choose your next step
Tell us what you are trying to make happen.
Choose product support, start Solo directly, or talk about a guided Team deployment.