Experience Lion CRM — The King of WhatsApp CRM 7 Days Free Limited Access
→ Request Access

HubSpot WhatsApp Integration: Complete Setup Guide (2026)

How to connect WhatsApp to HubSpot in 2026: the three routes, real setup steps, costs, tier limits, and the whitelabel option agencies sell to clients.

A marketing head runs a report in HubSpot and sees that last month’s campaign produced ninety-four leads and eleven replies. The number looks terrible, so she asks the sales team what went wrong. Nothing went wrong. The team spoke to more than sixty of those leads. They just did all of it on WhatsApp, from their own phones, and HubSpot never saw a single message. The report is not measuring the business. It is measuring the one channel the business stopped using.

This is the gap a HubSpot WhatsApp integration is supposed to close. Done properly, WhatsApp becomes a channel inside HubSpot like email is: messages land on the contact record, reps reply from the inbox, workflows can send approved templates, and reporting finally counts the conversations that actually move deals. Done badly, you pay for a Professional seat you did not need and your team quietly goes back to their personal phones anyway.

This guide covers what the integration really is, the three routes you can take, what HubSpot’s native channel does and does not do, what the whole thing costs in 2026, and how agencies package this setup for clients under their own brand. It is written for the person choosing an approach, and for the agencies and resellers who get paid to build it.

In this guide

What a HubSpot WhatsApp integration actually means

The phrase covers three quite different things, and most of the wasted money in this area comes from confusing them.

The first is a shared team inbox. WhatsApp messages arrive in HubSpot’s Conversations inbox or Help Desk, several people can answer from one business number, and every message is stitched onto the right contact record. This is what most businesses actually want when they ask for the integration, and it is what HubSpot’s native channel is built to do.

The second is automation. HubSpot workflows send WhatsApp template messages when something happens in the CRM, so a new lead gets an instant reply, a deal that reaches a stage triggers a reminder, and a customer gets an order update without anyone typing it. This is where the real time savings live, and it depends on your HubSpot tier.

The third is reporting and attribution. WhatsApp conversations show up in HubSpot’s reports, so you can finally see how many replies a campaign produced and which conversations turned into revenue. This one is almost invisible until you have it, and then it changes how you spend money.

A proper setup gives you all three. A shortcut usually gives you the first one only, and the gap shows up about two months later when someone asks why nothing is automated.

The three ways to connect WhatsApp to HubSpot

There are three honest routes, and the right one depends on your HubSpot tier and how central chat is to your business.

Route one: HubSpot’s native WhatsApp channel. HubSpot connects WhatsApp directly to the Conversations inbox. You link a WhatsApp Business Account through Meta, pick a number, and messages start flowing into HubSpot. This is the cleanest route because there is no third tool to pay for or debug, and support is one company. The catch is the plan requirement, covered in the next section.

Route two: a marketplace app or third-party WhatsApp platform. You run a dedicated WhatsApp tool alongside HubSpot and sync the two. The WhatsApp platform handles broadcasts, chatbots, agent routing, and campaign reporting, and it writes activity back to HubSpot contacts. This route costs more in software but gives you far stronger messaging features, and it works on HubSpot tiers where the native channel is not available.

Route three: a custom build on the WhatsApp Business API. You get API access through a provider, then use HubSpot’s API to move data between the two yourself. This makes sense when you have unusual requirements or an in-house developer already maintaining integrations. It rarely makes sense otherwise, because you have now taken on the maintenance of something two companies already maintain for you.

Most businesses should start at route one and move to route two when messaging outgrows a shared inbox. Agencies selling to clients usually end up on route two or on the whitelabel option described later, because a branded product is a better business than a configured connector.

The tier question: what HubSpot plan you need

This is the detail that derails more HubSpot WhatsApp projects than anything else, so check it before you plan anything.

The native WhatsApp channel is not available on HubSpot’s free tools or on the Starter tiers. It sits on the Professional and Enterprise levels of the relevant Hub. If you are on Starter today and the quote you were given assumed the native channel, the real cost of the project includes a HubSpot upgrade, and that upgrade is usually the largest single line in the budget.

There is a second tier trap around automation. Getting messages into the inbox is one thing; having workflows send WhatsApp templates automatically is a separate capability, and it also lives on the higher tiers. Teams sometimes get the inbox working, assume automation is included, and only discover the gap when they try to build the first workflow.

