Back to Blog
HubSpot WhatsApp Integration: Setup, Limits and Bots

HubSpot WhatsApp Integration: Setup, Limits and Bots

HubSpot WhatsApp Integration: Setup, Limits and Bots

Business lead configuring a WhatsApp channel connection

HubSpot connects to WhatsApp through a native channel in the conversations inbox. You link your WhatsApp Business account, and messages then appear in the CRM next to the contact record, where your team can reply, track and automate them. The setup takes a few minutes if your permissions are in order. What takes longer is deciding which messages to automate and how to stay within Meta’s rules. This guide covers both, plus the Salesforce equivalent, for teams working from France.

Botiqueai
botiqueai.com
Connect WhatsApp Automation to Your CRM
BotiqueAI builds custom chatbots, intelligent agents and automations tailored to business needs, including customer service and marketing workflows.
Explore BotiqueAI solutions

TL;DR

  • HubSpot’s native integration lets teams manage WhatsApp conversations in the CRM, track messages and automate personalized ones.
  • You need Super Admin rights in HubSpot, Admin rights on your Meta Business Manager and a number registered in the WhatsApp Business App.
  • Outside the 24-hour session window, only approved template messages can restart a conversation, and opt-in consent must name your company.
  • Salesforce connects to WhatsApp through Messaging channels, Omni-Channel routing and an optional enhanced bot, with more admin work than HubSpot.
  • A custom bot sits on top of either CRM to qualify leads and hand over to a human with the context already logged.

Table of Contents

What the integration does for your teams

The core benefit is that WhatsApp stops being a side channel living on one employee’s phone. Conversations land in the CRM, attached to contacts, and become visible to sales, marketing and support. HubSpot describes its integration as a way to manage conversations, track messages and automate personalized messages from inside the CRM.

In practice that means three things for each team:

  • Sales: an inbound WhatsApp message creates or matches a contact, so a lead from a click-to-chat button is not lost. Reps see the full history before they reply.
  • Marketing: you can send template-based follow-ups and trigger them from workflows, and attribute leads to the channel instead of treating them as untraceable.
  • Customer service: agents answer from the shared inbox, and ownership, status and notes stay in one place.

Salesforce pursues the same goal. Its Unified Conversations for WhatsApp is powered by Data Cloud, so marketers and service agents can work from a shared customer profile during conversations.

What you need before connecting WhatsApp to HubSpot

Most failed setups come down to permissions, not technology. Check these before you open the settings page:

  1. Super Admin permissions in HubSpot. A regular user cannot add the channel.
  2. Admin permissions on your company’s Meta Business Manager. HubSpot lists Super Admin in HubSpot, Admin on Meta Business Manager and a number registered in the WhatsApp Business App as the requirements for the coexistence method.
  3. A phone number already registered in the WhatsApp Business App. Use the number your customers already know.
  4. A verified Meta Business Manager if you plan volume. HubSpot requires verification to send more than 50 business-initiated conversations per day.

Verification takes Meta some time, so start it early if you plan campaigns. It is the step most teams discover too late.

How to connect WhatsApp to HubSpot, step by step

HubSpot’s current route is called coexistence. It lets the same number work in the WhatsApp Business App on your phone and in HubSpot at the same time, so your team does not have to abandon the app people already use.

  1. In HubSpot, open the settings and go to the conversations inbox channels, then choose to connect a WhatsApp channel.
  2. Sign in with your Meta account and select your business assets: the Meta Business Manager and the WhatsApp Business account.
  3. Scan the QR code shown on screen with the WhatsApp Business App on the phone that holds the number.
  4. Confirm, then create a WhatsApp view in your conversations inbox so your team sees the threads.

Follow HubSpot’s own page for the exact screens, which change over time: connecting a WhatsApp number with coexistence.

What syncs and what does not

