LumiLumi
Lead capture and inquiry management

Your marketing brings visitors; enough leads require a better inquiry path

SEO, ads and social media create opportunities to be discovered, but your website still needs to answer questions, capture intent and give your team useful follow-up context.

Small-business owner reviewing customer conversations on a laptop
5Maximum email notification recipients
2Visitor interaction formats: chat and voice
100 creditsTested optional top-up quantity
$12Tested price for that top-up
Quick answer

You may not have a traffic problem. SEO, ads and social media bring people to your website, but visitors can still leave when answers are hard to find or the next step feels unclear. Lumi is an AI Concierge that answers from your approved public information, captures inquiries in conversation and records context for follow-up. It strengthens the path from visit to inquiry; it does not guarantee leads, appointments, sales or revenue.

Key takeaways
  • Traffic acquisition and lead capture are different jobs: marketing attracts visits, while the website must turn visitor interest into a clear inquiry.
  • Lumi answers website questions using the public information your business has approved and can present an optional lead form within the conversation.
  • Captured inquiries include contact details, the conversation transcript, source and AI-derived context such as intent, goal, timeframe and meeting interest.
  • Your team receives inquiries by email, with optional SMS for high-intent leads, and manages them from Lumi’s private workspace.
  • Follow-up, pipeline status, assignment and CRM entry remain manual because Lumi does not currently provide CRM handoff or a lead-status pipeline.
01

Why more visibility has not automatically produced more leads

Lumi is an AI Concierge for business websites. It addresses the on-site portion of this problem by answering through chat and voice from information the business has approved for public use. It can also capture an inquiry within the conversation and hand the visitor a booking link. That makes Lumi part of lead capture and inquiry management, rather than another traffic-acquisition channel.

This distinction matters when marketing activity is already generating visits but inquiry volume remains disappointing. Sending more people into the same unclear experience can increase traffic without fixing what happens after arrival. Before adding another campaign, examine whether visitors can ask a specific question, receive a grounded answer and take an obvious next step without searching through multiple pages.

02

What Lumi changes on the website

After Lumi is added to a website, Customer Lumi becomes the visitor-facing chat and voice assistant. Its answers are constrained to public material the business has selected for use. This is important: the concierge is there to explain the business’s own information, not to improvise policies, fees, products or services that the business has not supplied.

The visitor-facing path

QuestionsVisitors can ask about the business instead of relying only on menus, page structure or search.
AnswersCustomer Lumi responds from the organization’s selected public material.
Inquiry captureAn optional in-chat form collects the visitor’s name, email address, company, phone number and stated challenge.
Booking directionLumi can provide a booking link when that is the appropriate next step.
Commerce assistanceWith a connected SHOPLINE store, Lumi uses synchronized catalog information to help shoppers find products and manage the store’s real cart.

The result is a more direct path from curiosity to declared intent. A visitor who is not ready to complete a form immediately can begin with a question. If the exchange develops into an inquiry, the form is already inside the conversation rather than disconnected from it. This does not promise a particular conversion rate, but it removes avoidable friction between finding the site and telling the business what help is needed.

03

What your team receives when a visitor becomes an inquiry

Lumi preserves more than a bare form submission. The lead record contains the submitted contact information and is linked to the relevant visitor and conversation. It also carries the transcript, language and source, helping staff understand where the inquiry came from and what was discussed before outreach begins.

Recorded inquiry context

Submitted detailsName, email address, company, phone number and challenge.
Conversation evidenceThe transcript and its connection to the visitor and session.
Source contextThe source and language associated with the inquiry.
AI-derived contextGoal, timeframe, intent, whether a meeting was requested, a recommended solution and an AI summary.
Language supportAI-derived content can be translated when the original inquiry is not in English.

Notifications can be emailed in the recipient’s language to as many as five addresses. Businesses can also enable SMS notifications for high-intent leads. Inside the private workspace, the Prospects list displays leads and meeting chips, while conversations can be marked as test, spam, internal or irrelevant. Those controls help teams separate actionable inquiries from records that should not enter follow-up work.

Anonymous conversations still contain useful signals even when a visitor does not submit the form. Keep that learning separate from the count of people your team can actually contact. The practical method is explained in learning from anonymous inquiries without inflating lead totals.

04

Where the process still depends on your team

Lumi captures and organizes inquiry context, but it is not a complete sales pipeline. Staff remain responsible for outreach, status tracking and entering records into any CRM they use. There is currently no lead assignment, lead-status pipeline, CSV export, generic outbound lead webhook or automated CRM handoff.

Booking activity also needs precise interpretation. A booking-start event indicates that someone began that path; it is not proof of a completed or confirmed appointment. Meetings appear only where the relevant booking or calendar connection supplies them. Teams should therefore distinguish an inquiry, a booking start and an actual meeting instead of reporting all three as the same outcome.

The same discipline applies to commerce and revenue. Connected SHOPLINE stores can provide commerce and cart events plus checkout references, but Lumi does not receive orders from SHOPLINE. Checkout reference tagging on the cart is limited and experimental, so it should not be presented as confirmed order or revenue attribution. Use verified revenue attribution for financial inquiries as a framework for separating measurable inquiry sources from confirmed business outcomes.

05

