WhatsApp Business Chatbot Development

What the official API gives you that a scraper does not

There is a category of cheap "WhatsApp automation" built on unofficial libraries that drive the consumer app. It works until Meta bans the number, which it eventually does, usually at the worst possible moment. We only build on the official WhatsApp Business API.

The official platform also unlocks things the unofficial route cannot do:

• Interactive buttons and list menus, which cut misunderstandings dramatically compared to free-text-only flows.
• Product catalogue browsing inside the chat.
• Message templates for anything you initiate, pre-approved by Meta.
• Broadcast to opted-in customers without the 256-contact limit of the consumer app.
• A green tick on verification, which measurably improves reply rates.
• Payment links and order status inside the conversation.

How Meta actually bills you

This is the number nobody quotes and the one that decides whether the project works economically. Meta charges per 24-hour conversation window, not per message, and the rate depends on who started it and why.

The design consequence is specific: a conversation that takes twelve messages to resolve costs exactly the same as one that takes three. Optimise for resolving the question inside the window, not for terseness. A bot that answers in four words and forces the customer to come back tomorrow costs you two windows instead of one.

Meta revises these rates. Before you commit we model your expected monthly cost at your actual volume, and we show the working rather than quoting a number.

Getting through Meta verification

Before a single message sends, you need a verified Meta Business account and an approved display name. This is where projects stall, and it is almost always a documents problem rather than a technical one.

You will need business registration matching the name you want displayed, a website that clearly belongs to that business, and a phone number you control. Display names that are generic, or that do not match the registered entity, get rejected. We handle the submission, but the documents have to be yours and they have to be consistent.

Budget one to two weeks for this in parallel with the build. Occasionally it is same-day; occasionally it takes three rounds.

Writing for how Indians actually message

Real WhatsApp messages are not clean sentences. They are code-mixed — Hinglish, Marathi typed in Roman script, English with Gujarati word order — full of abbreviations, voice notes and single-word replies.

A bot trained on tidy English fails on the first "kitna hoga bhai". We build language detection that handles Hindi, Marathi, Gujarati, Tamil, Telugu, Bengali and Kannada alongside English, and we specifically test against real transcripts from your own inbox rather than invented examples. Voice notes get transcribed and answered as text, which customers find slightly magical the first time.

What we hand over

A live agent on your verified number, template messages approved, catalogue connected if you have one, human handover to your team's phones, lead capture into your CRM, opt-in management for broadcast, and a dashboard of conversations, resolution rate and cost per conversation.

The cost dashboard matters. It is the only way to see whether a change to the flow made the bot cheaper or more expensive, and it is the first thing most suppliers leave out.