HubSpot’s WhatsApp integration routes incoming WhatsApp Business messages directly into HubSpot’s Conversations inbox and ties each thread to a contact record for workflow triggers and reporting. For teams in Southeast Asia where WhatsApp is the default business channel, this closes the gap between where clients actually communicate and where sales and support data lives.
This guide walks through the setup process and the automation options that matter most for SEA teams.
In HubSpot, go to Settings > Inbox > Inboxes, then click Connect a channel. Select WhatsApp. HubSpot will prompt you to log in to your Facebook account and grant permissions to the Facebook Business portfolio that owns your WhatsApp Business account.
After granting permissions, HubSpot pulls the WhatsApp Business phone numbers associated with your Meta Business Suite account. Select the number you want to connect. Only numbers with a verified WhatsApp Business account and an approved display name are eligible.
Choose which HubSpot Conversations inbox will receive WhatsApp messages. You can create a dedicated WhatsApp inbox or add the channel to an existing shared inbox. Assign the inbox to the relevant team or owner.
Set the default assignee, business hours, and initial bot response (if applicable). If you use HubSpot’s chatflow builder, you can attach a bot to handle incoming WhatsApp messages before routing to an agent.
Send a test WhatsApp message to the connected number from a personal device. Confirm the thread appears in the HubSpot inbox and that the correct contact record is created or matched.
What does the HubSpot WhatsApp integration actually do?
The integration turns your WhatsApp Business number into a channel inside HubSpot Conversations. Every inbound message from a WhatsApp contact appears as a thread in the inbox, alongside email and chat threads. Agents reply directly from HubSpot without switching to the WhatsApp Business app.
Beyond the inbox view, HubSpot uses the WhatsApp conversation as a data event. You can trigger HubSpot workflows based on conversation activity and report on WhatsApp volume alongside every other channel in the same dashboards.
This is the practical difference between the integration and simply monitoring WhatsApp manually: the CRM record becomes the source of truth for the relationship, not a chat thread only one agent can see.
Prerequisites before you connect
The integration requires a few things to be in place before setup:
- A verified WhatsApp Business account (not a personal WhatsApp number or a basic WhatsApp Business app account without API access)
- A Meta Business Suite account that owns or has been granted access to the WhatsApp Business number
- A HubSpot account on a plan that includes the Conversations inbox and WhatsApp channel support (Service Hub Starter or above, or certain Sales Hub configurations)
- Admin access in both HubSpot and Meta Business Suite
If your current WhatsApp setup is through the standard WhatsApp Business app rather than the WhatsApp Business API, you will need to migrate to the API tier before the integration becomes available. Meta’s documentation covers the migration path, and most WhatsApp Business Solution Providers can assist with this step.
How contacts are created and matched
When a new WhatsApp message arrives from an unknown number, HubSpot creates a new contact record using the phone number as the identifier. The contact appears in your HubSpot CRM with the phone number populated and the conversation thread linked.
If a contact with the same phone number already exists in HubSpot, the incoming message is matched to that record rather than creating a duplicate. This matching works on the phone number field, so the number format in HubSpot needs to be consistent with how WhatsApp delivers it (typically in E.164 format with country code).
One practical implication: if your existing contacts have phone numbers stored in local format without country codes (common in Thailand and other SEA markets), you may see duplicate creation rather than matching on those contacts. Cleaning phone number formats before the integration goes live avoids this problem.
Automation triggers from WhatsApp conversations
WhatsApp conversations surface as enrollable triggers in HubSpot’s workflow tool. Common triggers include:
- A conversation is created in the WhatsApp inbox (enroll a contact into a nurture sequence based on first contact)
- A conversation is assigned to a specific owner or team
- A conversation is closed (trigger a follow-up task or satisfaction survey)
- A contact property is updated as a result of the conversation (for example, lifecycle stage)
The automation layer works in both directions. Outbound WhatsApp messages can be triggered by workflow actions, though this requires pre-approved message templates under Meta’s messaging policy. For the first 24 hours after a contact initiates a conversation, free-form messages are permitted. After that window, only approved templates can be sent.
For sales teams, a practical setup enrolls WhatsApp-initiated contacts into a short sequence. The sequence assigns a deal and queues a follow-up task for the rep within a defined window.
Tips for Southeast Asian teams
Teams using WhatsApp across SEA markets like Thailand, Vietnam and Indonesia run into a few patterns that are worth addressing before rollout.
Response time expectations. WhatsApp is a high-expectation channel. Contacts who message on WhatsApp typically expect a response within minutes during business hours. Set realistic business hours in HubSpot and configure an automated acknowledgement message so contacts know the message was received, even if a human reply takes longer.
Language handling. Many SEA teams handle conversations in local languages as well as English. HubSpot does not automatically detect or translate message language. Routing by language capability rather than round-robin prevents mismatched conversations. A triage step in your chatflow can handle this automatically at the start of each thread.
LINE and WhatsApp side by side. In Thailand specifically, LINE remains the dominant messaging channel for many consumer segments. If your team runs both LINE and WhatsApp, each lives in a separate HubSpot inbox. Contacts who message on both will have separate conversation threads, but the contact record is shared if the matching identifiers (email or phone) align. Managing both channels from the same inbox view requires adding both as channels and assigning to the same team.
Template approval lead time. If you plan to use outbound WhatsApp messaging for follow-up sequences or reminders, submit your message templates to Meta for approval before launch. Approval can take several days, and templates that include promotional language are more likely to be rejected on the first submission.
Common setup issues
Permission errors during connection. The most common issue is connecting with a Facebook account that does not have admin access to the Meta Business portfolio. The person completing the connection in HubSpot needs admin rights in both HubSpot and the Meta Business Suite account that owns the WhatsApp number.
Channel not appearing after connection. If the WhatsApp channel does not appear in HubSpot after completing the Meta login flow, check whether the WhatsApp Business account status in Meta Business Suite shows as Active. Accounts pending verification or in a restricted state will not be available for connection.
Messages not routing to the inbox. If incoming messages are not appearing in HubSpot after connection, confirm the channel is assigned to an inbox and that the inbox has at least one active team member. Unassigned inboxes with no members can prevent message routing.
Duplicate contacts. As noted above, phone number format mismatches cause duplicate creation. Review your existing contact data for number format consistency before enabling the integration on a live account.
Frequently asked questions
Do I need the WhatsApp Business API, or does the standard app work?
You need the WhatsApp Business API tier. The standard WhatsApp Business app does not support the Meta Business Suite permissions that HubSpot requires for the integration. Most businesses can access the API through a Meta-approved WhatsApp Business Solution Provider, and some providers offer a straightforward migration path from the app tier.
Can I send proactive WhatsApp messages from HubSpot to contacts?
Yes, but only using Meta-approved message templates outside the 24-hour customer service window. Within 24 hours of a contact-initiated conversation, free-form messages are allowed. For outbound sequences and reminders, templates need to be submitted and approved through Meta Business Suite before they can be used in HubSpot workflows.
How does HubSpot handle WhatsApp messages from contacts not yet in the CRM?
HubSpot creates a new contact record using the phone number as the primary identifier. The conversation thread is linked to the new contact. From there, you can enrich the record manually or through workflow-triggered enrichment tools.
Is the HubSpot WhatsApp integration available on all HubSpot plans?
WhatsApp as a Conversations channel is included on Service Hub Starter and above. Some Sales Hub configurations also include it. Check the current HubSpot pricing page for the most up-to-date plan availability, as channel access can change between product updates.
This is an independent informational resource produced by a HubSpot Platinum Partner. HubSpot is a trademark of HubSpot, Inc.
Planning a HubSpot setup or integration in the region?
Contact us