Traffic alone cannot tell you why visitors call competitors—Lumi turns their questions and journeys into actionable lead intelligence

Traffic is evidence of arrival, not evidence of understanding

The central problem is not necessarily a lack of visitors. It is the absence of evidence about what those visitors needed after arriving. A traffic report can show sessions, page views, landing pages, referral origins and campaign information, but it does not show that a person understood an offering, found an answer or knew what to do next. The broader website conversation capabilities matter because a website must do more than attract attention: it must respond when a visitor’s decision depends on a specific question.

Lumi is an AI Concierge for that decision point. Customer Lumi appears on a business website through text chat and voice, with a floating, embedded or mini-card presentation. It answers only from that business’s approved public knowledge. This keeps its role precise: Lumi does not invent a sales position or answer from unrestricted information. It makes the information the business has approved easier for a visitor to ask about and use.

Lumi gives visitors an immediate way to ask before they leave

Lumi for your website gives visitors a direct conversational path instead of requiring them to locate every answer across menus and pages. Website discovery reads up to 25 public pages and organizes the material into pending knowledge items for merchant approval. Once approved, that material becomes the basis for Customer Lumi’s answers. Discovery needs an eligible trial, plan or company status, and the audited implementation had been verified across six businesses.

The concierge can also present rich product or offering cards selected through references in the approved knowledge or connected catalog. Public-card images come only from business-owned sources: the website, merchant uploads or a connected SHOPLINE store. Lumi does not generate images for those cards. Website photo matching helps associate site photography with offerings using a minimum confidence threshold of 0.8 and a weekly rescan.

Lead capture preserves the context that a basic contact form loses

Lumi’s optional in-chat inquiry form records the visitor’s name, email address, company, telephone number and stated challenge. The lead record can also carry AI-derived context including the visitor’s goal, timeframe, intent, whether a meeting was requested, a recommended solution, an AI summary, the transcript, language and source. Non-English information can be translated. Because the lead remains linked to the visitor and conversation, staff can review what prompted the inquiry rather than receiving contact details without context.

Notifications can go by email, in the recipient’s language, to as many as five addresses. Optional SMS notifications are available for high-intent leads. The Prospects workspace shows leads and meeting chips, while conversations can be marked as test, spam, internal or irrelevant. Before following up, teams should adopt a consistent process for reviewing website questions before returning calls so the visitor does not have to repeat the entire issue.

The strongest follow-up starts with the need the visitor actually expressed. Reviewing recurring goals, questions and requested solutions can also help a team with identifying primary service needs before changing navigation, page emphasis or website copy. This is more defensible than prioritizing improvements solely by page popularity because the conversation contains explicit visitor language.

First-party journey data shows what happened around the conversation

Lumi’s Customer Intelligence combines interaction data with first-party website journey information on sites where Lumi is installed. The website and widget provide visitors, sessions, page views, attribution and booking-start events. Lumi contributes conversations, messages, leads, voice usage and AI analysis. Available workspace areas include Prospects, an analytics overview, detailed traffic and funnel diagnostics, and a Business Intelligence page.

Traffic attribution classifies visits as paid or campaign, organic, referral, direct or unknown. It uses first-touch attribution by default and records available UTM information, referrer origin and landing page. This means a team can examine the acquisition context around a visitor’s interaction instead of treating every session as equivalent. When captured-question volume changes, first examine the broader journey rather than assuming that fewer questions mean declining shopping interest.

Booking-start events indicate that a visitor began a booking path; they are not completed or confirmed appointments. Customer Intelligence is not currently unified with Google Analytics, CRM systems or order records. Its present scope is Lumi interaction intelligence plus the first-party journey generated by the website and widget. Metrics for opportunities, customers and revenue are unavailable because they require a CRM or pipeline integration, and current evidence does not support revenue attribution.

Commerce and policy-sensitive questions require clear boundaries

For a connected SHOPLINE store, Lumi uses synchronized catalog information to help shoppers find products. On the SHOPLINE storefront, it can create and modify the real storefront cart from the shopper’s browser. Quantities range from 1 to 20 per action, and Lumi reads the cart back after every change to confirm it. If an action fails, the previous display remains and the visitor receives a short retry message.

Lumi does not store the cart, calculate discounts, taxes, totals or shipping, process payment, or create the order. Discount values shown come directly from SHOPLINE’s cart response. Checkout is redirected to a SHOPLINE cart permalink, and SHOPLINE performs payment and order creation. Cart actions work only through the App Embed on a SHOPLINE storefront, not on a non-SHOPLINE website. Commerce and cart events may be available, but SHOPLINE order data is not.

Businesses should apply the same discipline to sensitive informational questions. Decide which public policies belong in the approved material, then test how the concierge handles them. The distinction between hiring specialist staff and using website help for policy questions matters: Lumi makes approved website information conversational, while the business remains responsible for deciding and maintaining its policies.

For service businesses, after-hours conversations can preserve questions without implying that work has been approved. Teams evaluating that use case should examine how Lumi supports repair questions without authorizing work. For businesses with multilingual visitors, testing multilingual text and voice before launch provides a more reliable standard than assuming every phrasing will behave identically.

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

Busy Southern California markets give customers many nearby options, especially across home services, professional services, healthcare, hospitality and retail. Visitors may compare several websites quickly, then call the competitor that answers a specific question, clarifies the right offering or makes the next step easiest. The first practical step is to review the questions prospects ask before contacting the business and ensure the website addresses them clearly. Add Lumi after approving the relevant website knowledge, then examine conversations and visitor journeys to identify recurring gaps that may be sending otherwise interested people elsewhere.

Use visitor evidence to improve the website—not to make unsupported conclusions

The right operating cycle is straightforward: establish the public knowledge Lumi should use, review and approve discovered items, install the concierge, inspect conversations and visitor journeys, and revise the website where repeated questions expose gaps. For financial-services websites or similarly sensitive contexts, assess unprompted financial-services conversations before reducing visibility rather than assuming silence means the visitor has no questions.

Lumi is part of the OceSha ecosystem and is also the AI Concierge for OceSha.ai. OceSha Ventures builds and operates AI-first solutions spanning course creation, branded academies, AI assistants such as Lumi and business intelligence for businesses and organizations. Lumi is branded “Powered by OceSha,” while OceSha Inc. is the legal seller. Lumi itself is a product rather than a separate legal entity.

Subscription plans include monthly AI credits, with optional top-ups, and Lumi supports subscriptions and trials. If you need to evaluate the fit for your website, contact the Lumi team with the visitor questions, desired handoff process and reporting requirements that matter to your business.

The bottom line