What a WhatsApp Business API implementation includes

Most WhatsApp quotes people show us have two lines: "chatbot implementation" and a price. With that it's impossible to compare providers, and impossible to know what you're getting.

This is the complete scope of a properly done implementation. It serves two purposes: knowing what to ask for, and spotting what's missing from the proposal in your hand.

1. Onboarding and account ownership

The first line item, the most boring, and the one that decides whether the project is yours or rented.

• A Meta Business account in your company's name. Not the provider's. Meta documents the structure in WhatsApp Business accounts.
• Business verification with Meta, with tax and address documentation.
• An approved display name. Meta checks it matches the real business, and rejects it when it doesn't.
• Number onboarding, whether new or migrated from the app. If it's migrated, see migrating without losing history.
• Access handed over in your name, with at least two administrators.

How to spot it's missing: if the proposal doesn't mention business verification or display name, or if onboarding is resolved "in minutes", you aren't buying the official platform. It's explained in official API vs unofficial.

2. Conversation design

The part that determines whether the bot helps or annoys, and the most underestimated.

• A map of your customers' real intents. Not the ones we assume: the ones already arriving in your WhatsApp today. You get those by reading real conversations, not in a meeting.
• The flows, with their exits. Every flow needs a door to a human, and that door is what separates a useful bot from one people hate.
• Escalation rules. When it goes to a human, to whom, and during what hours.
• What the bot will NOT do. Defining this up front avoids 80% of the arguments later.
• Out-of-hours and holding messages. Sounds minor, gets used the most.

The underlying choice between flow-based and AI bots is in AI chatbot vs flow chatbot.

3. Templates

What almost no quote breaks out, and it's real, recurring work.

• Writing the templates by category (utility, marketing, authentication), because the category determines the cost.
• Submission for review and rejection handling. Meta rejects, and you need to know why and how to fix it. The approval guide covers it.
• Sample values for every variable, which is what avoids half the rejections.
• Who maintains templates afterwards. It isn't a one-off deliverable: templates get paused, degrade and need replacing.

How to spot it's missing: ask how many templates the scope includes and who responds if Meta rejects one. If the answer is vague, you'll be paying for it separately.

4. Integration

• With which system. CRM, ERP, your calendar, your store. Each integration is a project, not a checkbox.
• How identity resolves. WhatsApp gives you a phone number; your system has contacts. What happens when the number doesn't exist in the CRM is the first business rule to write down, and left to the default you end up with duplicates. For Salesforce it's in integrating WhatsApp API with Salesforce.
• Where history lives. The API has no inbox: history sits wherever you store it.
• Consent logging, with date and source. It's what protects you from a report.

5. Operations and handover

The line item that separates a delivered project from an abandoned one.

• Training for the team that will handle conversations. Without it the bot works and nobody answers what it escalates.
• Flow documentation so somebody else can modify them.
• Who watches the quality rating and how often. It's the indicator that predicts a block, and we review it in the WhatsApp risk audit.
• A volume ramp-up plan. Messaging limits start low. Sending everything on day one starts you with a poor rating.

6. What's always billed separately

So it isn't a surprise:

• Meta's conversation usage. Meta charges it, not the provider, and it continues month after month. Anyone who doesn't mention it didn't quote you the whole thing.
• The platform or inbox your agents use to handle conversations.
• Flow changes after the initial scope.

Five questions to compare proposals

1. Will the account be in my company's name, with my company as owner?
2. How many templates are included and who handles rejections?
3. What exact integration is inside the scope?
4. How do I see my Meta conversation usage?
5. If I stop working with you, do I keep the number and the account?

The fifth protects you most. The expanded questionnaire is in how to evaluate a WhatsApp automation agency.

We implement as an authorized Meta Tech Provider with the account in the client's name, precisely because point 1 is the one nobody can fix afterwards. If you want us to review a quote you already have, or build the scope for yours, that's what our WhatsApp automation service does. And if you're not sure automation is right for you yet, start with is it worth automating WhatsApp.