LumiLumi
Lead Capture and Inquiry Management

Your agency and sales team can both be right: traffic quality and lead quality are different questions

Lumi connects first-touch website attribution with visitor journeys, AI-enriched inquiries and conversation records so you can diagnose where the gap begins.

Small-business owner reviewing customer conversations on a laptop
6Traffic source classifications
5In-chat lead form fields
Up to 5Lead notification email addresses
First-touchDefault attribution model
Quick answer

“Great traffic” does not prove that inquiries are qualified, and “terrible leads” does not prove that the ads are failing. Lumi shows how visitors arrived, what pages they viewed, what they asked and which inquiries they submitted. Compare those signals in sequence. The evidence can reveal whether the problem lies in traffic sources, campaign-to-page alignment, visitor expectations, inquiry capture or follow-up—but confirmed customers and revenue require data beyond Lumi’s current first-party records.

Key takeaways
  • Judge traffic and lead quality separately before deciding whether the agency or sales team is right.
  • Lumi classifies traffic as paid/campaign, organic, referral, direct or unknown using first-touch attribution by default.
  • Each captured inquiry can include contact details, source, transcript, language, intent, goal, timeframe, meeting request and an AI summary.
  • Conversations can be marked as test, spam, internal or irrelevant so they do not distort the assessment of genuine demand.
  • Lumi does not currently connect ad spend, CRM pipeline status, orders or verified revenue to inquiries, so those claims require a separate comparison with business records.
01

Why both teams can be telling the truth

Lumi is an AI Concierge for a business’s website. It records first-party visitor journeys and connects them with conversations and captured inquiries, helping the business distinguish traffic activity from genuine buyer intent. That distinction is central to Lead Capture and Inquiry Management: an agency may accurately report that paid or campaign traffic reached the site, while sales may accurately report that the resulting inquiries lack fit, urgency or a clear buying goal.

The disagreement usually comes from each team measuring a different stage. Traffic reporting concerns visitors, sessions, page views, landing pages, referrer origins and campaign parameters. Sales feedback concerns the people who identify themselves, the challenges they describe and whether those inquiries deserve follow-up. Neither dataset independently proves completed sales. The useful question is not “Which team should we believe?” It is “At what point does the evidence weaken?”

02

Start with what Lumi can establish about traffic

Lumi, the AI Concierge for your website records first-party website activity including visitors, sessions, page views, UTM data, referrer origin and landing page. Its attribution logic classifies traffic as paid/campaign, organic, referral, direct or unknown. Attribution uses a first-touch default, so the recorded source represents the beginning of the tracked visitor journey rather than every influence that may have occurred later.

  1. Separate paid or campaign sessions from organic, referral, direct and unknown traffic.
  2. Inspect the landing pages associated with those sessions instead of relying on a combined sitewide traffic total.
  3. Review the visitor journey to see which pages were viewed before a conversation or inquiry began.
  4. Compare sessions and conversations by source to identify whether a campaign is producing engagement rather than visits alone.
  5. Treat first-touch attribution as one view of acquisition, not as a complete account of every marketing interaction.

This evidence can support a precise conclusion such as: campaign-attributed visitors reached the site and viewed particular pages, but relatively little useful inquiry information followed. It can also show that visitors from a source entered substantial conversations even if sales later rejected them. For organizations that need a consistent review routine, daily manual triage for website inquiries provides the natural next operational question.

03

Then inspect what the inquiries actually contain

Lumi’s optional in-chat lead form captures five direct fields: name, email, company, phone and challenge. The resulting record is linked to the visitor and conversation. It can also carry AI-derived details including goal, timeframe, intent, whether a meeting was requested, a recommended solution, an AI summary, the transcript, language and source. For non-English inquiries, translated information can be included.

Evidence available for lead review

Identity and contact detailsName, email, company and phone provide the submitted contact record.
Stated challengeThe visitor’s own description helps sales assess relevance before outreach.
Intent and timingAI-derived intent, goal and timeframe add context to the submission.
Conversation evidenceThe transcript and summary show what the visitor asked before becoming a lead.
Journey and sourceThe linked visitor, session and conversation connect the inquiry with its first-party acquisition context.
Meeting signalThe record shows whether the visitor requested a meeting, without treating that request as a completed appointment.

The Prospects list displays leads and meeting chips, while conversations can be marked test, spam, internal or irrelevant. Those controls matter because an unfiltered inquiry count can make a weak source appear productive. Review the transcript and stated challenge before accepting a blanket claim that every submitted lead is poor. Where inquiries include several issues, reviewing multi-question inquiries before replying helps frame a more disciplined response process.

04

Use a shared scorecard instead of competing summaries

The agency and sales team should review the same sequence of evidence rather than presenting separate dashboards and anecdotes. Lumi provides an Analytics overview, detailed analytics for traffic performance, funnel and diagnostics, a Prospects view and a Business Intelligence page. These views support a common discussion about acquisition and inquiry behavior, but the decision framework still needs to distinguish observed facts from internal sales judgments.

What each layer answers

AcquisitionWhich first-touch source classification, referrer, UTM and landing page brought the visitor?
EngagementWhich pages did the visitor view, and did a Lumi conversation begin?
InquiryDid the visitor submit contact details and describe a challenge?
IntentWhat goal, timeframe, meeting request and intent appear in the inquiry record?
TriageIs the conversation genuine, or should it be marked test, spam, internal or irrelevant?
OutcomeDid internal business records later show progress, a customer or revenue?

