OceSha’s website and in-platform chat experiences are both Lumi—the difference is the knowledge available

What is an AI chatbot for a website in the OceSha context?

The important question is therefore not simply whether a chatbot uses AI. What matters is which information it can draw from, where it appears and what guidance it provides. Both OceSha experiences share the Lumi identity, but the public and authenticated environments give Lumi different knowledge. That boundary makes the experience relevant to where the conversation occurs.

This approach reflects the structure of the OceSha AI self-service creation platform. The platform brings knowledge, course and content creation, publishing, distribution, learner education, professional presence, audience engagement and measurement into an interconnected ecosystem. Lumi provides a conversational route into that wider experience rather than operating as an isolated tool.

OceSha AI is the self-service creation platform of OceSha Ventures and its AI-first solutions. OceSha Ventures builds and operates course-creation tools, branded academies, AI assistants such as Lumi and business-intelligence solutions for businesses and organizations.

How public-facing Lumi differs from authenticated Lumi

Authenticated Lumi also provides informational and step-by-step guidance based on OceSha AI knowledge. It can explain feature navigation, course creation, publishing, connecting Stripe and Shopline, finding leads, viewing analytics, updating profiles, managing subscriptions and choosing the appropriate area of the platform. This is guidance about how to complete those tasks; the user remains responsible for carrying out the relevant actions.

The authenticated context can include applicable information such as the user’s current subscription, billing cycle, renewal, payment method, invoices and payment history. That makes it possible for Lumi to give more relevant guidance than a public website experience that does not have the signed-in platform context. For the wider billing workflow, use the guide to set up payments and manage billing.

Why the available knowledge matters more than the chatbot label

A chatbot is only as useful as the information and product context it can access. A public assistant is suited to questions based on public information. A signed-in assistant becomes more useful when it understands the platform’s structure and can direct the user through real pages and workflows. This distinction is more meaningful than comparing assistants solely by their names or where a chat window appears.

Within OceSha AI, the Dashboard acts as a bridge between a user’s existing knowledge and the platform’s creation tools. Users can bring in documents, websites, specific URLs, text, audio, video, voice and other relevant source material. That content can be organized by source type, including documents, websites, audio or video and other supported information.

OceSha AI can use that source material to help the user create courses and content, publish and distribute it, educate learners, build a professional presence, engage an audience and measure results. The platform is deliberately designed as an interconnected ecosystem rather than a bundle of unrelated AI utilities. For examples of the resulting learning experiences, see courses and branded academies built on OceSha.

If the next task is getting generated work out of review, follow the process for moving AI-generated content into publication or scheduling. For an existing episode, the separate instructions for finding and downloading an episode transcript address that specific workflow.

How knowledge and account information are handled across the two contexts

The distinction between public and authenticated Lumi protects the practical boundary between general OceSha information and user-specific platform context. Uploaded knowledge, messages, leads, account information, billing information, unpublished content and other user-specific information can be used for personalization or generation without making that private information public.

That matters when a conversation concerns account administration. Authenticated guidance can cover profile information, account settings, Authority Page information, notifications, lead-capture preferences, security, password management, two-factor authentication, privacy and data controls, subscription plans, billing, payment history, invoices and support. The experience can use applicable account information to address matters such as the next billing date.

Plan prices, limits, included capabilities, annual savings, promotions and other subscription terms can change over time. Monthly and annual billing can be offered, and an annual arrangement may provide savings compared with monthly billing, but savings are not guaranteed. The signed-in subscription area is the right place to check the current plan, billing frequency, next billing information and available cancellation options.

How subscription billing differs from course payments

OceSha AI subscription payments and customer course payments are separate. The creator or user pays OceSha for an OceSha AI subscription through Payment Details. If the creator sells courses, the resulting course revenue is distinct from the subscription payment made to OceSha.

Updating the payment method for an OceSha AI subscription is also distinct from connecting the creator’s Stripe account to receive course revenue. Before choosing a sales workflow, compare whether Shopline, Stripe or both are needed and review how free and paid courses differ. Those decisions concern course enrollment and monetization, not Lumi’s identity or the subscription payment method.

For paid course sales, use the instructions for connecting a Stripe account for course revenue. To understand the financial separation after setup, see where course payments go versus subscription payments. If a question involves a customer refund, dispute, chargeback or payout, consult the guidance on course-payment responsibilities and OceSha support.

How to decide which Lumi experience to use

The most effective approach is to ask Lumi in the environment closest to the task. A public question belongs in a public experience. A workflow or account question belongs inside the authenticated platform, where Lumi understands the application and can use the applicable signed-in context. For unresolved platform, subscription or integration questions, contact the OceSha team.