What is a WhatsApp chatbot, and when does a Singapore business need one?
A WhatsApp chatbot is software connected to your business number through Meta's WhatsApp Business Platform that replies, books and reminds automatically, and passes chats to people when needed. You need one when the same five questions and the same booking back-and-forth fill your staff's phones every day.
The signs are easy to spot. Front-desk staff juggle a phone and a counter queue. Messages sent at 11 pm wait until morning and the customer books elsewhere. Several people answer from one handset, so nobody knows who replied to whom. Reminders go out by hand, or not at all, and no-shows eat into the day.
A WhatsApp chatbot in Singapore fixes the repetitive part of that. It confirms an aircon servicing slot, tells a parent which trial class has seats, sends tomorrow's appointment reminder with a reschedule button, or collects the details for a renovation quote. It does not replace the conversation that needs judgement: complaints, custom quotes, delicate questions. Those go to your team with the full chat attached.
If your volume is a handful of chats a day handled by one owner, the free WhatsApp Business app is probably enough. The case for a bot starts when several staff share a number, when bookings live in a system the app cannot see, or when reminders and follow-ups must go out reliably.
WhatsApp Business app, BSP tool or Cloud API: which route suits a Singapore WhatsApp chatbot?
Choose the app for a one-person business, a Business Solution Provider (BSP) inbox tool when you want a ready-made shared inbox quickly, and a direct Cloud API build when bookings, integrations or data control matter most. All three sit on the same WhatsApp; the difference is how much you can shape.
The Cloud API is hosted by Meta. Your developer connects it to your own server, which receives incoming messages as webhooks and sends replies back. That server is where the logic lives: calendar checks, CRM updates, AI answers, consent records. Because it runs in your cloud account, the rules are yours and so is the data you keep.
BSP inbox subscriptions wrap the same API in a finished product with a flow builder, shared inbox and reports. They are a reasonable choice, and many Singapore SMEs start there. The trade-offs usually surface after a year: per-seat pricing as the team grows, flows that cannot reach your booking system, or data you would rather hold yourself.
Pick the app when
One person replies, volume is low, and quick replies plus an away message cover most needs.
Pick a BSP inbox when
You want a shared inbox working this week and your flows fit the vendor's builder without custom code.
Pick a Cloud API build when
The bot must read and write your calendar, CRM or database, follow consent rules you define, or keep logs in your own account.
Our explainer on the WhatsApp Business app versus the API goes deeper on the feature gap.
Since 1 July 2025 Meta charges per delivered template message, and the rate depends on the template category (marketing, utility or authentication) and the recipient's country. Free-form replies inside an open customer service window are free.
Meta's pricing documentation sets out the rules our builds are designed around. When a customer messages you, a 24-hour customer service window opens. Inside it, your bot and staff can send normal messages at no charge, and utility templates delivered inside that open window are free as well. Outside the window you can only start a conversation with an approved template, and delivered templates are billed. If the customer reached you from a click-to-WhatsApp ad or a Facebook Page button, Meta opens a 72-hour free entry point window instead.
For a booking business this matters in practice. Most of the chat happens after the customer messages first, so it is free. The paid messages are usually reminders sent a day later (utility), and promotions (marketing), which cost more. Meta publishes the rate card by market, so we read the current Singapore rates with you and estimate the month.
- Design reminders as utility templates with clear transactional wording, because Meta decides the category and marketing wording is billed at the marketing rate.
- Send reminders while a window is still open where the booking was made recently, so they fall inside the free period.
- Keep promotional sends small, opted-in and targeted rather than broadcast to every number you hold.
Meta's own WhatsApp Business Platform pricing page is the source to check before each budget review, since rates are updated from time to time.
Do Singapore's Do Not Call rules apply to WhatsApp messages?
Yes, for marketing. The PDPC's Advisory Guidelines on the Do Not Call Provisions say the DNC Provisions apply to every way a marketing (“specified”) message reaches a Singapore telephone number, naming data applications such as WhatsApp that use that number.
The same guidelines describe three registers (No Voice Call, No Text Message and No Fax Message) and a 21-day rule: before sending a marketing message to a Singapore number, the sender must hold a Registry check result obtained within the previous 21 days, unless the person has given clear and unambiguous consent in written or other accessible form. Marketing messages must also identify the sender and say how to contact them.
Not every WhatsApp message is marketing. The guidelines exclude, among other things, messages whose sole purpose is to facilitate, complete or confirm a transaction the recipient already agreed to, and warranty, recall or safety information about something they bought. A reminder for an appointment the customer booked sits in that transactional space; a “20% off this weekend” blast does not.
Here is what our build does to support you. Each contact carries a record of where and when they opted in and what they agreed to receive. Marketing templates can only go to contacts marked for marketing consent, or to numbers with a current DNC check result stored against them. A “STOP” keyword flips the contact to no-marketing immediately. Whether a particular message counts as marketing is a legal judgement, so please have your own lawyer or DPO confirm your templates.
How should customers opt in to WhatsApp messages?
Ask clearly, record it, and make it specific. Meta's WhatsApp opt-in rules require businesses to get the person's permission before messaging them, to state the business name they are opting in to, and to comply with applicable law.
The simplest opt-in is the customer messaging you first, for example by scanning a QR code at your counter or tapping a WhatsApp button on your website. That opens a conversation for the enquiry. Reminders and marketing need more: a checkbox on the booking form, a tap on a clear “Yes, send me reminders” button in the chat, or a signed form at the counter.
Keep separate choices for separate things. Many businesses ask once for appointment reminders and once, optionally, for promotions. That split helps with the PDPC's consent rules and with Meta's quality ratings, because people who never asked for promotions are the ones who block and report.
- Show your business name and what messages they will get, next to the opt-in control.
- Store the date, time, channel and wording shown at the moment of opt-in.
- Confirm the opt-in with a short welcome message that includes how to stop.
- Honour STOP or UNSUBSCRIBE instantly, and log the change.
- Never import a purchased list or numbers scraped from a directory.
For consent wording across your whole website, our PDPA-compliant website guide for Singapore covers forms, notices and cookie choices.
What does a good WhatsApp booking flow look like?
A good booking flow takes three or four taps, checks real availability, and ends with a confirmation the customer can screenshot. Anything longer and people give up and call.
We design it around WhatsApp's interactive elements rather than long typed questions. The bot greets the customer, offers a short list of services, asks for outlet if you have several, then shows the next available slots as buttons or a list. The customer taps one, confirms their name, and receives a confirmation with date, time, address and a map link.
Behind the scenes the bot reads and writes your real calendar. That might be Google Calendar, Microsoft Outlook, a booking tool with an API, or your own database. Slots are held for a few minutes while the customer confirms, so two people cannot grab the same one. If your staff also book by phone, they book into the same calendar and the bot sees it.
Rescheduling
The reminder carries Reschedule and Cancel buttons. A tap shows new slots, updates the calendar and frees the old one without staff involvement.
Deposits
Where you take a deposit, the bot sends the payment link or PayNow details your business already uses and holds the booking until staff or your system mark it paid.
Multi-outlet
Outlet choice filters staff, services and slots, and each outlet's team sees only its own hand-offs.
Out of hours
The bot keeps booking overnight, and anything it cannot handle is queued with a clear message about when staff will reply.
How does a WhatsApp chatbot hand chats to staff?
The chat moves to a shared inbox where a named staff member picks it up, sees everything the bot already collected, and replies from the same business number. The customer never has to repeat themselves or switch channel.
Hand-off triggers are agreed with you in writing: the customer types “staff” or “agent”, the bot fails to understand twice, the topic is on your always-human list (complaints, refunds, medical or legal questions), or the request is outside booking rules, such as a group of twenty. While a person owns the chat, the bot stays silent so two voices do not talk over each other.
Where that inbox lives depends on your tools. It can be a lightweight web inbox we build, a helpdesk you already pay for, or your CRM. Staff can mark a chat resolved and hand it back to the bot. Each hand-off records a reason, and after a few weeks those reasons show which flows deserve automating next.
Meta's 24-hour window applies to staff replies too. If a customer went quiet and the window has closed, staff need an approved template to reopen the chat, so we prepare a small set of neutral follow-up templates at launch.
Connecting a WhatsApp chatbot to your CRM, calendar and accounts
Integration is where a custom WhatsApp chatbot in Singapore earns its price. Each new contact, booking and hand-off lands in the system your staff already use, so nobody copies details from a phone into a spreadsheet.
Common links we build: new enquiries created as leads in your CRM with the chat transcript attached; bookings written to Google or Outlook calendars; paid deposits matched in your accounts; customer tags updated when someone opts in or out. Where no API exists, a shared Google Sheet can act as a simple bridge for a first version.
We keep integrations narrow. The bot gets exactly the permissions it needs, such as creating a booking or reading one customer's upcoming slot, rather than full database access. Every call is logged. If an integration fails, the bot tells the customer a person will confirm and alerts your staff rather than pretending the booking went through.
- CRM: HubSpot, Zoho, Salesforce or a custom CRM through their APIs.
- Accounting: invoice or payment status from Xero; see our Xero integration page.
- Calendars: Google Workspace or Microsoft 365.
- Your own systems: a booking database, POS or member portal through a small secure API.
Should your WhatsApp bot use AI or fixed menus?
Use fixed menus for anything that changes money or time (bookings, cancellations, payments) and add AI only for open questions where your approved documents hold the answer. That mix keeps the parts that must be exact under strict control.
A menu-only WhatsApp chatbot is predictable and cheap to run: every path is designed and tested. Its weakness is the customer who types a full sentence instead of tapping a button. A retrieval-based AI layer helps there. It reads the question, searches your service list, policies and FAQs, and replies from them, with a hand-off when it is unsure.
Singapore customers mix English, Singlish and sometimes Chinese in one message. We test the AI layer on real messages from your existing chats before launch, set a cautious confidence threshold, and never let the AI confirm a booking by itself; it hands over to the booking flow. Model usage is billed by the model provider to your account, on top of Meta's charges.
If the AI part is the main job, for example a policy assistant for staff, a separate custom AI chatbot on your website or Telegram may fit better, and it can share the same knowledge base.
How much does WhatsApp chatbot development cost in Singapore?
With us, a WhatsApp chatbot starts from US$600 for one number and one main flow, delivered in about 2 to 4 weeks. Other freelancers and agencies quote across a wide range; the spread comes from the scope items below, not from WhatsApp itself.
Think in three layers. First, the build fee: flows, integrations, hand-off inbox, consent records, testing and handover. Second, Meta's charges for delivered templates, billed to your own business account. Third, small running costs for hosting the webhook server and, if you add AI answers, model usage. We show all three in the quote so there are no surprises in month two.
- Number of flows: bookings alone is quicker than bookings plus orders plus promotions.
- Live integrations: each system the bot reads or writes adds build and testing time.
- Outlets and staff roles: routing chats by outlet or department adds logic and inbox permissions.
- AI answers: document preparation, retrieval tuning and mixed-language testing.
- Consent tooling: DNC check storage, marketing segments and opt-out handling.
- Migration: moving templates and contacts from a BSP inbox adds careful data work.
All starting prices are on our pricing page. If WhatsApp is one part of wider back-office automation, see AI automation services for Singapore.
What do you need to set up the WhatsApp Business Platform?
You need a Meta Business portfolio in your company's name, a phone number that will be dedicated to the platform, a display name that matches your business, and a payment method on the WhatsApp Business Account for Meta's charges. We guide each step on a screen-share while you stay the owner.
Business verification on Meta asks for documents that show your legal business name and address. It can take some days, so we start it on day one while we design flows. We are added as developers on your app with limited roles; nothing is registered under our names.
Decide early which number to use. A fresh number keeps the platform separate from any staff phone. If you want to keep a number customers already know, we check the current migration options with you before touching it, because a careless move can interrupt your existing chats.
Templates need Meta's approval before use. We draft them with you: booking confirmation, reminder, reschedule notice, a follow-up for closed windows, and any marketing templates you plan. Clear, specific wording tends to be approved faster and categorised correctly.
How to choose a WhatsApp chatbot developer in Singapore
Pick the developer who asks about your calendar, your consent records and your hand-off process before talking about features. A slick demo on a sandbox number tells you little about what happens with your real bookings.
Ask every shortlisted provider, local or remote, the same questions in writing and compare the answers side by side:
- Will the Meta Business portfolio, WhatsApp Business Account and number be in our name?
- Which messages will be templates, which category will each fall into, and what will they cost per month at our volume?
- How are opt-in, opt-out and DNC checks recorded?
- What happens when an integration is down?
- Where are chat logs stored, for how long, and who can read them?
- How do our staff edit replies, add services or change opening hours without a developer?
- What does handover include, and how is our access removed from yours?
If you are also weighing a solo local freelancer against a small remote team, our freelance developer guide for Singapore sets out the handover and continuity questions.
Red flags in WhatsApp chatbot proposals
The loudest red flag is any offer to message people who never opted in, or to send bulk messages through unofficial tools that automate a normal WhatsApp account. Meta can restrict or ban numbers used that way, and it ignores the PDPC's rules.
- The number or Meta account registered to the developer, so leaving means losing your number.
- “Unlimited messages” bundles that hide Meta's per-message charges inside a monthly fee.
- Promises that every message will be free, or that templates are never needed.
- No plan for opt-out keywords or consent records.
- Uploading a bought contact list as a “quick start”.
- No hand-off route, or a hand-off that just says “please call us”.
- Flows that confirm bookings without checking the real calendar.
Meta monitors quality signals such as blocks and reports, and a poorly targeted campaign can lower your number's quality rating and messaging limits. Sending less, to people who asked, is the dependable way to keep the channel healthy.
Working with a WhatsApp chatbot team in India from Singapore
India runs two and a half hours behind Singapore, so nearly your whole working day overlaps with ours: your 10 am stand-up is our 7:30 am, and a 5 pm check-in is 2:30 pm for us. WhatsApp builds happen entirely in cloud accounts, which suits remote work.
Week one: a video call to map your current chat traffic and pick the first flow, a written scope and quote within about two working days, then Meta business verification started in your name. We draft templates and a flow diagram you can mark up. Week two: a test number connected to a staging server, your staff trying bookings from their own phones, and the calendar link wired in. You get short progress notes on WhatsApp every couple of days, in English or Hindi if anyone on your side prefers.
Quotes and invoices are in USD and issued from India. You can pay by Wise (convenient from an SGD balance), international bank wire or PayPal, on the milestone schedule in your quote. Nothing is billed before written approval. How you treat overseas invoices for tax is a question for your accountant.
What we do not do: visit your outlet, install hardware, or staff your inbox. If you need someone on-site to train a front desk in person, pair us with your own operations lead, who runs the session with our recorded walkthrough.
Who owns the WhatsApp number, templates and data?
You do. The Meta Business portfolio, WhatsApp Business Account, phone number, templates, webhook server, code repository and contact database are all created in your name, and our access is removed at handover unless you keep us on.
That matters more on WhatsApp than on most channels. The number is how customers reach you; if it belongs to a vendor, switching vendors can mean a new number and lost chat history. Keeping ownership with you from day one avoids that trap.
The handover pack covers how to edit bot replies, add a service or outlet, submit a new template to Meta, read the hand-off report, export consent records, and rotate access tokens. A screen recording walks your staff through the inbox. Fixes are free for two months after launch; after that care starts from US$120/mo, or your own developer can take over. Anything beyond this is agreed in your written quote and our terms.
Worked example: an aircon servicing business in the north-east
This is a hypothetical scenario to show how the pieces fit, not a client story. Say a five-van aircon servicing business based near Hougang receives most enquiries on WhatsApp, and two office staff spend their mornings matching customers to van schedules.
The first WhatsApp chatbot flow takes bookings. The customer picks general servicing, chemical wash or repair, enters their postal code and unit count, and sees available half-day slots drawn from the van calendar, filtered by area. On confirmation, the booking lands in the shared calendar and the customer gets a summary with the technician's arrival window.
The day before, a utility template reminds the customer, with buttons to confirm or reschedule. Repair requests and anything with photos of leaks go straight to staff, since pricing a repair needs a person. Promotions such as a servicing contract are sent only to customers who ticked the marketing box, after a DNC check where needed.
Scope like this would start from US$600 and fit the 2 to 4 week range. Meta's charges would mostly be reminder templates. Success would be measured plainly: fewer morning calls, fewer missed slots, and a weekly hand-off report showing what customers still ask staff for.
WhatsApp chatbot checklist for Singapore businesses
Answer these before you brief any developer; they turn a vague request into a quote you can compare line by line.
- Which one flow wastes the most staff time today?
- Which number will the bot use, and who owns it?
- Where do bookings or leads live now (calendar, CRM, spreadsheet)?
- Which topics must always go to a person, and who covers them?
- How do customers opt in today, and do you have records?
- Will you send marketing messages, and to whom?
- Rough monthly chats, bookings and reminders.
- Languages customers write in, and who approves non-English replies.
- How long chat logs should be kept under your data policy.
- Budget range and a launch date you care about.
Send the answers on WhatsApp or through our contact page and you will receive an itemised quote in about two working days.