There is no single WhatsApp price. There are five cost parts.

1. Implementation

The one-off work to map your requests, agree what is automated, guided or always handled by a person, write and approve the knowledge, build the flow, connect systems where they allow it, and test on real request examples. It grows with the number of workflows, languages, channels and systems involved.

2. Operation

The ongoing work after launch: monitoring, fixing failures, updating approved information when prices, hours or policies change, reviewing handovers and unanswered questions, and a monthly review against the agreed measures. This is the part a self-service tool leaves to your own team.

3. Usage, including Meta’s charges

Usage covers conversation volume and any processing it requires. On the WhatsApp Business Platform, Meta currently charges per delivered template message, not per conversation. The rate depends on the template category (marketing, utility or authentication) and the recipient’s country. Free-form replies inside the 24-hour customer service window are not charged, and utility templates sent inside an open window are also free. Meta publishes rate cards, offers volume tiers for utility and authentication messages, and changes rates only at the start of a quarter.

• Charged: delivered template messages, by category and country
• Not charged: replies inside an open customer service window
• Lower rates with volume: utility and authentication only
• Check current rates on Meta’s official pricing page before you budget

4. Software vendor fees

If the workflow reads from or writes to your booking, clinic, order or CRM system, the vendor may charge for API access or require a higher plan. These fees are set by the vendor and should appear as their own line so they are not mistaken for the automation service.

5. Changes

New workflows, new channels, new branches or a new system all change the scope. Agree in advance how changes are requested, estimated and approved. Small knowledge updates are usually part of operation; new flows are usually a change.

Assumptions to bring to a quote

Cost estimates are only as good as their inputs. Bring rough numbers rather than waiting for perfect ones.

• Monthly customer conversations, by channel
• How many messages you start outside the 24-hour window
• Countries your customers message from
• Systems the workflow must read from or write to
• Languages and branches
• Who on your team approves and reviews