Lumi reveals what website visitors ask, where they came from and what they did before leaving without buying

Turn visitor conversations into first-party customer intelligence

Lumi is an AI Concierge for a business website. Customer Lumi answers from that business’s approved public knowledge, captures leads and can hand visitors a booking link. The merchant works in a private workspace containing knowledge management, conversations, leads, Customer Intelligence, Business Lumi, team management and billing. Start with the wider discipline of Customer and Executive Intelligence, then use Lumi’s website AI Concierge to collect the conversations and behavioral context that make the intelligence useful.

This is more informative than relying on a generic exit prompt alone. A visitor may ask whether a policy applies to a particular situation, whether an offering fits a need or how to take the next step. Those questions expose the specific information that was missing at the moment of decision. Customer Intelligence adds the anonymous session and journey around each interaction, helping the business distinguish a knowledge gap from a navigation problem or an incomplete action.

What Lumi records when a visitor does not convert

The tracking intentionally has defined boundaries. It does not record device, browser, geography or page title. For connected SHOPLINE stores, Lumi receives commerce and cart events but does not read orders. It also has no SHOPLINE customer identity. These boundaries matter because they determine which conclusions the evidence supports.

The same discipline applies outside commerce. An inquiry report describes inquiries; it is not automatically a complete account of acquisition. Use the distinction explained in keeping inquiry reports separate from whole-site acquisition claims when presenting findings to colleagues or leadership.

A practical workflow for learning why visitors leave

Classification is especially important when similar questions require different answers. A sales inquiry and an existing-customer service request may use overlapping language but belong to different workflows. Distinguishing service questions from sales inquiries is a useful model for preserving that difference instead of combining every conversation into one lead category.

Policy questions need the same care. For example, sale clothing gift exchanges may differ from standard returns. A business should encode the published distinction in its approved public knowledge rather than let a general return answer override it. The principle is explored in separating gift exchanges from standard returns.

How booking and commerce signals add context without overstating results

For booking, the business sets a scheduling URL and Lumi opens it with attribution while recording a booking_started event. Any scheduling provider’s URL can be used for that handoff. Lumi does not infer that an appointment was completed merely because the visitor opened the link. Confirmed meetings appear only when an active calendar source provides them.

Calendly webhook handling and a Google Calendar read sync exist, but self-service setup for new Lumi merchants was not confirmed in the October 2026 audit. If confirmed appointments are essential to your reporting, ask whether a supported calendar source is active for your business before using meeting totals. After-hours businesses can still use a scheduling or contact path, as illustrated by finding current service information after hours, but availability information must come from the business’s approved knowledge.

For commerce, a connected SHOPLINE store gives Lumi synchronized catalog information for product answers, conversational product discovery and real storefront cart actions. Visitors can add products, change quantity or remove items from the store’s own cart before a checkout handoff. SHOPLINE remains the commerce engine and system of record; Lumi never stores a cart, processes payment or reads orders.

Checkout-reference tagging is limited and experimental. Lumi can place a random, non-personal reference in cart attributes and record related checkout context on its server, but it cannot match that reference to an order without order access. Treat it as checkout-intent context, not revenue attribution. The same reasoning applies when a published payment stage is mistaken for a financing offer; separating payment stages from financing claims shows why labels must follow the evidence.

Use approved knowledge to discover gaps without exposing private information

Customer Lumi answers only from the business’s approved public knowledge. Private and internal business knowledge belongs in the merchant’s private workspace, where Business Lumi supports internal use. This separation lets a business learn from public visitor conversations without turning internal material into a website answer source.

That boundary is particularly important when a website or domain changes. Old drafts, internal notes or unfinished content should not become public simply because a visitor asks about the subject. The guidance on keeping draft information private after domain changes applies the same core rule: maintain a deliberate line between approved public answers and internal working knowledge.

Lumi also matches website photos to offerings using a vision model. Matching uses a minimum confidence of 0.8, and site photos are rescanned weekly. This can help the concierge connect visual website content with relevant offerings, but it does not replace accurate written knowledge. Product names, policies, conditions and availability still need reliable approved source material.

The interface supports 12 locales across the widget, website, workspace and emails. Those locales are machine-translated and native-language quality was not reviewed in the audit. Businesses serving multilingual audiences should review important customer-facing wording in the languages they rely on. When comparing uneven published information—such as different levels of detail across team biographies—follow the approach in comparing biographies when source information is uneven rather than filling gaps with assumptions.

For businesses in Orange County, Los Angeles and San Diego, CA

Across these busy Southern California markets, visitors may compare several restaurants, retailers, professional services or appointment-based businesses before acting. Their questions can reveal whether pricing, availability, policies, service areas or booking details are creating hesitation. The first practical step is to add Lumi to the website using approved public knowledge, then review visitor conversations beside anonymous page paths, referral sources, UTM information and relevant events. Group recurring questions by intent and note where journeys stop, while keeping leads, booking starts, cart activity and completed outcomes clearly separated.

Build a reporting practice that separates questions, intent and outcomes

A useful report should have three layers. First, summarize what visitors asked: recurring topics, objections, policy confusion and product-discovery needs. Second, show the surrounding anonymous journey: source, UTM information, language, page path and session events. Third, report outcomes only at the level the connected source supports, such as lead captured, booking started, cart changed or checkout opened.

Time boundaries also matter. A retry of an earlier consultancy request may look like a new inquiry if the report considers only the latest event. Distinguishing overnight retries from new requests demonstrates why conversation and session context should accompany raw event counts.

Lumi is part of the OceSha ecosystem and is powered by OceSha. It is a product rather than a separate legal entity; OceSha Inc. is the billing seller. 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 supports subscriptions and trials, with monthly AI credits and optional top-ups. A tested top-up provides 100 credits for $12. If you want to discuss installation, knowledge preparation, calendar requirements or connected SHOPLINE use, contact the Lumi team with the systems and reporting outcomes that matter to your business.

The bottom line