What does a WhatsApp chatbot developer build?
A WhatsApp chatbot developer builds software that sits between your WhatsApp business number and your own systems. When a customer messages you, Meta sends that message to the bot's server; the bot decides what to reply, looks up data where needed, and sends a response back through the API, all in a second or two.
The visible part is the conversation: menus, buttons, lists, product cards and replies. The larger part is invisible: the server that receives messages, the logic that tracks where each customer is in a flow, connections to your stock, bookings or CRM, message templates approved by Meta, and a dashboard where your staff can see chats and take over from the bot.
At BtechWaleTech, another of us leads the AI and data side, including answers drawn from your documents; one of us builds the server, integrations and admin screens; the third of us maps your processes into conversation flows and manages template approvals and testing. You deal with all three directly on WhatsApp, which is fitting for this kind of project.
- Webhook server that receives and sends messages
- Conversation flows with buttons, lists and free-text handling
- Integrations with your sheets, CRM, billing or calendar
- Approved message templates for updates and reminders
- Staff inbox with human takeover
- Reports on chats, conversions and drop-offs
WhatsApp Business app or Business API: which do you need?
The free WhatsApp Business app is for a person answering chats on a phone. The WhatsApp Business Platform, usually called the Business API, is for software answering chats. You need a WhatsApp chatbot developer only for the second.
The app gives you a business profile, catalogue, greeting and away messages, quick replies and labels. It works well for a small shop handling chats by hand. It cannot run real bots, connect to your systems, or let many staff share one number with proper routing.
The API has no phone app of its own. Messages arrive at a server, which is why a bot, a shared inbox or an integration has to be built or bought. It adds interactive buttons and lists, approved templates for messages you send first, and higher sending limits as your quality stays good. Meta has also introduced an option for some numbers already on the Business app to connect to the API while keeping the app; we check whether it applies to your number during setup.
Stay on the Business app when
One or two people handle a manageable number of chats and replies do not need data from other systems.
Move to the API when
Chat volume is growing, several staff share the number, or replies depend on orders, bookings or stock.
Which WhatsApp chatbot use cases actually pay off?
The bots that earn their cost do repetitive work customers already try to do on WhatsApp. Start by reading a week of your chats: the top five questions usually point straight to the first bot.
Order status, appointment booking, fee and payment reminders, price and availability questions, and lead qualification are the most reliable wins for Indian businesses. Each replaces a staff member typing the same answer many times a day, and each can be measured: fewer calls, faster replies, more completed bookings.
Weaker use cases are the ones that try to replace conversations customers want with a person, such as complaints, negotiations or complex medical questions. Those should reach a human quickly. A good WhatsApp chatbot developer designs the handover as carefully as the automation.
- Where is my order? Live status from your system
- Book, reschedule or cancel an appointment
- Fees, EMIs and invoices due, with a payment link
- Price, stock and availability questions
- Lead questions before a sales call
- Brochures, menus, timetables and location on request
Menu bot or AI chatbot on WhatsApp: which should you build?
Use menus and buttons for anything with a fixed set of steps, and AI for questions that are phrased a hundred ways but answered from the same material. Most good bots mix the two.
A menu-driven bot is predictable and cheap to run: customers tap options, the bot follows a flow, nothing is invented. It suits bookings, order tracking and payments. An AI bot uses a language model to understand free text and write answers from your price list, policies or course details. It handles “do you deliver to Kharar on Sunday?” far better than a menu can, but it needs guardrails: answers limited to your content, a confidence check, and a handover to staff when unsure.
Meta's rules matter here. Since 15 January 2026 the WhatsApp Business Platform no longer allows general-purpose AI assistants whose main purpose is open-ended chat. Bots that use AI to serve your own customers for your own business, such as support, bookings and sales questions, remain allowed. We keep every AI bot tied to your business and your content.
For AI projects beyond WhatsApp, see AI agent developer.
WhatsApp chatbot developer cost: what you pay and to whom
Budget for a one-time build and a monthly running cost. With BtechWaleTech the build starts at ₹40,000 (US$600) and covers flow design, the bot server, integrations in scope, template drafting, testing and launch.
Running costs go to others, not to us. Meta charges for template messages you send, at rates that depend on the category and the customer's country. Hosting for the bot server is usually modest for small and mid-sized volumes. If the bot uses an AI model, the provider charges per use, which we keep low by answering common questions from stored replies and calling the model only when needed.
Across the market, quotes for “a WhatsApp bot” vary widely because the term covers everything from a three-button menu to a system tied into billing and CRM. Compare by listing the flows, integrations and running costs each quote includes. Also ask who owns the Meta account and the chat data, because moving later is harder than choosing well now.
Wider AI budgeting is covered on hiring an AI developer.
Since 1 July 2025 Meta has charged per delivered template message rather than per conversation. The charge depends on the template's category and the recipient's country code, and Meta publishes the rates for India.
Three categories matter. Marketing templates, such as offers and announcements, are charged every time and cost the most. Utility templates, such as order confirmations and payment reminders, and authentication templates, such as login codes, cost far less, and utility templates are free when sent inside an open customer service window.
That window is the key to keeping costs down. Each time a customer messages you, a 24-hour customer service window opens, and within it your bot's free-form replies are not charged. When a chat starts from a Click-to-WhatsApp ad or a Facebook Page button, Meta also offers a 72-hour free entry point window after your reply. We design flows so most bot replies fall inside these windows, and templates are reserved for messages the business must start.
- Customer writes first: bot replies free for 24 hours
- Utility template inside the window: free
- Utility or authentication template outside it: charged at a low rate
- Marketing template: always charged, highest rate
- Chat from a Click-to-WhatsApp ad: 72-hour free window after your reply
WhatsApp opt-in rules: how to collect consent properly
Before your business sends anyone a WhatsApp message first, that person must have opted in to hear from you on WhatsApp. Meta's business messaging policy requires it, and ignoring it is the fastest way to get blocked, reported and restricted.
A valid opt-in makes clear that the customer agrees to receive messages from your business on WhatsApp. Good places to collect it: a checkbox on your checkout or booking form, a line on your enquiry form, a QR code at the counter that starts a chat, or the customer messaging you first. Record when and where each opt-in happened, so you can show it if ever asked.
Opt-out matters just as much. Give customers an easy way to stop marketing messages, such as replying STOP, and make sure the bot honours it across all your lists. Old phone numbers from a register, bought databases or numbers collected for one purpose and used for another are not opt-ins. We build the consent record and the opt-out handling into every WhatsApp chatbot rather than leaving it to a spreadsheet.
Message templates: approval, categories and common rejections
Any message your business sends outside the 24-hour window must use a template that Meta has approved. Templates have fixed text with placeholders, such as the customer's name or order number, and optional buttons.
Meta reviews each template and assigns or confirms its category. A template written as a delivery update but containing a discount code may be treated as marketing, which changes its price. Rejections usually come from vague wording, placeholders with no context, content that breaks commerce policy, or asking for sensitive details such as full card numbers.
We draft templates with your team, write them plainly with clear purpose, and prepare Hindi or regional-language versions where your customers need them. Each language is a separate template entry, so plan for the languages you truly use. Keeping a small, well-written set of templates makes approvals quicker and costs easier to predict.
Utility example
“Hi {{1}}, your order {{2}} has been dispatched and should arrive by {{3}}. Reply HELP for questions.”
Marketing example
“Hi {{1}}, our Diwali collection is live. Tap below to see this week's offers.” Charged as marketing every time.
Setting up the WhatsApp Business API in your own name
Your WhatsApp Business account should sit inside your own Meta business portfolio, not your developer's. The number, its quality history, the templates and the payment method for message fees then belong to you.
Setup follows a short list. You create or use your Meta business portfolio, verify the business with documents where Meta asks for it, add a phone number that can receive a verification code, choose a display name that matches your brand, and add a payment method for message fees. The bot then connects through Meta's Cloud API using a system user token, which we generate in your portfolio and store securely on the server.
The official business account badge is granted by Meta at its discretion and is not required to run a bot. Business verification, a clear display name and good message quality matter far more. We walk you through each step on a screen-share call, and you keep admin rights throughout.
- Meta business portfolio with you as admin
- Business verification completed where requested
- Dedicated phone number for the API
- Display name approved
- Payment method for Meta message fees in your name
- Developer access added as a partner or system user, removable any time
Connecting a WhatsApp chatbot to your sheets, CRM and billing
A bot is only as useful as the data it can reach. The biggest difference between a toy bot and a working one is integration with the systems your business already runs.
Common connections we build: Google Sheets for small teams that track orders or leads there; a CRM for lead scoring and follow-up; billing or accounting software for invoices and dues; a booking calendar for appointments; your online store for orders and delivery status; and your website, so a chat can begin from a button with the right context. Payments usually go through a UPI or card payment link sent in the chat, with the bot confirming once the payment is recorded.
Where a system has no API, we look for exports, email parsing or a small custom database as a bridge. If your data lives in scattered spreadsheets, we may suggest a simple admin panel so the bot and your staff read the same numbers. That kind of foundation is also covered on our Python automation page.
Messaging limits, quality rating and how to avoid restrictions
Meta watches how customers react to your messages. If many people block or report your number, its quality rating drops, and Meta can limit how many business-initiated messages you may send or restrict the account.
New accounts also start with a cap on how many unique customers can receive business-initiated messages in a rolling 24-hour period. The cap rises as you send good-quality messages and complete verification. This matters if you plan a large first campaign; a gradual ramp is safer than one big blast.
Protecting quality is simple in principle: message only people who opted in, send what they expect, keep marketing infrequent and relevant, and make opting out easy. We add frequency limits and opt-out checks into the bot, and show you the quality rating in your reporting so problems surface early.
Chat data, privacy and India's data protection law
WhatsApp messages are encrypted in transit, but once they reach your bot server, the data is yours to protect. Under India's Digital Personal Data Protection Act, 2023, your business is responsible for personal data it collects, including chat logs, phone numbers and anything customers share.
Practical steps we take: collect only what each flow needs, avoid asking for sensitive details in chat where a secure form is better, store logs in your own cloud account with access by role, set a retention period so old chats are deleted, and keep AI prompts free of details the model does not need. Health, finance and education bots get extra care over what is stored and who can read it.
If your staff read chats in a shared inbox, give each person their own login so actions are traceable. It helps with customer service as well as compliance.
How to choose a WhatsApp chatbot developer
Choose someone who talks about your customers and costs before technology. A WhatsApp chatbot developer who starts by asking what your top chat questions are, and how many messages you send a month, is thinking about the right things.
Ask for a live bot you can message yourself. Try to break it: type something unexpected, switch language, ask for a human. Then ask the ownership questions: in whose Meta business portfolio will the account sit, where is chat data stored, and can you remove the developer's access without breaking the bot?
Finally, check that the quote separates the build from running costs and states which flows and integrations are included. Vague “unlimited bot” promises usually hide either a platform subscription you will pay forever or limits you discover later.
- A working bot you can test on your own phone
- Account and number in your Meta business portfolio
- Chat data in your database or cloud account
- Opt-in, opt-out and human handover designed in
- Separate estimates for build and monthly running cost
- No promise of unlimited free messages
How long does it take to build a WhatsApp chatbot?
Most WhatsApp bots go live in 2–4 weeks. Meta account setup and verification run alongside design, so the calendar is rarely blocked by code.
Week one: we read sample chats, agree the flows, draft templates and start your Meta setup. Week two: the bot server, main flows and integrations are built on a test number, and your staff try them on their phones. Weeks three and four: AI answers if in scope, the staff inbox, reports, template approvals, a soft launch with a small group of customers, and fixes from real conversations.
Delays usually come from business verification documents, template rejections that need rewording, or integration access to older systems. Starting the Meta side early and having one person on your team who can approve flows quickly keeps the plan on schedule.
Worked example: a diagnostic lab's WhatsApp bot
This is a hypothetical example to show how a WhatsApp chatbot project is scoped, not a client story.
A diagnostic lab with two collection centres gets many chats a day asking about test prices, home sample collection slots and report status. Staff spend hours on repeat answers and reports sometimes go out late.
Version one would include a menu for booking home collection with area and time slot, price answers for common tests drawn from the lab's own list, report-ready notifications as utility templates with a secure download link, and a handover to the front desk for anything medical. Opt-in is collected on the booking form and at the counter by QR code. The build starts from ₹40,000, with a line for the lab software integration.
Most messages would fall inside customer service windows, because patients write first, so monthly Meta fees stay small. Test reports are not stored in chat logs; the bot only sends a link from the lab's own system.
WhatsApp chatbot developer for businesses across India
WhatsApp is how customers reach businesses in every Indian city and town, so our bot projects run fully remote: calls on Google Meet, tests on your own phone, and progress shared, naturally, on WhatsApp.
City pages describe local businesses and what they automate: traders in Delhi and Kolkata, leather firms in Kanpur and Agra, pilgrimage services in Varanasi, Tirupati and Ujjain, jewellers in Thrissur, coaching centres in Vijayawada and tea businesses in Siliguri.
Businesses abroad with customers in India or the Gulf use the same process and are billed in USD through Wise, bank wire or PayPal; see UAE and other countries.