Built a booking app for Kang Dedi, a one-man AC technician in Bandung (fictional client, very real problem).

Every booking used to be a WhatsApp marathon: "how much?", "which day?", "what time?", "send your location". Around 10 messages per job, answered at night after work. Then his days zig-zag across the city, and sometimes he shows up to an empty house because the customer forgot.

So I turned the whole chat into one link: ✅ Pick your neighborhood, you only see days he's already around (mornings in your area, afternoons in the center) ✅ Price and time on site show up instantly, only slots where the whole job actually fits ✅ Booked in about a minute, with a ticket and the exact WhatsApp confirmation ✅ Reminder the evening before: still on, or reschedule? No reply gets flagged for him ✅ Someone cancels? The slot goes straight to the next person on that area's waitlist ✅ Review request goes out after the job, on its own ✅ His whole day on one map, plus the week, the waitlist and every message sent

Ngl the fun part was the scheduling rule. My first version literally put him in two places at once, took a couple of rounds to get it right (the process video shows the whole thing, bugs included).

Try it: ademservice.lovable.app Owner view, no login: ademservice.lovable.app/demo (Messages are simulat:ed in the demo, production would go through the WhatsApp Business API.)