Two organisations can both ask for a WhatsApp assistant and need very different projects. One wants approved answers to routine questions. Another wants the assistant to identify a customer, check an order and create a support case. The channel is the same; the work behind it is different.
A useful quote separates the cost of building the service from the cost of operating and maintaining it. Start by defining the conversations it should handle, the records it needs and what happens when it cannot answer.
Define the first responsibility
“Answer customer questions” is too broad to price reliably. A better brief identifies the audience, recurring questions, approved answers and stopping points. Include examples that should lead to a person, such as a disputed account record or a request outside the service’s scope.
An illustrative first version might explain required application documents and collect details for a staff member. Adding authenticated application-status lookups changes the work: access checks, system connections, error handling and testing become part of the project.
Budget for knowledge preparation and integrations
An assistant needs usable source information. Scattered PDFs, conflicting policies and outdated FAQs require preparation and an owner who can approve updates. The cost depends on what must be organised and how often it changes, rather than the number of files alone.
Connections to customer records, ticketing or order systems add a separate set of questions. Is an API available? Who can authorise access? Which records may the assistant read or update? How should it behave during an outage? These details should be established before promising a fixed implementation scope.
Separate messaging charges from the complete service cost
Meta’s published WhatsApp Business Platform pricing depends on the recipient market and message category, with rules for free service messages and other exceptions. Use the current rate card for the intended traffic; do not assume every message is billed identically (WhatsApp Business, accessed 26 October 2026).
That platform charge is only one budget item. Depending on the chosen setup, there may also be a messaging-provider or inbox subscription, automation hosting, model usage and storage. A free message category does not make the whole assistant free to operate.
Estimate the work inside each conversation
A short FAQ exchange and a conversation involving several document searches or system lookups can consume different resources. Ask a supplier which usage is included, how overages are measured and what assumptions support the estimate.
Use low, expected and busy-period traffic scenarios. Record the audience, message mix, typical conversation length and number of connected actions for each. A single monthly message count without those assumptions can conceal important differences.
Include the human handoff and maintenance
Someone needs to receive difficult conversations, understand the context and own the response. Define the receiving team, its actual availability and how users learn what happens next. The cost of staff handling remains part of the operating picture.
After launch, source information changes, integrations need attention and answers need review. Agree who monitors failures, maintains approved content, tests changes and supports incidents. Clarify which work is included in support and which changes require a new scope.
What to bring when asking for a quote
Prepare a short brief with your common enquiries, approved information, target languages, audience locations, expected traffic, connected systems and escalation owner. Ask for implementation costs, recurring charges, usage assumptions, account ownership, support scope and handover arrangements to be shown separately.
The useful question is what it will cost to run a defined service well. A focused pilot gives both teams a smaller set of assumptions to test before expanding it.
Explore Spiritus WhatsApp AI assistants, review our engagement approach or bring your brief to a conversation.
Source
WhatsApp Business (accessed 26 October 2026), Business Platform Pricing. Supports the platform charging structure; it is not evidence of a Spiritus price or total implementation cost. The other cost categories are a project-scoping framework, not a measured market-price study.