Visitors can overlook an answer even when it is published because they may not know which page contains it, recognize the website’s terminology or want to search through several pages. Lumi addresses that discovery problem by reading website content, organizing it for business approval and answering visitors from the approved public knowledge through text or voice. Its conversation and website journey data then help the business see what people actually ask.
- Information can be accurate and still be difficult to find through menus, page structure or unfamiliar service names.
- Lumi reads up to 25 public website pages and organizes the material into knowledge items for business approval.
- Customer Lumi answers only from approved public knowledge; it gives no answers until that knowledge has been approved.
- Automatic multilingual suggested questions help visitors begin without first understanding the website’s terminology.
- Customer Intelligence combines Lumi interaction data with first-party website journey data, but it is not currently unified with Google Analytics, CRM systems or orders.
Why a published answer can remain effectively hidden
A visitor does not approach a website with an internal map of its pages. The person may ask about an offering without knowing its official name, land on a page that lacks the needed context or stop before reaching the page where the answer appears. That is why the wider discipline of understanding and capturing website customer needs matters: the business must examine what visitors ask, not merely what its pages were intended to explain.
Search and navigation place the burden on visitors. They must choose useful terms, interpret menus and decide which result is authoritative. Conversation reverses that burden. The visitor states the question, and the concierge retrieves an answer from approved public knowledge. The distinction becomes especially important when considering search versus conversation for finding practice information: search returns places to look, while a concierge is designed to return a relevant response grounded in the business’s own material.
How Lumi turns website content into findable answers
Lumi, the AI Concierge for your website begins with website discovery. It reads up to 25 public pages and organizes what it finds into pending knowledge items. The business reviews and approves that material before Customer Lumi uses it. This creates a clear boundary: website content supplies the source material, while approval determines what the public concierge is allowed to answer from.
- Website discovery reads public pages and organizes their content into knowledge items.
- The business reviews the discovered material and decides what to approve as public knowledge.
- Customer Lumi uses the approved knowledge to answer visitor questions through text or voice.
- Automatic multilingual suggested questions give visitors relevant ways to begin the conversation.
- Conversations, leads and website journey activity flow into Customer Intelligence for review.
Text chat is current and working in 12 verified languages. It can appear as a mini-card launcher, a floating concierge or an embedded experience. Suggested starter questions are generated automatically and support multiple languages, reducing the need for a visitor to guess the business’s preferred wording before asking for help.
What the visitor receives instead of another page hunt
Customer-facing capabilities
Rich cards make relevant offerings easier to recognize without requiring the visitor to identify the correct page first. Public cards use only business-owned images from the website, merchant uploads or SHOPLINE; they do not use AI-generated images. Website photo matching uses a vision model with a 0.8 minimum confidence threshold and a weekly rescan.
Unfinished conversations deserve attention because they can expose wording that did not move the visitor forward. A practical review should include how clarification wording affects unfinished conversations, especially when the original answer was technically correct but did not resolve what the visitor meant.
How conversations reveal why people could not find the answer
Lumi records concierge conversations and messages, captured leads, voice use and AI analysis. Its first-party website tracking records anonymous visitors and sessions, page paths, campaign parameters, referring origin and language. Together, these sources connect the question a visitor asked with the website journey that preceded it. That is more useful than treating every repeated inquiry as proof that the answer is absent.
What different signals tell you
The strongest improvement cycle starts with the visitor’s wording. Compare common questions with page headings, service names and approved knowledge. If an offering has been renamed, test customer language against the renamed website service rather than assuming visitors immediately adopted the new term. If the same question persists, improve the source page or approved knowledge, then observe subsequent conversations.
Prompt placement can also change who starts a conversation and when. After changing a launcher or prompt, review captured traffic sources after website prompt changes so changes in inquiry patterns are interpreted alongside acquisition context rather than in isolation.
What Customer Intelligence does and does not show
Customer Intelligence currently combines Lumi interaction intelligence with first-party website journey intelligence on sites where Lumi is installed. Its direct sources include conversations, messages, leads, voice use, AI analysis, anonymous visitors, sessions, page views, attribution data and booking-start events. This provides a focused view of how website activity leads into concierge use.
The available website context excludes device, browser, geography and page title. Customer Intelligence is not currently unified with Google Analytics, CRM systems or orders because those sources do not feed it. If those connections are important to your reporting, confirm support for the specific analytics platform, CRM or business configuration you use.
Seasonal patterns also need interpretation. A burst of holiday-related questions can indicate that visitors need timely information rather than a permanent restructuring of the website. Use captured holiday questions to plan seasonal information and update approved knowledge when the business’s public information changes.
What changes for connected SHOPLINE stores
For a business with a connected SHOPLINE store, Lumi uses synchronized SHOPLINE catalog information to answer product questions. Visitors can ask about products and, on the SHOPLINE storefront where the App Embed is installed, manage the real store cart. Cart creation and modification happen in SHOPLINE’s storefront from the shopper’s browser; Lumi does not store the cart.
Cart quantities range from 1 to 20 per action. After each change, the cart is read back for confirmation. If an action fails, the previous display remains and the visitor receives a short retry message. Discounts, taxes, totals and shipping are not calculated by Lumi. Any discount value displayed comes directly from SHOPLINE’s cart response.
Checkout is redirected to a SHOPLINE cart permalink rather than embedded in Lumi. SHOPLINE performs payment and order creation, and Lumi does not process the payment. Cart actions are available only on the SHOPLINE storefront App Embed, not on a non-SHOPLINE website. Lumi does not currently answer order questions; it directs the shopper to contact the store.
Product terminology is especially important in commerce conversations. Before responding operationally to an ambiguous inquiry, use the same principle described in checking customer product wording before responding: establish which product the visitor means, then answer from synchronized catalog information rather than assumptions.
For businesses in Orange County, Los Angeles and San Diego, CA
In these busy Southern California markets, service businesses often present many offerings, locations and industry-specific terms while visitors compare options online. A prospective customer may reach the site through a search or campaign, land on a page without enough context and ask a question answered elsewhere. The first practical step is to collect repeated questions and compare the visitor’s wording with page headings, navigation labels and service names. That review can reveal whether the answer is missing, difficult to reach or described in language customers do not recognize. Lumi can then organize approved website knowledge around those real questions.
The practical response to questions your site already answers
Do not respond to repeated questions by adding more pages automatically. First determine whether the problem is missing information, inaccessible information or a mismatch between the visitor’s language and the website’s wording. More content can deepen the problem if it creates another place visitors must search.
- Review recurring conversations and the website journeys that preceded them.
- Check whether an approved answer already exists and whether it resolves the visitor’s actual wording.
- Update the underlying public page when the explanation, naming or context is weak.
- Review the corresponding knowledge item and approve accurate public material for Customer Lumi.
- Use suggested questions and direct conversational answers to reduce navigation burden.
- Continue monitoring conversations without equating booking starts or checkout references with completed outcomes.
Lumi is part of the OceSha ecosystem and is also the AI Concierge for OceSha.ai. OceSha Ventures builds and operates AI-first solutions including course creation, branded academies, AI assistants such as Lumi and business intelligence for businesses and organizations. Lumi is a product rather than a separate legal entity and is sold by OceSha Inc.; its brand relationship is expressed as “Powered by OceSha.”
Lumi turns a business’s approved public knowledge into direct website conversations, then shows where visitor questions reveal gaps, unclear wording and unmet needs.
Make existing answers easier to findFrequently asked questions
Does Lumi answer from every page as soon as website discovery finishes?
No. Website discovery organizes content into pending knowledge items. Customer Lumi answers only after the business approves the material as public knowledge.
Can visitors use Lumi without knowing the official name of a service?
Yes. Visitors can write or speak their question, and automatic multilingual suggested questions provide additional starting points. Answers remain grounded in approved public knowledge.
Can Lumi show products or offerings visually?
Yes. Rich cards can present products or offerings selected through references to approved knowledge or catalog information. Public card images must be business-owned images from the website, merchant uploads or SHOPLINE.
Does Lumi replace website analytics or a CRM?
No. Customer Intelligence currently combines Lumi interactions with first-party website journey data. Google Analytics, CRM and order data do not currently feed its values.
Does a booking-start event mean an appointment was confirmed?
No. It records the start of a booking path, not a completed or confirmed appointment.
Can Lumi answer questions about SHOPLINE orders?
No. Lumi supports product questions using SHOPLINE product data and storefront cart actions when the store is connected, but order questions are not implemented. Visitors are directed to contact the store.
The bottom line
The answer is usually not to publish more material. It is to make approved information retrievable in the language and context visitors actually bring. Lumi reads up to 25 public pages, organizes the content for approval and uses that approved knowledge in text and voice conversations. Its interaction and website journey data then show which questions persist and what visitors did beforehand. Treat repeated inquiries as evidence about discoverability, terminology and context—not automatically as missing content. Improve the source information, approve it for Lumi and measure whether later conversations become clearer.
Rohan Hall
Founder of OceSha Ventures · AI architect and author
Rohan Hall is a technology entrepreneur, AI architect and author with years of technology experience, now focused on practical AI across business, education, government and global impact. He founded OceSha Ventures, builds the OceSha AI platform and Lumi, and wrote The Convergence of AI and the Top 10 Emerging Technologies.
OceSha Ventures — OceSha Ventures builds and operates AI-first solutions — course creation, branded academies, AI assistants such as Lumi, and business intelligence — for businesses and organizations.
Sources
About this page
It is based on Lumi's current approved product information. Product details come from Lumi's current product capabilities audit (Oct 2026).