What does integrating WhatsApp Business actually involve?
Four separate things get bundled under the word "integration," and confusing them is the most common reason a rollout stalls halfway through. The first is a phone number that can be registered to WhatsApp and is not already tied to the consumer WhatsApp app or the free WhatsApp Business app. The second is access to the WhatsApp Business Platform, which is Meta's API product, either through Meta's Cloud API directly or through a provider that resells it. The third is a Meta Business account that has gone through verification, with a display name Meta is willing to approve. The fourth is the actual connection into your support tool, so inbound messages arrive as conversations, replies go out from the same number, and the thread attaches to a customer record rather than floating loose in a chat channel.
The order of those steps matters more than people expect. Teams often buy the software first and then discover that their main business line lives in the WhatsApp Business app on a team member's phone, and that moving it to the API means losing the chat app that person has been using with customers every day. Decide early which number will carry WhatsApp, whether its existing history has to be preserved, and who inside the business owns the Meta account. A number can be migrated, but it is a one-way door for that handset, so make the decision deliberately rather than mid-setup.
Should you use the WhatsApp Business app, the Cloud API, or a provider?
The free WhatsApp Business app is a phone app built for a single business with one or two people answering. You get labels, saved quick replies, a catalog and an away message. What you do not get is shared assignment, conversation history that survives a staff change, reporting, or any connection to a help desk. It works until two people need to answer at the same time, and then it quietly becomes the bottleneck.
The WhatsApp Business Platform, commonly called the Cloud API, is what every genuine integration runs on. It supports many agents on one number, programmatic routing, automation, approved message templates for business-initiated contact, and webhooks that let your support tool receive and send messages. You can connect it yourself if you are comfortable with Meta's developer console, or go through a Business Solution Provider such as 360dialog, Twilio or Infobip, which handles registration, template approvals and billing in exchange for a platform charge on top of Meta's messaging charges. A growing number of support tools embed that onboarding directly, which removes the provider as a separate relationship and a separate invoice. If you are a small team without a developer, that embedded route is almost always the one to take.
How do the main customer service tools handle WhatsApp?
Zendesk treats WhatsApp as one of several messaging channels and surrounds it with mature routing, SLA tracking and reporting. It suits organizations that already have defined support processes and the headcount to run them, and its pricing is built per agent seat with AI capabilities layered on top, which is why many smaller teams start looking at Zendesk alternatives once their roster grows. Intercom comes from the opposite direction: it is messaging-led, strong at proactive outbound and at blending support with sales, and its AI agent is billed per resolution, so your cost moves with how often the AI succeeds. Freshdesk covers WhatsApp through the Freshchat side of its suite and is a reasonable fit if you want ticketing and chat from one vendor at a moderate entry price, though features are spread across tiers.
Gorgias is worth a serious look if you sell on Shopify, because it pulls order and refund context into the WhatsApp thread and is priced around ticket volume rather than seats. Tidio is aimed squarely at smaller businesses and pairs live chat with an AI assistant metered on conversations. Help Scout keeps things deliberately simple and email-centric, which is a strength if WhatsApp is a side channel and a limitation if it becomes your main one. Chatwoot is open source: you can connect the Cloud API yourself and self-host, which makes the license cheap and the operational burden real. Corebee sits in this group as a flat-rate option, with WhatsApp live alongside web chat, email, voice, Slack, Facebook, Instagram, SMS and Telegram in a single shared inbox, and no per-seat or per-resolution charge on top.
Why do WhatsApp support bills end up higher than expected?
There are usually three meters running at once, and most teams only budget for one. The first is Meta itself. Replies you send inside the service window that opens when a customer messages you are not billed by Meta, but business-initiated template messages (marketing, utility and authentication) are billed per message at rates that vary by country. If you plan order updates or re-engagement campaigns, read Meta's current rate card for the countries you actually serve before you model anything.
The second meter is your provider, if you use one, which typically adds a platform charge per number or per message volume. The third is your support tool, and this is where small teams get caught. A per-seat model punishes you for adding the warehouse manager who only answers twice a week, so people share logins and lose the audit trail. A per-resolution AI model means a busy month costs more than a quiet one, which makes forecasting awkward exactly when you need it. Flat pricing removes two of those three variables: Corebee is $99 per month with unlimited teammates and unlimited AI conversations, so the only number that still moves is Meta's own messaging charge. Whichever tool you pick, write out all three meters before you sign, because the headline price rarely describes the whole bill.
Where does AI belong in a WhatsApp conversation?
WhatsApp is where customers expect a fast, human-feeling reply, which makes it both the best and the riskiest place to put automation. The pattern that holds up is narrow and honest. Let the AI answer the repetitive questions it can source from your own material, point it at your website and knowledge base rather than letting it improvise, and have it hand the thread to a person the moment the customer asks for one or the answer is not clearly supported. On voice, say plainly that the caller is speaking to an AI; on chat, do not pretend otherwise if asked.
The other half of the value is what happens after the answer. A WhatsApp thread that books a meeting through Cal.com or Calendly, or that writes the contact and conversation summary into HubSpot, Salesforce, Pipedrive, monday or Zoho, has done something your team would otherwise do by hand. That is the part worth automating hardest, because it is invisible to the customer and pure time back for you.
What does a working setup look like step by step?
Start by choosing the number and confirming it is free of any existing WhatsApp registration. Create or claim the Meta Business account and begin business verification early, since that step depends on Meta's review queue and not on you. Pick the support tool and connect WhatsApp through whatever onboarding it offers, then set the display name and profile so customers recognize who they are messaging.
Next, load your real answers: shipping and returns policy, hours, pricing, the five questions you answer every single day. Set the handoff rules, including which keywords escalate immediately and who receives the conversation out of hours. Submit any templates you need for business-initiated messages and expect a review cycle. Finally, test from a phone that is not on your team, deliberately asking something the bot should refuse to answer, so you can see the handoff work before a customer does. With an embedded onboarding flow this is roughly a ten-minute job on the tooling side and needs no developer; the Meta verification and template reviews run on their own clock.
How should a small team actually choose?
Answer three questions honestly. How many people will touch WhatsApp over the next year, including part-timers and the owner? How much of your WhatsApp volume will be you contacting customers rather than them contacting you? And do you have anyone who will happily maintain infrastructure? If the answer to the last one is yes and budget is tight, Chatwoot self-hosted is credible. If you live inside Shopify, Gorgias earns its place. If you need deep reporting, governance and formal SLAs across a large support organization, Zendesk and Intercom are built for that and it shows.
If you are a small or mid-size team that wants WhatsApp answered alongside every other channel, with the whole business able to log in and without a bill that climbs each time volume does, a flat unmetered option fits the shape of the problem better. Compare the plan details against your own three meters, run a week of real conversations through whichever two tools make your shortlist, and judge them on how the handoff feels rather than on the feature grid.