When an interested visitor does not book, Lumi gives your team a practical follow-up record: contact details submitted through the in-chat form, the conversation transcript, language, source, stated goal, timeframe, intent, meeting request and an AI-generated summary. Your team then follows up directly. A booking-link click is recorded as a booking start, not a completed appointment, so check for a confirmed meeting before referring to a booking.
- Lumi captures submitted contact details and links each lead to the visitor and conversation that produced it.
- The lead record includes the transcript, language, source and AI-derived context such as goal, timeframe and intent.
- Interested visitors can receive a scheduling link, but opening it records only a booking-start event.
- Follow-up, status tracking and CRM entry are currently manual responsibilities for your team.
- Lead notifications can be emailed in the recipient’s language to as many as five addresses, with optional SMS for high-intent leads.
What Lumi records when an interested visitor does not book
Lumi, the AI Concierge for your website handles the first part of this process while a visitor is still engaged. Customer Lumi works as a text assistant in a chat, mini-card launcher, floating placement or embedded placement. It answers from the business’s approved public knowledge, captures leads and can hand visitors a scheduling link. This keeps the initial conversation available even when the visitor leaves without completing a booking.
The in-chat form records the visitor’s submitted name, email, company, phone number and challenge. Lumi also stores AI-derived fields including the visitor’s goal, timeframe, intent, whether a meeting was requested, the recommended solution and an AI summary. The record includes the transcript, language and source, and it is connected to the corresponding visitor and conversation.
That context is the main advantage over following up from an isolated email address or phone number. Your team can see what the visitor asked, what outcome they described and whether they requested a meeting before making contact. For a wider view of how the concierge supports visitors outside staffed hours, see how to answer website visitors after hours.
A practical follow-up process for visitors who showed interest
The right follow-up starts by separating genuine inquiries from incomplete or irrelevant conversations. Lumi’s Prospects list displays leads and meeting chips, while conversations can be marked as test, spam, internal or irrelevant. Review that context before contacting anyone so staff time goes toward actual prospects.
- Open the prospect record and review the submitted contact details, transcript, language, source and AI summary.
- Check the visitor’s goal, timeframe, intent and whether the record says a meeting was requested.
- Look for a confirmed meeting before assuming the scheduling process was completed. A booking-start event records that the visitor opened the scheduling link; it does not confirm an appointment.
- Use the conversation’s language and stated challenge to write a relevant response rather than sending a generic booking reminder.
- Contact the prospect manually, then maintain any follow-up status and enter the record into your CRM if that is part of your process.
This division of work matters when comparing automated assistance with human coverage. Website assistance versus morning replies is the useful next question for solo service providers deciding how quickly a person should take over from the concierge.
How booking activity should guide your follow-up
A business can configure a scheduling URL from a provider such as Calendly. Lumi opens that URL with attribution and records a booking_started event. Treat this event as evidence that the visitor began the scheduling process—not as proof that the visitor completed it. Your follow-up language should say that the visitor explored or started booking, rather than stating that they missed or canceled an appointment.
Confirmed appointments appear only when a supported calendar source is active. A signature-verified Calendly webhook can record created and canceled invitees as meetings, and a Google Calendar connector can read real meetings. These components came from the earlier OceSha Ventures system, and current self-service setup for new Lumi merchants has not been verified. If confirmed calendar reporting matters to your workflow, ask whether the calendar service you use is supported for your business.
The same distinction is valuable when deciding between concierge coverage and live staff chat. Website assistance compared with staff chat frames that choice for solo retailers, while holiday assistance for hours and pickup questions considers a period when inquiry volume and customer expectations may differ.
What your team receives—and what remains manual
Information available for follow-up
Lead notifications can be emailed in the recipient’s language to as many as five addresses. Optional SMS notifications are available for high-intent leads. These alerts help the right people notice an inquiry, but the subsequent outreach remains a staff task.
Customer Intelligence combines Lumi interaction information with first-party website journey information on sites where Lumi is installed. Its current sources include conversations, messages, leads, voice use, AI analysis, visitors, sessions, page views, attribution and booking-start events. It is not unified with Google Analytics, CRM or order data. To understand why these records represent engaged prospects rather than every person who visited the site, read why Lumi prospects differ from all website visitors.
Use language and source context to make follow-up more relevant
Lumi records the lead’s language and can provide a translated AI summary when the conversation is not in English. Notification emails are sent in the recipient’s language. These details give your team a clear starting point: review the original transcript and translated context, then respond in the language appropriate for that prospect.
Language support is especially important when a business serves visitors who do not all ask questions in the same language. Evaluating multilingual assistance for seasonal tourism visitors explores that broader service decision. For teams testing how language affects actual outreach, mixed-language follow-ups about garage services provides a closely related scenario.
Source and journey information can also improve the relevance of the response. Lumi’s first-party tracking records an anonymous visitor and session, page path, UTM information, referrer origin and language. It does not record device, browser, geography or page title. Use the available journey context to understand where the inquiry began, but base the message primarily on what the visitor actually said and submitted.
For businesses in Orange County, Los Angeles and San Diego, CA
In these busy Southern California markets, service businesses often compete for visitors who compare several options online before choosing one. When someone asks detailed questions or starts scheduling without confirming an appointment, timely, relevant outreach can keep the conversation moving. First, review the submitted contact details, transcript, source, language, stated goal, timeframe and AI-generated summary. Check whether a meeting was confirmed, then contact the prospect directly using language that reflects their inquiry. Refer to a booking-link click only as starting or exploring the scheduling process.
Set up Lumi to capture better follow-up context
Useful follow-up begins with accurate source material. Lumi’s website discovery reads up to 25 public pages and organizes what it finds into pending knowledge items for merchant approval. This process has been verified across six businesses. Once the relevant public information is reviewed, Customer Lumi answers from the business’s public knowledge rather than improvising unsupported details.
Rich cards can present products or offerings selected through references in the knowledge or connected catalog. Images in public cards come only from the business’s website, merchant uploads or SHOPLINE; they are not AI-generated. Website photo matching uses a 0.8 minimum confidence threshold and performs a weekly rescan. These capabilities help visitors understand an offering before they submit an inquiry.
A connected SHOPLINE store adds synchronized catalog information for product answers. On the SHOPLINE storefront, Lumi can help shoppers find products and modify the store’s own cart, but SHOPLINE handles checkout, payment and order creation. Lumi receives commerce, cart and checkout-reference events but no orders. That means a checkout reference is not confirmed revenue or proof of an order.
Questions that are absent from the business’s source material need a deliberate response. Handling undocumented assembly-service questions illustrates why missing service information should be resolved before it shapes follow-up. Policy-sensitive requests also require care; who can request a gift voucher transfer addresses a related case where the business’s own rules need to guide the answer.
Lumi is part of the OceSha ecosystem and is 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. Lumi is a product rather than a separate legal entity, and OceSha Inc. is its billing seller.
Lumi identifies interested visitors, records their inquiry and booking intent, and gives your team the context needed for a relevant manual follow-up.
Plan your visitor follow-up workflowFrequently asked questions
Does Lumi automatically contact a visitor after they leave?
The current workflow captures the lead and sends notifications to your team. Staff then perform the follow-up manually. Optional SMS is for notifying the business about high-intent leads, not a stated automated prospect-nurture sequence.
What contact information can the in-chat form collect?
The form stores the visitor’s submitted name, email, company, phone number and challenge. The record also includes AI-derived intent context, the transcript, language and source.
Can Lumi tell whether a visitor completed a booking?
Lumi records when a visitor opens the configured scheduling URL. A completed appointment appears only where an active calendar source records a real meeting. A booking-start event alone is not a confirmed appointment.
Does Lumi assign leads to team members?
No current lead-assignment workflow is stated. The Prospects list organizes leads and meeting chips, but staff handle assignment, follow-up and status tracking through their own process.
Can I export leads to a CRM or CSV file?
Lumi currently has no CRM handoff, export or CSV function. Your team must enter information into its CRM manually. Confirm a specific connector before relying on CRM connectivity.
Does Customer Intelligence include order and revenue data?
No. Customer Intelligence currently uses Lumi interactions and first-party website journey information. Connected SHOPLINE activity can provide cart and checkout-reference events, but Lumi receives no orders and does not provide verified revenue attribution.
The bottom line
Lumi solves the information gap between website interest and human follow-up. It captures submitted contact details, the full conversation, language, source and structured intent context, then alerts your team so it can respond with relevance. The crucial discipline is to distinguish booking interest from a confirmed appointment: opening a scheduling link records a start, not a completion. Use Lumi to preserve and organize the visitor’s context, but plan for staff to handle outreach, lead status and CRM entry manually. That combination creates a clear, honest follow-up process without losing what the visitor already told you.
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.
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
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).