The LoloDesk story

LoloDesk started with a $350 monthly software bill.

One of my clients was paying for a broad messaging platform while using only WhatsApp and website chat. The features they needed most still came with limits. So I proposed something simpler: build the inbox around the work they actually do.

Read the story See what we built
The original mismatch
At the time

Approximate monthly cost

$350

Paid by one client for their existing customer-messaging setup.

What the team actually used

WhatsApp

Primary customer channel

Website chat

Questions from site visitors

Where the team needed more room

Character limitsKnowledge basesHTTP actions

A story of discovery

It began with a client problem, not a product pitch.

Respond.io was built for a wider range of channels and teams. My client did not need that breadth. They needed fewer limits around the work happening inside two channels.

  1. 01

    The cost stopped making sense

    One of my clients was paying about $350 each month for Respond.io. The platform covered many channels and workflows, but this team depended on only WhatsApp and website chat.

  2. 02

    The limits kept showing up

    The team ran into character limits and restrictions around knowledge bases and HTTP actions. Those were not side features for them. They were part of answering customers and checking real business information.

  3. 03

    We chose a smaller product

    I asked why we should reproduce a large platform when the business needed a focused shared inbox. We decided to build around the two channels, the AI workflow, and the business actions the team used every day.

  4. 04

    A focused product took shape

    That first workflow still shapes how I build LoloDesk: start with real conversations, remove what the team does not need, and keep a person in control.

What that decision changed

We did not need to copy everything.

The frustration was not a reason to build another oversized platform. It gave LoloDesk a clear boundary: solve the customer-conversation workflow small teams already have.

Two channels, one inbox

WhatsApp is the primary channel. Website chat sits beside it, with the same customer context and team ownership.

Business knowledge matters

Lolo answers from information the business approves. Missing answers become visible knowledge gaps instead of confident guesses.

Actions are part of the conversation

Approved HTTP actions let Lolo check availability, find a booking, or look up an order before replying.

People keep the final say

When a request needs judgment, Lolo stops and hands the full conversation to the right teammate.

Reymar Ocero, founder of LoloDesk

A note from the founder

I am building the tool I wanted my client to have.

LoloDesk came from watching a small team pay for more software than it needed while still working around limits in the parts that mattered. I want to build something focused, practical, and priced for businesses that depend on every customer conversation.

Reymar Ocero

Software Engineer

LoloDesk is coming soon

Join the early-access list.

LoloDesk is not open to the public yet. Join the list for priority access when we launch.

The first 20 founding customers can subscribe for $29 per workspace each month, instead of the regular $39, for each workspace's first 12 paid months.

  • No payment today
  • No credit card required
  • Priority launch invitation
  • $29 founding price per workspace
  • New workspaces also qualify
  • No obligation to subscribe

Reserve your founding price

Enter your work email. We will use it to prepare an early-access request.

Joining the list does not start a paid subscription. We will contact you when LoloDesk is ready. See our Privacy Policy.