Autonomous AI agent engine, implemented with you. Your team has
better things
to do.

Agents that start from a message, a webhook, a call to your API or a schedule, and work inside your ERP, your CRM or your own API. We implement them with you, one process at a time, and you oversee every action.

Pilot with a dedicated implementer
Your tools turn into finished workA customer asks about an order. Lummy checks the ERP with read-only access and sends an answer. Animated concept demo.Customer · Webchat“Where is my order #1042?”ONE QUESTION. YOUR OPERATIONS ANSWER.LUMMYYour ERPOrder found#1042 · In transitReply sentYour order is on its way.It arrives Thursday, October 24.TASK DONE. TEAM FREE.Read-only accessYou set the limit.CONCEPT SCENARIO · YOUR SYSTEMS STAY WHERE THEY ARE
YOUR SYSTEMS. YOUR AGENTS. ONE PLATFORM.See how ↓
AGENTS THAT DO THE WORK

See the work.
Follow every action.

Your tools, connected to an agent.
A flow you can understand and oversee.

Running
UPDATES AND CONFIRMS

A delivery change, handled in your systems.

The agent verifies the customer, looks up the order and changes the address when your rules allow it. If it hits a restriction, it hands off to your team.

THE AGENT RECEIVES THE REQUESTWorks out what needs to be solvedTools are called with the permissions you defined.
Changes only before shipping

EXECUTION VIEWThis is how your agent works. Every lookup and action is logged.

A delivery change, handled in your systems. The agent verifies the customer, looks up the order and changes the address when your rules allow it. If it hits a restriction, it hands off to your team.Lummy checks permissionsOrder updatedChange saved · ERPConfirm to customerResult sent · ChannelCustomer requestsa changeCustomer serviceAI agentVerify customerCRMLook up orderERPChange addressShippingConfirm changeWebchatEVERY ACTION IS LOGGEDLOOKUP · WRITE · CONFIRMATION
Your agent is working

Customer service agent

In progress
Customer
Pending
Order
Looking up
Operation
Pending
Notification
Pending
Concept scenario · The run illustrates capabilities subject to validation.Connections subject to validation.
FROM AN EVENT TO A FINISHED TASK

Every repeated task
takes time from what comes next.

Copying a record from the CRM. Looking up an order status. Answering the same question again. Each one interrupts something your team could be solving.

Hand that work to an agent connected to your operations. Lummy keeps its instructions, connections, permissions and tests in one platform. Your team keeps the work that needs human judgment.

FOUR WAYS TO START

An agent doesn't wait
for someone to message it.

Chat is just one way in. A Lummy agent also reacts to what happens in your systems, answers when your code calls it, and runs on its own on the schedule you set.

  1. 01

    A message

    WhatsApp, email or webchat. Someone asks, and the agent answers with data from your systems.

    ExampleA customer asks about an order and gets the delivery date from the ERP.
  2. 02

    A webhook

    Your system reports that something happened, and the agent acts without being asked.

    ExampleA new order comes in: the agent checks stock and notifies the customer.
  3. 03

    The Lummy API

    Your application calls the agent like any other service and gets the result back.

    ExampleYour portal sends a ticket, and the agent classifies and routes it.
  4. 04

    A schedule

    The agent runs on its own every hour, every day or every Monday, even if nobody writes.

    ExampleEvery morning it reviews late orders and updates each customer.
WHAT CHANGES

One question.
Five open tabs.

Today, your team is the bridge

  • Someone copies the order from WhatsApp into the ERP by hand.
  • The same question gets answered ten times a day.
  • Messages sent at night wait until morning.
  • Nobody knows which data a customer's answer came from.

With a Lummy agent

  • The agent looks up the order in your ERP and answers with that data.
  • Your team handles only what needs judgment.
  • WhatsApp and email get answers at any hour.
  • Every lookup and every answer is kept in the log.
START WITH ONE PROCESS. GROW FROM THERE.

We implement it with you.
You decide when it goes live.

