There is no single verified minute or hour at which every website lead goes cold. The practical standard is to engage visitors while they are still on your site, collect enough context for a useful handoff and alert staff without waiting for someone to check an inbox manually. Lumi does this in chat, then emails the captured inquiry to designated recipients. Your staff must still complete all follow-up, qualification, status tracking and CRM entry.
- Do not build your response process around a universal lead-expiry deadline; no single threshold applies to every inquiry or business.
- Lumi engages visitors during the active website session using text chat, with voice output also available.
- The optional lead form captures name, email, company, phone and the visitor’s challenge, together with conversation context.
- Lead notifications can go by email to as many as five addresses; high-intent SMS is optional when a provider is configured.
- Lumi does not provide a lead pipeline, assignment, export or CRM handoff, so staff must own the follow-up workflow.
The right response time starts during the website visit
That distinction matters because “response” can mean two different things. The first is an in-session response to the visitor’s question. The second is a later human reply from sales, service or another responsible team. A strong lead capture and inquiry management process addresses both: it helps the visitor now and creates a clear handoff for staff afterward.
Lumi, the AI Concierge for your website handles the first part through a floating, embedded or mini-card text experience, with voice output available. It answers from the business’s reviewed public information rather than improvising outside that source material. When lead capture is enabled, it can gather contact details and the visitor’s challenge inside the conversation.
Lumi acknowledges interest and captures context before the visitor leaves
Customer Lumi is a website chat and voice assistant. It can answer questions using material the business has reviewed for public use, present relevant product or offering cards and invite the visitor to submit an inquiry. Lead capture is optional for each business, so it can be enabled where an explicit handoff is useful rather than appearing in every interaction.
What the inquiry record contains
This context makes the morning review of an overnight inquiry more useful, but accuracy still matters. If a visitor later corrects a phone number, company name or other detail, use a process for reviewing corrected inquiry details before follow-up rather than relying on the first version that appeared in the conversation.
Notifications shorten the gap, but staff still own the reply
When a visitor submits the lead form, Lumi stores the inquiry and supports email notification to as many as five addresses. The email is sent in the recipient’s language. Optional SMS can be used for high-intent leads when an SMS provider has been configured. The lead also appears in the private Lumi workspace, where a Prospects list can show meeting chips.
- Let Lumi answer eligible public questions during the active website session.
- Use the optional in-chat form to collect contact details and the visitor’s challenge.
- Route the notification to staff who are responsible for reviewing new inquiries.
- Check the transcript, AI summary, goal, timeframe and meeting-request context before responding.
- Have a staff member complete the reply, qualification, status tracking and any CRM entry.
The team should also check whether an overnight inquiry was withdrawn or changed before starting outreach. A simple overnight withdrawal review before morning contact helps prevent a fast response from becoming an unwanted one. Speed matters, but acting on the latest available intent matters more.
For regulated or sensitive inquiry journeys, test the full acknowledgment experience before launch. That includes what the visitor sees, what information is collected and what reaches staff. The same principle is covered in testing after-hours financial inquiry acknowledgments. Lumi supplies interaction and website-journey intelligence; it does not turn an automated acknowledgment into professional advice from the business.
Do not confuse inquiry capture with booking, purchase or revenue
An inquiry, booking start, cart action, checkout reference and completed transaction are different events. Keeping those distinctions intact prevents teams from reporting engagement as an outcome that has not occurred. For example, a booking-start event is not a completed or confirmed appointment.
What each event means
Connected SHOPLINE stores can use synchronized catalog information for product answers. On the SHOPLINE storefront, Lumi can help shoppers find products and modify the real storefront cart, with quantities from one to 20 per action and every change checked by reading the cart back. Lumi stores no cart, does not calculate discounts, taxes, totals or shipping, and redirects checkout to SHOPLINE. The boundary between retail inquiry capture and purchase processing should therefore remain explicit.
The same caution applies to reporting. Customer Intelligence currently combines Lumi interaction data with first-party website journey data where Lumi is installed. It is not unified with Google Analytics, CRM records or orders. If revenue measurement is important, distinguish engagement data from verified revenue attribution across inquiry sources.
Your follow-up process must account for Lumi’s current workflow boundaries
Lumi records conversations and leads, sends notifications and presents prospects in the workspace. It does not currently provide a lead-status pipeline, assignment, CSV export, generic outbound lead webhook or CRM handoff. HubSpot, Salesforce, Pipedrive and Zoho are not implemented, and there is no contact, activity, notes or bidirectional synchronization with those systems.
Businesses with detailed inquiry requirements should decide what Lumi can answer publicly and what needs human review. Catering is a good example: published minimums, lead times and submission requirements can shape whether an inquiry is ready for follow-up. A structured approach to published catering requirements and inquiry readiness helps keep the initial conversation aligned with the information the business has actually made available.
Some sectors also require an external approval before work can proceed. For property-related service requests, for example, the next operational question may be whether landlord permission is needed before a repair inquiry. Lumi can communicate information supplied and reviewed by the business, while staff remain responsible for handling case-specific decisions.
For businesses in Orange County, Los Angeles and San Diego, CA
Busy Southern California markets give customers many nearby providers to compare online, especially across home services, professional services, healthcare, hospitality and retail. An inquiry can lose momentum when a visitor receives no useful guidance and the message remains unread in a shared inbox. The first practical step is to review the path from website question to staff notification. Make sure visitors can share their needs while they are still engaged, then route that context to designated employees who can respond promptly, verify any updated details and continue the conversation.
Use the concierge response to protect the opportunity, not to replace your team
The best use of an AI concierge is not to pretend every inquiry has already received a complete human response. It is to prevent silence while the visitor is actively seeking help, answer eligible questions consistently and create a richer record for the people who will take over. That is especially valuable after hours, when an unanswered website form otherwise provides no assistance beyond confirmation that it was submitted.
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 itself is an AI Concierge rather than a separate legal entity; OceSha Inc. is its billing seller.
Before launch, review the website material Lumi will use. Website discovery reads up to 25 pages and organizes the findings into pending knowledge items for approval. Public rich cards use business-owned images from the website, merchant uploads or a connected SHOPLINE source; they do not use AI-generated images. This review step makes the first response more useful because the concierge is grounded in material the business has selected for visitors.
If you need to map notifications, after-hours coverage or staff responsibilities, talk to the Lumi team about your inquiry workflow. The goal should be simple: give visitors relevant help during the session, preserve their context and make the human next step unmistakable.
Lumi handles the first response during the website visit by answering approved questions, capturing inquiry details and notifying staff, but your team remains responsible for personal follow-up.
Plan your after-hours responseFrequently asked questions
Does Lumi follow up with the lead automatically after the inquiry?
Lumi captures the inquiry and can notify staff by email, with optional high-intent SMS when a provider is configured. Staff must perform all subsequent follow-up.
Can Lumi send a lead directly into our CRM?
No current CRM provider is implemented. There is no CRM OAuth, contact sync, activity sync, outbound lead webhook, export or bidirectional synchronization. Staff must enter the lead into their CRM manually.
How many people can receive a lead notification?
Lead notification emails can be sent to up to five addresses. The lead also appears in the private Lumi workspace.
What information does Lumi collect from an inquiry?
The optional in-chat form stores name, email, company, phone and the visitor’s challenge. The record can also include goal, timeframe, intent, meeting interest, an AI summary, transcript, language and source.
Does a meeting request mean an appointment is confirmed?
No. A meeting request or booking-start event indicates interest or activity, not a completed or confirmed appointment. Confirmation depends on the connected booking process where one is active.
Can Lumi answer product questions after hours?
Yes. Lumi answers from information reviewed by the business. With a connected SHOPLINE store, it can use synchronized catalog data to help shoppers find products; cart actions are available only on the SHOPLINE storefront.
The bottom line
Do not wait for a universal “lead goes cold” deadline; none is reliable for every website inquiry. The stronger operating standard is to respond within the active visit whenever possible, capture the visitor’s need and notify the responsible people with enough context to act. Lumi provides that first layer through website chat, optional voice, lead capture and email notifications to as many as five recipients. It does not replace the team behind the business: staff still handle follow-up, qualification, pipeline updates and CRM entry. Use Lumi to eliminate unattended silence, then make human ownership explicit.
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).