Launch rich WhatsApp campaigns faster with 500+ industry-ready templates

WhatsApp Campaigns is a library of 500+ ready-to-use WhatsApp campaign templates, spanning 80+ categories across 12+ industries, plus 100+ multi-step conversation flows. You customize a template, connect your messaging provider (Twilio and Meta today, or your own gateway), and launch branded campaigns without building each message from scratch. Pro adds CSV personalization, AI automated responses grounded in your knowledge base, and an agent toolkit (MCP server and CLI) so AI agents can run campaigns too.

There are three plans: Free ($0), Pro ($49 per month), and Enterprise (custom pricing). Free includes full access to the 500+ template library plus 10 free sends to test. Pro includes 500 messages a month in the $49 (about $0.10 per message, with no separate per-message charge for those 500), CSV personalization, AI automated responses, conversation flows, the agent toolkit (MCP server and CLI), and provider integrations. Enterprise is for higher volumes and custom needs across brands, teams, and regions.

500+ professionally designed, campaign-ready templates spanning 80+ categories across 12+ industries (retail, hospitality, healthcare, events, real estate, finance, automotive, and more) plus 100+ ready-made multi-step conversation flows. Every template ships with polished copy, on-brand media, and the right buttons and quick replies already in place, so you start from something proven rather than a blank canvas. Full access to the entire library is included on every plan, including Free; Pro and Enterprise add personalization, AI automated responses, flows, and higher send volumes on top.

No, it's built for marketing and ops teams, not developers. Every template is drag-and-edit: swap the copy, colors, images, buttons, and quick replies in a visual editor without touching code. When you're ready to send, you connect your provider once and reuse it for every campaign. Pro layers on CSV personalization (map fields like first name, booking date, or offer in a few clicks), multi-step conversation flows, and AI automated responses, all configurable by anyone on the team. Developers can go deeper via your provider's API if you want to, but nothing here requires it.

Twilio and Meta are active now, Vonage and Bandwidth are coming soon, and you can bring your own WhatsApp gateway and we'll help you wire it up. The key idea is build once, connect anywhere: you design and personalize your templates a single time, then point them at whichever backend fits your stack. Switch providers or add new ones whenever you need to, without rebuilding a thing.

Yes. Bring-your-own-gateway is a core part of the design, so if you already have a WhatsApp provider or sender set up, you can connect it and keep your existing numbers and relationships. If you don't, you can start with one of our active integrations like Twilio or Meta. Either way you build and personalize your templates once and route them through whatever backend you choose, which keeps you in control and avoids lock-in.

Yes. On Pro you can upload a CSV and map fields like first name, appointment date, order number, or a custom offer into any template in a few clicks, so every recipient gets a message that reads like it was written for them. Personalization works hand in hand with conversation flows and AI replies, which means you can tailor not just the first message but the whole back-and-forth. It's the difference between a generic blast and a message that feels one-to-one, at scale.

Yes. With Pro, an LLM grounded in your own knowledge base (FAQs, policies, listings, hours, pricing, and docs) can answer customer responses in your brand voice, around the clock. It handles real back-and-forth: answering questions, rebooking or updating reservations, routing inquiries, suggesting the right next action, and handing off to a human the moment a conversation gets complex or high-value. Pair it with conversation flows to trigger the right message at the right time, branch on how the customer replies, and follow up automatically, so conversations keep moving even outside business hours.

Approval time depends on the reviewers, not on us: every template is reviewed by Meta, and each provider applies its own content and opt-in rules. A single missing detail, such as a sample message that doesn't match your use case or unclear opt-in language, can send a submission back to the start. WhatsApp Campaigns streamlines it: because your campaign starts from templates modeled on similar campaigns that are already approved, with branding, opt-in language, and message structure aligned to what reviewers expect, you submit correctly the first time and avoid most rejection-and-resubmit loops. We also help resolve any flags directly with the provider. We can't guarantee approval (that decision is Meta's and your provider's), but a pre-vetted, correctly formatted submission is the biggest lever for getting live faster.

WhatsApp Campaigns shows it on every template: the category Meta actually approved, color-coded, with a clear flag the moment a submission comes back different from what you requested. That matters because Meta's review can approve a template you submitted as Utility as Marketing instead, and most tools only show "Approved."

Yes, by duplicating it: fork the approved template into a fresh draft, edit the draft, and submit it for approval again. Drafts can be revised in place, and every revision re-runs the same validation that gates creation.

A template is a single message; a flow is a complete two-way conversation. In a flow, the customer taps a button or quick reply and the next message answers that specific choice, through to the booking or confirmation that follows. The library includes 100+ ready-made flows alongside the 500+ templates.

