A booking system for a laundry and dry cleaning studio in Gurgaon: customers book on the website or through a WhatsApp bot, follow their order, and staff run the day from one admin panel.
[01]
// BOOK ON WHATSAPP
Real screenshots
The customer's side of the bot: my own test chats on a real phone, in the order the bot asks. Phone numbers, a typed address and a price are masked.
01 Hi, then the menu
Any message gets the menu: book a pickup, track an order, prices, or talk to us
02 Choose a service
Dry cleaning, laundry, steam ironing, or sofa, mattress and carpet
03 Add another, or that's all
More than one service per pickup: "Add a service" or "That's all"
04 Pincode, then the address
The pincode first, then the flat and building, then the street (or "skip"). The typed address is masked
05 Pick a time slot
The open slots for the chosen day. The address behind the list is masked
06 Booked, with a tracking link
The confirmation with its reference and a Track order button. The later price is masked
07 Updates at each step
Collected and checked, ready with the delivery day, on its way, then complete with a link to rate. The price is masked
[02]
// THE PROBLEM
Why it exists
Laundry Studio is a new dry cleaning, laundry, steam ironing and home-care studio in Gurgaon. It collects from the customer's door, counts every piece with them, and brings everything back on the day it promised.
Customers book in three ways: on the website, on WhatsApp or by phone. All three had to follow the same rules for areas, days and slots, land in one place, and let a small team run each order from pickup to delivery, from a phone.
[03]
// WHAT I BUILT
The rules
01
Website, WhatsApp and phone bookings are all created by the same database function, with the same rules for service areas, slots and capacity. They land in one admin panel, each tagged with the channel it came from.
Book
Lands in
02
It runs on Meta's WhatsApp Cloud API, called directly with no middleman. The bot asks for the service, the pincode and address, then a day and a slot, shows a summary and books on Confirm. Every option also works typed, including common Hindi and Hinglish phrasings.
03
What, where and when, then your details. The pincode is checked first, and an area that isn't served yet can leave a number instead. A booking confirms at once when the slot has room; a full slot becomes a request for staff to confirm. Nothing is paid online.
04
Asking for a person, or three misunderstood replies in a row, hands the chat to staff. The bot goes quiet, the thread shows "Waiting for you" in the admin inbox, and "Hand back to bot" restarts it at the menu.
05
Today's requests, pickups, home visits and deliveries, each with one next-step button, plus orders, the WhatsApp inbox, customers, leads, reports and settings. Before any step messages a customer, staff see the exact WhatsApp text and confirm it.
06
Each order has a private link with its progress and times, the items and final price once counted, and buttons to message, call, change the day or cancel while that's still allowed. Status changes are also sent to the customer on WhatsApp.
[04]
// SCREENS
Gallery
Live site, nothing submitted
Local build, made-up data
[05]
Request path
Prices, statuses, order numbers and delivery dates are decided in the database, and slot capacity is checked inside a locked transaction, so two bookings can't take the last place in a slot.
The bot is a fixed set of steps, not a language model, so every reply is predictable and each step has its own unit test.
Every WhatsApp message is checked against Meta's signature, stored, and claimed once, so a redelivered message never books twice. Failed sends are retried on a schedule, and none can go out twice.
The website never shows saved addresses or past orders for a typed number. Only WhatsApp, which verifies the phone, offers a returning customer their saved addresses.
[06]
// OUTCOMES
Confirmed only
Ways to book, one admin panel
Days from first commit to its own domain
[07]
// More Projects
Related