Plan names and packaging change, so verify against HubSpot’s current pricing page for your Hub before you commit. The stable point is the shape of the rule: the native channel and its automation are paid, higher-tier features, and if you are not on those tiers your realistic options are route two or the whitelabel route.

This is also the moment where the honest comparison happens. If WhatsApp is the main way your team sells, paying to upgrade HubSpot so that chat becomes one tab inside a CRM can be worse value than putting a chat-first tool at the centre and letting HubSpot do what it is genuinely good at.

Before you start: what you need ready

Gather these before you touch any settings. Every one of them has stalled a setup mid-way.

A Meta Business account, verified. You need a Meta Business account with business verification either complete or in progress. Verification asks for documents that prove the business is real, and approval is not instant. Start this first, because everything else waits on it.

A phone number that is free. The number you connect cannot be currently active on the normal WhatsApp app or the WhatsApp Business app. If your business number is already in use there, you have to remove it from that app first, and the chat history stored on that device is lost when you do. Many teams choose a fresh number for the integration and migrate customers across gradually.

The right HubSpot tier and permissions. Confirm the plan question above, and make sure the person doing the setup has admin rights in both HubSpot and Meta Business. Half-finished setups are usually a permissions problem, not a technical one.

Clean phone numbers in your CRM. The integration matches incoming numbers to contacts as text. If your database has a mix of formats with spaces, dashes, missing country codes, and leading zeros, matching will fail on a large share of your contacts. Standardise to one international format before you go live, not after.

A short list of message templates. Decide the first three or four messages you want to send outside a live conversation, because those need approval before they work. New lead acknowledgement, appointment reminder, and order or status update cover most cases.

Setting up the native HubSpot WhatsApp channel

The sequence below is the order that avoids rework. The exact button names shift as HubSpot updates its interface, so treat these as steps rather than a click script.

Step one: prepare Meta. Log into Meta Business, confirm the business account exists and verification is underway, and check that the number you plan to use is free of the WhatsApp apps. Doing this first prevents the most common failure, which is getting three screens into HubSpot and discovering the number is unavailable.

Step two: add the channel in HubSpot. In HubSpot’s inbox and channel settings, add a WhatsApp channel. HubSpot will send you through a Meta login and permission flow to link your WhatsApp Business Account.

Step three: connect the number and verify it. Choose the number, complete the verification code step, and give the sender a display name customers will recognise. The display name is what people see when you message them, so use the business name rather than an internal label.

Step four: route the conversations. Decide which inbox the channel feeds and who gets assigned. Unassigned WhatsApp conversations are the fastest way to lose the trust of a team that was told this would be an improvement. Set the routing rules and the working hours before anyone starts using it.

Step five: create and submit your templates. Build the messages you listed earlier and submit them for approval. Approval usually takes anywhere from minutes to a day. Write them as useful, specific messages rather than promotional filler, because vague marketing copy is the most common rejection reason.

Step six: test properly. Message the business number from a phone that is not a team phone. Confirm the message lands in the right inbox, the contact is created or matched correctly, an outgoing reply arrives, and the whole exchange is visible on the contact record. Then test with a number already in your CRM, which is the case that exposes phone-format problems.

Step seven: go live in one team first. Point one team or one campaign at the channel for a week before you move everyone. Problems found by three people are cheap. The same problems found by thirty people become the reason the project gets abandoned.

Using WhatsApp inside HubSpot workflows

Once the channel works, automation is where the payback is, and the rule that governs all of it is the messaging window.

WhatsApp lets you reply freely for a limited period after a customer’s last message, commonly twenty-four hours. Inside that window you can send normal messages. Outside it, you can only send a template that Meta has approved in advance. Every automation you design has to respect this, and it is the single thing that catches teams out.

The automations worth building first are simple. An instant acknowledgement when a form is submitted, so a lead hears from you in seconds rather than hours, tends to produce the biggest measurable lift because it lands while the person is still interested. An appointment or demo reminder cuts no-shows, which is usually the easiest number to move in the whole business. A status update after a deal reaches a stage removes a category of incoming questions your team currently answers by hand.

