Vol. 01
The HubSpot + WhatsApp Playbook
Workflows that actually convert.
- Each play on a two-page spread
- The WhatsApp copy, ready to paste
- Blueprints you can build in HubSpot
flowella.ioField manual
Send the out-for-delivery update from HubSpot with tracking and a one-tap Flow for when they won’t be in, so the parcel goes today or is rebooked before anyone calls support.
Tell them before they have to ask.
Amira is waiting for a parcel. Each step shows what she sees on WhatsApp and what lands on her HubSpot record, from the out-for-delivery update to a plan that works. Your answer in the Flow decides the branch. All four properties are custom ones the play creates.
The status lands in HubSpot, and Amira is enrolled.
The status lands in HubSpot, and Amira is enrolled. The update lands on WhatsApp straight away. Answer as Amira. Your tap decides the branch. Two answers, two clean properties. It can still go today, so the delivery goes ahead. Not today, so it’s rebooked before anyone calls. Delivered first time, no call to support. Goal met. Rebooked in the chat, not on the phone. Goal met.
Yes, today: save the note and deliver
No, another day: rebook, no ticket
Today: order_note_saved, team told
Rebook: order_rebook and a new day
Today
The opener lands here
Properties
order_status delivery_choice delivery_note delivery_plan Activity
1 of 4 properties written
Step 1 of 5, the trigger: your order system sets Amira’s order to out for delivery in HubSpot, and the workflow enrols her.
Workflow triggers and actions need HubSpot Professional or Enterprise. Workflow actions guide
Scan the code with your phone to open one in WhatsApp. It’s Flowella’s own Flow, not this playbook.
Open it in WhatsApp (opens in a new tab)Out for delivery, a tracking link and a one-tap Flow for when they won’t be in, then one branch: the parcel goes today or is rebooked. You build it in a HubSpot workflow, from Flowella’s WhatsApp triggers and actions.
order_status: out_for_deliverySet by your shop or courier system. Confirmation, dispatch and delays each get their own send.
Write each status to HubSpot as it happens. A nightly sync is too slow for same-day news.
order_out_for_delivery, with the window, the tracking link and “Won’t be in?”
It’s the update people wait for. Keep it to the window and one link, with no marketing.
The choice lands as delivery_choice, with an optional delivery_note.
No answer: they’ll be in, and the parcel goes as planned.
delivery_choice a way to deliver today?A safe place or a neighbour goes today; another day waits for a rebook.
order_note_saved, with the tracking link
The delivered status starts the clock for the review prompt
order_review_request, while the goodwill is fresh
No “where is my order?” call, and a review asked for
order_rebook, with a link to pick a new day
delivery_plan: rebookAnd a task for the delivery team, so nobody waits on a call
The new day is set in the chat, not in a phone queue
If the status turns delayed instead, its own send gives the new window before anyone asks.
A week on, the review prompt inherits the goodwill. Earlier, the parcel may still be in its box.
Order updates with no promotion are utility templates, which Meta prices below marketing.
Workflow triggers and actions need HubSpot Professional or Enterprise. The answers land as contact properties on every HubSpot plan, Free included. Workflow actions guide
The out-for-delivery update, the Flow it opens and two replies carry the delivery day. All three are utility templates tied to the order, with no promotion, and a review prompt follows a week after delivery.
order_out_for_deliveryUtilityEnglish (UK)Sample data
Sends when order_status turns out_for_delivery
One message, one link, one way to change the plan. No marketing in the update people wait for.
order_delivery_optionsWhatsApp Flow1 screenSample data
Opens from the opener’s button, synced from your HubSpot form
No problem. Tell us what to do with today’s parcel, and we’ll add it to your order.
What should we do if you’re out?
No problem. Tell us what to do with today’s parcel, and we’ll add it to your order.
What should we do if you’re out?
The Flow, If you’re not in: what should we do if you’re out (leave it in a safe place, leave it with a neighbour, deliver another day) and an optional question, where, or which neighbour.
Amira’s Flow, with leave it in a safe place chosen and the optional question left blank.
A safe place, a neighbour or another day, plus a note for the driver. The choice lands on the record.
order_note_savedUtilityEnglish (UK)Sample data
Sends when delivery_choice means it can still go today
Confirms the change in seconds, so nobody rings support to check it landed.
order_rebookUtilityEnglish (UK)Sample data
Sends when delivery_choice is another day
A new day in the chat, instead of a failed drop, a card through the door and a phone queue.
order_review_requestMarketingEnglish (UK)Sample data
Sends 7 days after order_status turns delivered
Asks a week on, once the order is in use, with one tap to the same review page for everyone.
Sample templates. Meta approves each template before it can send, and the Send WhatsApp Template action maps HubSpot properties to its variables.
The play captures all five, and each lands in HubSpot as something a workflow can read, not a note someone has to interpret.
| Signal | Weak signal | Strong signal | Lands in HubSpot as |
|---|---|---|---|
| Whether they’ll be inA choice before the van arrives saves a failed drop and a card through the door. | No answer | Deliver another day | delivery_choice |
| Where it can goA safe place or a neighbour, in their words, ready for the driver. | Left blank | Behind the side gate | delivery_note |
| How fast they open itFlowella logs how long the update took to read. A quick read means they’re watching for it. | Read hours later | Read in minutes | timeToReadSecondsOn the Message read event |
| Whether they replyA typed question needs a person. Route it to your inbox, not another template. | No reply | “Can you come at 2?” | flowella_last_reply_messageUpdated on every Text Reply |
| Whether it landsDelivered starts the review clock; a delay gets its own apology first. | Delivered on time | Delayed by a day | order_statusWritten by your order system |
Customers chase an order when its status feels invisible. WhatsApp puts the status where they already look, before support gets involved.
Tracking emails get missed, courier pages confuse and a delay feels personal when nobody explains it. An update with the window and one link answers the question first.
Send the confirmation and dispatch updates in the same style, add a location header for the delivery area, and route replies that mention damage straight to support.
Keep every update utility: put an offer in an order message and Meta treats it as marketing. Don’t promise a time your courier can’t keep, and stop once it’s delivered.
The point: every clear update is one less support ticket.
The HubSpot + WhatsApp Playbook, Vol. 01, puts each play on a two-page spread: why and when it works on the left, the blueprint on the right, and the WhatsApp copy ready to paste. Order & Shipping Updates is one of them.
Free. Reply STOP at any time to stop the messages.
Vol. 01
The HubSpot + WhatsApp Playbook
flowella.ioField manual
Every play is a two-page spread. The left page says why and when; the right page is the blueprint, with numbered notes and the WhatsApp copy.
Field manualHow to read it
Trigger: the order goes out for delivery. Goal: delivered first time, or rebooked in the chat, with no “where is my order?” call.
Support, customer successOrder & Shipping Updates
Page 1 of 3The coverPage 3 of 3This play: Order & Shipping Updates
Twenty plays, each a working blueprint. These six sit closest to order updates.
This play is filed under Support Customer success Agencies
Recover abandoned carts with WhatsApp reminders, purchase-status exits, support-first rescue, and controlled incentives.
Check in privately on WhatsApp first, invite a public review while the goodwill is fresh, and give unhappy customers a manager first, with the review link still open to them.
Collect two-tap CSAT or NPS answers on WhatsApp, thank happy customers, and route every unhappy one to a person and a HubSpot ticket.
Cut no-shows with WhatsApp appointment confirmations, timed reminders, prep requests, self-serve reschedule, and attendance follow-up.
Refresh stale CRM records with WhatsApp confirmations, structured corrections, one reminder, and a clear freshness flag.
Guide new customers to first value with milestone WhatsApp prompts, setup nudges, support rescue, and HubSpot onboarding status updates.
Turn HubSpot order statuses into WhatsApp updates that answer the question first. Start free today, or book a 30-minute demo and we’ll map this play to your own orders.
Or book a 30-minute demo