How to diagnose a lead shortage before buying more traffic

  1. Check acquisition separately from inquiry capture. Use available traffic information such as visitors, sessions, page views and attribution to determine whether people are arriving before concluding that the marketing channel has failed.
  2. Review the questions people ask. Conversations can reveal what visitors need clarified, including repeated areas of uncertainty that static pages may not resolve efficiently.
  3. Inspect the inquiry path. Confirm that the optional form is enabled where appropriate and that visitors have a clear transition from receiving an answer to sharing their details.
  4. Audit notification coverage. Decide which staff should receive inquiry emails, up to five addresses, and whether optional SMS for high-intent leads belongs in the workflow.
  5. Define daily ownership. Because assignment, pipeline status and CRM entry are manual, specify who reviews the Prospects list, who follows up and where the outcome is recorded.
  6. Separate signals from outcomes. Keep conversations, leads, booking starts, meetings, checkout references, orders and revenue as distinct measures. Do not treat an early action as proof of a later result.

Different industries may need different operating routines even though the core discipline is the same. A retailer needs to distinguish after-hours questions from actual purchase processing; after-hours retail inquiry capture versus purchase processing addresses that boundary. Appointment-based practices need an explicit owner for each request, as shown in clarifying follow-up for dental appointment inquiries. Service teams facing overnight demand can use prioritizing salon inquiries before morning outreach to think through the order of response.

This review prevents a common mistake: diagnosing every lead shortage as a reach problem. If visitors are arriving but not identifying themselves, the website experience and response process deserve attention before traffic budgets rise. If few visitors are arriving, acquisition may still need work. The two conditions require different remedies and should not be blended into one headline number.

06

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

In these busy Southern California markets, service businesses often compete for customers who compare several options online before making contact. Strong search visibility, paid campaigns and social activity may bring steady website visits, yet unclear service details, pricing expectations or next steps can interrupt the path to inquiry. Start by reviewing the questions prospects ask most often, then confirm that each answer is easy to find and approved for public use. This gives Lumi reliable information for immediate conversations while creating a clearer route from initial interest to a well-documented inquiry.

07

What Lumi measures—and what it does not prove

Lumi’s private workspace brings together knowledge management, conversations, leads, team management, billing and first-party analytics called Customer Intelligence. Available views include Prospects, an analytics overview, detailed analytics covering traffic performance, funnel information and diagnostics, and a Business Intelligence page. Data can come from Lumi conversations, messages, leads, voice use and AI analysis, as well as website visitors, sessions, page views, attribution and booking-start events.

Read each measure at its proper level

ConversationEvidence that a visitor interacted with the concierge, not necessarily that contact details were supplied.
LeadA captured inquiry linked to a visitor and conversation, not a promise that the person will buy or book.
Booking startEvidence that the booking path began, not confirmation of an appointment.
MeetingA meeting record received where the supported booking or calendar connection provides one.
Checkout referenceA limited cart-side reference, not a confirmed order or verified revenue attribution.
RevenueUnavailable without an implemented CRM or pipeline connection that can verify it.

This measurement discipline protects decision quality. Metrics labeled opportunities, customers and revenue exist conceptually in the workspace but remain unavailable because they require a CRM or pipeline integration. Reporting should therefore stop at the strongest evidence actually received. That gives the team an honest view of visitor behavior and inquiries without turning intent signals into unsupported commercial results.

Lumi is part of the OceSha ecosystem and is also the AI Concierge for OceSha.ai. It is a product rather than a separate legal entity or seller; billing is through OceSha Inc., and the product relationship is shown as Powered by OceSha. 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.

SEO, ads and social media create opportunities to be discovered, but your website still needs to answer questions, capture intent and give your team useful follow-up context.

Evaluate your inquiry path

Frequently asked questions

Does Lumi replace SEO, advertising or social media?

No. Those channels help people discover the website. Lumi works on the website as a chat and voice concierge, answering questions from selected public information and capturing inquiries when visitors choose to provide their details.

Can Lumi guarantee more leads from my existing traffic?

No. Lumi can reduce friction by answering questions, presenting an optional in-chat form and preserving inquiry context, but it does not guarantee leads, appointments, sales, conversion rates, traffic or revenue.

Where do captured leads go?

Leads appear in the Lumi workspace and can be sent by email to as many as five recipient addresses. Optional SMS notifications are available for high-intent leads. Staff must handle follow-up, status tracking and CRM entry manually.

Does Lumi connect directly to my CRM?

No CRM provider is currently implemented. There is no CRM contact sync, activity or notes sync, bidirectional sync, CRM webhook, generic outbound lead webhook, export or CSV. Evaluate the manual process if CRM connectivity is central to your operation.

Can Lumi tell us which inquiries produced revenue?

Not currently. Lumi records first-party website and conversation activity, but verified revenue attribution requires an implemented CRM or pipeline connection. SHOPLINE data includes commerce and cart events and checkout references, but not orders.

How is Lumi purchased?

Lumi supports subscriptions and trials. Subscription plans include monthly AI credits, with optional credit top-ups. A tested top-up is 100 credits for $12. Billing is sold by OceSha Inc. because Lumi is a product, not a separate legal seller.

The bottom line

SEO, ads and social media solve discovery, not the entire lead journey. If visitors arrive but leave without identifying themselves, buying more traffic repeats the same weakness at greater scale. Fix the on-site inquiry path first: answer real questions, make contact capture part of the conversation, preserve the transcript and assign clear responsibility for follow-up. Lumi provides that website concierge and inquiry context. Your team still owns outreach, CRM entry and outcome tracking, so pair the technology with a disciplined daily process rather than expecting automation alone to produce leads.

Rohan Hall headshot
About the author

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.

Who stands behind this

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

  1. Lumi — lovelumi.ai
  2. OceSha Ventures — ocesha.com
  3. Rohan Hall — rohanhall.com

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).