A Lummy implementer configures, connects and tests your agent. Your team defines what it handles and oversees it.

Together we pick one concrete task, the systems involved and what the agent must not do.

Scope one processEXAMPLE
Process

Order status over WhatsApp

Systems involved

Odoo · WhatsApp Business

What it must not do

Offer discounts or promise dates

Example implementation for a distributor. Every pilot is scoped during discovery.

THE PLATFORM

Everything your agents do,
in one place.

Your team oversees everything from Lummy. Customers keep writing through the channels they already use.

What your agents resolved, in numbers.

How many conversations they handled, how many they resolved without a person, the time they saved your team and what it cost, in dollars.

Sample distributorExample
Resolved without a person78.8%Pilot target: 60%
Conversations handled676533 resolved · 143 with a person
Time saved35.5 h533 resolved × 4 min
Handed to your team143Each with its reason
AgentConversationsNo personWith a person
Orders and deliveriesWhatsApp, email52081.0%99
Stock for sales repsInternal webchat15671.8%44
YOU STAY IN CONTROL

It can do a lot.
You decide how much.

Every agent has a list of what it can and can't do. Anything it writes to your systems asks for confirmation, and anything outside its rules goes to a person.

Can and can't

Whatever you don't enable stays blocked, even if someone asks.

Handoff to a person

Credit, complaints or out-of-policy cases go to your team.

Tamper-proof log

Every lookup and write is recorded; nobody can delete it.

Lookup allowedOnly the information needed
Actions with limitsYour business rules
THIS DECISION IS YOURS
Approve the refund?

The agent prepared the request. You give the go-ahead.

AUTONOMY WITH OVERSIGHT · INTERACTIVE EXAMPLE
CONTINUOUS IMPROVEMENT

Every fix sticks.
Nothing breaks along the way.

  1. 01
    We show you what to review

    Answers missing the data, with a guessed date or outside your rules show up in “To review”.

  2. 02
    You request the fix

    You write what the agent should have done. Your implementer adjusts its instructions or tools.

  3. 03
    It becomes a test case

    Every approved fix joins the cases the agent is tested against.

  4. 04
    The new version passes every case

    If something that used to work breaks, the version isn't published.

Test cases · Orders and deliveriesExample
Version 7 · published46 / 5092% of cases
Version 8 · draft47 / 50 Clears the 90% minimum
CaseVersion 7Version 8
Invoice number instead of order numberFailPass
Order without a route: no date promisedPassPass
Balance question: handed to SalesPassPass
INTEGRATIONS

Your agents work
with what you already use.

You don't switch systems. The agent reads and writes in them using only the operations we enable for its task.

  • WAWhatsApp BusinessChannelAvailable

    Your agent replies from your official number. It connects through Meta's own window, with no shared passwords.

  • @EmailChannelAvailable

    Gmail, Google Workspace or Microsoft 365. It reads the inbox you choose and replies in the same thread.

  • OOdooERPAvailable

    Orders, stock, customers and invoices. It uses a technical user and respects its permissions.

    AI agent for Odoo
  • APIYour own APIAny systemAvailable

    From its OpenAPI spec, a Postman collection or cURL calls. You choose which operations it uses and set their limits.

    Connect your ERP or API
Coming soon
  • Salesforce
  • Google Drive
  • SAP Business One
  • HubSpot
  • Shopify
  • Microsoft Teams

We build them based on demand. Don't see your system? Tell us which one you use

TWO SIDES OF YOUR BUSINESS. ONE PLATFORM.

Serve customers outside.
Move work forward inside.

An agent receives an address change, looks up the order and updates the delivery in the ERPORDER #1042REQUEST FROM YOUR CUSTOMERPlease change my delivery address.Address updated in your ERPThe order stays on track.CONVERSATION → ORDER → ACTIONConcept scenario

Your customer asks.
Your agent handles it.

One customer asks about an order. Another looks for a product. Your agent checks your systems and takes the next allowed step.

  • Answers grounded in your operations
  • Opportunities logged in your CRM
  • Conversations handed to your team when needed
