{
  "title": "Contact AlefOS",
  "internal_name": null,
  "slug": "contact",
  "url": "https://alefos.ai/documentation/contact",
  "json_url": "https://alefos.ai/documentation/contact.json",
  "summary": "Tell AlefOS what you are trying to make happen and choose the right route: Support, Solo or Team deployment.",
  "description": "Choose one of three clear routes for product support, questions about working with AlefOS Solo or a guided Team deployment.",
  "category": "Business",
  "last_updated": "2026-07-10",
  "keywords": [
    "contact AlefOS",
    "support",
    "sales",
    "Team deployment",
    "provider compatibility"
  ],
  "sections": [
    {
      "heading": "Contact paths",
      "content": "AlefOS support can help route the request to the right path.\n\nCommon paths include:\n\n- Product support.\n- Solo questions.\n- Team / Tenant deployment.\n- Call Provider compatibility.\n- Meeting Provider compatibility.\n- WhatsApp onboarding questions.\n- Sales enquiries.\n\nThe public support email is support@alefos.ai."
    },
    {
      "heading": "Product support",
      "content": "For product support, include a short description of the issue, the affected workspace when relevant, and the page or feature where the issue happens.\n\nDo not include passwords, API keys, access tokens, payment data or private exports in a public support message.\n\nAlefOS Support can ask for more information when needed to identify the account, workspace or request."
    },
    {
      "heading": "Solo questions",
      "content": "Solo questions usually concern personal operational memory, contacts, missions, accessible groups, offers, follow-ups and assistant access.\n\nAlefOS can help explain what Solo includes, what remains limited, and when a Team setup becomes more appropriate."
    },
    {
      "heading": "Team deployment",
      "content": "Team deployment questions usually concern tenant setup, owner configuration, managers, permissions, groups, integrations, onboarding and company memory.\n\nTeam is not only a subscription.\n\nIt is a deployed operating model for shared operational memory, manager visibility and controlled execution."
    },
    {
      "heading": "Provider compatibility",
      "content": "Provider compatibility depends on the source, permissions, plan and data available from the provider.\n\nFor Call Providers, AlefOS can review whether the provider can supply useful call events, metadata, transcripts, summaries or follow-up signals when configured and authorized.\n\nFor Meeting Providers, AlefOS can review whether transcripts, summaries, participants, recordings metadata or meeting context are generated and accessible.\n\nAlefOS only uses data that exists, is connected and is authorized."
    },
    {
      "heading": "WhatsApp onboarding",
      "content": "WhatsApp questions can concern onboarding, authorized business conversations, voice notes, Meta WhatsApp Business Platform usage, provider setup and message validation.\n\nAlefOS is not an automatic WhatsApp bot.\n\nIt can extract, organize, structure and prepare drafts.\n\nAny external or engaging WhatsApp message prepared by AI must be validated by the user before sending."
    },
    {
      "heading": "Sales enquiries",
      "content": "Sales enquiries can cover Solo, Team, deployment, provider compatibility, onboarding needs and the structure of a company workspace.\n\nFor Team, the useful information is usually:\n\n- Company name.\n- Approximate company size.\n- Number of managers.\n- Main communication and call tools.\n- Whether WhatsApp, calls or meetings are important sources of work.\n- What the company needs managers to see or validate."
    },
    {
      "heading": "Key takeaway",
      "content": "Contact AlefOS when you need help choosing the right path.\n\nSupport questions, Solo questions, Team deployment, provider compatibility and sales enquiries should all reach the same public contact surface first.\n\nThe goal is simple: route the request without exposing internal inboxes, admin routes or tenant data."
    }
  ],
  "typical_questions": [
    "How do I contact AlefOS support?",
    "Who should I contact for Team deployment?",
    "Can AlefOS work with my call provider?",
    "Can AlefOS work with my meeting provider?",
    "How do I ask about WhatsApp onboarding?"
  ],
  "related_pages": [
    "mcp-cockpit",
    "solo",
    "team",
    "deployment",
    "whatsapp",
    "call-provider",
    "meeting-providers"
  ],
  "important_notes": [
    "Use support@alefos.ai for product support and public enquiries.",
    "Do not send secrets, access tokens, payment data or private tenant exports through a public contact message."
  ],
  "markdown": "# Contact AlefOS\n\nLast updated: 2026-07-10\n\nChoose one of three clear routes for product support, questions about working with AlefOS Solo or a guided Team deployment.\n\n## Contact paths\n\nAlefOS support can help route the request to the right path.\n\nCommon paths include:\n\n- Product support.\n- Solo questions.\n- Team / Tenant deployment.\n- Call Provider compatibility.\n- Meeting Provider compatibility.\n- WhatsApp onboarding questions.\n- Sales enquiries.\n\nThe public support email is support@alefos.ai.\n\n## Product support\n\nFor product support, include a short description of the issue, the affected workspace when relevant, and the page or feature where the issue happens.\n\nDo not include passwords, API keys, access tokens, payment data or private exports in a public support message.\n\nAlefOS Support can ask for more information when needed to identify the account, workspace or request.\n\n## Solo questions\n\nSolo questions usually concern personal operational memory, contacts, missions, accessible groups, offers, follow-ups and assistant access.\n\nAlefOS can help explain what Solo includes, what remains limited, and when a Team setup becomes more appropriate.\n\n## Team deployment\n\nTeam deployment questions usually concern tenant setup, owner configuration, managers, permissions, groups, integrations, onboarding and company memory.\n\nTeam is not only a subscription.\n\nIt is a deployed operating model for shared operational memory, manager visibility and controlled execution.\n\n## Provider compatibility\n\nProvider compatibility depends on the source, permissions, plan and data available from the provider.\n\nFor Call Providers, AlefOS can review whether the provider can supply useful call events, metadata, transcripts, summaries or follow-up signals when configured and authorized.\n\nFor Meeting Providers, AlefOS can review whether transcripts, summaries, participants, recordings metadata or meeting context are generated and accessible.\n\nAlefOS only uses data that exists, is connected and is authorized.\n\n## WhatsApp onboarding\n\nWhatsApp questions can concern onboarding, authorized business conversations, voice notes, Meta WhatsApp Business Platform usage, provider setup and message validation.\n\nAlefOS is not an automatic WhatsApp bot.\n\nIt can extract, organize, structure and prepare drafts.\n\nAny external or engaging WhatsApp message prepared by AI must be validated by the user before sending.\n\n## Sales enquiries\n\nSales enquiries can cover Solo, Team, deployment, provider compatibility, onboarding needs and the structure of a company workspace.\n\nFor Team, the useful information is usually:\n\n- Company name.\n- Approximate company size.\n- Number of managers.\n- Main communication and call tools.\n- Whether WhatsApp, calls or meetings are important sources of work.\n- What the company needs managers to see or validate.\n\n## Key takeaway\n\nContact AlefOS when you need help choosing the right path.\n\nSupport questions, Solo questions, Team deployment, provider compatibility and sales enquiries should all reach the same public contact surface first.\n\nThe goal is simple: route the request without exposing internal inboxes, admin routes or tenant data.\n\n## Typical questions\n\n- How do I contact AlefOS support?\n- Who should I contact for Team deployment?\n- Can AlefOS work with my call provider?\n- Can AlefOS work with my meeting provider?\n- How do I ask about WhatsApp onboarding?\n\n## Important notes\n\n- Use support@alefos.ai for product support and public enquiries.\n- Do not send secrets, access tokens, payment data or private tenant exports through a public contact message."
}