OceSha AI helps answer questions when you’re away through published content, course-based Lumi support, and clear human handoffs

Start by turning repeated questions into knowledge people can reach

The practical goal is not to automate every conversation. It is to make dependable answers available at the point where people need them. OceSha AI supports a content path in which your source knowledge becomes published material, that material attracts visitors to your Authority Page, and those visitors can become leads, learners, or customers. Analytics then helps you understand the resulting activity.

This approach works best when you identify the questions that repeatedly interrupt sales, onboarding, or learning and address them in durable content. A published explanation gives every visitor the same starting point. A structured lesson gives learners more depth. Lumi can then assist within a course by drawing on its educational material and knowledge supplied by the creator.

Use the right answer format for each kind of question

A single FAQ is rarely enough. Different questions need different forms of explanation. Short, stable answers belong in published material. Topics that need sequence, context, or instruction belong in a course. Questions that arise while someone is learning are suited to Lumi’s course experience, where the assistant can use the applicable course content and creator-provided knowledge.

If the answer is part of a paid learning experience, decide whether the course should be free or paid before designing its enrollment path. The distinction affects purpose, enrollment, and who handles payment responsibilities; see how free and paid courses differ before publishing the offer.

OceSha Academy demonstrates the course and academy side of the ecosystem. Explore courses and branded academies built on OceSha when you need to understand how structured learning differs from a loose collection of answers.

What Lumi answers—and where its knowledge comes from

Lumi is OceSha AI’s AI Concierge, but its role depends on context. Public-facing Lumi is trained on OceSha’s public information. Visitors, prospective customers, partners, and other users can ask about OceSha, its products, capabilities, services, plans, and other publicly available information without searching across multiple pages.

Authenticated Lumi has a broader platform-help role. Signed-in users can ask general questions about OceSha as well as detailed questions about features, navigation, workflows, account functions, content, courses, publishing, analytics, integrations, settings, and subscriptions. It provides informational and how-to guidance, including where to find leads, how to choose the appropriate platform area, and how to navigate course creation or publishing workflows.

Inside a course, the grounding changes to the learning context. Lumi uses the applicable lessons and knowledge provided by the creator to support instruction, clarify concepts, and respond to learner questions. That makes the course itself the essential foundation: clear, accurate source material produces a better reference base for learner support.

Build a reliable self-service answering workflow

The strongest workflow begins with source knowledge rather than an empty chatbot. Gather the information people repeatedly need, turn it into suitable content, publish it where visitors can reach it, and use course-based assistance where the subject requires instruction. Then examine activity and improve the material instead of relying on one-time personal replies.

Publishing is the dividing line between content that is still being prepared and information people can actually use. If your generated material is waiting in review, follow the process for moving AI-generated content toward publication or scheduling so the answer does not remain inaccessible.

When an existing episode contains an answer you want to reuse, first determine whether a written version is available. The guidance on finding and downloading an episode transcript is the natural next step before adapting that material for another destination.

Keep payments, subscriptions, and customer transactions clearly separated

Questions about buying a course are not the same as questions about your OceSha AI subscription. Creators can connect supported payment services to receive money from customers purchasing their courses. Those customer course payments are separate from the subscription payments a creator makes to OceSha through Payment Details.

Payment Details covers the OceSha AI subscription, including the current plan, billing frequency, renewal information, payment method, transaction history, and invoices. Plans can offer monthly or annual billing, and an annual arrangement may provide savings compared with monthly billing, although savings are not guaranteed. Prices, limits, included capabilities, promotions, and other subscription terms can change over time.

Before selling a paid course, decide which supported services your workflow requires. Review whether Shopline, Stripe, or both are needed, then use the separate instructions for connecting Stripe for paid course sales if Stripe is part of your setup. Keeping this distinction explicit prevents visitors’ purchase questions from becoming mixed with your own platform-billing questions.

Course revenue belongs to the creator’s customer-payment flow, while OceSha AI subscription charges belong to the creator’s account with OceSha. The explanation of where course payments go and how subscription billing differs clarifies the two money flows.

Know when automation should hand off to a person

Self-service information is effective for repeatable questions with a clear source. Human assistance remains the correct destination for unresolved support issues, creator-managed transactions, and situations requiring judgment or action beyond an informational answer. Lumi explains OceSha and how the platform works; Contact Us provides a path to the OceSha support team when human help is needed.

For platform questions, OceSha AI subscription questions, or the OceSha side of an integration, direct the matter to OceSha support when appropriate. Authenticated Lumi can explain how to change plans, update subscription payment methods, access invoices, change account settings, and reach support, but it provides guidance rather than carrying out those actions on the user’s behalf.

Account decisions also require precise language. Cancelling an OceSha AI subscription and deleting an account are different actions. Available subscription-management controls show the terms applicable to the user’s subscription, while account data can include uploaded knowledge, messages, leads, billing information, unpublished content, and other user-specific information. Using private information for personalization or generation does not make it public.

If someone wants to stop paying rather than remove their account, direct them to the explanation of subscription cancellation versus account deletion. This avoids treating two distinct actions as interchangeable and helps the person choose the path that matches the intended outcome.