Two design habits keep this from going wrong later. Send WhatsApp from a workflow only when the message is genuinely useful to the person receiving it, because WhatsApp is a personal channel and people block businesses that abuse it far faster than they unsubscribe from email. And always leave a human path, so that when someone replies to an automated message a real person picks it up quickly rather than the reply sitting unread in an inbox nobody watches.

What the integration costs in 2026

There are three separate bills, and people usually plan for one of them.

Meta’s messaging charges. Meta bills for business-initiated template messages, and the rate varies by country and by category, with marketing messages costing more than utility ones. Conversations the customer starts, and your replies within the open window, are treated far more cheaply or as free. Meta has revised this model more than once, so check the current rate card for the countries you message rather than trusting a figure from a blog post, including this one.

Your software cost. On the native route this is your HubSpot subscription, and if it requires moving from Starter to Professional the jump is significant and per-seat. On the third-party route it is your existing HubSpot plan plus the WhatsApp platform fee, which is often the cheaper total when the upgrade would only be for this one feature. Do this comparison with real seat counts before you decide, because the two routes can differ by several times.

Setup and training time. This is the line everyone forgets and the one that actually decides whether the project works. Verification, number migration, template writing and approval, phone-number cleanup, workflow building, and getting a sales team to change where they type all take real hours. Budget them honestly.

The pattern across most rollouts is that messaging spend comes in lower than people fear while setup effort comes in higher than people plan. Build the budget accordingly.

What the native HubSpot WhatsApp integration cannot do

The native channel is good at what it is designed for. It is worth being clear about where it stops, because these gaps are the reason teams add a second tool later.

Large broadcast campaigns. A conversations inbox is built around one thread at a time. Sending a segmented campaign to thousands of contacts with proper delivery reporting, retry handling, and per-segment results is a different job, and it is what dedicated WhatsApp platforms exist to do.

Chatbots and deep routing. Automated qualification flows, menu-driven self-service, and rule-based routing across shifts and languages are usually thin or absent in a CRM’s native channel. If you want a bot to handle the first three questions before a human joins, expect to add a tool.

A chat-first way of working. The inbox is a CRM inbox. Teams that live in chat all day tend to want a pipeline they can see and drag conversations through, and that visual, chat-first workflow is not what a CRM inbox is shaped like. This is a genuine adoption risk, not a feature checkbox, and it is the most common reason a technically successful setup goes unused.

Your own branding. Everything the client sees says HubSpot. For an agency this matters commercially, which is the subject of the next section.

None of these are reasons to avoid the native channel. They are reasons to know in advance which category you are in, so you buy once instead of twice.

The whitelabel route: selling this setup to clients

If you are an agency or consultant, there is a business decision sitting underneath the technical one, and it is worth more than the setup fee.

Configuring a client’s HubSpot WhatsApp channel is a project. You scope it, you do it, you invoice once, and the client now owns a thing that runs without you. It is honest work and it pays honestly, but it ends.

Selling a branded WhatsApp CRM is a product. The client uses a platform with your name and your logo on it, they pay every month, and you keep the margin between what the platform costs you and what you charge them. The setup work is similar. The revenue is recurring rather than one-off, and it compounds with every client you add.

The two are not in conflict. The useful question is where the client’s work really happens. If HubSpot is genuinely the centre of the business, with marketing, deals, and reporting all living there, then connecting WhatsApp to it is the right recommendation and you should make it. If the sales team spends its day in chat and HubSpot is mostly a record-keeping system, then a branded chat-first platform will get used every day while a CRM channel quietly gets abandoned, and recommending it serves the client better as well as you.

For agencies taking the branded route, the practical requirements are the same ones that decide whether the business scales: your own domain and logo throughout, the ability to create and manage client accounts yourself without asking anyone, per-client licence pricing you control, and a support path that does not expose the platform behind your brand. Lion CRM’s whitelabel programme is built around exactly this shape, with a minimum of ten licences to start and the reseller admin panel needed to run client accounts under your own brand.

Common problems and how to fix them

The number will not connect. Almost always because it is still active on the WhatsApp or WhatsApp Business app. Remove it there first, accept that the on-device history goes with it, then retry. The second most common cause is business verification that has not finished.

Messages arrive but do not attach to the right contact. This is a phone-format problem, not a settings problem. The match happens on the number as text, so a leading zero, a missing country code, or stray spaces will stop it finding a contact a human can see is the same person. Standardise the whole database to one international format and retest.

