The short version: a WhatsApp chatbot connects to the WhatsApp Business API to answer customer messages on its own, retrieve order status, recover carts, and escalate edge cases to a human. An AI agent handles natural language and fails at a fraction of the rate of a rule-based flow builder. This guide covers API requirements, the per-message pricing model that has run since July 2025, the three template types, AI agent vs flow builder, Meta compliance, and how Zipchat deploys on Shopify without custom development.
What a WhatsApp chatbot does
A WhatsApp chatbot is an automated system connected to the WhatsApp Business API that handles inbound customer messages at scale. When a customer messages your WhatsApp number, the bot replies in real time: answering product questions from your catalog, pulling order status from Shopify’s API, processing returns within policy, and handing complex cases to a human agent.
The distinction matters. A WhatsApp chatbot is not the WhatsApp Business App, which is free, manual, and tied to one device. It is an API-connected system that runs 24/7, handles unlimited simultaneous conversations, and knows your full catalog before a customer sends the first message.
For the complete strategy, see the WhatsApp marketing guide. For automation sequences, see WhatsApp automation for Shopify. For full cluster context, see the WhatsApp commerce hub.
Why WhatsApp is worth the setup
WhatsApp gets read. Opt-in messages see a 60 to 80% measured read rate, far above email open rates (Chatarmin, 2026). Transactional messages can climb higher, but treat the bare “98%” figure as a vendor estimate, not a Meta-published number.
Shoppers have moved to messaging. 36% of consumers have bought through a messaging app, up from 11% in 2021, and they now use 11 or more channels to reach brands (Salesforce Connected Shoppers, 2024). A WhatsApp chatbot meets that demand without adding headcount.
The revenue case is concrete. WhatsApp cart recovery recovers 13 to 40% of abandoned carts when the message lands in a channel people actually open.
WhatsApp Business API pricing: how billing works
WhatsApp bills per message, not per 24-hour conversation. Meta switched to per-message pricing on July 1, 2025, so your cost now tracks how many template messages you send, not how many conversations you open.
What you pay for and what you don’t:
- Free: service and customer-initiated messages, plus any replies you send inside the 24-hour customer service window, including automated follow-ups.
- Charged: marketing templates and authentication templates, billed per message.
- Free inside an open window: utility templates sent while a 24-hour service window is active. Outside that window, utility templates are charged.
Meta’s per-message rates vary by country, so model your cost against your actual destination markets before scaling broadcasts. The practical takeaway: answer fast inside the 24-hour window to keep replies free, and reserve paid marketing templates for messages that earn their cost.
WhatsApp template types
Every outbound message sent outside an active 24-hour window uses a pre-approved template, and the template category sets the price and the rules.
| Template type | Use | Billing |
|---|
| Marketing | Promotions, launches, cart recovery, broadcasts | Charged per message |
| Utility | Order confirmation, shipping updates, account alerts | Free inside an open 24h window, charged outside it |
| Authentication | One-time passwords, login codes | Charged per message |
Submitting a promotional template as Utility to get cheaper pricing is a policy violation and will get the template rejected or your number flagged. Match the category to the message’s true purpose.
The platform choice sets the ceiling. A flow builder (rule-based) is fast to deploy and cheap, but it only answers questions you scripted, so it breaks on anything off-path. An AI agent reads natural language, reasons across your catalog and order data, and answers questions you never anticipated.
| Dimension | Flow builder (rule-based) | AI agent (Zipchat) |
|---|
| Setup time | Hours | 2 to 4 hours |
| Natural language | No | Yes |
| Handles off-script queries | No | Yes |
| Product catalog knowledge | Manual configuration | Automatic from Shopify sync |
| Multi-step reasoning | No | Yes |
| Learning from conversations | No | Yes |
| Escalation logic | Rule-triggered | Intent and sentiment |
Independent benchmarks put rule-based chatbot deflection at 20 to 40%, AI ecommerce agents at 40 to 60%, and mature AI deployments at 65 to 75%. Zipchat’s first-party success stories run higher, above 90% and up to 97% on well-trained catalogs.
That gap is where sales live. A customer asking “is this supplement safe for someone with celiac disease?” gets “I didn’t understand that” from a flow builder. An AI agent reads the ingredient list, answers accurately, and drops in a checkout link.
Tropicfeel automated 85% of customer inquiries with an AI agent. Read the Tropicfeel story.
WhatsApp Business API requirements
Before building a chatbot, you need API access. Three requirements:
1. Meta Business Account (verified). Go to business.facebook.com and create or claim your business account. Complete verification with legal business name, business phone number, and website URL. Verification takes 1 to 5 business days. If you run Meta Ads, your account is likely already verified.
2. Dedicated phone number. The number used for the WhatsApp Business API cannot be registered to any existing WhatsApp account, consumer or Business App. Use a new SIM, a VoIP number, or a landline that can receive a verification call. Numbers with an existing WhatsApp registration must be deregistered first.
3. Business Solution Provider (BSP) or direct API access. Two paths:
- Direct Meta Cloud API: free, but requires developer setup. Fit for teams with engineering resources.
- BSP (Zipchat, Twilio, 360dialog, Vonage): managed API access. The BSP handles the connection; you configure behavior in its dashboard. Faster to deploy, lower maintenance.
Zipchat is a BSP, so WhatsApp API access is included in your subscription. No separate Meta Cloud API setup required.
Step by step: building a WhatsApp chatbot on Shopify with Zipchat
Phase 1: Account and API setup (Day 1, around 2 hours)
- Verify your Meta Business Account at business.facebook.com.
- Get a dedicated phone number (new SIM or VoIP).
- Install Zipchat from the Shopify App Store.
- In Zipchat, go to Channels > WhatsApp > Connect. Enter your WhatsApp Business Account ID and phone number ID from Meta Business Manager. Zipchat establishes the connection and activates your sending number.
Phase 2: Template creation and submission (Day 1 to 2, around 30 minutes)
- In Zipchat, go to Templates > New Template. Create templates for abandoned cart recovery (3 messages), order confirmation (1), shipping dispatch (1), and post-purchase follow-up (1).
- Submit all templates for Meta review. Review takes 24 to 48 hours.
Phase 3: AI knowledge base configuration (Day 2 to 3, around 2 hours)
- Zipchat imports your Shopify catalog automatically. Review the imported knowledge: descriptions, pricing, variants, policies.
- Add supplementary knowledge: shipping times, return policy details, and the FAQ answers your team handles most.
- Set escalation rules: which question types go to a human (disputes above a threshold, returns beyond a window, negative sentiment).
Phase 4: Opt-in collection setup (Day 3)
- In Zipchat, open Checkout Opt-In. Enable the WhatsApp opt-in checkbox on your Shopify checkout. Configure consent text: “I agree to receive order updates and marketing messages via WhatsApp from [Store Name].”
- Enable GDPR consent recording (timestamp plus consent text stored per customer).
Phase 5: Automation activation (Day 3 to 4)
- Once templates are approved, activate the sequences: cart recovery, order confirmation, shipping updates, post-purchase.
- Set delay timings: cart recovery message 1 at 60 minutes, message 2 at 24 hours, message 3 at 72 hours. Activate stop conditions.
Phase 6: Test and go live (Day 4)
- Place a test order, abandon checkout, and confirm message 1 fires. Check variable substitution (product name, customer name, checkout link).
- Complete the test order. Confirm the order confirmation fires and the stop condition blocks cart recovery messages 2 and 3.
- Send test questions via WhatsApp: product question, order status, return request, off-topic question.
- Go live.
1. Opt-in required. You cannot send outbound marketing to contacts who have not explicitly opted in to WhatsApp messages from your brand. A phone number collected without WhatsApp consent is not a valid marketing contact.
2. Templates required for outbound. Any message sent outside a 24-hour active conversation needs a pre-approved template. Free-form messages are allowed only in reply to a customer-initiated conversation within 24 hours.
3. Opt-out in every message. Every outbound message needs a clear opt-out, such as “Reply STOP to unsubscribe.” Remove anyone who opts out from future marketing immediately.
4. No prohibited content. Templates cannot contain adult content, alcohol marketing without age disclaimers, financial services without required disclosures, or gambling content where it is restricted. Review Meta’s commerce policy for your product category.
5. Template category accuracy. Submit each template as Marketing, Utility, or Authentication based on its real purpose. Mislabeling a promotion as Utility for cheaper pricing is a violation.
6. Protect your quality rating. Opt-out rates above 2% per campaign damage your number’s quality rating. A Red rating restricts daily volume. Segment your audience and send relevant messages.
7. GDPR (for EU/EEA customers). Consent must be explicit and specific. Store consent records with timestamp and consent text. No pre-ticked checkboxes. Processing must match the stated purpose.
8. Approved number registration. Your API number must be registered and approved by Meta and cannot run the WhatsApp API and the WhatsApp Business App at the same time.
| Metric | Underperforming | Target | Top performers |
|---|
| Containment rate | Below 50% | 70% to 80% | 85%+ |
| First response time | Over 10 seconds | Under 5 seconds | Under 1 second |
| Cart recovery rate | Below 8% | 13% to 18% | 20%+ |
| CSAT (AI-handled) | Below 75% | 80% to 90% | 90%+ |
| Opt-out rate per campaign | Above 3% | Below 2% | Below 1% |
| Escalation rate | Above 40% | 15% to 25% | Below 15% |
Family Nation automated 80% of inquiries, which puts their containment rate at 80%. Read the Family Nation story. That is the 2026 production baseline for a well-deployed AI chatbot.
When the chatbot fails: common failure modes
Failure: AI gives wrong product information. Cause: stale catalog sync or incomplete descriptions. Fix: schedule daily Shopify syncs and complete descriptions to cover the compatibility, ingredient, and spec details customers ask about.
Failure: cart recovery fires after the order is completed. Cause: stop condition not set, or a Shopify order webhook delay. Fix: set the stop condition to “order confirmed,” not “checkout started,” and add a 15-minute grace window before message 1 to absorb payment delays.
Failure: template rejected by Meta. Cause: vague CTA, wrong category, or flagged content. Fix: make the CTA specific (“Complete your purchase at [URL]”), confirm the category matches purpose, and review Meta’s template policy before resubmitting.
Failure: low containment rate (under 50%). Cause: thin knowledge base or an agent not trained on your range. Fix: review unanswered questions in Zipchat analytics, add the top 20 to the knowledge base, and re-check escalation thresholds.
FAQ
How much does a WhatsApp chatbot cost to run?
You pay Meta per message, not per conversation, since July 1, 2025. Service and customer-initiated messages and replies inside the 24-hour window are free, including automated follow-ups. Marketing and authentication templates are charged, and utility templates are free only inside an open window. Rates vary by country.
Do I need the WhatsApp Business API for a chatbot?
Yes. The free WhatsApp Business App is manual and single-device. A chatbot needs the WhatsApp Business API, which you reach either through Meta’s Cloud API directly or through a Business Solution Provider like Zipchat that includes API access in the subscription.
What is the difference between an AI agent and a flow builder?
A flow builder follows scripted rules and only answers questions you mapped in advance, so it breaks on off-script queries. An AI agent reads natural language, reasons across your catalog and orders, and answers questions you did not anticipate. Rule-based deflection runs 20 to 40%; mature AI runs 65 to 75%.
What are the WhatsApp template types?
Three: Marketing (promotions, charged per message), Utility (transactional, free inside an open 24-hour window), and Authentication (one-time passwords, charged). Submit each in its correct category, since mislabeling is a Meta policy violation.
What is a good WhatsApp read rate?
Opt-in WhatsApp messages see a 60 to 80% measured read rate (Chatarmin, 2026), well above email. Transactional messages can run higher, but the often-quoted 98% is a vendor estimate, not a Meta figure.
How long does it take to build a WhatsApp chatbot on Shopify?
With Zipchat, around four days end to end. API setup and templates take Day 1 to 2, knowledge base and opt-in take Day 2 to 3, and automation plus testing finish on Day 4. Meta template review adds 24 to 48 hours.