Tell us what your customers ask See the use case: an AI agent for Odoo
An agent finds the expense policy among your company's documents and prepares the request for approvalExpense policyQUESTION FROM YOUR TEAMHow do I request travel expenses?Request ready for reviewYour manager takes the next step.KNOWLEDGE → REQUEST → APPROVALConcept scenario

The answer exists.
Make it easy to find.

The answers your team needs are already in the company. Bring them to the channels they work in with an agent that knows your processes.

  • Policies and processes at hand
  • Lookups in internal systems
  • Requests with their permissions and approvals
Tell us what your team needs See the use case: an agent on your own API
PRICING

A monthly fee
plus what they use.

No surprises: you see each agent's spend in the dashboard, in US dollars, before taxes. The pilot quote comes after the discovery call.

  • Pilot with an implementer

    We start with one process. Someone from Lummy configures, tests and refines your agents with you.

  • Usage in US dollars

    You pay for what your agents use: the AI model and WhatsApp messages. Meta's fees pass through at cost.

  • A budget you set

    We alert you at 50, 80 and 100%. You decide whether agents keep working at the limit or everything goes to your team.

  • Monthly invoice

    One invoice a month, paid by card or international wire transfer.

FOR AGENCIES AND INTEGRATORS

More clients.
One foundation to grow on.

Deploying agents for more clients shouldn't mean running separate infrastructure for each one. Our vision for agency mode is to manage them all from Lummy, with a workspace per client and its own connections and permissions.

I want to offer agents to my clients Agency mode in exploration
Your agency
N
Norte StudioCustomer service
O
ÓrbitaSales and follow-up
M
MeridianoInternal operations
A SEPARATE WORKSPACE FOR EACH CLIENTConcept view · Fictional clients
STRAIGHT ANSWERS

Before you start.

Have a use case in mind?
Tell us about it

What is Lummy?

An autonomous AI agent engine for businesses. Each agent starts from a message, a webhook, a call to the Lummy API or a schedule, and works in your systems with the permissions you give it. We implement it with you, and you oversee every action from Lummy.

Is it only for WhatsApp?

No. WhatsApp, email and webchat are one way to trigger an agent. It can also react to a webhook from your systems, respond when your application calls the Lummy API, or run on its own on the schedule you set.

Who sets up the agents?

A Lummy implementer assigned to your company. You define what the agent should handle, review its work and request changes. Every correction is tested before it goes live.

Which systems does it work with today?

WhatsApp Business, email (Gmail, Google Workspace and Microsoft 365), Odoo, and any API with an OpenAPI spec, a Postman collection or cURL calls. Salesforce, Google Drive, SAP Business One, HubSpot, Shopify and Microsoft Teams are in development based on demand.

Do I have to change my systems?

No. The agent works on top of what you already use: WhatsApp Business, your email, Odoo or your own API. It reads and writes there with a user and permissions you define, and your customers keep using the same channels.

What does my team review?

Whatever the agent hands off to a person, answers flagged for review, and actions that ask for confirmation before they're recorded. Everything else stays in the log for whenever you need it.

What if the agent gets something wrong?

It only answers from your systems and sources, never runs operations you haven't enabled, and asks for confirmation before recording anything. Anything outside its rules goes to a person, and doubtful answers are flagged for review so you can correct them.

How much does it cost?

A monthly fee plus your agents' usage, billed in US dollars, with a budget you set. We send the pilot quote after the discovery call.

Can I use Lummy for multiple clients?

Agency mode is part of the product vision and is in exploration. If you deploy agents for other companies, let's talk about the workspaces, permissions and controls you need.

Where do we start?

With a discovery call about a single process: what task you want handled, which systems are involved and what the agent must not do. From there we define the pilot.

BOOK A DISCOVERY CALL

That backlog of work
already has a next step.

Leave your email and we'll reach out to review one process.
We start with what your business needs solved.

Who are you building agents for?
We'll email you to schedule the discovery call and share Lummy updates. Read our privacy notice (in Spanish).