This is the question that surprises people most. With coexistence, HubSpot imports conversation history from the last 180 days. With the standard channel connection of an existing account, only messages sent after you connect are synced, and earlier conversations stay out of the CRM.

Comparison of WhatsApp conversation history sync methods

So if you have months of customer conversations on a phone, decide which method fits before you connect. If the history matters for sales context, use coexistence and check the imported threads on a few key accounts after the first sync.

Messages, windows and templates: what you can send

WhatsApp works with a 24-hour customer service window. Once a customer writes to you, you can reply freely for 24 hours after their last message. After that, you need an approved template to restart the thread. HubSpot confirms that once a session closes, you can reinitiate the thread by sending a template message.

A simple rule of thumb for your team:

Situation What you can send
Customer wrote within the last 24 hours Free-form replies
Customer’s last message is older than 24 hours An approved template only
First contact with a person who never wrote to you An approved template, after valid opt-in

Templates need Meta’s approval, so write them clearly: one purpose per template, a variable for the first name and a clear next step. Reminders, order updates and follow-ups after a demo are typical examples.

Automating with HubSpot workflows and a WhatsApp bot

Two layers of automation exist, and they solve different problems.

Workflows handle triggered messages. A form submission, a deal stage change or a missed meeting can send a template, create a task or assign the contact to a rep. They are ideal for follow-ups and reminders because the logic is rule-based and predictable.

A bot handles the conversation itself. It greets the customer, asks qualifying questions, answers frequent questions and passes the thread to a person when needed. This is where a custom-built assistant helps most, because the quality depends on your product knowledge, your qualification criteria and your tone, none of which a generic template captures.

A good first bot does only a few things well:

  • Collects the need, company size and timeline, and writes them to contact properties.
  • Answers the ten questions your team gets every week.
  • Books a meeting or hands over to a human, with the transcript attached.
  • Stops cleanly when a customer asks to stop.

We go deeper on the CRM side in our article on messaging flows that close deals and on AI integrations for HubSpot and Pipedrive.

Limits to plan around

  • The 24-hour window shapes every flow: design bots to resolve or hand over inside it, and keep a template ready for late follow-ups.
  • Templates require approval, so a new campaign needs lead time.
  • Daily business-initiated volume is capped until your Meta Business Manager is verified.
  • Everything the bot says must remain consistent with what you promised at opt-in.

Connecting WhatsApp to Salesforce

Salesforce is more configurable, and the setup reflects it. Instead of one channel screen, you assemble several pieces. Salesforce’s activation checklist covers assigning Messaging permission licenses and permission sets, configuring routing with an Omni-Channel flow and a fallback queue, and setting up the Service Console and Messaging Session record page.

For a team lead, that translates into a short checklist:

  1. Decide who handles WhatsApp conversations and give them the right licenses and permission sets.
  2. Define routing: which queue receives which conversation, and which queue catches anything unrouted.
  3. Prepare the agent workspace so the messaging session sits next to the customer record.
  4. Decide whether a bot answers first.

Salesforce WhatsApp bots

Salesforce recommends adding an enhanced bot to your support process and referencing it in an Omni-Channel flow, which controls which sessions reach the bot. On the marketing side, Marketing Cloud Engagement supports carousel messages, quick reply buttons and location requests for richer interactions than plain text.

The pattern is the same as in HubSpot: the CRM stores and routes, and the bot handles the first exchange. The difference is that in Salesforce the routing logic is yours to design, so mapping the conversation paths before building saves rework.

HubSpot or Salesforce: which fits your team

Both work. The choice usually follows the CRM you already run, not the WhatsApp feature list. Still, the setup effort differs:

Criterion HubSpot Salesforce
Setup path Connect a channel, scan a QR code Licenses, permission sets, Omni-Channel flow, queues, record pages
Best fit SMEs with a small sales and support team Organizations with defined service operations and admins
Bot route Workflows plus a connected assistant Enhanced bot referenced in an Omni-Channel flow
History Coexistence imports 180 days Depends on channel and configuration

