Lumi answers recurring prospect questions before your team has to email them again

Turn repeated email answers into approved website knowledge

Lumi is an AI Concierge that answers questions about your business on your website. Instead of asking a team member to locate an old email, rewrite the same explanation and send it again, you place the reusable information in Lumi’s knowledge system. Once that public knowledge is approved, Customer Lumi uses it to answer visitor questions through text and voice. This is the practical foundation for helping customers get reliable business answers without making your team the bottleneck.

Approval is the essential control. Text chat reads approved public knowledge and the business’s configuration; it does not produce answers before knowledge is approved. That makes the quality of your source material more important than the quantity. Start with the questions prospects genuinely repeat: what you offer, who it is for, what happens next and the public policies or details needed to make an informed inquiry.

What prospects can do without waiting for an email

A prospect can open Lumi on your website, choose an automatically generated starter question or write a question of their own. Suggested questions are multilingual and based on the available knowledge. Verified text chat supports 12 languages, giving visitors a direct route to approved information even when they would otherwise send an email in another language.

This is different from an automated email acknowledgment. An acknowledgment confirms that a message arrived; Lumi addresses the visitor’s actual question using controlled knowledge. Teams comparing those approaches can review email acknowledgments versus approved website answers before deciding where automation creates the most useful customer experience.

How to move your best recurring answers into Lumi

The strongest setup does not begin with technology. It begins by identifying the answers your team already gives repeatedly and deciding which version is accurate enough to publish. Treat the latest approved business information as the source, rather than relying on whichever employee email happens to be easiest to find.

Testing matters because the same fact can appear in several places and change over time. If you are preparing a larger website change, use a structured process for reviewing rewritten answers before a redesign launch. After content is imported again, recheck approved answers after website reimports so older material does not quietly displace information your team had already approved.

What your team receives when a prospect raises a hand

When a visitor submits Lumi’s in-chat form, the stored record includes name, email, company, phone and challenge. It also carries AI-derived context: goal, timeframe, intent, whether a meeting was requested, a recommended solution, an AI summary and a translation when the conversation is not in English. The transcript, language and source remain connected to the visitor and conversation.

Lumi can notify as many as five email addresses, using the recipient’s language. Optional SMS notifications are available for high-intent leads. In the private workspace, a Prospects list displays leads and meeting indicators, while conversations can be marked as test, spam, internal or irrelevant. This gives the team more context than a bare contact form submission and makes the original conversation available for follow-up.

Booking links help prospects continue, but clicks are not appointments

A business can set a scheduling URL from its chosen provider. When a visitor is ready, Lumi opens that link with attribution and records a booking-start event. This removes a common email step: your team does not need to reply merely to send the same scheduling link again.

Apply the same discipline to every contact detail Lumi provides. Phone numbers, booking URLs and other business information should be tested in each language you intend to support. A useful companion process is testing approved telephone numbers in multilingual answers, especially when several locations or teams use different contact details.

Use the conversation data to improve answers, not to invent outcomes

Lumi’s Customer Intelligence area includes an overview, funnel, insights, prospects and detailed analytics based on first-party data. Teams can inspect traffic performance, conversation activity, funnel behavior and diagnostics, then use what visitors actually ask to improve approved knowledge. This creates a useful operating loop: publish an approved answer, observe the questions around it, clarify the answer and review later conversations.

The analytics do not currently supply revenue or opportunity reporting because the required integrations do not exist. Checkout reference tagging on a connected SHOPLINE cart is experimental; it is not confirmation of an order or proof that Lumi generated revenue. Use the available data to understand conversations, inquiries and booking starts, while evaluating sales outcomes in the systems that actually record them.

For connected SHOPLINE stores, Lumi can use synchronized catalog information to answer product questions, help shoppers find products and manage the real store cart. It does not answer order questions; shoppers are directed to contact the store. If your use case involves service availability rather than products, distinguish approved business information from live operational data—for example, whether website answers can know a technician’s location.

Lumi is part of the OceSha ecosystem and is also the AI Concierge for OceSha.ai. It is built within OceSha Ventures and its AI-first solutions, which include course creation, branded academies, AI assistants and business intelligence for businesses and organizations. Lumi is a product rather than a separate legal entity; the billing seller is OceSha Inc., and the brand relationship is shown as “Powered by OceSha.”

The bottom line