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 a two-tap survey after a closed ticket or a finished project, thank the happy customers, and give every unhappy one a person and a ticket before the feeling hardens.
Two taps to answer. One person to put it right.
Isaac’s IT problem has just been fixed. Each step shows what he sees on WhatsApp and what lands on his HubSpot record, from the survey to a thank-you or a recovery call. Your answers in the Flow decide the branch. The properties are custom ones the play creates, apart from the owner.
A closed ticket or a finished project. Pick one.
A closed ticket or a finished project. Pick one. An hour later, the survey lands on WhatsApp. Answer as Isaac. Your taps decide the branch. Three answers, three clean properties. 100 points. 80 or more, so a thank-you goes back. 100 points. Under 80, so recovery starts now. Thanked, and asked for an introduction. Goal met. Ben has the ticket and the comment. Goal met.
Yes, 80 or more: thank them, ask for an intro
No, under 80: apologise, open a recovery ticket
Thanks: csat_thanks and a referral ask
Recovery: csat_sorry and a ticket
Today
The opener lands here
Properties
feedback_trigger csat_rating issue_resolved csat_comment feedback_score feedback_segment hubspot_owner_id Activity
3 of 7 properties written
Step 1 of 5, the trigger: support closes Isaac’s printer queue ticket, and the workflow enrols him.
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)A finished job, one survey on WhatsApp, a three-question Flow, then one branch: happy customers get thanks and the rest get a person. You build it in a HubSpot workflow, from Flowella’s WhatsApp triggers and actions.
Ticket closed or project delivered, and no survey in the last 90 days.
A closed ticket or a finished project, never a random date mid-journey.
Long enough to know the fix held, soon enough to remember it.
csat_ask, naming the job, with the Flow button “Rate our help”.
last_survey_date set to today, answered or not.
Set the survey date when it sends, so nobody is asked twice in 90 days.
The answers land as csat_rating, issue_resolved and csat_comment.
No answer in 7 days: the workflow ends. No second ask.
feedback_score 80 or more?Satisfaction and resolution add up to the score: up to 60 and 40 points.
Happy but not sorted is still a problem, so resolution carries 40 of the 100 points.
csat_thanks, with an introduction ask
feedback_segment set, for reports by owner and team
Score and comment attached, for the account manager (Service Hub Professional or Enterprise)
csat_sorry, with Call me instead
The ticket closes when the customer says it’s sorted
The person putting it right needs the customer’s comment, not just a score.
Workflow triggers and actions need HubSpot Professional or Enterprise. The answers land as contact properties on every HubSpot plan, Free included. Workflow actions guide
Three WhatsApp templates and the Flow they open carry the whole loop. Each one names the job it asks about, and every variable comes from the HubSpot record.
csat_askUtilityEnglish (UK)Sample data
Sends an hour after a ticket closes or a project is signed off
Names the job it asks about, which keeps the survey specific and short.
csat_surveyWhatsApp Flow1 screenSample data
Opens from the survey’s button, synced from your HubSpot form
Two taps and an optional note. Your answers go to the team that helped.
How satisfied are you with our help?
Is it sorted?
Two taps and an optional note. Your answers go to the team that helped.
How satisfied are you with our help?
Is it sorted?
The Flow, Rate our help: how satisfied are you with our help (very satisfied, satisfied, dissatisfied, very dissatisfied), is it sorted (yes, sorted; not yet) and an optional question, what could we do better.
Isaac’s Flow, with very satisfied and yes, sorted chosen, and the optional question left blank.
A rating, a yes or no on the fix, and an optional note. Each answer lands as its own property.
csat_thanksMarketingEnglish (UK)Sample data
Sends when feedback_score is 80 or more
Thanks a happy customer while it’s fresh, and asks for an introduction, not a public review.
csat_sorryUtilityEnglish (UK)Sample data
Sends when feedback_score is under 80, once the ticket has an owner
Apologises, names who has it and offers a call, before the frustration hardens.
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 number buried in a survey tool.
| Signal | Little to go on | Something to act on | Lands in HubSpot as |
|---|---|---|---|
| How satisfied they areA rating tied to one job tells you which fix, and which team, to look at. | No answer | Rated, tied to a job | csat_rating |
| Whether it’s sortedHappy but unsorted still needs a person, so resolution sits beside the rating. | Assumed sorted | Asked and answered | issue_resolved |
| What they’d changeTheir words reach the person putting it right, not just a dashboard. | Left blank | A named problem | csat_comment |
| How fast they open itFlowella logs how long the survey took to read. A quick read means the job is still fresh. | Read days later | Read in minutes | timeToReadSecondsOn the Message read event |
| Whether they finishOnly a finished Flow fires Form Completed, so a half-answer never opens a ticket. | Opened, then left | Every question done | Form CompletedThe Flowella trigger |
People will tap a score in the chat they already use for service. The value is in routing the answer, not just collecting it.
A long survey link feels like homework and arrives when the job is forgotten. Two taps in the chat, an hour after the fix, catch the feeling while it’s fresh.
Run NPS the same way with a 0 to 10 question, report scores by owner and team in HubSpot, assign a Breeze Customer Agent to recovery chats, and invite happy customers to refer a friend.
Don’t survey anyone twice in 90 days, skip contacts with an open ticket, make recovery someone’s job, and don’t send review links only to happy customers: Google’s review policy forbids it.
The point: feedback should create the next best action, automatically.
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. NPS / CSAT 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: a closed ticket or a finished project. Goal: happy customers thanked, and every unhappy one with a person and a ticket.
Support, customer successNPS / CSAT
Page 1 of 3The coverPage 3 of 3This play: NPS / CSAT
Twenty plays, each a working blueprint. These six sit closest to listening well.
This play is filed under Support Customer success Professional Services B2B SaaS Charity & Non-profit Healthcare Hospitality Education
Ask guests two quick questions on WhatsApp after a visit or stay, invite reviews, put the manager on unhappy guests first, and tag every answer in HubSpot.
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.
Turn happy customers into tracked referrals with WhatsApp invites, unique links, friend signup checks, thank-you messages, and two-sided rewards.
Guide new customers to first value with milestone WhatsApp prompts, setup nudges, support rescue, and HubSpot onboarding status updates.
Wake dormant contacts with a WhatsApp preference prompt, branch interest, snooze, and opt-out paths, and clean HubSpot automatically.
Renew more memberships: a WhatsApp reminder 30 days out, a one-screen Flow, the renewal link for members who stay, and a person for anyone unsure.
Turn every closed ticket into a two-tap WhatsApp survey that routes the answer in HubSpot. Start free today, or book a 30-minute demo and we’ll map this play to your service.
Or book a 30-minute demo