Businesses use AI concierges, lead forms, booking links and analytics to capture more website opportunities

The modern website lead stack starts with a responsive conversation

For businesses assessing which audiences and use cases fit Lumi, the essential shift is from passive pages to active assistance. Traditional websites rely on visitors finding the right page, interpreting the information and completing a separate contact form. An AI concierge puts question answering and inquiry capture into one interaction. Lumi is the AI Concierge for small and mid-sized businesses and online stores. It works on a business’s website, using that organization’s curated public material to answer visitor questions rather than presenting Lumi as the provider of the underlying products, services, prices or policies.

The useful tools are therefore not just more forms. They are connected parts of a visitor journey: immediate question answering, a structured way to collect contact details, a path to booking, contextual records for staff and analytics showing what happened before the inquiry. Lumi’s website AI Concierge brings those functions together. A business installs one script tag, or enables the SHOPLINE App Embed when using the supported commerce connection, and Customer Lumi becomes available to website visitors through chat and voice.

Lumi captures inquiries without separating the form from the conversation

Lumi’s lead-capture form appears inside the conversation and is optional for each business. It records the visitor’s name, email address, company, phone number and stated challenge. The resulting lead remains linked to the visitor and the relevant conversation, so staff can review what the person asked before deciding how to respond. This is more useful than a disconnected form submission because the inquiry and its source conversation stay together inside the private Lumi workspace.

Staff can review leads in the Prospects list, where meeting indicators accompany relevant records. Conversations can also be marked as test, spam, internal or irrelevant, helping teams keep operational activity distinct from genuine inquiries. This review process is especially important in regulated or context-sensitive settings. For example, teams can apply a disciplined review process when checking Lumi answers after acquiring a dental practice rather than assuming that inherited website material is complete or current.

Booking links and consultation paths turn interest into a clear next step

A visitor who receives a useful answer often needs an immediate route to continue. Customer Lumi can hand that person a booking link, keeping the next step close to the conversation instead of making the visitor search for a contact or scheduling page. The tool also records booking-start activity from the website or widget, and meetings appear where the business’s supported booking or calendar connection supplies them.

Calendar support should be checked for the individual business rather than assumed across every deployment. The same principle applies when staff serve people in different regions: verify the applicable scheduling context before responding, particularly when clarifying overseas callback time zones. This keeps the handoff useful without turning a preliminary signal into a promised meeting.

Online stores add product discovery and real-cart assistance

For a connected SHOPLINE store, Lumi extends beyond general website questions. It uses synchronized catalog information in conversations, helping shoppers search for products, choose a variant and view relevant items. Customer Lumi can also help the shopper manage the store’s real cart. These commerce tools require the business to connect its SHOPLINE store; they are not generic capabilities for every commerce platform.

There is no dedicated product-comparison tool, so the strongest use case is guided discovery rather than a specialized side-by-side comparison experience. Lumi also receives cart events and checkout references from SHOPLINE, but it does not receive completed orders. Checkout reference tagging is experimental and is not confirmed order or revenue attribution. Businesses should therefore treat it as interaction context, not as a sales ledger.

The same separation matters for policy questions. The concierge can present the store’s documented policy, while individual exceptions remain decisions for staff. A practical workflow for triaging e-commerce policies and exception requests prevents a general website answer from being mistaken for approval of a customer-specific exception.

First-party analytics show the path to an inquiry, not guaranteed revenue

Lumi’s Customer Intelligence receives information from conversations, messages, leads, voice use and AI analysis. It also receives website and widget signals including visitors, sessions, page views, attribution and booking-start events. Connected SHOPLINE stores contribute commerce and cart events plus checkout references. These inputs support the Prospects area, analytics overview, detailed views of traffic performance, funnel and diagnostics, and the Business Intelligence page.

This distinction keeps reporting useful. Lumi provides first-party evidence about what visitors did in the concierge and on the website, but it does not guarantee leads, appointments, sales, conversion rates, traffic or revenue. Even when a source describes a sensitive operational safeguard, teams should evaluate the exact published evidence rather than infer broader credentials, as illustrated by reviewing published shredding safeguards carefully.

Setup begins with controlled knowledge and a private operating workspace

Lumi’s website discovery process reads as many as 25 public pages and organizes what it finds into pending knowledge items. The process is working and has been verified across six businesses. It requires the applicable trial, plan or company status. Pending items give the business an opportunity to organize its source material before Customer Lumi uses it with visitors. Private and internal business knowledge can also be held within the system for appropriate workspace use.

Knowledge review is not a one-time task. A business should confirm the exact service descriptions, policies and visitor guidance it wants the concierge to use. This applies to routine questions as well as specialized requests such as checking spa aromatherapy options with Lumi, where the assistant’s answer should reflect the spa’s own current information instead of filling gaps with assumptions.

Multiple businesses can operate within a workspace subject to plan limits, and an account can have multiple workspaces. Merchants use the private workspace for knowledge management, conversations, leads, Customer Intelligence, Business Lumi, team management and billing. Subscriptions and trials are supported, with monthly AI credits and optional credit top-ups.

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

Across these competitive Southern California markets, service businesses and online stores often face visitors comparing several options before making contact. A responsive website conversation can answer location, availability, service and product questions while giving interested visitors a direct path to share their details or book a consultation. The first practical step is to review the public pages customers rely on most—especially service descriptions, coverage areas, policies and contact information. Once those details are accurate and organized, they can support consistent answers while staff remain responsible for follow-up, CRM entry and moving each inquiry forward.

Lumi is the website layer; the business remains responsible for the outcome

Lumi is a product in the OceSha ecosystem and is powered by OceSha. It is not a separate legal entity or seller; OceSha Inc. is the billing seller. 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. That relationship explains who stands behind the product without changing Lumi’s role on a customer’s website.

The right operating model is straightforward: let Customer Lumi handle immediate questions, inquiry collection and supported handoffs, then let staff apply judgment. Business teams remain responsible for checking source information, responding to leads, deciding whether to grant exceptions, tracking pipeline status and recording outcomes in their own systems. Lumi improves the continuity between a website visit and staff review; it does not replace ownership of the commercial relationship.

The bottom line