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
Ask new customers for ID on WhatsApp, learn which document they’ll use in a two-question Flow, then send a secure upload link. The AI Document Reader fills in HubSpot, and only exceptions reach a person.
Two taps, a secure link, and only exceptions wait.
Omar, a new customer, applies through your form or signs up in your app. Each step shows what he sees on WhatsApp and what lands on his HubSpot record, from the request to the upload link. Your answers in the Flow decide which way the branch goes.
New accounts come from a form or your app. Pick one.
New accounts come from a form or your app. Pick one. Five minutes later, the request lands on WhatsApp. Your app enrols them at once, so the request goes now. Answer as Omar. Your taps decide the branch. Two answers and a note, and no documents in the chat. 100 points. A standard case, so the upload link goes. 100 points. Under 100, so a person reviews it. Upload on a secure page, then the AI Document Reader reads it. A named reviewer, and Omar knows what happens next.
Yes, 100: the secure upload link
No, under 100: a person reviews it
Standard: kyc_upload_link, then a read
Review: kyc_review and an owner
Today
The opener lands here
Properties
signup_source kyc_document_type kyc_pep_declared kyc_notes kyc_route_score kyc_status hubspot_owner_id Activity
2 of 7 properties written
Step 1 of 5, the trigger: Omar sends your Open an account form, and the workflow enrols him with kyc_status set to pending.
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)Request, a two-question Flow, then one branch: standard cases get a secure upload link and an automatic read, and exceptions go to a person. You build it in a HubSpot workflow, from Flowella’s WhatsApp triggers and actions.
kyc_status is pendingSet by your application form, or by your app when it writes the new customer to HubSpot.
Customers from your app get the request straight away.
kyc_request, with the Flow button “Start verification”.
The answers land as kyc_document_type, kyc_pep_declared and kyc_notes.
No answer in 2 days: one reminder, then a task for onboarding.
Knowing the ID type first tells your team which document and which checks to expect.
kyc_route_score 100?A listed ID and a no to the declaration make 100. Anything else scores less.
Most customers take the standard route. People review the cases that need judgement.
kyc_upload_link, to a HubSpot form with a file upload field
The form submission puts the file on the record
Nothing uploaded in 2 days: one reminder naming what’s missing.
Writes the name, date of birth and expiry date to the properties you map
Your checks pass: kyc_status is verified. Anything flagged goes to review.
A named reviewer for each exception
kyc_review, so they know what happens next
kyc_status is manual_review; the reviewer asks for what’s needed
ID images go to a secure upload page, never the WhatsApp thread.
Blanks are skipped unless you tick Clear HubSpot properties when empty. Map only what you check.
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 play. ID images never travel in the chat: the upload happens on a secure page, and every variable comes from the HubSpot record.
kyc_requestUtilityEnglish (UK)Sample data
Sends 5 minutes after the application, or straight away from your app
Says what’s needed and why, and starts with two taps, not a document.
kyc_checkWhatsApp Flow1 screenSample data
Opens from the request’s button, synced from your HubSpot form
Two questions so we ask for the right document. You’ll upload it on our secure page next.
Which ID will you use?
Are you a politically exposed person?
Two questions so we ask for the right document. You’ll upload it on our secure page next.
Which ID will you use?
Are you a politically exposed person?
The Flow, Verify your identity: which ID will you use (passport, UK driving licence, national identity card, none of these), are you a politically exposed person (no, yes or a relative is) and an optional question, anything we should know.
Omar’s Flow, with passport and no chosen, and the optional question left blank.
The ID they’ll use and a declaration as taps, a note optional. No documents in the chat.
kyc_upload_linkUtilityEnglish (UK)Sample data
Sends when kyc_route_score is 100
A secure upload page, one document, and a promise to confirm in the same chat.
kyc_reviewUtilityEnglish (UK)Sample data
Sends when kyc_route_score is under 100
A named reviewer and a clear next step, so nobody has to chase.
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. The answers land in custom properties the play creates, next to Flowella’s own events and actions, so a workflow can read them.
| Signal | Needs review | Will clear | Lands in HubSpot as |
|---|---|---|---|
| The ID they’ll useA listed document means the standard route and the right upload page. | None of these | Passport | kyc_document_type |
| The declarationA politically exposed person needs enhanced checks, so a person reviews it. | Yes, or a relative is | No | kyc_pep_declared |
| How fast they open itFlowella logs how long the request took to read. Minutes beat days. | Read days later | Read in minutes | timeToReadSecondsOn the Message read event |
| Whether they finishOnly a finished Flow fires Form Completed, so the upload link waits for both answers. | Opened, then left | Every question done | Form CompletedThe Flowella trigger |
| Whether the document readsWith Clear HubSpot properties when empty ticked, a field the reader can’t find shows as blank. | Blank fields | Every field read | AI Document ReaderThe Flowella workflow action |
KYC stalls when instructions sit in email and status sits in a spreadsheet. A request they read, two taps and a secure upload keep the customer moving and the status in HubSpot.
A new customer is keenest the day they sign up. A request on WhatsApp that day, with a secure link that takes two minutes, gets the document in before the account goes cold.
Ask for proof of address only when the ID needs it, send instructions in the customer’s language, hand stuck customers to a Breeze Customer Agent, and file a summary PDF with Generate Document.
Keep ID images out of the chat, cover the Flowella to HubSpot flow in your data processing agreement, nudge once per missing file, and send only exceptions to review.
The point: customers know what’s missing; your team knows who’s blocked.
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. KYC Onboarding 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 new account with KYC pending. Goal: standard cases verified through a secure upload, and only exceptions reviewed by a person.
Support, customer successKYC Onboarding
Page 1 of 3The coverPage 3 of 3This play: KYC Onboarding
Twenty plays, each a working blueprint. These six sit closest to KYC.
This play is filed under Support Customer success Verify details FinTech
Confirm sensitive changes on WhatsApp first, then your app sends a one-time code through the Flowella API, with fail-closed holds and every outcome logged in HubSpot.
Guide new customers to first value with milestone WhatsApp prompts, setup nudges, support rescue, and HubSpot onboarding status updates.
Refresh stale CRM records with WhatsApp confirmations, structured corrections, one reminder, and a clear freshness flag.
Convert SaaS trials with WhatsApp activation nudges, usage-based branching, support rescue, upgrade CTAs, and paid-plan exits.
Improve candidate experience with WhatsApp application confirmations, stage updates, interview booking, offer or regret messages, and hiring outcome tracking.
Qualify captured leads with WhatsApp questions, scoring, high-fit sales routing, and nurture for low-urgency contacts.
Turn every new account into a WhatsApp request, a two-question Flow and a secure upload. Start free today, or book a 30-minute demo and we’ll map this play to your checks.
Or book a 30-minute demo