← Work

Case study — KK Dimsum

From slow conversations to orders that move on their own.

A website and WhatsApp automation that cut response time while keeping the buying habit customers already had.

Visit kkdimsum.store
01 / Problem

The admin became the bottleneck.

Before the new system, customers waited up to 45 minutes for a response. Every order detail moved through a manual conversation, so sales capacity was limited by admin availability.

The channel was fine. The problem was that every order had to be started and completed by hand, from scratch.

02 / Approach

Keep the habit. Fix the process.

The website became the ordering entry point and connected straight into WhatsApp. Customers stayed in the channel they knew, and order data arrived ready to process.

03 / Solution

Three components, one connected flow.

01

A website for direct orders

Customers browse the menu, choose their order, and enter the WhatsApp flow without waiting for an admin to explain everything.

OutputStructured order
02

WhatsApp order automation

Orders are processed automatically, context stays complete, and an admin only steps in when needed.

OutputQualified handoff
03

Self-healing monitoring

Services are monitored in production and recover from common failures on their own.

OutputOperational signal
04 / Results

Faster, more independent, measurable.

22.5×faster
Response time: 45 minutes → 2 minutes
70%orders via web
Up from 0%
60%auto-handled
Orders handled automatically
40%self-resolved
No admin assistance
59.5hours saved/month
Operational time recovered
+35%revenue
After the system went live

Reported results for the KK Dimsum project. The measurement period and calculation methods have not been published; these figures are not a forecast for another business. Revenue growth does not establish the effect of software alone.

What did not change: KK Dimsum still has to make great food, promote it, and care for its customers. Software removes obstacles that should not be there; the restaurant does the rest.
05 / Stack

Built to keep running.

Next.jsDockerCoolifyTraefikWhatsApp API

The stack was chosen for operational needs, straightforward monitoring, and long-term system ownership.

Is a manual process starting to hold you back?

Discuss your workflow