Yes. Conversational surveys deliver branded, tappable questions inside the chat: star ratings, 1–5 scales, NPS, multiple choice, and review prompts. Respondents answer with buttons and quick replies instead of typing into a form, and each answer chooses the next question, so everyone gets a short, relevant path.

It is Meta's official way for businesses to message customers on WhatsApp at scale, through a provider such as Twilio or directly with Meta. Messages arrive as a chat from your business profile and can carry images, buttons, carousels, and quick replies. It is not the same as automating the consumer app or WhatsApp Web, which is against WhatsApp's terms and is the most common cause of bans.

Yes, to start a conversation you need a template that Meta has approved. Once a customer replies, a 24-hour service window opens, and during it you can send free-form messages without a template. Outside that window, every message you send has to be an approved template.

A Utility template is a message the customer needs about something they already started, such as an order, a booking, an appointment, or an account action, and it names that specific thing. Marketing is everything else, including requests that fire right after a real interaction: "Your order #4471 is out for delivery" is Utility, while "How was your delivery? Tap to rate us" is Marketing. Meta enforces the category, and its review can approve a template you submitted as Utility as Marketing instead.

Not currently: as of our August 2026 guide, Marketing-category templates are blocked from delivering to US numbers. That is why a template that Meta re-files from Utility to Marketing can start silently failing every send to US customers while still showing "Approved." Check the category Meta actually approved, not just the approval status.

Usually because Meta throttled it or the recipient blocked you. Every user has a rolling limit on how many marketing template messages they will be delivered, counted across all businesses; when someone is over it, Meta accepts your message and quietly drops it (error 63049). A block looks similar: the message is accepted and sits at one tick, with no error. Sending the same campaign again to a silent list makes both worse.

Policy violations, not volume. The main causes are sending through unofficial tools (QR-linked browser extensions, WhatsApp Web automation, or modified apps), messaging people who never opted in, dressing a marketing message as a Utility template, leaving the opt-out out of marketing messages, and prohibited content. On the official platform, with approved templates and real consent, a ban is unlikely and almost entirely within your control.

It is Meta's green, yellow, or red rating of your sender, based mainly on blocks and reports from recipients over a rolling seven-day window. Yellow freezes your messaging limit while Meta looks, and usually clears after about a week of clean traffic; red can cut your limit and trigger an account review. A low rating also makes marketing throttling bite sooner, so it is the number to watch.

Start small and grow over a few weeks. Send to the low hundreds first, increase gradually, and watch the quality rating rather than the calendar; if it turns yellow, stop increasing until it clears. A brand-new sender messaging tens of thousands of strangers on day one is exactly the profile that gets limited.

Most rejections come down to category, samples, or consent: a promotional ask written to look like a Utility message, sample messages that don't match the use case you declared, or opt-in language that isn't clear. Meta's reviewers specifically look for marketing dressed in transactional wording, so if a message is really a request (a review, a referral, a win-back), submit it as Marketing. A template can also be approved but re-filed into a different category, which never shows up as a rejection.

It is the 24 hours after a customer messages or replies to you, during which you can send free-form messages without a template. Messages inside the window are also exempt from the marketing delivery limit. Once it closes, you have to use an approved template again; a free-form message sent after the window fails with error 63016.

Meta doesn't publish the number. Each person has a rolling limit on marketing template messages, counted across every business that messages them, and it is far tighter for people who never engage. Treat any exact figure you see quoted as illustrative, and watch your own error codes and reply rates instead.

Two blue ticks mean the message was read, two grey ticks mean it was delivered, and a single tick means it was accepted but not delivered. A message that sits at one tick forever usually means the recipient blocked you or Meta throttled it, and neither produces an error code. You can't see who blocked you.

63049 means Meta declined to deliver a marketing message because the recipient is over their limit; don't resend the same template to that person. 63024 means the number isn't reachable on WhatsApp at all, which is list decay, not a problem with your sender. 63016 means a free-form message was sent after the 24-hour window closed; send an approved template instead. 63028 and 21656 are template variable problems, such as a missing merge field.

Send through the official WhatsApp Business Platform, with approved templates, only to people who opted in. Before each send, check that you can produce each recipient's opt-in wording, that the template's approved category is the one you meant, and that your sender's quality rating is green. Exclude contacts who ignored your last two campaigns, warm up new numbers gradually, and make sure you can stop a send mid-flight if it starts going wrong.

