A WhatsApp automation quote usually mixes four different businesses into one number. Meta charges for messages, a platform charges for software, an implementation team charges for building the workflows, and your own team pays for the ongoing operation. Until those layers are separated, a cheap quote and an expensive quote cannot be compared.
This guide gives you the layers, a formula and a calculator. It does not publish per-message rates or a fixed project price, because Meta’s rates vary by market and category, platform pricing varies by provider, and the build depends on how many systems the workflow must touch.
Layer 1: Meta message charges
WhatsApp Business Platform messages are priced by category. Marketing, utility and authentication templates are charged differently, and customer service conversations follow a separate rule set. Meta has changed its pricing model before, so treat the official pricing page as the only current source of truth.
The cost driver is not the total number of chats. It is the number of billable template messages by category and market, plus any charges that apply to the service window. A support inbox that mostly replies inside an open conversation has a different cost profile from a campaign that sends a template to thousands of opted-in contacts.
Layer 2: platform and provider fees
The platform is the shared inbox, automation builder, template manager and reporting layer. Providers price it in different ways: per agent, per number, per conversation, per message, by tier, or as a bundle with implementation. Ask which unit is charged and what happens when usage crosses a tier.
Also ask who owns the number, what happens to conversation history on exit, and whether the provider supports your countries and payment methods. A low platform fee is expensive if leaving means rebuilding both.
Layer 3: implementation and integration
This is usually the largest one-off line. It includes discovery, template writing, conversation and workflow design, integration with your order, CRM, inventory or accounts systems, testing, training and documentation.
Integration effort depends on how many systems must agree on the same customer and order. A shared inbox is one project; a flow that creates a lead, reserves stock, sends a payment link, confirms dispatch and writes back to accounts is another.
Include a contingency line for change requests. Template rules, API behaviour and internal processes rarely stay fixed through a build.
Layer 4: operations
The monthly bill continues after launch. Someone must own template quality, opt-in evidence, agent access, escalation rules, reporting and the relationship with the provider. Agent seats may grow with the team. New products and seasonal campaigns create new templates and new flows.
Internal time is a real cost even when no invoice arrives. If the owner is a operations manager spending several hours a week on the channel, that time belongs in the budget.
The formula
One-off cost = discovery + workflow and template design + integration build + testing + training + documentation + contingency.
Monthly cost = Meta message charges + platform fee + support and maintenance + internal owner time.
Three-year cost = one-off cost + (monthly cost multiplied by 36) + planned change budget + exit or migration reserve.
Compare vendors on the three-year figure; a low build fee can hide a high per-agent fee.
Calculator inputs
- Monthly template messages by category. Count marketing, utility and authentication separately, because each is priced differently.
- Service conversations. Estimate how many customer-initiated conversations need a reply and whether they fall inside a free or charged window under the current rules.
- Agent seats. Count the people who need a login, including supervisors and part-time staff.
- Systems to integrate. Order management, CRM, inventory, accounts, helpdesk and payment links each add build and testing work.
- Workflow count and exceptions. A simple notification flow is not the same as a flow with approvals, refunds and failed-payment handling.
- Languages. Bangla and English templates, plus any regional language, need separate review and approval.
- Internal owner hours. Estimate weekly hours multiplied by a loaded rate and add them to the monthly figure.
A calculation you can complete
Let M, U and A be the number of marketing, utility and authentication template messages you expect to send in a month. Let pM, pU and pA be the per-message rates your provider quotes for your market. Then:
Monthly message charge = (M × pM) + (U × pU) + (A × pA).
Add the platform fee, support fee and internal owner cost to reach the monthly run rate. Multiply by 36, add the one-off build and the change budget, and you have a three-year comparison. If a provider quotes per conversation instead of per message, replace the formula with conversation volume multiplied by the applicable rate, and check which conversation categories are included.
Budget worksheet
- Meta message charges: basis — monthly volume by category multiplied by current rates. Owner — marketing or support lead. Evidence — official pricing page and volume forecast.
- Platform fee: basis — seats, numbers or conversations, confirmed in writing. Owner — operations lead. Evidence — contract and tier schedule.
- Implementation: basis — written scope, integration list and test plan. Owner — project lead. Evidence — acceptance criteria and change log.
- Training and documentation: basis — staff groups and sessions. Owner — support lead. Evidence — training record and runbook.
- Support and maintenance: basis — monthly retainer or internal hours. Owner — operations lead. Evidence — support log.
- Internal owner time: basis — weekly hours multiplied by loaded rate. Owner — business owner. Evidence — time log.
- Contingency: basis — agreed percentage of build cost. Owner — finance lead. Evidence — approved change requests.
- Exit reserve: basis — estimated migration and data export effort. Owner — operations lead. Evidence — contract exit terms.
Cost traps to check before signing
- Seats included in the pilot but charged later. Confirm the price at your expected team size, not the pilot size.
- Template revisions billed as change requests. Agree how many rounds are included.
- Integration assumptions. “We connect to your CRM” is not a specification. Ask for the exact objects, fields and failure handling.
- Reporting lock-in. Confirm you can export conversation and campaign data in a usable format.
- Number ownership. The business should own the number and the verified business profile, not the agency.
90-day plan
- Weeks 1–2: map the current WhatsApp process, volumes and handoffs.
- Weeks 3–4: write the workflow specification and integration list.
- Weeks 5–7: build templates and the first workflow, then test with staff.
- Weeks 8–9: run a controlled pilot with a small customer group.
- Weeks 10–11: fix exceptions, train agents and publish the runbook.
- Week 12: review cost per conversation, response time and failure rate.
If you need help costing and building the workflow, start with Business Automation. The pricing page explains how discovery and build are separated. For the platform choices behind the cost, read WhatsApp workflow automation options compared.
Sources
- Meta, WhatsApp Business Platform pricing, accessed 17 November 2026.
- Meta, WhatsApp Cloud API documentation, accessed 17 November 2026.
- WhatsApp Business, Business Messaging Policy, accessed 17 November 2026.
- Meta, WhatsApp Business Platform overview, accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.