Capture WhatsApp opt-in and log verifiable consent before any template is sent
One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.
Professional
Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Marketing Hub Professional.
OutcomeEvery contact who agrees to WhatsApp messages carries a dated, sourced consent record and a usable WhatsApp number, and one gate property tells every other WhatsApp workflow whether it may send.
Workflow mapmessaging-004
When to use it, when not to
Use it
- Use it before you build any workflow with the Send WhatsApp message action. The action needs verifiable opt-in consent, and this fiche is where that proof is created.
- Use it when WhatsApp consent comes from a form checkbox, a landing page or an import of documented opt-ins.
Read more on when to use itShow less
Skip it
- Do not use it to send a first WhatsApp message. This workflow sends nothing. Templates go out in messaging-005, messaging-007, messaging-013 and messaging-019.
- Do not reuse SMS or email consent as WhatsApp consent. Each channel needs its own opt-in, see marketing-ops-006.
The rest of this spec
Not the workflow you needed?
More in SMS and WhatsApp
25 specs in this section
FreeAppointment reminder by SMS 24 hours before a booked meeting, opted-in contacts only
Order or contract confirmation by WhatsApp template when a deal is closed won
Ticket status update by WhatsApp template, with the status copied to a contact property for the token
Event day logistics: SMS with the join link to registrants, WhatsApp template as fallback
Read 12 complete specs before you pay.
One per category, same format as the paid ones. Email only, no card.
We email the link, then a short note when specs change. Nothing else.
Here it is. Download the pack now (.zip) The link is in your inbox too.
Read the free SMS and WhatsApp spec