P2P means person-to-person: two people chatting in their messaging apps. A2P means application-to-person: a business application sending messages to customers, like order updates, appointment reminders, or promotions. Business messaging on WhatsApp is A2P, which is why it carries the extra structure around it: verified brand identity, content review, opt-in requirements, and analytics. When this site talks about marketing and customer messaging, it's A2P we mean.

Yes: you can see delivery receipts, read receipts (when the recipient has them enabled), button taps and clicks, and replies. Together they give you a real picture of engagement rather than the near-total blind spot plain SMS leaves you with. That visibility lets you see which templates, offers, and flows actually move customers, and iterate accordingly.

Yes on both counts. The channel is genuinely two-way, so customers can reply in the same thread, and quick-reply buttons make responding as easy as a tap. You can automate those conversations with flows that trigger the right follow-up based on how someone replies, and with WhatsApp Campaigns Pro you can layer in an AI assistant, grounded in your own knowledge base, that answers questions, reschedules, and routes to a human when things get complex. That keeps conversations moving around the clock without anyone watching the inbox.

Yes. Meta requires active, per-number opt-in: a deliberate act by that person, naming your business, saying what they will receive and how often, and how to stop. A ticked checkbox next to the disclosure, a reply, or a tap on one of your buttons counts; purchased or scraped lists never do, however clean they are. Keep the exact wording each person agreed to, not just a date, and include an opt-out in every marketing message. Every WhatsApp Campaigns template ships with opt-in and opt-out language already built in, so you start on the right side of the line.

Yes, it can be run compliantly: the channel doesn't change your legal obligations, it inherits them. The same frameworks that govern text and data outreach apply: get clear opt-in consent, identify yourself, honor opt-outs immediately, and handle personal data per regulations like GDPR. Your compliance depends on how you collect consent and manage your lists, so treat it like the rest of your messaging program and you'll be on solid footing.

With a deliberate action by each person: a form, checkout box, or QR code where they tick an unticked box next to text that names your business, says what they'll receive and how often, and explains how to stop. A reply to you, or a tap on a button in one of your messages, also counts. If you import contacts, keep the date, the source, and the exact wording each person agreed to.

Yes. WhatsApp Campaigns is agent-native. An authenticated gateway (/api/agent) lets an autonomous AI agent discover, author, clone, render, and send campaign templates without anyone clicking through a dashboard. The same gateway is exposed three ways over one typed contract: a Model Context Protocol (MCP) server, a command-line tool, and an embeddable client. So whether you're building on Claude, an agent SDK, or your own service, the platform behaves like a first-class tool rather than a website you have to script a browser against.

Yes. The @wa-campaigns/agent-toolkit ships an MCP server called wa-mcp (hand-rolled, zero runtime dependencies, JSON-RPC over stdio). Register it once with any MCP host — for Claude it's a single `claude mcp add` command pointing at npx -y -p @wa-campaigns/agent-toolkit wa-mcp with your agent key (the toolkit talks to the hosted gateway by default) — and your agent gains 48 native tools spanning templates, conversational surveys, grounding knowledge, audiences, contacts, the conversation inbox, webhooks, and usage — starting with capabilities, which returns the whole catalog plus the scopes your key actually holds. The MCP server is available on the Pro plan.

Yes to both. Under the hood everything runs over the /api/agent HTTP gateway, and the agent toolkit wraps it as a JSON-in/JSON-out CLI (the `wa` command) so you can search, render, clone, create, and send from a shell, CI, or an agent loop — pipe it straight into jq. There's also a typed GatewayClient you can embed in your own code. The packaged MCP server and CLI are Pro-plan features; the gateway and typed client are available to embed in your own service.

Agents authenticate with scoped API keys (prefixed wak_), minted by an org admin and shown only once before being stored as a hash. Each key carries a least-privilege set of scopes — read, write, submit, clone, send, usage — so a key can only do what it was minted for, and it's revocable at any time. The agent gateway is a separate rail from the human app: neither token works on the other's surface. Sending is hardened too — destinations are validated as E.164 numbers, the gateway is rate-limited, and an agent send must clear the exact same provider-approval gate as a human send, so there's no back door to ship an unapproved template.

Yes. Four packaged skill chains string the tools into repeatable jobs: find-and-buy-template (shop the marketplace and clone the best fit), author-and-publish (turn a brief into a validated template and submit it for approval), campaign-in-a-box (clone, validate, send, and report the delivery funnel), and reply-bot (draft a grounded reply from a template's knowledge doc). Each declares the least-privilege scopes it needs, so you can mint a key that matches exactly one workflow. A per-call crypto payment rail (x402) for buying and sending without an account is fully designed and coming soon.