How to Build WhatsApp Chatbots for Agency Clients (No Developer Required)
Here is something true: your clients want WhatsApp automation.
WhatsApp has two billion users. Two billion. That's not a demographic, that's a geological feature, an iceberg if you will. Open rates hover around 98%, which, compared to email, is like comparing a conversation to leaving a “sorry I hit you” note under someone's windshield wiper and hoping for the best. The shift toward conversational commerce is not coming.
It's here. It’s been here.
The good news, and there is good news, is that you don't need a developer. You don't need to understand APIs in the way that requires you to understand APIs. You need Manychat, a working email address, and the specific kind of patience that agency people develop after years of explaining to clients why their nephew's kid, who "does computers," cannot, in fact, just handle this. (So beat it, nerd.)
What follows is the guide. All of it. Client onboarding, WhatsApp Business API access, template approvals — which are their own special bureaucratic theater, more on that later — multi-client management, and the per-conversation billing structure that WhatsApp uses, which is either completely reasonable or mildly insane depending on your current client roster and emotional state.
Let's get cookin’.
TL;DR
- WhatsApp has 2B+ users and 98% open rates. Your clients want in. Here's how to get them there without a developer.
- You need: a verified Meta Business Manager, a clean phone number, and a business display name approved by Meta.
- Connect in Manychat under Settings → Channels → WhatsApp.
- Build welcome messages, keyword triggers, and lead capture flows in the no-code builder.
- Submit message templates for Meta approval before you need them — approval takes up to 24 hours.
- Manage multiple clients from one dashboard with role-based access.
- Track WhatsApp conversation costs per client monthly. Decide early whether you're absorbing or passing through.
- Build a repeatable onboarding checklist. Run it the same way every time.
Why Agencies Are Adding WhatsApp to Their Stack
The numbers, since we are professionals who respond to numbers: WhatsApp is the most used messaging app on Earth. Two billion monthly active users. 98% open rates. Click-through rates that make email marketers stare quietly at the ceiling at 2 a.m., questioning every decision that led them to a career built around a 22% open rate and a prayer.
In certain markets — Brazil, India, large portions of Europe, anywhere that is not, historically, the United States — WhatsApp is not an alternative to texting. It is texting. It is also customer service. It is also commerce. Look, we're not here to kink-shame anybody; if your business wants to do all three at the same time, WhatsApp will hold that space for you without judgment.
It is also how people buy things, complain about things, return things, and occasionally propose marriage. The app is a load-bearing infrastructure for how a significant portion of the planet conducts its life.
What is conversational commerce?
Conversational commerce, which is the slightly clinical term for the very human act of messaging a business and receiving a response that does not feel like being processed by a DMV — is growing faster than any agency's ability to staff for it, faster than any client's ability to understand what they're actually asking for when they say they want it, and faster than the collective willingness of most marketing teams to learn a new platform.
Clients want to be where their customers are. Their customers are on WhatsApp. They have been on WhatsApp. They’re less engaged with email. This math is not complicated. What is complicated is that you've been nodding along to WhatsApp questions in client calls for 18 months without a clean answer, and now here we are.
How do you set this up?
What's complicated, or at least what appears complicated from the outside, is the setup. WhatsApp Business API access runs through Meta's verification process, which has the approximate energy of applying for a liquor license in a state that doesn't really want you to have one, reviewed by a notary who is also somehow on vacation. Message templates require approval from people who have seen everything and are impressed by none of it. There's per-conversation billing that will make complete sense after you read about it three times and then explain it wrong to a client anyway.
There are compliance requirements that vary by client, industry, market, and the specific emotional weather of whoever is reviewing your template submission on any given Tuesday afternoon after lunch.
This is why agencies have historically avoided it, or outsourced it to developers who absolutely knew what they were doing and simply chose to charge as though they were also building a rocket, or simply told clients that WhatsApp was "on the roadmap" with the specific confidence of someone who has never once looked at the roadmap. The roadmap does not exist. It has never existed. It was a vibe.
The subject has not changed. The clients have not forgotten. They have, in fact, brought it up again, in the meeting you thought was about something else, with the calm persistence of someone who has been waiting 18 months to say, "So, where are we on WhatsApp?"
Here is how you actually do it, fam.
Connect Your Client's WhatsApp Business Account in Manychat
Before anything else, a clarification that will save you at least one confused phone call with a client: WhatsApp Business and WhatsApp Business API are not the same thing.
WhatsApp Business is a free app. It's fine. It's what a small restaurant uses to answer reservation questions. WhatsApp Business API is what enables automation, what allows Manychat to function, and what lets you build anything worth billing for. Your clients need the API. This is where you start.
The process runs through Meta, because WhatsApp is Meta, and Meta would like you to remember that. Here is what you need before you touch anything in Manychat:
1. A verified Facebook Business Manager account
Verified, specifically, not just created. Meta's business verification process requires a legal business name, a business phone number, and documentation proving the business exists as it should. This takes two to seven business days. Build this into your client onboarding timeline, or you will have an awkward conversation in week two.
2. A phone number that has never been associated with a WhatsApp account
Personal numbers don't work. Numbers already running WhatsApp Business won’t work without being migrated, which is a separate process. Get a clean number. A VoIP number works. A dedicated SIM works. Just get one that hasn't existed on WhatsApp before.
3. The client's business display name
Meta will review and approve this separately, so be sure to account for some more review time in the process with your clients.
Once verification is complete, log in to Manychat. Navigate to Settings, then Channels, then WhatsApp. Connect the Facebook Business Manager account. Add the phone number. Verify via SMS or voice call. Submit the display name.
That's it.
No, seriously. That's it. You're connected. Take a moment to celebrate like a man who has just parallel-parked a semi-truck on the first try and cannot believe what he has done.
Everything that comes next happens in Manychat's builder, which responds to your inputs immediately, without a review period, without a queue, without a committee, and without the lingering spiritual weight of knowing that somewhere a server is considering whether your business display name adequately represents your brand values.
Just you, the builder, and a drag-and-drop interface that does exactly what you tell it to. It's going to feel like a gift. Because after what you just went through, it is.
Build Your First Client Chatbot Flow
Manychat's flow builder is a visual, drag-and-drop interface that makes the process easy: drag, drop, connect, done.
Welcome messages
Start with a welcome message. This is the message that fires when someone contacts the client for the first time. It should do three things: acknowledge that a real human-ish entity received the message, tell the customer what to expect, and give them somewhere to go. "Hi, thanks for reaching out to [Business]. What can we help you with today?" followed by buttons for the three most common inquiries is not exciting, but it is functional, and functional is what keeps people from calling the main line.
Keyword triggers
From the welcome message, build out your keyword triggers. Keyword triggers are exactly what they sound like: when someone sends a message containing a specific word or phrase, the bot responds with a specific flow. HOURS returns the hours. PRICING returns the pricing. APPOINTMENT routes to the booking flow. HUMAN, or HELP, or any variation of "I want to talk to a real person" should immediately escalate to a live agent, because the fastest way to destroy a chatbot's reputation is to make it impossible to escape.
Lead capture flows
For lead capture flows — which is the thing most clients actually want when they say they want "automation" — the structure is: greeting, qualifying question, qualifying question, contact capture, confirmation, handoff. Ask what they need. Ask when they need it. Ask for an email or phone number. Confirm you received it. Route it to the sales team. This is not complicated. This is a conversation, just automated.
Build one flow. Test it by messaging the number yourself. Fix the thing that feels wrong. Then build the next one.
Set Up Auto-Replies and Message Templates
Here is where WhatsApp diverges from every other platform Manychat supports, and where agencies most frequently lose time they did not budget for losing.
WhatsApp divides messages into two categories: session messages and template messages.
- Session messages are responses within a 24-hour window after a customer contacts the business first.
- Template messages are everything else: outbound messages, messages sent after the 24-hour window closes, promotional messages, appointment reminders, and follow-ups.
Important note: Template messages require pre-approval from Meta before they can be sent. This is not optional. This is not something you can move fast and fix later. You submit the template, Meta reviews it, Meta approves or rejects it, and then you can use it.
Approval typically takes 24 hours for standard templates. It takes longer for templates that Meta's review process finds ambiguous, promotional in a way that crosses whatever invisible line exists, or written in a way that suggests the sender might be trying to get around the rules. Write clean templates. Be literal. Describe exactly what the message does. Do not try to be clever in a WhatsApp template submission. Clever is for the copy inside the template, not for the submission itself.
Template categories matter. Utility templates — transactional messages, order updates, appointment reminders — have higher approval rates and lower per-conversation costs than marketing templates. If a message can reasonably be categorized as utility, categorize it as utility. Your clients' billing will thank you.
A few things that get templates rejected:
- vague calls to action
- unclear opt-out language
- anything that reads like a cold outreach
- promotional language in a template submitted as a utility
Learn these once. Apply them across every client account. Build a template library that lives on your agency's shared drive and serves as the starting point for every new client, because rebuilding it from scratch each time is how junior team members develop a complicated relationship with their jobs.
Manage Multiple Client Accounts Without Losing Your Mind
The promise of agency work is leverage; one team, many clients, expertise that scales. The reality of agency work is that every tool eventually proves slightly more annoying to manage across multiple clients than the sales deck suggested.
Manychat's multi-account structure is built to handle this. Each client account is separate, with its own contacts, flows, analytics, and billing. You switch between accounts from the main dashboard. You do not accidentally send one client's promotional message to another client's contact list, which is the kind of error that ends retainer relationships and generates LinkedIn posts about "lessons learned."
Access management works through roles:
- Owner access for the agency lead
- Admin access for account managers who need to build and edit flows
- Viewer access for team members who need to view and report, but not touch the automation.
Set this up at onboarding. Do not give everyone access and assume it will work out. It will not work out.
Per-client analytics live inside each account: message volume, conversation counts, flow completion rates, and opt-outs. Pull these monthly. Put them in the client report. Clients who see numbers remain clients. Clients who receive monthly emails that say "everything is going well" without evidence eventually begin to wonder whether everything is, in fact, going well.
Agency tip: Build a standard onboarding checklist that runs the same way for every new client. Business Manager verification, phone number setup, welcome message, three keyword triggers, and two templates submitted for approval. Every time, in that order. Consistency is how agencies scale. Chaos is how agencies hire a fifth account manager to manage the problems created by the first four.
WhatsApp Billing: Track Costs Per Client
WhatsApp charges per conversation, not per message. A conversation is a 24-hour messaging window, and the cost of that window depends on who opened it and why.
Two conversation types matter for most agency use cases:
- User-initiated conversations, where the customer messages the business first, are charged at a lower rate.
- Business-initiated conversations, where the business sends the first message via a template, are charged at a higher rate that varies by country.
Note that Brazil, India, and other high-volume WhatsApp markets have their own pricing tiers. If your client has an international customer base, factor this into the cost conversation before it becomes a cost surprise.
Meta provides conversation-level reporting inside WhatsApp Manager. Manychat surfaces this at the account level. Neither of these, on their own, produces the clean per-client cost breakdown that your accounting team would prefer to exist. Build a simple tracking spreadsheet — client name, month, conversation volume by type, cost per conversation, total cost — and update it when you pull analytics. This takes 20 minutes a month and prevents the conversation where a client asks what they're paying for, and you explain it in a way that makes it sound like you're not entirely sure.
On pricing strategy for clients: most agencies either absorb WhatsApp conversation costs inside a retainer or pass them through with a management fee. Passing through a transparent breakdown — here is what Meta charged, here is our fee for managing it — is cleaner than embedding it in retainer math, which becomes difficult to explain when costs increase. Make the call early, put it in the contract, and stick to it.
Agency tip: Set a monthly cost threshold alert for each client account. WhatsApp conversation volume can spike when a campaign goes out or when a client runs a promotion that drives unexpected inbound messages. Knowing about the spike before the invoice is better than knowing about it after the invoice.
One Builder, All Your Clients
WhatsApp automation is not a feature your clients will stop asking about. The numbers are too big, the open rates are too good, and too many of their customers are already there having conversations with businesses that are not your clients, which is the kind of thing that looks bad in a quarterly review when someone pulls up a competitor's engagement metrics and sets them next to yours as a before-and-after photo nobody asked for.
The agencies that figure out a repeatable process for deploying WhatsApp automation — clean onboarding, solid template library, consistent account management, a shared drive folder that actually has the right files in it — are the ones that turn it into a service line instead of a one-off project that lives in a Slack thread from eight months ago that nobody can find.
Manychat is how you build that process without a developer on retainer, without rebuilding from scratch for every client, and without the specific kind of exhaustion that comes from managing five different tools across twelve client accounts while explaining to a sixth client why their account is different.
Start with one client. Run the onboarding. Build the flows. Get the templates approved. Then do it again, faster, because the second time you know where the 24-hour approval window is and you've stopped being surprised by it, and the third time you do it in your sleep, and by the fourth time you've turned it into a PDF and started charging for the PDF, which is honestly good for you.
That's the play. Now run it.
Frequently asked questions
No. Manychat's no-code builder handles the full setup — welcome messages, keyword triggers, lead-capture flows, and template messages — without writing a single line of code. The Meta Business verification process requires documentation, not development.
Meta Business verification typically takes two to seven business days. WhatsApp message template approval usually happens within 24 hours for standard templates. Submit templates before you need them. Approvals do not care about your launch date.
Yes. Manychat's dashboard lets you switch between client accounts, assign team roles, and pull per-client analytics from a single login. Each account stays separate — separate contacts, separate flows, separate billing.
WhatsApp charges per conversation, not per message. Rates vary by conversation type — user-initiated or business-initiated — and by country. Track monthly costs per client and decide upfront whether you're absorbing them into the retainer price or passing them through as a management fee — either works. Ambiguity does not.
