WhatsApp customer support bot: how it works and what Meta allows

WhatsApp offers two products for businesses, and only one is built for bots. The WhatsApp Business app is a free app for small businesses that answer customers by hand and use basic automated replies. The WhatsApp Business Platform is a set of APIs for medium and larger businesses. Cloud API is its main messaging product, and it is what chatbots, helpdesks and CRMs connect to.

If you already use the app, Meta supports onboarding an existing WhatsApp Business app number to Cloud API so both can run on the same number. After onboarding, messages sent from the app are not subject to the customer service window, while messages sent through Cloud API are, and some app features, such as group chats, are not supported on the API side. Check that your helpdesk supports this setup before you rely on it.

Every WhatsApp support flow depends on one timer. When a customer messages or calls your business, a 24-hour customer service window starts, and each new message or call from them resets it to 24 hours. While it is open, your bot or agents can send free-form service messages through the API with no pre-approval.

Once the window closes, templates are the only messages you can send. Templates are pre-written formats that need approval before use, and each belongs to a category: marketing (promotions), utility (follow-ups on something the customer did or asked for) or authentication (verifying identity).

For a support bot this means two practical rules: answer inside the window whenever you can, and prepare utility templates in advance for late follow-ups such as "your ticket was updated" or "we need one more detail".

Meta requires businesses to get opt-in permission before messaging people on WhatsApp. The opt-in does not have to be WhatsApp-specific, but it must clearly say the person is agreeing to receive messages from your business and must state your business name. You are responsible for choosing an opt-in method that meets the laws that apply to you. Meta lists these methods:

• SMS
• Your website
• A phone call using an interactive voice response (IVR) flow
• In person or on paper

Meta also recommends opt-in that covers each kind of message you plan to send, plus clear opt-out instructions. In practice, collect and record opt-in wherever customers first give you their number, such as checkout, sign-up or your contact form, so templates for ticket updates are never a guess.

Meta charges per delivered message and only for messages a business sends to users. The price depends on the message category and the recipient's country code. Rate cards are published per market and change from time to time, so check Meta's current pricing page instead of a number from a blog post.

Two points matter for support teams. Conversations that start from a Click to WhatsApp ad or a Facebook Page call-to-action can open a free entry point window: if you reply within the customer service window, your messages aren't charged, and Meta's current pricing page says that window can stay open for up to 7 days (the older conversation-based pricing gave 72 hours). And helpdesk vendors can add their own fees: Freshworks' documentation, for example, states that it adds a markup on top of Meta's WhatsApp charges.

A WhatsApp bot should never be a dead end. When it can't resolve something, the conversation should reach an agent with the context already attached. Zendesk and Freshdesk both offer native WhatsApp channels:

• Zendesk: WhatsApp is added as a messaging channel in Admin Center (Channels > Messaging and social > Messaging). You need a Meta Business Manager that belongs to your business, and the person connecting the number must be an admin in it. Zendesk notes that agents can't respond more than 24 hours after the customer's last message, and that WhatsApp group messages are not supported.
• Freshdesk: WhatsApp is a Freshdesk Omni channel with support for approved message templates. Per-number settings include linking an AI agent, routing to agent groups, template management, automations and SLA policies. Freshdesk's guide notes a limit of 250 business-initiated conversations per 24 hours until Meta's business verification is complete.

Whichever helpdesk you use, map the details the bot collects (name, order number, issue type) into ticket fields so agents don't ask again, and tag bot-handled conversations so you can see what the bot actually resolves.

TascaLab builds WhatsApp bots on top of the tools you already use, such as Zendesk, Freshdesk, Jira, Slack or internal systems, using APIs, webhooks, and Make or n8n. A Starter Chat Bot ($400) covers one or two channels with FAQs and basic info collection; a Standard Chat Bot ($575) covers three to five channels with more complex conversations and smoother handoffs. Every project includes 30 days of post-launch support and basic documentation, with no hidden fees, and most setups take 1–3 weeks. A free 30-minute Health Check call is a simple way to check whether WhatsApp fits your support volume.