If you run neither well yet, fix the CRM basics first. Clean contact properties and clear lifecycle stages matter more than the channel. Our guide on automating CRM data enrichment helps with that.

WhatsApp automation fails commercially when it feels like spam, and fails technically when Meta restricts the account. Three checks keep you safe.

Meta’s rules require explicit opt-in before you initiate messages. The consent must include the business name and clearly state that the person agrees to receive WhatsApp messages from that company. A generic newsletter checkbox does not do this. Add a dedicated, unticked checkbox on your forms with your company name in the wording, and store the proof of consent on the contact record.

The same policy says businesses must respect requests to block, stop or unsubscribe. Configure a keyword such as STOP in your bot and a workflow that updates the contact’s consent property immediately. For GDPR questions specific to your data, consult your data protection officer or counsel.

Consent that names your company

Costs

The WhatsApp Business Platform charges per delivered message, based on the recipient and the message category, and rates vary by market and category. Read the official rate card for France before you budget a campaign, because the category of your template (marketing, utility, authentication) changes the price. Service replies inside the 24-hour window are the simplest way to keep costs predictable. For two worked budgets, see our WhatsApp chatbot cost examples for French buyers.

A short compliance checklist

  • Opt-in wording names your company and mentions WhatsApp.
  • Each template has one clear purpose and matches what the person agreed to.
  • Opt-out works in one message and is honored everywhere.
  • Your Meta Business Manager is verified before you scale volume.
  • A human can take over any thread.

Our perspective

Most companies we meet do not struggle to connect WhatsApp to their CRM. They struggle with what happens next: who answers at 8 p.m., what the bot may promise, and where the qualification data goes.

We build the bot and the integration as one project. The assistant is designed around your sales process, writes clean data into HubSpot or Salesforce, and hands over to your team with the full context. Our approach is designed to show results fast: we often deliver a proof of concept within 14 days, and the initial audit is free, with no long-term contract required.

Our deployments are designed to be GDPR-compliant, which matters when consent, templates and message logs all live inside a CRM. Our advice for a first project: pick one use case, such as lead qualification or order follow-up, measure it for a few weeks, then extend.

Botiqueai

Build it with us

If you would rather not assemble channel, bot, templates and CRM mapping yourself, we can do it for you. We develop WhatsApp assistants and integrate them with your CRM, using the Meta Cloud API or Twilio. See our WhatsApp Business integration service for the scope, or look at our WhatsApp Business chatbot if you want to see the product first.

Botiqueai

If you sell online, our guide to launching WhatsApp commerce in six weeks shows how the same setup supports orders. To discuss your own case and book the free audit, start from our main page.

FAQ

Can I connect WhatsApp to HubSpot without losing my current app?

Yes, with coexistence. The same number works in the WhatsApp Business App and in HubSpot at once. You need Super Admin rights in HubSpot, Admin rights on the Meta Business Manager and a number registered in the WhatsApp Business App.

Will my old WhatsApp conversations appear in HubSpot?

It depends on the method. Coexistence imports the last 180 days of history. A standard channel connection syncs only messages sent after you connect. Choose before connecting if history matters to your team.

Can I build a WhatsApp bot on HubSpot or Salesforce?

Yes, on both. In HubSpot you combine workflows with a connected assistant. In Salesforce you reference an enhanced bot in an Omni-Channel flow to control which sessions it handles. In both cases, design a clear handover to a human.

Yes. Meta requires explicit opt-in that names your company and states that the person agrees to receive WhatsApp messages from you. Outside the 24-hour window you can only use approved templates, and you must honor any request to stop.

How much does it cost to send WhatsApp messages?

Meta charges per delivered message, depending on the recipient’s market and the message category. Check the official rate card for France. Replies within the 24-hour window are the easiest to forecast.

Sources

© 2026 BotiqueAI — Reproduction prohibited without attribution.