Templates keep getting rejected. Rejections usually come from vague promotional wording, missing context around variables, or a category that does not match the content. Rewrite the message as something specific and genuinely useful to the recipient, make the variables obviously meaningful, and resubmit. Copying the tone of a transactional email works better than copying the tone of an ad.

Automated messages are not sending. Check the messaging window first, because a workflow trying to send a free-form message outside the open window will fail by design. If the message is a template and it still fails, confirm the template is approved and that the workflow is on a tier where WhatsApp sending is available.

The team is not using it. Nothing here is technical. Either the routing is wrong so conversations do not reach the right person, or the tool does not match how the team works. Watch someone use it for an hour. The answer is usually obvious within ten minutes and is almost never the one raised in the meeting.

A 14-day rollout plan

Days 1 to 3: preparation. Start Meta business verification, confirm your HubSpot tier covers what you need, free up or choose the phone number, and start the phone-number cleanup in your database. Verification and cleanup run in the background, so beginning them on day one removes them from the critical path.

Days 4 to 6: connection. Add the channel, connect and verify the number, set the display name, and configure inbox routing, assignment, and working hours. Do not skip routing. It is the setting that decides whether the pilot feels like an improvement.

Days 7 to 9: templates and testing. Write and submit the first three or four templates. While they are in review, test the inbound path thoroughly from outside numbers and from numbers already in the CRM. Fix the matching problems this uncovers before anyone else sees them.

Days 10 to 12: pilot. One team, one campaign, real customers. Watch what happens rather than asking for feedback in a meeting. Build the first workflow, usually the instant reply to a form submission, and check that replies to it reach a human quickly.

Days 13 to 14: rollout and measure. Extend to the rest of the team with a short written guide of the three things they must do differently. Record your starting numbers now, because response time and reply rate are what you will be judged on in a month, and nobody remembers what they were before.

Frequently asked questions

Does HubSpot have a native WhatsApp integration?
Yes. HubSpot offers a native WhatsApp channel that connects a WhatsApp Business Account to the Conversations inbox and Help Desk, so messages land on contact records and a team can reply from one shared business number. The important qualifier is that it is not available on the free tools or the Starter tiers, and the automation side is also a higher-tier capability. Check your current plan against HubSpot’s pricing page before you scope any project around it.

Can I use WhatsApp with HubSpot on a free or Starter plan?
Not through the native channel. The realistic option on those tiers is a third-party WhatsApp platform that syncs activity back to HubSpot, which lets you keep your current subscription and often works out cheaper than upgrading purely for this one feature. Run the comparison with your real seat count, because a per-seat upgrade across a whole team can cost several times what a dedicated messaging tool costs.

Do I need a new phone number for the HubSpot WhatsApp integration?
Usually yes, and it is the cleaner path. The number you connect cannot be active on the regular WhatsApp or WhatsApp Business app, so an existing business number has to be freed up first, and the chat history on that device is lost when you do it. Many teams start with a fresh number and move customers across gradually with a message from the old one. Either approach works, but decide before you begin rather than halfway through.

How much does a HubSpot WhatsApp integration cost?
Plan for three bills: Meta’s per-message charges, which vary by country and message category; your software cost, which is either a HubSpot tier that includes the channel or your current plan plus a WhatsApp platform; and the setup and training hours, which is the line most often left out. Messaging spend usually comes in lower than people expect while setup effort comes in higher, so check Meta’s current rate card for your countries and budget the hours honestly.

Can HubSpot workflows send WhatsApp messages automatically?
Yes, on the tiers that support it, and within WhatsApp’s rules. Outside the roughly twenty-four hour window after a customer’s last message you can only send a template Meta has approved in advance, so every automation has to be designed around that. The highest-value ones to build first are an instant reply to a form submission, an appointment reminder, and a status update when a deal changes stage.

Should I connect WhatsApp to a client’s HubSpot or sell them my own branded CRM?
It depends on where the client’s work actually happens, and both can be right. If HubSpot is genuinely the centre of the business, a connector is the honest recommendation. If the sales team lives in chat all day, a branded chat-first platform will get used while a CRM channel gets abandoned. For an agency the branded route is also the better business, because a setup fee is earned once while a monthly per-licence margin keeps paying.

Become a Reseller