Small businesses use Lumi to answer website questions and capture qualified lead context in the conversation

AI lead capture begins with a useful website conversation

For small and mid-sized businesses, the useful tool is not simply a chatbot that produces generic text. It is a concierge connected to the business’s own information, able to recognize an inquiry and preserve enough context for a person to continue it. Lumi’s website concierge capabilities cover chat and voice answers, optional in-conversation lead collection, booking-link handoff, conversation records and first-party analytics.

Lumi answers only from the individual business’s public knowledge. Website discovery reads as many as 25 public pages and organizes the material into knowledge items. The business manages that material and its conversations from a private workspace. This approach keeps the interaction focused on what the business actually publishes rather than relying on broad, unrelated answers.

That makes lead capture part of a wider question about which businesses and audiences Lumi fits. The strongest use case is a business whose visitors arrive with questions that can be answered from its website information, then need a clear route to identify themselves, request contact or move toward booking. The tool supports that journey, but the business still owns its claims, policies, service details and human response.

What Lumi records when a visitor becomes a lead

Lumi’s optional in-chat form captures five direct fields: name, email, company, phone and the visitor’s challenge. The resulting record is linked to the visitor and the full conversation. This gives staff both contact information and the exchange that led to the inquiry, instead of leaving them with a bare email address and no explanation.

The lead notification is sent by email in the recipient’s language to as many as five addresses. A business may also use optional SMS for high-intent leads. Inside the workspace, a Prospects list displays leads and meeting chips, while conversations can be marked as test, spam, internal or irrelevant. Those controls help staff separate genuine inquiries from records that should not enter their sales work.

How the lead-capture workflow works from visit to follow-up

The handoff matters as much as the initial collection. Lumi stores structured information and gives staff the preceding conversation, but it does not replace the business’s sales process. A prompt human response, a clear owner for each inquiry and a consistent method for recording outcomes remain essential. When the inquiry involves details that need professional review, the transcript gives the responsible person a starting point rather than an automatic final decision.

For example, after a business acquisition, staff may need to confirm that responses still match the new owner’s services and policies. The process for reviewing Lumi answers after buying a dental practice illustrates why knowledge review and operational ownership should accompany automated capture.

Booking links and commerce tools support the next step

Lead capture works best when the visitor receives an appropriate next action. Lumi can hand a visitor a booking link. Treat that handoff accurately: a booking-start event means the visitor began the booking path, not that an appointment was completed or confirmed. Calendar support can vary by business, so confirm the setup for the booking service the business uses before relying on it.

For online stores, a connected SHOPLINE service adds a different set of tools. Lumi uses synchronized catalog information to search products conversationally, choose variants and show items. It can also manage the visitor’s real store cart on the SHOPLINE storefront. There is no dedicated product-comparison tool; comparisons happen conversationally. Cart actions work only on the SHOPLINE storefront, and checkout redirects rather than appearing as an embedded checkout.

These commerce interactions help a shopper move from a question toward a product or cart action, but they should not be reported as completed revenue. Lumi receives cart events and checkout references from SHOPLINE, not order data. Checkout reference tagging is experimental and is not confirmed order or revenue attribution. For policy questions, businesses should also separate published rules from requests requiring individual judgment; triaging e-commerce policies and exception requests explains that distinction.

Customer Intelligence shows how inquiries developed

Lumi receives first-party data from its conversations, messages, leads, voice use and AI analysis. The website widget contributes visitor, session, page-view, attribution and booking-start information. The workspace presents this through Prospects, an analytics overview, detailed analytics for traffic performance, funnel and diagnostics, and a Business Intelligence page.

This information helps a small business examine which conversations produced inquiries, what visitors asked and where the interaction began. The connection among visitor, session, conversation and lead is particularly useful because it preserves the path around the submitted form. Staff can use the record to identify gaps in website information, understand recurring questions and improve how they respond.

Interpret the metrics according to the data Lumi actually receives. Device, browser, geography and page-title capture are not available. The system defines metrics for opportunities, customers and revenue, but those metrics remain unavailable without a CRM or pipeline connection. A booking-start event is not a completed meeting, and a checkout reference is not an order. If a visitor is overseas, clarifying callback time zones before responding is a sensible human step because geography is not captured.

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

In these busy Southern California markets, service businesses often compete for visitors who are comparing several options online before making contact. An AI concierge can answer common questions in the moment, gather the visitor’s contact details and challenge, and preserve the conversation for staff follow-up. The first practical step is to review the public website information Lumi will use, especially services, service areas, hours and next steps. Then assign one person to monitor notifications and respond promptly, using the inquiry summary and transcript to continue the conversation with relevant context.

Where Lumi stops and the business’s follow-up tools begin

Lumi currently has no implemented CRM provider. That includes HubSpot, Salesforce, Pipedrive and Zoho. There is no CRM authorization, contact synchronization, activity or note synchronization, bidirectional sync, CRM webhook, generic outbound lead webhook, export or CSV. Leads reach staff through the Lumi workspace and email, with optional SMS for high-intent inquiries.

There are additional operating boundaries to account for. Lumi supports 12 languages and one voice per business. Voice transcription accepts WAV files only, and PDF ingestion is not available. These constraints should shape the knowledge and media a business prepares: keep source information on accessible public web pages, use supported voice inputs and arrange a separate process for documents that exist only as PDFs.

Lumi is a product in the OceSha ecosystem, not a separate legal entity. It is powered by OceSha, and OceSha Inc. is the billing seller. Readers who need the commercial context can review why Lumi billing names OceSha Inc.. Lumi 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.

When evaluating any AI tool, published safeguards or operational claims should be read precisely rather than expanded into assumptions. The same evidence-led method appears in evaluating published safeguards without assuming certifications. For questions about setup, business fit or supported connections, contact the Lumi team and describe the website, booking process, commerce platform and follow-up system you use.

The bottom line