No—you do not have to translate your whole website to answer customers in other languages

A multilingual concierge is an alternative to translating every page

Lumi is an AI Concierge for business websites. It adds text chat through a mini-card launcher, a floating interface or an embedded experience. When a visitor asks about the business, Customer Lumi responds from that business’s approved public knowledge. This makes it a practical part of a broader approach to helping customers get reliable business answers, especially when language would otherwise prevent a visitor from finding information already present on the site.

The distinction matters. A full translation project reproduces complete pages in another language, including navigation, calls to action and every passage on those pages. Lumi instead addresses the visitor’s immediate information need. A person can ask a question, receive an answer grounded in approved business content, and continue the conversation without searching through pages written in an unfamiliar language.

That does not make website translation obsolete. It gives businesses a more focused first step. Use Lumi as the AI Concierge for your website when the priority is answering questions across supported languages. Translate complete pages when the visitor needs the full page experience, exact localized wording or content that should be read in its original structure rather than summarized conversationally.

How Lumi turns an existing website into approved multilingual knowledge

Lumi’s website discovery process reads public website content and organizes what it finds into knowledge items. The discovery process can examine up to 25 pages. The resulting items are pending rather than immediately available for public answers, giving the business an approval step between website discovery and visitor-facing use.

Approval is the control point. Language support is useful only when the underlying answer is dependable. A polished response in another language is still a poor customer experience if it is based on an outdated fee, policy or service description. Businesses should therefore establish ownership for reviewing content before launch. The practical starting point is deciding how a business should review and approve knowledge before multilingual answers go live.

The same discipline applies when a website changes. A redesign can alter headings, rewrite service descriptions or remove context that made an earlier answer accurate. Before a new site launches, review rewritten website answers before a redesign rather than assuming the new wording carries exactly the same meaning. Lumi’s approved-knowledge approach makes that review explicit instead of automatically publishing every discovered statement.

What visitors can do in another language

Text chat is Lumi’s broadest multilingual channel. It has been verified in 12 languages and answers from approved public knowledge. Visitors can ask direct questions instead of navigating an unfamiliar site, and the conversation can continue with follow-up questions that use the same controlled information source.

Rich cards provide a more visual answer when the knowledge or connected catalog supports them. Public card images come from business-owned sources: the website, merchant uploads or a connected SHOPLINE store. Lumi does not generate images for these public cards. For connected SHOPLINE stores, synchronized catalog information can also support product answers and help shoppers find products.

A booking link is a handoff, not proof of a completed appointment. Lumi records a booking-start event when the scheduling URL opens. It knows whether the meeting was completed only where a calendar source is connected. If the distinction between a fast website response and a later staff response matters, compare immediate answers with next-day shared inbox replies and decide which questions should be handled instantly.

When full website translation is still the right choice

A conversational answer layer and a translated website solve different problems. Lumi is the better fit when visitors need fast answers to recurring questions and the business wants those answers restricted to reviewed information. Full translation is the stronger choice when people must read an entire page, compare every detail in a fixed layout, or rely on precise wording throughout a complete document or transaction.

The combined approach is often the most practical. A business can translate the pages that carry the greatest reading burden while using Lumi for questions that would otherwise require visitors to search multiple pages. This avoids treating every page as equally important and keeps the concierge focused on clear, approved responses.

Conversational comparison also has boundaries. Lumi can discuss information contained in approved knowledge, but comparison is conversational only; it is not a separate side-by-side comparison interface. Likewise, consistency needs active maintenance. Review approved website answers against chat responses when policy wording changes so the same business question does not produce conflicting guidance across channels.

Keeping multilingual answers accurate after your website changes

Multilingual access increases the number of visitors who can use your business information, but it also raises the importance of knowledge maintenance. If a fee, return condition, booking policy or service description changes, the approved answer should be reviewed. The source language and translated response both depend on the same underlying fact being current.

Website reimports should therefore be treated as review events rather than silent replacements. Teams need to distinguish a genuine source update from wording that is merely different. After a new import, recheck approved answers against the website so changed content does not leave an older answer active. When a correction was made intentionally, determine whether reimports preserve approved corrections before replacing the existing item.

Some questions also depend on information that is not present in static website content. A location-sensitive service question, for example, requires a reliable source for the relevant technician or service area information. Review whether plumbing website answers can know a technician’s location before promising that kind of real-time context. Multilingual output cannot compensate for missing operational data.

Where Lumi fits in your customer-response process

Lumi should handle the questions that can be answered confidently from approved public knowledge, then provide a sensible handoff where the visitor needs a person or an external action. It can capture a lead, send the details to staff by email and optional SMS, display the lead in the private workspace, or open the business’s booking URL.

Email acknowledgments and approved website answers have different jobs. An acknowledgment confirms that a message arrived; it does not necessarily resolve the visitor’s question. An approved concierge answer can provide the relevant business information immediately, while staff remain responsible for requests outside the available knowledge. Use the distinction between email acknowledgments and approved website answers to design a clear response path.

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.

If you are deciding which pages to translate, which knowledge to approve or how to structure the visitor handoff, contact the Lumi team to discuss your website. Start with the questions customers already struggle to answer, then decide whether each one requires a full translated page, an approved concierge response or direct staff involvement.

The bottom line