“How much is a WhatsApp chatbot?” needs an earlier question: what will it do, with which systems and for whom? A question-and-answer menu differs from a service that reads order status and hands a conversation to staff. Even with an agreed scope, build fees differ from messaging, platform and ongoing operation.
Request three clear groups: setup costs, recurring subscriptions and usage-dependent charges. One price cannot be generalized across Egypt and Gulf markets or every message type. Establish who bills you and which units they count before selecting the implementation company.
Write the task you are purchasing
In a fictional spare-parts distributor, customers need order status, opening hours and an employee when something differs. Define whether the system answers from fixed content, reads order status through an API, or can change anything. These are scope decisions; technology names alone do not price them.
Record languages, expected message types and the channel through which staff receive handovers. WhatsApp integration is not automatically a shared inbox, ticketing system or AI service. Each may be a separate proposal component. Ask the provider to identify the product or work delivering each capability.
A budget worksheet separating components
| Item | Required description | Billing question |
|---|---|---|
| Account and channel setup | Inputs, responsibilities, number setup and permissions for the proposed solution. | Is there a separate setup fee, and what completes it? |
| Conversation flows and content | Included questions, states, languages and templates. | What does setup cover, and how are later changes priced? |
| System integration | Data read or changed, test environment and integration limits. | Does the fee build a missing API or connect to an existing one? |
| Platform and employee inbox | Subscription name, team seats and required capabilities. | Who invoices it, and are there add-ons or usage limits? |
| WhatsApp messages | Usage categories, markets and assumed message volumes. | How are current rate cards and intermediary charges applied? |
| AI services, if used | Service, task boundaries, knowledge sources and measurement. | Is usage included up to a defined limit or billed separately? |
| Operation and support | Monitoring, updates, incident handling and administrative handover. | What recurs, and what constitutes additional work? |
For every cost, record the charging entity, frequency, unit, currency and underlying assumption. Leave unknown costs explicitly unknown and request clarification. Do not convert them to zero to produce a reassuring total.
Customer count is not billable-message count
The official WhatsApp Business page relates platform pricing to delivered messages, recipient markets and message categories, referring to current rate cards. Customer or conversation count alone cannot determine the bill. Request a calculation showing the messages, categories and assumptions included.
Do not reuse old rates or exemptions without checking them when contracting. A platform provider or intermediary may add its own charges; separate them from the underlying WhatsApp fees. This article assumes no category is free and supplies no fixed message price or guaranteed free allowance.
Distinguish an available connection from integration development
The distributor's order system may provide a ready API, or only a staff screen. In the latter case, “system integration” is insufficient without identifying who enables data access and how unauthorized access to another person's order is prevented.
Request test data, a successful lookup and an unavailable-data scenario. Define what the bot says when it cannot verify a result. Confidently showing an incorrect status is not preferable to a clear follow-up route. Reading order data also does not justify giving the bot permission to change orders.
Messaging policy affects the workflow
WhatsApp's policy includes permission to contact recipients, respecting opt-outs and approved templates where required. It distinguishes replies inside the customer-service window from messages outside it. Ask how the solution handles these cases and who prepares content, approves templates and monitors their status. A messaging window is neither the implementation company's support period nor proof of a particular price.
Review your activity and use case against current policies, and define a clear escalation route when automation is insufficient. Do not assume account setup or template approval happens immediately. Identify external dependencies, the company's commitments and what can be tested while those steps remain pending.
Test the expected bill against the actual workflow
Use one journey where a customer asks about an order and requests an employee, plus another where your company initiates a message. Ask the provider to explain the components used, expected outgoing messages and potentially billable items. Repeat for integration failure or retry. The aim is to expose hidden charges and dependencies, rather than guess an amount.
Agree how usage can be monitored, how alerts work near a limit chosen by your organization and who may increase a paid service's budget. At handover, request an account, subscription, flow and template register with the process for ending or transferring service under available terms.
For team responsibilities, see the CRM guide's distinction between licences and implementation. When discussing business chatbot development, begin with the task and component worksheet. Compare what will work and what remains payable, rather than a starting price disconnected from operation.
Sources and dates
The WhatsApp Business Platform pricing page and messaging policy were opened on 3 November 2026. The policy carries an update date of 23 September 2026. Changeable rate tables and exemptions are not reproduced here. The example and budget are illustrative guidance. The text was prepared with AI assistance and review of its information and sources.
