WhatsApp marketing is permission-based communication for customer service, product discovery, lead nurturing, or promotions. The right WhatsApp product depends on how messages are initiated, who handles replies, and whether business systems must trigger or record them.
Choose the WhatsApp Business App when a small team can manage conversations manually with profiles, catalogs, quick replies, labels, and basic response tools. Evaluate the WhatsApp Business Platform when you need approved templates, CRM-triggered messaging, programmatic routing, or larger-scale automation. These are distinct products, not interchangeable names for the same features.
For example, a neighborhood shop answering stock questions may start with the App. A retailer triggering eligible campaign messages from CRM events needs a Platform-based operating process, including consent checks, template controls, exception handling, and message records.
What WhatsApp marketing is and the first decision to make
Document the channel functions you need before choosing a product. Record expected message volume, CRM involvement, who will answer inbound conversations, whether staff must continue using the WhatsApp Business App, and which outcomes you need to measure.
Small-team conversations
Choose this path for a business profile, catalog, greeting and away messages, quick replies, labels, and staff-managed conversations. It supports basic response tools, not an unrestricted chatbot or API workflow. See the official Business App overview.
API-based messaging
Evaluate this path for business-initiated template messages, interactive messages, media, product messages, and programmatic workflows. It requires a defined consent, eligibility, and message-handling process. Review Platform capabilities.
Coexistence is a separate setup, not a third WhatsApp product. HubSpot documents a coexistence option that lets eligible businesses use the same number with the WhatsApp Business App and HubSpot. Its behavior and limitations differ from HubSpot’s standard connection, so choose it only when continued App use is an explicit requirement.
Set up the Business App for a small-team workflow
WhatsApp’s high-level setup sequence is to download the Business App, register and verify a phone number, and create a business profile. Complete the profile with accurate details such as the business description, hours, website, and contact information. The official Business App setup guide covers registration and profile creation.
Prepare the customer-service process before promoting the number:
- Verify the number and confirm who can access the device or account.
- Complete the profile with current business information and a recognizable image or logo.
- Configure greeting and away messages, quick replies, and labels for common requests and ownership.
- Create and maintain a catalog if customers need to browse products or services.
- Test an incoming inquiry, assign a staff owner, and define how unanswered or out-of-hours requests will be handled.
The Business App documents profiles, response features, catalogs, catalog links, and broadcasts. Business Broadcasts are available only to eligible users in select countries, so do not plan a campaign on the assumption that every account has the same broadcast options. Labels and quick replies organize work; they do not verify inventory or create unrestricted chatbot automation. See the official Business App feature reference.
Catalog availability, broadcast behavior, account eligibility, and other features can change. Confirm what the specific account exposes before promising a customer or a team that a feature is available.
Use the Business Platform when messaging needs an operating system
The Platform supports customer-initiated conversations and business-initiated messages using templates, along with interactive messages, media, product messages, and API-based automation. A CRM-triggered send or larger-scale routing process therefore needs more than a connected number. It needs controlled inputs, eligibility checks, error handling, an audit trail, and an owner for exceptions.
HubSpot documents a WhatsApp channel connection to its conversations inbox. The standard connection requires a WhatsApp Business account, Meta Business Manager administration, access to the business phone number, and a number that can be verified. HubSpot lists Marketing Hub Professional or Enterprise, or Service Hub Professional or Enterprise, as required subscriptions. Confirm current requirements before setup. A personal WhatsApp account is not sufficient.
HubSpot’s standard connection syncs new messages after connection and routes message handling to the HubSpot inbox rather than the WhatsApp mobile or web app. Coexistence has different behavior and may be preferable when staff must continue using the Business App. A channel connection does not prove that every contact, historical message, delivery status, or media item will synchronize.
For Platform and CRM workflow planning, HubSpot systems consulting may be relevant.
Build the send gate before writing campaigns
For a business-initiated Platform message, obtain customer opt-in and use an appropriate template. Keep these checks separate:
- Consent: confirm that the person opted in through a traceable source and that the consent covers the intended purpose.
- Category: classify the message as marketing, utility, authentication, or service according to what it does for the customer.
- Template: confirm the template name, language, variables, category, and approval state.
- Eligibility: check the recipient market, suppression status, number validity, and current regional rules.
Marketing, utility, authentication, and service categories describe different purposes. Classify by the message’s actual customer value, not by the label a campaign team prefers. Meta’s marketing category guidance and service category guidance describe these distinctions.
A user-initiated service conversation creates a 24-hour customer-service window for service replies. Use the received-message timestamp to calculate the window, not the time a workflow happens to run. Outside the window, an approved template is generally needed to reinitiate a conversation where permitted.
Platform pricing is based on delivered messages and depends on recipient market and message category. Meta’s current pricing page also describes circumstances in which service messages, user-response utility messages, or messages from certain free entry points are not charged. Do not describe all business messaging as free. Review the current pricing model before launch.
HubSpot’s template guidance states that Meta paused marketing template messages to US-based phone numbers beginning April 1, 2025, while describing separate treatment for utility, authentication, and in-window service responses. Check the live rule before any launch involving US recipients.
The following is a proposed operational contract, not a vendor-prescribed schema:
{
"whatsapp_business_account_id": "waba-example-001",
"recipient_phone_normalized": "+15550101234",
"recipient_country": "US",
"consent_record_id": "consent-example-014",
"template_name": "approved_campaign_template",
"template_version": "2026-01",
"template_category": "marketing",
"template_approval_status": "approved",
"campaign_id": "illustrative-campaign-001",
"business_event_id": "event-example-884"
}Before sending, validate the normalized number, consent evidence and scope, recipient country, suppression status, template name and category, approval state, required variables, and any applicable service-window or market rule. Reject missing or out-of-scope consent, an unapproved template, a category mismatch, invalid variables, or a recipient blocked by current rules. Send uncertainty to a named messaging-policy owner instead of repeatedly retrying it.
Design the operational chain: trigger, record, decision, action
Keep a small number of distinct workflows rather than one loosely controlled automation. The examples below use proposed implementation patterns, not vendor-published CRM modules or schemas. Use deterministic rules for binary policy decisions. AI can classify a free-text request, extract structured information, or draft a reply for review. For supervised AI agent design, keep the decision boundary explicit.
| Trigger | AI job | Validation | Action and fallback |
|---|---|---|---|
| Approved campaign event selects an opted-in contact | Flag possible copy or category mismatch for review | Check consent, country, template approval, variables, suppression, and the outbound idempotency key | Submit through the Platform path; marketing operations owns policy exceptions |
| Inbound service message arrives | Suggest intent and a draft reply | Preserve event ID and received time; match contact unambiguously; calculate the service window | Route to CRM inbox or unmatched-contact queue; an agent owns ambiguity |
| Team prepares a HubSpot channel connection | None required | Confirm plan, Meta access, number eligibility, connection type, history expectations, and test results | Administrator selects standard connection or coexistence; stop cutover if behavior differs from requirements |
For an inbound request, use the received-message timestamp, not workflow execution time, to assess the service window. Normalize the phone number and associate it with a contact only when the match is unambiguous. A hypothetical AI output might classify “I need help with my recent order” as order_support and draft a response. A service agent verifies order facts before replying. Route payment disputes, identity or account-access questions, health information, legal requests, and uncertain intent to a person.
Model records at the right grain:
- MessageEvent: one raw inbound or outbound message event, including the provider event ID, direction, timestamps, content reference, and provenance.
- Conversation: one thread or customer-service session, with contact, assignment, session boundaries, and escalation state.
- TemplateSendAttempt: one attempt to send one template to one recipient for one campaign or business event, including status, retry information, and the idempotency key.
- ConsentRecord: one consent grant, change, or withdrawal, including source, time, scope, and evidence.
Keep raw observations separate from CRM contact or deal updates and from campaign-level summaries. Store source IDs, timestamps, campaign or business-event ID, template version, consent reference, policy decision, and human reviewer where available. Limit access to personal content and follow applicable retention requirements.
A conversation is not a message. For inbound events, use a provider message ID where available and enforce uniqueness with a database constraint or transactional upsert. For outbound attempts, include the account, recipient, template version, campaign or business-event ID, message purpose, and scheduled send bucket. A date-plus-phone key alone can suppress two legitimate messages to the same customer on one day.
A read-then-insert check alone can race when workers run concurrently. Use a database-enforced unique index or transactional upsert on the provider event ID or a clearly marked provisional composite key. If an event ID is unavailable or unverified, record the composite key and its provenance rather than presenting it as a confirmed provider identifier. These are implementation recommendations, not WhatsApp or HubSpot standard fields. For contact ownership, event records, and reporting design, CRM systems consulting is a relevant service.
Connect WhatsApp and HubSpot without assuming a universal sync
Choose the connection path based on how staff need to work and what history matters. Before setup, confirm the current HubSpot subscription, Meta Business Manager administration, access to the WhatsApp Business account, and phone-number eligibility. A number already connected to another WhatsApp account or integration may need to be disconnected unless the selected setup supports coexistence.
Standard connection
HubSpot documents a standard connection that syncs new messages after connection and routes handling to the HubSpot conversations inbox. The documented behavior differs from using the WhatsApp mobile or web app. Do not assume that historical conversations, contacts, media, delivery statuses, or read statuses will all be imported or exposed. Test the specific fields and routing behavior the team needs before cutover.
Coexistence
HubSpot’s separate coexistence setup allows an eligible WhatsApp Business phone number to be used in both the Business App and HubSpot. HubSpot documents importing up to 180 days of conversation history, with media backfill limitations, and describes other differences between device-sent and HubSpot-sent messages. It also documents a maximum send rate of 20 messages per second for coexistence numbers. Treat these as setup-specific conditions and confirm them against the live guide before rollout.
- Choose standard connection or coexistence based on whether staff must continue using the Business App.
- Confirm the required HubSpot tier, Meta permissions, WhatsApp Business account access, and number eligibility.
- Test an inbound message, contact association, outbound reply, and template behavior with a controlled contact.
- Confirm expected history and media behavior, especially when using coexistence.
- Test voice notes or other message types the team relies on, rather than assuming they backfill or route identically.
- Name an owner for unmatched contacts, duplicate matches, number conflicts, and unexpected inbox behavior.
See HubSpot’s guides for the standard connection and coexistence setup. Product capabilities, country availability, categories, pricing, plan requirements, and regional restrictions can change, so recheck the official Meta and HubSpot documentation before publication and again before launch.
Measure message operations, not just campaign volume
Choose measures that match the job. For a campaign, track eligible recipients, send attempts, available delivery outcomes, replies, qualified inquiries, and completed business actions. For service, track incoming requests, response or resolution outcomes, escalations, and unresolved cases. The exact metrics and exports depend on the WhatsApp product and connected system. Do not imply that every account exposes the same fields.
Report each attempt at message-event grain, then aggregate to campaign grain using an explicit date range and denominator. Keep raw delivery or provider observations separate from CRM contact updates and reported campaign summaries. Preserve the source event or message ID, campaign or business-event ID, consent record, template version, processing timestamp, and policy decision where available. Assign an operations owner to investigate rejected sends, unmatched contacts, and missing status data rather than counting them as successful outcomes.
Use campaign examples as inspiration, not performance evidence
The HubSpot source article describes Hellmann’s WhatsCook as an interactive recipe concept based on ingredients a customer had available. It describes Beck’s as a branded chat experience and Tikkie as a historical branded-sticker idea. These accounts offer useful design prompts, but the source article and linked pages do not independently establish the reported Hellmann’s budget or reach, Beck’s awareness or chat-duration effects, or current Tikkie payment availability.
The transferable ideas are useful interaction, a clear customer action, and brand utility. Turn an example into a testable hypothesis by specifying the audience, the action the customer can take, the staff or system that fulfills it, and the outcome to measure. Treat the reported results as historical claims requiring primary-source confirmation, not as performance evidence for a new campaign.
Sticker packs also have a real implementation path, but it is an app workflow rather than a ready-made campaign. WhatsApp’s official sample repository describes Android and iOS sticker-pack applications, metadata, validation, and explicit user installation. For the documented sample implementation, static stickers are 512 by 512 pixels and no larger than 100 KB. Animated stickers have separate limits, packs must meet additional metadata and pack-size requirements, and static and animated stickers must not be mixed. Check the current platform-specific requirements before producing assets.
Make the workflow fit the product
Start with the Business App when a small team can manage conversations with a profile, catalog, quick replies, labels, and defined staff ownership. Evaluate a Platform-based design when the business needs controlled template messaging, CRM-triggered outreach, programmatic routing, or message-level records.
Before connecting either path to a CRM, test number eligibility, consent handling, contact matching, duplicate prevention, ownership, and the exact history and inbox behavior the team needs. The strongest WhatsApp marketing operation is not the one with the most automation. It is the one that can explain why each message was eligible, who handled the response, and how the resulting business event was recorded.