Case study: how an Ipoh wedding venue cut 70% of booking-enquiry work with an AI concierge

This is a case study. For the category-level read — when a Perak business should build a WhatsApp bot and when the cheaper fix is the right answer — see When a WhatsApp chatbot works for a Perak business (and 3 cases where it doesn't).

The business

A 9-year-old garden wedding venue on the southern edge of Ipoh, set in a converted colonial bungalow with an outdoor lawn that seats 280. The owner runs it with her sister and a team of six full-time staff — three in events, two in F&B, one part-time finance. They host an average of 22 weddings a month, plus corporate launches and family events in the off-season. Roughly 60% of enquiries come via WhatsApp, 25% from wedding-planner referrals, and the rest from Instagram and walk-ins. The owner had been on the venue since it opened in 2017 and was known personally by every planner in the Perak wedding scene.

This is the case study for the AI chatbot side of what we do — a small, opinionated build for an Ipoh wedding venue that did not need "a chatbot to look modern." It needed to stop eating the owner alive.

The problem they were actually trying to solve

By early 2026, the venue was fielding 1,200 to 1,500 WhatsApp messages a month. About 70% of them were what the owner called the "Saturday morning stampede" — newly engaged couples messaging four to five venues in parallel, asking the same trio of questions: availability on a specific date, package price for a given headcount, and whether a particular weekend is open. The owner was answering these from the gym, the school run, and from inside the venue office while a wedding was being set up around her.

"I became a WhatsApp receptionist, not a wedding venue owner. I missed my own daughter's school concert because a couple wanted to know if we had a Friday slot in March 2026. That's when I knew I had to do something."

Three concrete problems, each costing real money:

• Slow replies at 11pm and 6am were costing her bookings. Couples message in their timezone and book the venue that answers fastest. The owner estimated she was losing 4-6 high-value weddings a year — at RM 28,000 to RM 45,000 average ticket — to faster competitors.
• She was double-booking dates. Two different staff members had said "yes" to the same weekend in two different chats, and the conflict only surfaced when both couples arrived for the site visit. The venue comped the second couple a free menu upgrade worth RM 6,800 to fix it.
• She was turning away serious corporate work. Year-end dinners, product launches, AGM-style events with 150-400 pax were coming in via the same WhatsApp number, but she didn't have the bandwidth to quote them properly. The owner estimated RM 180,000 in unquoted corporate enquiries in 2025.

What we built — and why this approach

We built a small AI WhatsApp concierge for the venue's existing WhatsApp Business number. Three parts, sitting on top of a fine-tuned model trained on the venue's own 6 months of enquiry transcripts:

1. A concierge grounded in the venue's actual catalogue. Seven packages, 38 add-ons, three seasonal pricing bands (peak, off-peak, super-peak around Chinese New Year), and the deposit/cancellation policy. The bot quotes in the venue's voice — the same way the owner had been quoting for nine years — not a generic Malaysian wedding-bot script.
2. A live availability feed from the venue's existing booking sheet. When a couple asks "is 14 March 2026 open," the bot reads the calendar in real time and gives a definitive answer in the same message. This is the only question that actually converts a casual enquiry into a booked site visit.
3. A small business automation layer on the back end. Every qualified enquiry is pushed into the events team's existing Notion-style sheet. Duplicate "yes" replies — the same problem that cost the venue RM 6,800 last year — are flagged automatically so the on-duty staff member catches them before the couple does.

The build was 11 days from kickoff to live. We chose this approach over the two obvious alternatives: a human receptionist at RM 2,800 a month would have answered the same questions but with a 9-to-5 cap, missed after-hours leads, and still required the owner to handle escalations. A generic SaaS chatbot (the kind that comes free with WhatsApp Business) would have answered the FAQs but couldn't see live availability — which is the only question that matters. The custom build costs more upfront but pays back in the after-hours leads it captures alone.

Total build: RM 14,800. Ongoing retainer for AI maintenance and small model upgrades: RM 1,200 a month.

How the operation changed

The owner now opens her phone on a Saturday morning and sees a single summary in the events Telegram channel: 18 enquiries overnight, 14 handled by the concierge, 2 routed to a human for custom menus, 2 marked as low-priority follow-up. She spends 20 minutes scanning the summary and another 15 minutes on the 2 escalated chats. The Saturday-morning stampede — the part that was eating her week — is now her planning time for the weddings on the floor.

The events team got a different change. They used to type the same "yes, that date is open, package starts at RM xxx per pax" reply eight to ten times a day. They now spend that time on actual site visits and on the couples who came in through the concierge. The owner noticed a second-order effect within six weeks: the couples who book through the concierge arrive at site visits already pre-qualified — date, headcount, budget range — so the site visits themselves convert to confirmed bookings at a higher rate. They went from a 38% site-visit-to-booking rate to 54% in the first 12 weeks.

The corporate work, which was the second problem, also moved. The concierge recognises the difference between a 180-pax wedding and a 180-pax corporate enquiry and routes accordingly. Corporate leads now go straight to the owner's sister with a one-page brief attached, and the venue quoted RM 240,000 in corporate business in the first 90 days — versus the RM 180,000 the owner estimated she was losing the year before.

The numbers, 12 weeks in

• 70.4% of WhatsApp enquiries handled end-to-end by the concierge without a human reply
• 22.0% handled by the concierge with a human follow-up — mostly custom-menu and accessibility chats
• 7.6% escalated to a human immediately — high-value corporate, vendor-restriction questions, accessibility edge cases
• Site-visit-to-booking conversion: 38% → 54% over 12 weeks
• After-hours (9pm-8am) response time: 4 hours 18 minutes → under 90 seconds
• 11 additional weddings booked from after-hours enquiries in the first 90 days — RM 312,000 in revenue
• RM 240,000 in corporate business quoted in the first quarter, vs. RM 180,000 estimated lost in the prior year
• Total program cost: RM 14,800 build + RM 1,200/month retainer
• Payback period: 5.4 weeks on the after-hours weddings alone

What it would cost for your business

Three pricing bands, based on what we see for Ipoh and Perak hospitality and events venues:

• Starter — RM 9,800 to RM 12,800 build + RM 800/month. Single venue, one WhatsApp number, the venue's own package catalogue and availability feed. Fits a 60-100 pax wedding venue or boutique hotel doing 8-15 events a month. 2-3 week build.
• Growth — RM 16,800 to RM 22,800 build + RM 1,400/month. Multi-venue group (2-4 properties) or a venue running both weddings and corporate events with separate catalogues. Adds vendor-restriction logic, multi-language routing (Malay / English / Manglish), and a real-time dashboard for the events team. 4-5 week build.
• Scale — RM 28,000+ build + RM 2,200/month. Wedding venue chain or events group, integrated POS, deposit collection via ToyyibPay or Billplz, and a small CRM layer for the planner-referral pipeline. 6-8 week build.

See the Perak AI agency hub for the full breakdown, or the Perak chatbot build page for the technical scope.

What this looks like for your business

If you're running an Ipoh or Perak wedding venue and the Saturday-morning WhatsApp stampede is eating your week, this is the build. The 11-day build is short enough that you'll be in the new flow before your next wedding season. The cost is around what you'd pay a part-time receptionist, but the bot doesn't sleep, doesn't take leave for Thaipusam, and doesn't book the same date twice.

We've now done versions of this for a boutique hotel in old-town Ipoh and a beach resort in Langkawi — same pattern, slightly different catalogue. The Ipoh wedding venue was the first to layer in the corporate-events routing, which is the piece most Perak venues don't realise they need.

If you want to talk it through, book a 30-minute call with our team. We'll look at your enquiry transcripts, your package structure, and your current booking sheet, then come back with a number and a build week. We don't pitch you either way — about a third of the venues we talk to end up with a human receptionist instead, and that's the right answer for them.