Skip to content

Week-one onboarding by WhatsApp: three templates with exit on first login

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.

Contact22 stepsUpdated for HubSpot seat pricing
OutcomeA new customer who opted in to WhatsApp gets a welcome, a setup tip and a check-in over the first week, and the series stops the moment the first login is recorded.
Workflow mapmessaging-019
Onboarding start date set and no login leads to WhatsApp opt-in and number. WhatsApp opt-in and number leads to No: Send welcome email and end; Yes: Send welcome template then delay 2 days. Send welcome template then delay 2 days leads to First login recorded. First login recorded leads to Yes: Exit on login; No: Send setup tip then delay 3 days. Send setup tip then delay 3 days leads to Send check-in template and call task if still no login. No Yes Yes No Onboarding start date set and no login WhatsApp opt-in and number Send welcome email and end Send welcome template then delay 2 days First login recorded Exit on login Send setup tip then delay 3 days Send check-in template and call task if still no login
Onboarding start date set and no login leads to WhatsApp opt-in and number. WhatsApp opt-in and number leads to No: Send welcome email and end; Yes: Send welcome template then delay 2 days. Send welcome template then delay 2 days leads to First login recorded. First login recorded leads to Yes: Exit on login; No: Send setup tip then delay 3 days. Send setup tip then delay 3 days leads to Send check-in template and call task if still no login. No Yes Yes No Onboarding start date set and no login WhatsApp opt-in and number Send welcome email and end Send welcome template then delay 2 days First login recorded Exit on login Send setup tip then delay 3 days Send check-in template and call task if still no login

When to use it, when not to

Use it

  • Use it when activation depends on a first login in the first days and your customers read WhatsApp faster than email.

Skip it

  • Do not use it without verifiable WhatsApp opt-in. A signed contract is not consent to be messaged on WhatsApp. Capture consent with messaging-004.
  • Do not build it as a deal-based or ticket-based workflow. The Send WhatsApp message action is documented for contact-based workflows only. Enroll the contact and copy any deal value you need onto a contact property first.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 10 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 22 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 4

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 5 cases, 2 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV

The properties JSON creates the fields in one call. The workflow JSON documents the build.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free SMS and WhatsApp spec

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.

149 EUR199

Full library, 565 specs
Get the full library