Connect your AI bot to WhatsApp Business

Once you connect your WhatsApp Business number, every inbound message becomes a conversation your bot can handle on its own. The bot reads what the customer wrote, searches the knowledge base you’ve trained it on, and replies in plain language — usually within a couple of seconds. If the question is something it can answer — your refund policy, your delivery zones, the difference between two product variants, your store hours during a holiday weekend — it answers without paging anyone on your team.

Connectors and integrations make the bot more than a knowledge lookup. With your CRM or helpdesk wired in — HubSpot, Intercom, Salesforce, Shopify, Slack, Zendesk, Zoho, Freshdesk — the bot does real work inside a WhatsApp thread: look up an order by number, check a ticket status, capture a lead’s email and phone, hand off a hot prospect to your sales team, escalate an angry customer to a human agent. The customer never leaves WhatsApp. Your team never leaves the unified inbox.

When the bot can’t or shouldn’t answer, the conversation escalates. A human agent on your team takes over the WhatsApp thread from the NebulaHex inbox, with the full conversation context already loaded. The customer sees a smooth transition from automated assistant to a named human, without having to repeat anything.

WhatsApp’s Business Platform has one rule that shapes everything your bot can do: the customer service window. After a customer messages your business, you have 24 hours to reply with anything you want — text, images, documents, interactive buttons. This is the window your bot lives in.

Almost every support and sales interaction your bot handles happens inside this window. A customer messages you, the bot replies within seconds, the conversation continues, the window stays open. You don’t need template approval for any of it.

The second rule applies when you want to start a conversation outside that window — for example, sending an order confirmation, an appointment reminder, or a shipping update to a customer who hasn’t messaged you recently. WhatsApp requires those to be template messages: pre-written formats that Meta reviews and approves before you can send them. Templates carry quality scores that affect daily volume, and you have to collect explicit opt-in from each customer.

Business verification is the other piece. Unverified accounts can still send and receive messages, but Meta caps your daily template volume. Verifying your business through Meta unlocks higher throughput and the green checkmark customers recognize. Verification happens on the Meta side; once verified, nothing changes inside NebulaHex — your bot just keeps doing what it was doing, with more headroom underneath.

WhatsApp Business comes in two shapes. The free WhatsApp Business app is the consumer-grade version a single shop owner downloads from the app store and runs on their phone. That’s not what NebulaHex connects to. NebulaHex connects to the WhatsApp Business Platform (the WhatsApp Cloud API), the programmatic version Meta runs on its own infrastructure.

The Cloud API is hosted by Meta, which means you don’t run any servers, install any software, or manage any messaging infrastructure yourself. Meta has been steadily consolidating around the Cloud API as the only supported path for new business integrations; the older self-hosted on-premises version has been winding down. Building a WhatsApp integration today is a Cloud API project.

For businesses, the Cloud API is the difference between “we have a WhatsApp number a person checks on their phone” and “we have a WhatsApp number that talks to our actual systems.” Order confirmations, support routing, lead capture, automation — none of that is possible from inside the consumer Business app. It all happens through the Cloud API, and that’s the surface NebulaHex sits on top of.

The connection is a form, not a project. Inside your bot’s Channels tab there is a WhatsApp Business card that walks you through six steps — some on Meta’s side, some in NebulaHex. From a clean start it takes a few minutes.

Once you’re connected, the card flips to a live state showing when the channel was created, when it was last updated, and whether it’s currently active. If something is wrong — a token has expired, the webhook isn’t reaching us — you’ll see a clear error message rather than silence.

You can pause a channel without losing the connection. Each card has an active/inactive toggle; flipping it off stops the bot from answering on that channel while keeping every setting intact. To remove the channel entirely, the Disconnect button at the bottom of the card requires a confirmation step before anything is removed.

Your WhatsApp channel doesn’t run a separate bot from your website widget. The same bot powers both, plus Instagram DMs, Messenger, and Telegram if you’ve connected them. When you update the knowledge base, every channel learns the new answer. When you adjust tone or handoff rules, the change applies everywhere.

This matters more than it sounds. Most multi-channel “solutions” are really five separate tools wired together with webhooks; if you change something in one, you have to remember to mirror it in the others. NebulaHex treats the bot as the source of truth and the channels as transports. WhatsApp is one of the transports.

What WhatsApp actually does, in the situations that matter:

You can integrate against the Cloud API directly. Meta’s documentation is good; the API is well-defined; if you have an engineering team with bandwidth, you can build it. The question is what you’re actually building.

NebulaHex is that whole stack as a product. You don’t write code to connect WhatsApp; you fill out a form. You don’t build an inbox; you use ours. You don’t model a knowledge base; you upload your sources. The argument for buying instead of building isn’t that the API is hard — it’s that the system aroundthe API is hard, and the months you’d spend rebuilding it would be months you weren’t doing the actual work of selling, supporting, and growing.

WhatsApp itself encrypts messages end-to-end between the sender and the WhatsApp Business Platform. On our side, your bot’s configuration, your channel credentials, and the conversation transcripts are encrypted at rest and in transit. The access token you paste into the WhatsApp connection form is encrypted before it’s stored — it never sits in plain text inside our database, and it never appears in audit logs.

Access to your bots and channels is controlled by role-based permissions. Owners and admins can connect or disconnect channels; editors can manage knowledge and tune bot behavior; viewers have read-only access. Sensitive actions require confirmation. Outbound integrations use OAuth 2.0 wherever the provider supports it, and webhooks coming back from external systems are signed and verified.

We don’t use your conversation data to train AI models. The knowledge sources you upload power your bot’s answers, not anyone else’s. If you want even more control, the Bring Your Own Key option lets you provide your own model API key so prompts and responses pass through the AI provider you choose, on the terms of your account with that provider.

See our privacy policy and terms for the full posture.

If you already have a WhatsApp Business account in Meta Business Suite and a Meta App with the WhatsApp product enabled, you’re a few minutes away from your first automated reply. Open your bot’s Channels tab, find the WhatsApp Business card, paste your Phone Number ID and Access Token, click Connect, and send a test message.