Your AI team for taking care of every customer.

We’re building Lumys to talk with your customers, understand what they need and follow up. Your business defines the scope; your team supervises and handles exceptions and sensitive decisions.

Product in development · closed pilot. Intelligent conversations with the Lumys are not yet integrated with the platform’s channels.

Guided questions · no account needed. Your answers stay in this tab. No agents are activated and no customers are contacted.

Lumy, the coordinator of your AI team

LumyOne context. Your whole team.

A conversation that moves forward.

Try a reply. See how your Lumy gathers context, keeps the conversation going and finds the next step.

Guided demonstration · fictional conversations and data

Three conversations, step by step

Prepare an appointment

Prisma learns what the person is looking for. Milky continues with that context and proposes a time.

Interested person: I’m comparing two options. Could I speak to someone on Thursday?

Prisma: Of course. To help you find the right fit, what matters most to you when choosing?

Staying within budget

Interested person: The most important thing is that it fits my budget.

Prisma: Understood: budget comes first. I’ll keep that context for the conversation and pass your preference for Thursday to Milky.

Milky: Prisma passed your context to me. This example’s fictional calendar has an option on Thursday at 10:30 to discuss the options and your budget. It’s a proposal; nothing is booked yet.

A handoff to an adviser would only be assigned once a person accepts it. This example checks no calendar.

Another possible reply: Understanding the differences

Interested person: I want to understand the differences and choose what works best for me.

Prisma: Then the conversation should help you compare, without assuming a decision. I’ll pass that interest and your preference for Thursday to Milky.

Milky: I received your interest in comparing the options. This example’s fictional calendar shows Thursday at 10:30. That would be a proposed time for the conversation, without making a booking or assuming a choice.

A handoff to an adviser would only be assigned once a person accepts it. This example checks no calendar.

Pick up a conversation

Aura picks up what happened, offers help and asks the team for support when needed.

Customer: I’m still waiting for the missing part of my order. I explained it yesterday.

Aura: I’m sorry for the delay. I have the context and requested a review. Meanwhile, shall we check the shipment or prepare your request for the team?

Check the shipment

Customer: I’d like to know what’s happening with the missing shipment.

Aura: The missing part of your order is still being prepared and doesn’t have a confirmed delivery date yet. I included that question in the review so the team can clarify what’s still pending.

Aura: I’ve kept the shipment status and your question together. While we wait for the team’s response, I can help you go over the order details. Once we have a confirmed date, I’ll let you know.

This example creates no real follow-up and guarantees no date. The team hasn’t accepted the case yet.

Another possible reply: Request compensation

Customer: I’d like a person to consider compensation for what happened.

Aura: I understand. I’ve added your compensation request alongside what happened and yesterday’s inquiry. That way, you won’t have to start over when a person reviews the case.

Aura: The review has been requested; a person still needs to accept the case and decide on compensation. In the meantime, I can keep helping you with your order’s status.

This example assigns the case to no one and grants no compensation.

Discover an improvement

Nova brings together unanswered questions and suggests what the team could review before the appointment.

Your team: People ask about our options, but don’t end up booking. What could we improve?

Nova: I found questions about times and what each option includes. I have a proposal for each topic. Which should we start with?

Review the times

Your team: Let’s start with people who need a later time.

Nova: I found messages like ‘I can only come after work’, followed by morning options. I put together a proposal to try a later time, if the team has capacity.

Nova: The proposal is ready for the team to decide whether it can offer that time. If approved, we can see whether interested people choose it before keeping it. For now, the calendar stays the same.

No trial has started and no increase in bookings is promised.

Another possible reply: Clarify the options

Your team: I’d like to understand which pricing questions go unanswered.

Nova: I found questions like ‘What does the lower-priced option include?’ and ‘What’s different between the two?’ I prepared a draft comparing what’s included, the price and the differences, using the company’s approved information.

Nova: The proposal is to use that comparison when answering questions, before offering an appointment. I’ve marked the missing details so the team can complete and review the reply.

This example sends no replies. With approved information, the Lumys could handle routine questions without approval for every message.

Only this example changes. It sends no messages, books no appointments and contacts no customers.

Intelligent conversations with the Lumys are not yet integrated with the platform’s channels.

Explore the cases in detail

One conversation. A team with different strengths.

You talk to Lumy. Lumy brings in the specialist each moment needs. Your company defines the scope and keeps supervision.

Select a Lumy to explore their role.

Meet the team we’re building. Showing a Lumy here does not mean its connected capabilities are available yet.

With initiative. With your judgment.

The Lumys are being built to carry on conversations within the scope your company authorises. Your team supervises, resolves exceptions and keeps authority over sensitive decisions.

Trust & scope

You define the scope.

Your company sets the rules, permissions and boundaries that guide the Lumys’ work.

People handle exceptions.

Your team steps in for sensitive decisions and situations requiring human judgement. A handover is assigned only when a person accepts it.

WhatsApp first.

The first planned customer journey. Conversations still need channel integration and validation with each company’s configuration and permissions.

A team that starts with your business.

Your team tells Lumy what it needs to know: your business, your documents and rules, your scripts, how you qualify interested people and who your advisers are.

Available today, by invitation

Invited accounts answer guided questions and save company text documents as drafts. Saving them does not publish knowledge, train a model or activate customer conversations.

  1. Tell Lumy about your business.Your goals, your customers and the decisions that stay with your people.
  2. Write your documents and rules.Enter offers, scripts and policies as text drafts for your team to review.
  3. Next: rehearse the WhatsApp journey.The planned stage is to test conversations and exceptions with your rules. Intelligent conversations must be integrated with channels and validated before customer use.

The first customer journey: WhatsApp

Your team prepares its business context in Starlumon. The first customer journey is planned for WhatsApp. Intelligent conversations with the Lumys are not yet integrated with the platform’s channels. Telegram, web, email, voice and social media are part of the broader vision, with configuration, permissions and validation for each company.

Before you begin

Trust & scope
What works today?

You can explore Lumy’s guided questions without an account; your answers stay in that tab. In the closed pilot, invited accounts can also sign in and save company documents as drafts. Intelligent conversations with the Lumys are not yet integrated with the platform’s channels.

What is Starlumon?

Starlumon is a team of AI agents, the Lumys, being built to talk with customers, qualify enquiries, coordinate appointments and follow up within each company’s authorised scope. People supervise and handle exceptions and sensitive decisions. It is in development, in a closed pilot.

Who is it for?

For businesses with advisers or customer-facing teams that want to qualify enquiries, coordinate appointments and support customers before and after each interaction. During the pilot, access is by invitation.

Does it work on WhatsApp?

WhatsApp is the first planned customer journey. Intelligent conversations with the Lumys are not yet integrated with the platform’s channels. Your company’s configuration, permissions and journey need to be validated before the Lumys can converse with customers.

How do I prepare my business?

Invited accounts save the context from Lumy’s guided questions and create company text documents as versioned drafts. The separate preparation notes stay only in the browser tab. Saving a draft does not publish knowledge, train a model or activate agents. Without an invitation, you can try the guided questions in a preview; its answers stay only in that tab.

How do the Lumys work with my advisers?

Lumys are being built to converse and follow up within the scope your company authorises. Advisers supervise and take over for exceptions, sensitive decisions or situations needing human judgement. A proposed handover becomes an assignment only when a person accepts it.

Meet Lumy. Imagine your team.

Guided questions · no account needed

Try guided questions

Your answers stay in this tab. No agents are activated and no customers are contacted.

Product in development · closed pilot

Already invited? Sign in