HubSpot WhatsApp integration:pick the right route, connect it, and prove it works.

The native route is HubSpot’s own WhatsApp channel. Messages arrive in the conversations inbox, threads sit on the contact timeline, and templates can be sent from records, the inbox or workflows. It is the cleanest option when your portal already has the right hub, because there is no second inbox for reps to check.

The provider route uses a WhatsApp Business Solution Provider (BSP) such as Wati, Interakt or AiSensy, each of which publishes its own HubSpot integration. The provider owns the WhatsApp connection, the chatbot and the bulk-send tool, and pushes contacts, messages or events into HubSpot. How much reaches HubSpot varies by provider, which is exactly why the comparison of Interakt vs Wati vs AiSensy focuses on CRM sync depth rather than features.

The automation route uses Zapier, Make or Pabbly Connect to copy events from a WhatsApp provider into HubSpot: create or update a contact when a new chat starts, set a property when someone opts in, create a deal when a keyword is used. It is useful glue, but it does not give reps a two-way inbox inside HubSpot. One limit to know: HubSpot’s webhook workflow trigger (Professional or Enterprise) only enrols a record that already exists with a matching unique property value, so it updates known contacts but does not create new ones.

Coexistence is the variant for numbers already on the WhatsApp Business App. HubSpot’s coexistence article lists Super Admin permission in HubSpot, admin rights on Meta Business Manager, and a number registered in the Business App on a device. If the number was connected to HubSpot or another integration, disconnect it and wait 10 to 15 minutes before reconnecting. Once connected, HubSpot imports the last 180 days of conversations and messages sync both ways. Media in the backfill shows as placeholders, templates cannot be sent from the phone, voice notes can only be sent from the phone, and the send rate is capped at 20 messages per second.

After connecting, build a custom inbox view filtered to source WhatsApp so the team can see WhatsApp threads apart from email and chat, and assign ownership rules the same way you would for any other channel. If leads should be distributed across reps, use the same logic as your round robin lead routing in HubSpot rather than a separate WhatsApp-only rule.

HubSpot’s documentation says a WhatsApp session stays open for 24 hours after the contact’s last response. Inside it, reps can send free-form messages. Once it closes, the only way to restart the thread is a template; if the contact replies to the template, a new 24-hour session opens.

Templates are created in your WhatsApp Business account and sync into HubSpot. HubSpot syncs only templates your team created, not WhatsApp’s auto-generated samples, and its template article notes that templates with multiple button types, a location header or flow buttons do not sync. Two limits matter for automation:

• Personalisation is contact and company only. HubSpot states that only contact and company personalisation tokens work in WhatsApp templates. Deal, ticket and custom object tokens do not, so an order number or deal amount must be copied to a contact property first.
• Workflow sends need recorded opt-in. HubSpot requires verifiable opt-in consent before sending through a contact-based workflow, and recommends a Manage communication subscriptions action before the Send WhatsApp message action. Meta’s own opt-in rules require that the person is clearly told they are opting in to messages from your business, by name.

Meta classifies every template as marketing, utility or authentication, and the category sets the price. A utility template follows a user action and must be non-promotional; Meta’s guidelines give “an order update with a promo” as an example of mixed content that is treated as marketing, and since 16 April 2025 a utility template can be recategorised to marketing instantly.

The question that separates provider apps is not features but what they write into HubSpot. Ask each provider, in writing, which of these its HubSpot app does:

1. Creates or updates a contact when a new number messages you, and how it matches existing contacts.
2. Logs every message to the contact timeline, or only the first message and a link out.
3. Lets reps reply from HubSpot, or only from the provider’s inbox.
4. Triggers templates from HubSpot workflows, and whether it can read deal or ticket properties.
5. Writes opt-in status to a HubSpot property your workflows can check.
6. Stores the click-to-WhatsApp ad referral and click ID on the contact.

Matching is the one that causes silent damage. HubSpot’s deduplication works on email address for contacts. A WhatsApp lead usually arrives with a phone number and no email, so a careless integration creates a second contact for someone who already exists. Ask how the app matches on phone, normalise numbers to one format with the country code, and test with a contact who is already in the CRM.

The search phrase wati hubspot vs interakt hubspot is really this checklist. Both publish HubSpot integrations, as do AiSensy and others; the neutral provider comparison scores them on CRM sync depth, Shopify triggers, markup and seat pricing. If you also need WhatsApp in Zoho, the same questions apply, and the WhatsApp automation service covers both CRMs.

Two paths start a WhatsApp conversation. A website button (a wa.me link) opens WhatsApp from your site, so the ad click ID exists on the landing page but not in the chat. A click-to-WhatsApp ad skips the site entirely, and Meta passes referral data, including the click identifier ctwa_clid, in the webhook for the first inbound message. HubSpot’s documentation for the native channel does not say whether that click ID is stored on the contact, so treat it as something to test, not assume.

The reliable pattern is the one in the guide to tracking WhatsApp leads in Google Ads and Meta: put a short reference code in the prefilled message, store the click IDs and UTMs against it on your site, read the code when the chat lands in HubSpot, and write the source to contact properties. Then send qualified and won outcomes back to the ad platforms. For Meta that means the Conversions API, set up as described in the Meta Conversions API setup guide; for Google it is offline conversion import, the same mechanism covered for CRMs in enhanced conversions for leads with HubSpot and Zoho.

Keep the field design simple: Original source, WhatsApp entry point (website button, click-to-WhatsApp ad, QR code, organic), campaign, reference code, and first message time. Add them to your CRM data dictionary so the next admin knows who writes each one.

If WhatsApp is one channel in a portal that also needs routing, lifecycle stages and reporting fixed, scope it as part of a wider HubSpot portal audit rather than a one-off connection. If the deeper question is why leads do not turn into revenue, start with the Revenue Diagnostic: two weeks with read-only access to ad platforms, analytics and CRM, at ₹90,000 for companies in India ($1,500 elsewhere), ending in the binding constraint in writing and a 90-day plan.

For the commercial question of who to hire for HubSpot work in India, read the HubSpot consultant guide; for the licence side, the HubSpot price in India guide covers tiers, seats and GST. Teams with portal leads from marketplaces can pair this with the IndiaMART HubSpot integration guide, since both channels produce phone-first leads with the same matching problem.