If your website redesign did not increase leads, inspect the inquiry journey—not the design again

Start with the inquiry journey, not another visual redesign

Lumi is the AI Concierge for a business website. It gives visitors text-based answers from that business’s approved public knowledge, presents relevant offering cards, captures inquiries and records first-party journey information. When a redesigned website still produces traffic without leads, the next task is to inspect how a visitor moves from a question to an answer, an inquiry and staff follow-up. That is the broader discipline covered in lead capture and inquiry management. A new layout can improve presentation, but it cannot compensate for missing answers, weak capture points or a follow-up process that loses context.

Begin by separating four questions: Are the right visitors arriving? Can they find reliable answers? Are they invited to identify themselves when their intent becomes clear? Does the team receive enough context to respond well? Lumi for your website addresses the middle of that journey by answering from approved knowledge, capturing leads and preserving the related conversation. It does not guarantee leads, appointments, sales, conversion rates, traffic or revenue; its value is making the visitor journey observable and actionable.

Check whether visitors can get specific, approved answers

A visitor who cannot resolve a practical question has little reason to submit an inquiry. Lumi’s website discovery reads up to 25 public pages and organizes the material into pending knowledge items for the business to review. The business approves what Customer Lumi uses, and the public concierge answers only from that approved knowledge. This creates a direct test after a redesign: does the new site actually contain the information visitors need, and has that information been reviewed for use in answers? Discovery needs an eligible trial, plan or company status and has been verified across six businesses.

Lumi also selects rich product or offering cards through references to approved knowledge or a connected catalog. Public card images come from business-owned sources: the website, merchant uploads or SHOPLINE. They are not AI-generated. Website photo matching uses a 0.8 confidence minimum and runs on a weekly rescan. The practical goal is not to make every page longer; it is to make accurate answers and relevant offerings easier to retrieve at the moment a visitor asks.

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 a product rather than a separate legal entity, and OceSha Inc. is its billing seller.

Inspect capture behavior and the context attached to every inquiry

Lumi’s lead form is optional for each business and works inside the conversation. It can collect the visitor’s contact identity, organization, telephone number and the challenge they want to solve. The resulting record is linked to the visitor and conversation rather than stored as an isolated form submission. It also carries the transcript, language and source, along with AI-derived fields covering the goal, timeframe, intent, whether a meeting was requested, a recommended solution and an AI summary. Non-English information can be translated.

Use this context to diagnose the redesigned site. If visitors ask substantial questions but rarely submit details, review where and how the optional form is offered. If submissions contain weak intent, compare them with the preceding transcript and landing page. If anonymous conversations reveal recurring needs, use a separate method for learning from anonymous inquiries without overstating follow-up leads. An anonymous question is useful demand intelligence, but it is not a contactable prospect.

Use first-party journey data to find the drop-off

Customer Intelligence combines Lumi interaction data with first-party website journey intelligence on sites where Lumi is installed. The website and widget contribute visitors, sessions, page views, source attribution and booking-start events. Lumi contributes conversations, messages, leads, voice use and AI analysis. The workspace includes Prospects, an analytics overview, detailed traffic and funnel diagnostics, and a Business Intelligence page.

Traffic attribution uses the first touch by default and groups sessions by broad source type, including advertising, tagged campaigns, search or other organic arrival, referrals, direct visits and sessions whose source cannot be determined. The journey data also includes UTM information, referrer origin and landing page. Use those dimensions to compare what different visitors do after arrival. A high-traffic page with few meaningful interactions requires a different response from a low-traffic page that produces detailed conversations.

Current Customer Intelligence is not unified with Google Analytics, CRM records or completed orders. Revenue and customer metrics remain unavailable without the relevant pipeline connection. For financial analysis, use verified revenue attribution when comparing inquiry sources rather than assigning revenue to a source from a conversation, lead or checkout reference alone.

Fix the staff workflow after an inquiry arrives

A functioning capture form can still produce disappointing results when no one owns the next action. Lumi sends lead notifications by email in the recipient’s language to as many as five addresses. Businesses can also enable SMS notifications for high-intent leads. Staff can review leads and conversations inside the private Lumi workspace, but they remain responsible for every follow-up action, status update and CRM entry.

There is currently no lead-status pipeline, assignment function, CSV export, generic outbound lead webhook or CRM handoff. No connector is implemented for HubSpot, Salesforce, Pipedrive or Zoho. If CRM connectivity is central to your process, plan how staff will transfer and track qualified inquiries before launch. The same principle applies to ownership: establish a daily routine for reviewing the workspace and notifications. Daily manual triage for website inquiries is especially important when named responders have not been assigned.

Correct contact information before outreach where necessary, then have staff review the change rather than silently assuming every submitted field is accurate. The process in reviewing corrected inquiry details before follow-up helps preserve human judgment. For teams handling overnight demand, prioritizing overnight inquiries before morning outreach provides a useful next workflow question.

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

Busy Southern California markets give customers plenty of service providers to compare online, so a polished redesign may not remove the friction that prevents an inquiry. Start by reviewing the full journey for visitors from Orange County, Los Angeles and San Diego: what source brought them in, which pages they viewed, what questions they asked and where they left. Then test the inquiry experience yourself on mobile. Confirm that useful answers appear before the visitor loses interest, the form is offered at a natural decision point and a specific staff member is responsible for prompt follow-up.

Distinguish commerce assistance from completed business outcomes

For a connected SHOPLINE store, Customer Lumi can answer with synchronized catalog information, help shoppers find products and manage the store’s real cart. Cart actions work only on the SHOPLINE storefront through the App Embed, not on a non-SHOPLINE website. The shopper’s browser creates and modifies the SHOPLINE storefront cart, and Lumi does not store the cart. Each action supports quantities from 1 through 20 and confirms the result by reading the cart back.

Discount values displayed by Lumi come directly from SHOPLINE’s cart response. Lumi does not calculate discounts, taxes, totals or shipping. Checkout uses a redirected store cart permalink rather than an embedded payment experience. SHOPLINE performs payment and order creation, and Lumi is not notified of the resulting order. That means cart activity and experimental checkout references are useful journey signals, but they cannot prove that revenue occurred.

This distinction also matters outside commerce. Handing someone a booking link is not the same as recording a completed meeting. A submitted inquiry is not a customer. Traffic is not demand until behavior supplies additional evidence. If your business needs to compare a messaging handoff with on-site capture, examine repair shop messaging handoffs versus website capture as an adjacent workflow. Retail teams should similarly separate after-hours inquiry capture from purchase processing.

The bottom line