Choosing a WhatsApp Business API platform for HubSpot means looking past feature lists and into how the integration actually behaves day to day, from lead capture to conversation handoff. This FAQ answers the most common questions UK businesses ask when evaluating WhatsApp-to-HubSpot integrations, based on real onboarding and integration discussions with teams making the switch.
Before comparing platforms, it helps to understand what "native HubSpot integration" actually means in practice and why the underlying WhatsApp API matters as much as the CRM connection itself.
A native integration connects WhatsApp Business API conversations directly to HubSpot's CRM records, so messages, contact details, and conversation history sit alongside the rest of a lead's activity rather than in a separate app. This means a sales or lettings team working inside HubSpot can see WhatsApp messages next to email history, deal stages, and notes without switching tools. The integration is built specifically to improve lead management and communication, rather than simply forwarding messages into HubSpot as an afterthought. For businesses that already run their pipeline through HubSpot, this removes the need for staff to check a second inbox to know where a lead stands.
There are three forms of WhatsApp, and only one is built for team-based CRM integration: the personal WhatsApp app, the free WhatsApp Business app for solo users, and the WhatsApp Business API for teams. A HubSpot integration depends on the API version, because the Business app is built around a single phone with QR-code access and cannot connect properly to a CRM at team scale. Businesses evaluating platforms should confirm which version of WhatsApp they're being sold before assessing HubSpot compatibility, since the app-based version simply isn't built to sync structured conversation data into a CRM. Getting this distinction right upfront avoids a common onboarding mistake where a team buys the wrong tier and then finds the HubSpot connection doesn't behave as expected.
Onboarding for the WhatsApp API platform includes a detailed walkthrough covering both Meta Business Suite setup and the HubSpot connection itself. This is documented as a structured process rather than a self-serve toggle, reflecting the fact that WhatsApp API access requires Meta-side verification alongside the CRM-side configuration. Teams going through onboarding can expect discussion of platform integration specifics, not just a generic "connect your account" flow. Because both the WhatsApp and HubSpot sides need to be configured correctly, onboarding conversations typically walk through both systems together rather than treating them as separate setup steps.
Once the connection is live, the value of a WhatsApp-HubSpot integration shows up in how leads move through the pipeline and how much of that movement can be automated.
Automation is a core part of the integration, covering how WhatsApp Business connects with HubSpot for lead management and communication workflows. The discussion of this automation centres on reducing manual handling of leads as they arrive, rather than treating WhatsApp purely as a messaging channel bolted onto the CRM. This matters most for teams handling volume, where every lead needs a first response fast and every conversation needs to land in the right CRM record without manual re-entry.
AI is discussed as part of the WhatsApp solution for customer interaction and lead management, sitting alongside the marketing and CRM functionality rather than as a separate product. The integration conversation specifically raises the potential use of AI to support how leads are handled once they arrive through WhatsApp. This is distinct from the API and CRM connection itself: AI sits on top of the messaging and integration layer to help manage the volume and speed of incoming conversations.
Sales team use is a specific focus of WhatsApp Business API integration discussions, covering both platform capabilities and how those capabilities apply to a sales workflow. This includes evaluating the API's capacity to support the practical needs of a sales team working leads through to conversion, not just the technical mechanics of message delivery. For a HubSpot-connected sales team, this means the integration needs to support the pace and structure of an active pipeline, not just casual one-off messaging.
The platform includes a notification mechanism for unresponded chats, flagging conversations after 5 minutes without a reply. This is built into the operational metrics of the service rather than being an optional add-on, reflecting how important fast response time is to WhatsApp lead handling. For sectors where speed to lead determines whether a prospect stays engaged, this kind of built-in alert reduces the risk of a lead going cold inside a shared inbox.
Some sectors have integration needs that go beyond general CRM connectivity, and estate agency is one of the most detailed examples covered.
WhatsApp integration solutions for estate agents are analysed as a distinct category, reflecting how property businesses use WhatsApp differently from general sales teams. This analysis covers integration solutions specifically built around estate agency communication needs. Estate agents evaluating a WhatsApp-HubSpot connection should look for this kind of sector-specific analysis rather than assuming a generic sales integration covers the same ground.
Bullhorn is named alongside HubSpot as a system these integrations are built to connect with, particularly in the context of bulk broadcasting and staff adoption. This shows the integration conversation isn't limited to HubSpot alone, but treats HubSpot as one of the primary CRM targets discussed alongside recruitment-focused platforms like Bullhorn. Businesses running HubSpot alongside other systems should confirm that any integration platform they choose has demonstrated experience with the specific combination they need.
Understanding how the integration is priced and how WhatsApp's own messaging rules work day to day helps set realistic expectations before signing up.
The HubSpot integration carries a subscription fee of £50 per month, separate from WhatsApp's own per-message fees. WhatsApp messaging itself is charged at approximately 1.6p for utility messages and 3.8p for marketing messages, meaning starting 500 conversations in a month on utility messages costs around £8. Contracts run for an initial 3 months with a 30-day rolling option after that, giving businesses a low-commitment way to trial the integration before scaling up. This pricing structure means the total monthly cost depends on both the integration fee and actual message volume, so businesses should model expected conversation counts before comparing quotes.
WhatsApp's API allows free-form messaging within a 24-hour conversation window once a customer has replied, without needing a pre-approved template. Over 90% of templates sent through the platform actually use this natural chat feature rather than triggering the template-based flow. This matters for HubSpot-connected teams because it means most day-to-day conversation happens as normal back-and-forth chat, with templates reserved for re-opening conversations outside that window.
Template approval for WhatsApp messages typically completes within 10 minutes, with a maximum turnaround of up to 24 hours. This is relevant to HubSpot integration planning because any automated or templated message sent outside the 24-hour conversation window needs an approved template first. Teams planning automated re-engagement sequences through HubSpot should factor this approval window into their campaign timing, particularly for time-sensitive follow-ups.
Bulk broadcasting is a supported capability, with real examples including a broadcast sent to 109 contacts tagged as "opportunity". This kind of segmented broadcast relies on CRM tagging, such as HubSpot lists or lifecycle stages, to define who receives which message. Alongside broadcast capability, the platform discussion also covers user permissions, compliance considerations, and staff adoption challenges that come with rolling out bulk messaging across a team.
The platform is used by customers ranging from small teams up to organisations with 3,000-4,000 staff on the WhatsApp API, with hundreds of customers currently on the platform. AI bots have been deployed within the platform in as little as 4-5 weeks for some customers, showing that even AI-assisted setups can move quickly once onboarding begins. This range demonstrates the integration model scales from small sales or lettings teams through to large multi-department organisations without changing its fundamental CRM connection approach.
Businesses should confirm which version of WhatsApp API the provider uses, how pricing is structured between subscription and per-message fees, and what the onboarding process covers for both Meta Business Suite and HubSpot configuration. It's also worth asking what questions should I ask a WhatsApp Business platform provider before signing up to ensure they have documented experience with sector-specific needs, such as estate agency communication patterns, rather than a purely generic sales integration. Confirming contract terms upfront, including rolling options after the initial term, avoids longer-term commitments before the integration has proven its value.