This structure prevents a common reporting error: allowing a strong number at one stage to stand in for success at every later stage. It also makes anonymous behavior useful without adding it to the sales queue. The distinction is explored further in learning from anonymous inquiries without inflating follow-up leads. For teams reviewing inquiries outside business hours, prioritizing overnight inquiries before morning outreach addresses the next workflow decision.

05

Know where Lumi’s evidence stops

Lumi receives data from its own conversations, messages, leads, voice use and AI analysis, as well as website visitors, sessions, page views, attribution and booking-start events. Connected SHOPLINE stores can provide commerce and cart events plus checkout references. Those references are experimental and are not confirmed orders or revenue attribution. A booking-start event likewise shows that a visitor began a booking action, not that an appointment was completed or confirmed.

Leads reach staff in the Lumi workspace and by email, with notifications available in the recipient’s language to as many as five addresses. Optional SMS is available for high-intent leads. These notifications support prompt action, but they do not establish what happened after outreach. When financial performance is the deciding issue, compare Lumi’s source and inquiry records with verified business records using the principles in comparing inquiry sources with verified revenue attribution.

The same discipline applies to appointment-oriented businesses: separate an inquiry, a booking start and a completed appointment. Clarifying who needs follow-up on appointment inquiries focuses on that handoff, while testing after-hours inquiry acknowledgments before launch addresses how to examine the customer-facing response before relying on it operationally.

06

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

Across these busy Southern California markets, service businesses often compete for customers who compare several options online before making contact. That can produce strong campaign traffic alongside inquiries with weak fit, unclear urgency or expectations shaped by the wrong message. The first practical step is to review one recent campaign as a shared sequence: source and landing page, pages viewed, conversation details and submitted inquiry. Compare those signals with sales’ reasons for rejecting each lead. This gives the agency and sales team a common evidence base and identifies the first stage where buyer intent begins to weaken.

07

What to do when the evidence identifies the gap

Once the review shows where quality declines, assign the remedy to that stage. A source producing visits but irrelevant conversations calls for an acquisition or message review. Relevant conversations that do not become captured inquiries call for closer attention to the website experience and optional lead-capture setup. Useful inquiries that stall afterward call for a tighter staff process, because Lumi records and notifies but does not perform sales follow-up or maintain a CRM pipeline.

  1. Choose a review period and separate traffic by Lumi’s source classifications.
  2. Inspect landing pages, visitor journeys and conversations for each important source.
  3. Remove test, spam, internal and irrelevant conversations from the operational review.
  4. Read the challenge, transcript, goal, timeframe, intent and meeting-request fields for genuine inquiries.
  5. Have agency and sales representatives classify the same records and document where their conclusions differ.
  6. Compare any claimed customers or revenue against verified business systems rather than inferring them from leads, booking starts or checkout references.
  7. Change the campaign, page experience or follow-up process only after identifying the stage where the evidence weakens.

Lumi is part of the OceSha ecosystem and is powered by OceSha Ventures, the business behind Lumi. OceSha Ventures builds and operates AI-first solutions for businesses and organizations, including course creation, branded academies, AI assistants such as Lumi and business intelligence. If you want to discuss applying this diagnostic approach to your website, contact the Lumi team with the traffic and inquiry questions you need to resolve.

For retail sites, remember that inquiry capture and purchase processing remain distinct workflows. After-hours retail inquiry capture versus purchase processing explains why a shopper conversation should not automatically be treated as a completed transaction.

Lumi connects first-touch website attribution with visitor journeys, AI-enriched inquiries and conversation records so you can diagnose where the gap begins.

Diagnose the gap with Lumi

Frequently asked questions

Does a paid or campaign source mean the visitor came from an ad?

Lumi classifies traffic using available first-party attribution signals such as UTM data, referrer origin and landing page. Paid/campaign is one of six classifications, alongside organic, referral, direct and unknown. The default model is first-touch.

Can Lumi show why sales rejected an inquiry?

Lumi records the submitted challenge, transcript, AI summary, goal, timeframe, intent, meeting request, language and source. Sales can review those details and mark conversations test, spam, internal or irrelevant. Lumi does not provide a lead-status pipeline for recording the complete sales disposition.

Can anonymous website activity still help the diagnosis?

Yes. First-party visitor journeys include sessions, page views, attribution signals and landing activity. Anonymous behavior can help explain how sources and pages perform even when a visitor does not submit the optional in-chat lead form.

Does Lumi calculate return on ad spend or customer acquisition cost?

No. Ad spend and customer acquisition cost require an ads integration and are currently unavailable. Lumi’s traffic and inquiry evidence should be compared with verified spend and outcome records held elsewhere.

Does a meeting chip prove that an appointment happened?

No. A meeting request or booking-start event is not a completed or confirmed appointment. Confirmed appointment status must come from the relevant booking or business record.

How do connected SHOPLINE stores affect this analysis?

A connected SHOPLINE store lets Customer Lumi use synchronized catalog information for product answers and help shoppers find products and manage their real store cart. Lumi receives commerce and cart events plus experimental checkout references, but not orders; those references do not establish revenue.

The bottom line

Do not choose between the agency’s traffic report and sales’ lead-quality complaint on instinct. Make both teams use the same evidence chain: source, landing page, visitor journey, conversation, inquiry details, triage and verified business outcome. Lumi provides the first-party traffic, conversation and lead context needed to locate many breaks in that chain. It does not currently prove ad efficiency, CRM progression, completed appointments, orders or revenue. The right conclusion is the narrowest one the data supports—and the right fix belongs to the stage where quality actually drops.

Rohan Hall headshot
About the author

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.

Who stands behind this

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

  1. Lumi — lovelumi.ai
  2. OceSha Ventures — ocesha.com
  3. Rohan Hall — rohanhall.com

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).